Well, that is sensationalism at it’s best! I am going to be “OOF” next week (Out Of Office) so this blog will sit idle for about 10 days (yeah, like it hasn’t done that before).
I do have some good stuff coming in January. I am going to migrate my SBS install at home and plan to document/blog the entire process. As the title implies, I will be using the Virtual Server/DCPromo method. It will likely be a series of blogs over a week or so, like Migration Part 1, Migration Part 2, etc. I have been documenting my process/concerns/gotchas over the last week or so. I have never had to think this entirely through and there are new things every day that pop up, like:
- I am hosting email for a couple of people, gotta let them know it will be down for about 2-3 hours “one day in January”
- Shares…forgot to consider custom shares on the server
- IMF/RBL/Connection Filtering settings/SMTP Connector settings…will all that stuff need to be recreated or will DS2MB push it from Active Directory to the metabase when I install Exchange?
- To install ISA2004 or not to install ISA2004?
- WSUS?? Mess with it or simply re-install it on the new install of SBS
- I need to re-org my Recipient Policies so that the “other” domains I am hosting do not get my default Recipient Policy settings…do this before the migration of after?
- SharePoint data…I have no data but I think I am going to populate it with bogus data and then follow the “How to recover SharePoint data” article just for kicks.
- Keep the same servername or go with a new one?
- I am hosting my own DNS…how to keep it intact?
- I need to get the SBS2003 media with SP1 slipstreamed so I don’t have to mess with the Companyweb/SharePoint install issue!
- Certificates in ISA2004. I have several RPC over HTTP users and several Mobile Device users…if I create a new cert with the CEICW then I will have to go “touch” each of these remote users to get the new cert installed.
I already have the answers to most of these and the others I can figure out. Like a good admin, I am going to test this migration scenario in a test lab prior to doing it on my production server.
I “had” Virtual Server installed on my SBS box (BAD!!!! DON’T DO THIS) with a replica Windows 2000 domain controller.
Here is what I have done so far in anticipation of the migration:
- Installed Virtual Server on my Windows XP machine that is part of my SBS domain.
- Shut down the replica Domain Controller
- Set the Virtual Server service on the SBS box to disabled
- Copied the VHD files to my Windows XP machine
- Booted up the replica Domain Controller in Virtual Server on the Windows XP box
- Installed DNS on my replica domain controller
- Uninstalled and reinstalled the Virtual Server “add-on’s” on the replica domain controller
- Upgraded the replica domain controller to Windows 2003 and then got it fully patched (this is a “best practice” step, if you are planning to transfer FSMO roles between DC’s, you want both the source and target at the same operating system/service pack level)
- Tested replication, works perfectly
- Made all of my DNS zones “Active Directory Integrated” so they would replicate to the other DC.
- Got a copy of SBS2003 with SP1 “slipstreamed”
So, when I get back from “OOF”, I will begin my testing phase in the lab environment (insert –> at the office). Once that is complete, I will start the actual migration.