microsoft.public.exchange.admin

Firstly, let me say that I was brought onsite to do analysis and this is one
of many things I've found wrong with the Exchange config.



To answer your question, I think it was put in place when the server was
replaced, and they didn't want to run around to workstations reconfiguring
exchange profiles. They didn't know Exchange is smart if you move a mailbox
(headstones,etc.). Problem is, old server no longer exists in the
organization.



Any ideas of the implications of this?

"Bharat Suneja [MVP]" wrote in message
news:esrSXPYFIHA.5328@TK2MSFTNGP05.phx.gbl...
>- What are you trying to accomplish with multiple A records mapped to same
>IP address?
>
>
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
>
>
> "Scott Klein" wrote in message
> news:Obq4D4XFIHA.4712@TK2MSFTNGP04.phx.gbl...
>> The Exchange server has multiple A records in DNS, intentionally.
>>
>> For example:
>> Exchange.domain.com 10.1.1.150
>> Exchange2.domain.com 10.1.1.150
>>
>> 1 problem is that if I try to connect to an share on the Exchange server,
>> from the Exchange server, by using the server name that is NOT the actual
>> name (in My Computer) it doesn't work.
>>
>> If I use the name that matches the name in My Computer, I can map the
>> drive.
>>
>> I'm wondering what negative implications this conifguration could have.
>>
>> Clients use either FQDN to connect to the server.
>>
>> Thanks in advance
>>
>>
>
>