Lanwench
Fri Sep 23 10:01:40 CDT 2005
In news:41B810D5-5E12-4894-8F99-0884AC52755F@microsoft.com,
peter <peter@discussions.microsoft.com> typed:
> We are using Exchange 2003. The reason we want to keep the same name
> is to prepare for a disaster if the original Exchange dies.
Having a different name shouldn't matter all *that* much, should it? There
are plenty of profile generation utilities if you're concerned that your
Outlook clients won't be able to find the new server....
>
> I remember somebody posted a MS internal procedure to do this (to
> reset the computer account of Exchange server, join the new Exchange
> server to the domain, modify permission for Exchange objects in AD,
> restore database and logs, etc), just can not find it...
>
> Wondering if there are any KBs now...
Sorry, I don't know.
>
> Thx.
>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:EDF35B29-D3A5-49C0-A8B9-34672C9CAE0E@microsoft.com,
>> peter <peter@discussions.microsoft.com> typed:
>>> Hi,
>>>
>>> Is there a KB article on how to do this? Or detailed procedures?
>>>
>>> Thx,
>>> Peter
>>
>> NB: When you post, put a consise summary of your question in the
>> subject line, and the full details in the body of your post. Also,
>> include your version, SP level of Exchange, and any other pertinent
>> details.
>>
>> First question: what version of Exchange?
>>
>> Second question: why do you need it to have the same name? You don't
>> need to do this just so you avoid modifying profiles - if the old
>> server is kept up and running while the new one is up, and users
>> open their Outlook profiles once, Outlook will find the new server.
>>
>> See
>>
http://www.swinc.com/resources/exchange/faq_db.asp?status=questions&faqID=1001&faqname=Exchange%202000§ionID=1024§ionName=Exchange%202000%20Move%20Server%20Method
>>
>> If you really want the same server name, you can do this twice...