Now we can prepare a new Hyper-V guest to become the SBS 2011 machine. Create a new VHD of the appropriate size, set the network to the same as the Source SBS box and set the memory to at least 6 gig. In my scenario I am migrating V2V, with SBS that requires at least 12 gig of ram to be confident of success.
If you were going V2P you should be able to get away with 6-8 gig on the Hyper-V machine. Once we have our V or P source machine ready to roll we can start following the MS White Paper and see what blows up first.
The first thing I found on my SBS box was that I had apparently been doing a poor job patching it. I tried to run the Migration Prep tool and found that I needed to install several things before I could install it. Here is a great link with screen shots of what I saw. I downloaded and installed the appropriate patches and several reboots later got to the point where I was informed Exchange 2007 SP3 was not installed. I downloaded it and extracted it to my desktop, not the best move, it did not create its own folder. I cut and pasted what I thought was all of it into its own folder and tried to run it. Seems you need Windows Installer 4.5 to install exchange 2007 SP3. Another download and reboot later I ran the service pack again, this time it started. The first set of checks it went through fine,
the second, it stopped on the updating Schema task. It gave me a link to the error file, ldife.err, which read
Entry DN: CN=ms-Exch-ELC-Expiry-Action,CN=Schema,CN=Configuration,DC=blank,DC=com
Add error on entry starting on line 1: Busy
The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with atleast one replication partner.
The extended server error is:000021A2: SvcErr: DSID-030A0AF2, problem 5001 (BUSY), data 0
An error has occurred in the program
I researched that error and found that I probably had a stray DC or 2 from the past that was still In AD. Here is a great VB script that I used to clean the defunct DCs from AD just copy into a text file and rename metacleaner.vbs.
So I ran it again and it made it past the Schema upgrade and continued on through numerous other tasks at which point it blew up saying it could not find relnotes.htm (which I had apparently left on the desktop). I had no choice at this point other than click finish. This left me with Exchange hosed, all exchange services disabled and unable to rerun the SP3 setup. At this point I am very happy that it is not on a live production network that I am working on and that I can restore the VHD with a fresh copy in an hour or two.
Attempt Number 2
This time I get all the prereqs taken care of and successfully Install SP3. I move on to create the answer file on a virtual floppy disk. When chosing migration mode on the SBS setup the answer file must be on removable media. The next step is to boot the SBS 2011 destination machine of the DVD and make sure the answer file virtual floppy is attached. Then we wait.............. Here are screenshots of a migration in progress http://bnwinc.blogspot.com/p/sbs-migration-screenshots.html . Still not finished.
