Before i attempted the migration i performed a ton of research, probably in the region of 20+ hours. I found information at the http://www.smallbizserver.net/ forum amongst other places. Although there are lots of recommendations for Jeff Middleton's Swing Kit (which is no doubt a good investment), i felt capable enough to perform the migration unaided once i believed i'd got the jist of the overall process.
Worth a read if you're unsure of the constraints regarding SBS and additional DCs in a domain (http://blogs.technet.com/sbs/archive/2007/10/04/debunking-the-myth-about-additional-domain-controllers-replica-dcs-in-an-sbs-domain.aspx)
The below points are purely a brain dump of the issues that i encountered and resolved throughout the migration. If you're feeling brave enough to try a Swing migration then they may assist. Use at own risk or consider Jeff's Swing Kit.
- On current server perform a full backup and Exmerge mailboxes
- Backup data to be transferred over and note Shares currently on the server along with their local paths (net share >shares.txt)
- Domain Prep and Forest Prep Current Domain to 2003 Schema
- Build and join a VMware SBS Install to current domain
- On VMWare server install DNS
- DCPROMO VMWare server
- Tick Global Catalog box and wait for event 1119 (Confirmation of Global Catalog)
- Ensure AD and DNS has replicated, test by creating a user and check that details are replicated between servers.
- Disconnect VMware server from current server
- On VMWare server, Seize FSMO Server Roles - http://www.petri.co.il/seizing_fsmo_roles.htm
- Cleanse AD of old DC (AD and DNS) - http://support.microsoft.com/kb/216498. (To remove the DC from DNS i just scoured the zones for all references for the old server and deleted them)
- Build New physical server
- Add New server to Domain running on VMWare
- Install DNS on new physical server
- DCPROMO New server
- DC PROMO VMWare server
- Tick Global Catalog box and wait for event 1119 (Confirmation of Global Catalog)
- Ensure AD and DNS has replicated, test by creating a user and check that details are replicated between servers.
- Disconnect new server from VMWare server
- On new physical DC Seize FSMO Roles (See previous links)
- On new DC, cleanse AD and DNS of VMWare DC
- Fix Authoritative Time Server events due to the change in PDC role - http://support.microsoft.com/kb/816042
- Install the rest of SBS using the SBS Setup (Exclude Exchange)
- Forest Prep and Domain prep in preparation for the updated Exchange install (2000 - 2003)
- Perform Exchange Disaster recovery install (setup.exe /disasterrecovery) Necessary due to entries for the previous server still being present in the Exchange Org and two servers with the same name can't co-exist regardless of whether one of them being offline.
- Install Exchange Service Pack(s).
- Install Exchange System Manager as this isn't installed as part of the DR Install. (I found this helpful)
- Test Exchange services but a permission change is required for the Exchange computer account to be able to modify the Exchange portion of the schema. (http://support.microsoft.com/default.aspx?scid=kb;en-us;325674)
- Forklift Exchange Database to new server or Recreate mailboxes and exmerge in from previously created PSTs - More clues can be found here for the forklifting exchange databases.
- The IUSR_%SERVERNAME% user account password may need changing to ensure that IIS sites relying on Anonymous access such as OWA work correctly due to the mismatch in passwords between the user account and the IIS metabase (Find out how to sync them here)
- Copy over data and recreate shares with correct permissions
- Some notes on a Fax service install are here regarding some permission issues when moving from 2000 - 2003 (http://support.microsoft.com/kb/842207)
I'll update and correct this once I've had a good think. This is designed purely as a list of pointers and not a full migration guide.
No comments:
Post a Comment