at a customer I have single SBS 2011, utilizing DC, Exchange and File share as the only server and only DC in domain. Customer wants me to convert this SBS 2011 to virtual machine on ESXi 5.5 u3 on the same physical server which it currently runs on.
How will SBS as a Domain Controller act when it comes up after being shut down few hours due to all conversion tasks? Wouldn't it be lost after awakening, because it does not have and other DC as a reference? I guess I would need to do Authoritative Restore on SBS box when it powers up in virtual environment....or not?
So, taking my concerns into account, I made a hell of a PLAN:
1. ) Setup a temporary ESXi 5.1 with 2 VMs:
- one VM would be Regular Server 2008R2, which I would DCPROMO to SBS domain to act as a secondary DC
- the other VM would be the converted SBS
2.) Then I'd use VMWare Converter, install it into SBS 2011 physical box, shut down some services (like Exchange, Backup etc...temporarily) and run conversion to that above mentioned 2nd VM on temporary ESXi
3.) Then I'd do fresh install ESXi on the phisycal server, overwriting SBS server
4.) Finally, copy over converted SBS 2011 from temporary ESXi to this fresh ESXi
5.) When virtualized SBS comes up, it would have a "reference" DC up and running, so it should just naturally sync all domain services with this temporary DC and no restore would be needed.
Is this a good scenario?
...or should I go some other path? For example by employing SBS 2011 native BACKUP and thereafter RESTORE into virtual hardware, without this temporary DC?