So, this was my first time doing a migration from an absolutely awful sbs 2003 machine to a brand new sbs 2008. We support a company of >15 users. I used MS's instructions on the whole thing. I ran all the wizards pre migration prepped the source server, created answer file etc. There were no errors found before the transfer and we have backups and things were good to go.
Long story short. Several spots of the migration hung for 2 hours or so until we finally restarted the host (this is all VM by the way). I don't believe the installation ever completed because when we FINALLY got logged into the server, the networking was all messed up, almost every program lagged or got hung up and it's already producing an incredible amount of errors in the logs.
This device is already deemed a DC and AD has already been transferred over. I turned that VM off and tried to do another fresh installation on a new VM but it said it couldn't make the machine a DC.
My question: is the only way to redo a migration to restore the source server before everything? Unfortunately we didn't get a snapshot before hand =S We did get a backup the night before, but the longer we wait to do a full restore (if we have to) the more data the users will lose again because we cant do another backup of all of the changed configurations on the source server. Can I run something like "dcpromo" and remove the 2008 DC from the network?
In a time-sensitive deep hole right now. Need any way out. Thanks!