Based on what you write, it sounds like you are trying to move your SBS 2003 installation to a new hardware platform....
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
There are many ways to approach this task, as well as many reasons for doing it, and some of them could take many pages of writing to explain.
I am a big fan of the "swing migration" technique, which utilizes tools and procedures provided by Microsoft, but recently consolidated, documented and clarified by Jeff Middleton (SBS MVP). I prefer this for its relative simplicity and the fact that most of the work is done offline and will not cause any downtime, except for the few hours of actual server transition.
In addition, you will not need to modify workstations at all. As far as they are concerned, the SBS has the same machine name and Active Directory has not changed. They will function as always.
In a nutshell:
- Build a temporary server (call it TempDC, for example) and promote it to a domain controller on the existing SBS domain using DCPROMO.
- After replication has occurred, take TempDC offline and seize all the FSMO roles using the NTDSUTIL application. With a bit of additional cleanup, TempDC will be THE operations master for the domain and will have no record of any other domain controllers on the network.
- Build your new server (the one that you want to ultimately contain SBS and Exchange Server), give it the same computer name as the original SBS, join it to the domain hosted by TempDC and then promote it to a domain controller.
- Once again, go through steps similar to #2. Take the new server offline, seize all the FSMO roles and do your additional cleanup.
- Upgrade the new server to SBS 2003. When complete, you will have an exact replica of the original SBS in terms of Active Directory.
- Copy the Exchange databases from the original server to the new server, and then mount them using Exchange System Manager. Now you have not only a replica of the original domain controller in terms of AD, but also with respect to Exchange Server.
MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A:
I have a few questions regarding this response.
- Step 2 says" take TempDC offline." Should it say "take original server offline"?
- Step 3 says "build your new server," but it doesn't indicate which operating system -- [Windows] 2003 Standard or Windows SBS?
- Step 5 says to upgrade the new server to Windows SBS 2003, but upgrade from what?
Regarding your questions...
- Step 2: This is correct the way that it is.
- Step 3: Build the new server with Windows Server 2003 using the media for Windows SBS. Install the OS to the point of the first secure logon (meaning the user is prompted by CTL-ALT-DEL).
- Step 5: Upgrade the server from the OS installed in Step 3 to Windows SBS 2003 (assuming that is your final goal).
Per my original response, there is a hyperlink to Jeff Middleton's Web site that gives all the gory details of this technique. You should go to that site to get the information that you need, because my description is only a general outline.
Brad Dinerman, Exchange Server and SBS Expert
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:
Related Q&A from Bradley Dinerman
Find out how you can avoid DNS issues related to a Exchange 2003 server only collecting email from specific POP3 domains.continue reading
Are you having trouble with duplicate appointments in your Microsoft Outlook 2003 calendar? Learn what may cause this to happen.continue reading
Learn the best way to configure the default recipient policy in an Exchange 2003 test environment.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.