> To make a long story short. Our current exchange server was installed 3
> years ago. Needless to say, this box is sloooow, and is running out of
> space in a hurry.
> The new server is here and ready to go. Here's the problem:
> the old box is not only the Exchange server, but is also the PDC, DHCP,
> WINS server. To eliminate client problems after the swap, I'd like to
> give all these functions to the new box also (to get things running).
> worry about breaking these functions apart later.
> I've read the Microsoft server move method for boxes with the same name.
> Are there any readers out there who have done something similar, and have
> suggestions about where major complications may occur? I know I'll have
> promote another BDC to PDC temporarily, and copy the stores to a third box
> before bringing the server offline. I would appreciate any tips....
Why bother with the server names? Unless you have something else, like
SQL Server running, then bring up another server in the same site and use
the Move Mailbox command to transfer the mailboxes. The clients, if they're
using the Exchange Server service in Outlook to connect, will have their
profiles updated automatically and transparently. Read the Ed Crowley Move
Server Method at http://www.swinc.com/resource/exch_faq_appxa.htm for
step-by-step instructions on moving everybody to a new server.
The only potential problem is with the DHCP leases. What I would do is
gradually shorten the leases to, say, 8 hours, and then shut down the old
DHCP server on Friday evening and bring up the new server (ditto for WINS).
As users come in on Monday morning, their leases will have expired. They
will then wind up getting new leases from the new server.