Re Build Exchange box

[bobej]

Our Exchange 2003 box is getting on a bit so I intend to virtualise it on vmware. I need to keep the same node name and IP. what is the best way to approach this.
Or if I build a server with a different node name is there an easy way of changing all of the Outlook clients server settings?
Many thanks

 

[58sniper]

Why is the same name and IP needed?

Outlook will automatically update the profile info as long as the old server is left online long enough for all clients to connect once.

Follow KB 822931 to the letter.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[bobej]

I do not quite understand how the clients will update themselves can you point me at a paper or tell me how that happens

Thanks

 

[SteveRoadWarrior]

58sniper is wise (of course). Don't make a "replacement" Exchange server unless you really have to. If you can run both servers simultaneously, then migration is a harder but safer way to go. It will result in less down time for the users.

As far as moving user's mailboxes goes:

Open the Exchange enabled Active Directory Users and Computers MMC. It's the Orange one, not the tan/brown one.

Right click on a user, you'll see a submenu that says "Exchange Tasks". One of the tasks is to MOVE a user's mailbox to another Exchange server (or storage group).

Do this to a test or template user first and get the feel for it.

The end user's copy of Outlook (running on their computer) will realize their mailbox has moved to another Exchange server.

At this point, the user will be prompted to close Outlook and re-open it again. Their mail will not function until they close and re-open Outlook. After one (or two) times closing and re-opening Outlook, the user will see that they're connected to the Exchange server and mail is now working.

 

[bobej]

Steve Many thanks