Directory Services Restore to Virtual from Physical

I've restored Windows Server 2003 Active Directory Directory Services from a physical to a virtual server lately probably more times than is reasonable, four successful, one unsuccessful (see note about cavalier deletion of network registry keys below). I've been playing with Domain Rename operations in Windows Server 2008 (R2 in this case) and the hiccups. Unfortunately, it doesn't sound like my company will be changing our .local domain to .com any time soon as Microsoft does not support domain name changes in Microsoft Exchange 2007 or 2010 (http://technet.microsoft.com/en-us/library/cc816848%28WS.10%29.aspx). I found that three of our more important server applications can handle it, it seems. Earlier, I elucidated steps to backup physical/restore virtual Active Directory involving 3 virtual machines and a bunch of tools. I think now I'm doing it more streamlined:

1) Backup the system state of the Domain Controller (or Active Directory Server or Directory Services server) using NTBackup (in Advanced Mode to select only the System State) on Windows Server 2003 (we're moving to 2008 soon though).
2) Create the Windows Server 2003 virtual server (up to date, with the virtual machine additions) and copy over the backed up system state.
3) Move the virtual server off the production network to prevent interfering with the production environment.

4) Give the network adapter of the virtual server a static address. I matched the address of the physical server and also added the Domain Controller (Active Directory) role to match the configuration I was restoring. As I was restoring the system state, this step might be unnecessary.
5) Restart in Directory Services Restore Mode by pressing F8 after the BIOS screen before the Windows screen, selecting the option and pressing enter.
6) Log in to Windows, run NTBackup in Wizard Mode, select the backup file, and restore the system state. After completing the restoration, clicking Close prompts a restart. Restart.
7) Pressing F8 after the BIOS but before the Windows splash screen, selecting Safe Mode, and pressing enter allowed Windows to detect the new hardware (trying to boot into Windows in normal mode would hang in my case), but because I was restoring an OEM copy, I had to repair Windows.

8) After restoring the system state, I was left with (not strictly necessary) services that no longer started that I could delete. I used sc delete to delete them. I also changed the mfevtp and mfehidk services to manual start. Not necessary if you don't mind seeing "One or more services failed to start..." on startup.
9) Give the presumably new network adapter a static IP address. Again, I matched the restored configuration.
10) Open DNS from Start -> Administrative Tools. Expand to the forward lookup zone(s), right-click the zone and click Properties. Click the Name Servers tab, select, and remove the Name Servers not being restored. Do the same for the reverse lookup zone(s), if applicable.
11) Open Active Directory Sites and Services from Start -> Administrative Tools. Make sure for the server(s) that remains, that GC is checked by right-clicking its NTDS Settings and clicking Properties. Delete the servers that won't be restored from under its NTDS Settings. For each server not restored under Sites - - Servers, expand NTDS Settings and remove the other servers. Delete NTDS Settings, choose "This domain controller is permanently offline and can no longer be demoted using Active Directory Installation Wizard (DCPROMO)", and click Delete. Delete the Server as well.
12) Open Active Directory Domains and Trusts from Start -> Administrative Tools. Right-click Active Directory Domains and Trusts and click operations Master. A restored server should be Domain Naming Operations master. If not, change the role by seizing it.
13) Open Active Directory Users and Computers from Start -> Administrative Tools. Right-click Active Directory Users and Computers, click All Tasks - Operations Masters...
Make sure a restored server is Operations master for RID, PDC, and Infrastructure roles. If not, change the roles by seizing them.
14) If not installed, install the Windows Server Support Tools from the installation media ( \SUPPORT\TOOLS\SUPTOOLS.MSI). Click Start->Run, type regsvr32 schmmgmt.dll and click OK, OK. Click Start -> Run MMC and click OK. Click Console Root and click Add/Remove Snap-In..., click Add, select Active Directory Schema, click Add, Close, and OK. Right-click Active Directory Schema and click Operations Master
Make sure a restored server is Operations master.
15) Open Active Directory Users and Computers from Start -> Administrative Tools. Expand the Domain and click Domain Controllers. Press delete for the domain controllers not being restored, select "This domain controller is permanently offline and can no longer be demoted using Active Directory Installation Wizard (DCPROMO)" and click Delete and Yes.
16) Open DNS from Start -> Administrative Tools. Delete (Same as parent folder) entries for other DCs in domain.local forward lookup zones for domain controllers not being restored. Double-click DomainDnsZones and delete (Same as parent folder) entries for other DCs
Expand DomainDnsZones - _sites - Default-First-Site-Name - _tcp and delete entries for domain controllers not being restored. Expand DomainDnsZones - _tcp and delete entries for domain controllers not being restored. Double-click ForestDnsZones and delete (Same as parent folder) entries for domain controllers not being restored. Expand ForestDnsZones - _sites - Default-First-Site-Name - _tcp and delete entries for domain controllers not being restored. Expand ForestDnsZones - _tcp and delete entries for domain controllers not being restored. Expand _msdcs - gc and delete entries for domain controllers not being restored.
17) Make sure SYSVOL and NETLOGON are being shared (browse \\HOSTNAME or \\localhost). The most recent time I did this, I saw a folder called NtFrs_Preexisting___See_EventLog under c:\Windows\Sysvol\Sysvol\Domain.local\, so I made a copy, moved the scripts and policies out of the folder and under the domain.local folder and deleted the NtFrs_... folder. Then I opened regedit (Start -> Run -> regedit OK), changed BurFlags to d4 under HKLM\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Processes and restarted the NtFrs service to get Sysvol (c:\Windows\Sysvol\Sysvol) and Netlogon (c:\Windows\Sysvol\Sysvol\Domain.local\scripts) shared.
18) At this point, I have a domain controller that can be joined to. Unfortunately, in my cases, this domain controller now has Registry entries, Add\Remove Program entries, and files that may be suspect, so at this point, I preferred to join to it a clean virtual server, promote that server to a domain controller with DNS, and transfer operations master roles to it then demote and disjoin the "dirty" server from that domain.

Backup Active Directory from hardware, restore to Virtual sandbox

Let's say you experienced a disaster scenario. You had domain controllers hosted on Dell server hardware that are no longer accessible. You have a backup but only of one domain controller's system state from Windows Server 2003 R2's NTBackup. The Dell ran an OEM-licensed version of Windows Server 2003 R2 Standard Edition. You need to restore Active Directory to a virtual machine to a volume licensed version of Windows Server 2003 Standard (not R2). This is the closest to an imaginable scenario I could come up with for what I did.

I want to test out server software on a sandbox domain resembling our production environment. I want to learn VMWare (we're looking to virtualize, at least partially, for the sake of server consolidation, disaster planning, high availability, and colocation). Beyond a lab learning environment, I'd never had to recover Active Directory. All that being said, there are better ways to do what I'd done, and I knowingly went against Microsoft recommendations (more accurately, I did things Microsoft recommends against doing) in at least a couple of places. For example, I could have much more easily used VMWare Converter to virtualize servers, but I didn't want to install VMWare Converter on a production domain controller (DC). Microsoft recommends against seizing roles in favor of transferring them and recommends recovering all your DCs (then transferring roles and demoting servers). Microsoft recommends against locating the global catalog on the infrastructure master server (I am only in a single domain forest though).

Here's a play by play:
I backed up the system state of our first domain controller (DC) holding most operations master roles using NTBackup, which is running OEM installed Windows Server 2003 R2 Standard Edition on reliable, powerful Dell server hardware.
I created an up to date (Windows Updates) virtual Windows Server 2003 Standard server with VMWare Tools and set it up to mirror that production DC (set it up as the typical first server, with Active Directory Domain Services, DNS, and DHCP adding WINS). This server was not connected to the production network (only an internal virtual network).
I copied over the backup, rebooted into Directory Services Restore Mode (DS RM), and restored the system state.
Side note: Doing nothing else, if I rebooted, Windows Server would not start reliably (I think it started once... maybe). The hardware was too different. The HAL and kernel were for a multiprocessor system, the virtual server was a single processor. I could get it to boot by replacing hal.dll, ntoskrnl.exe, ntkrnlpa.exe, and kernel32.dll, but then I couldn't log in due to a licensing/activation issue. On Windows Server 2008 or 2008 R2, I may have been able to work around this but I couldn't figure it out on Windows Server 2003 (seen mention registry locations, wpa.dbl, licensing libraries - dlls, and executables - I'm sure a Microsoft guy would cringe at my attempt) .
I rebooted to the Windows Server 2003 installation media, pressed enter to install, accepted the license, and r to repair.
Side Note: Now some of the virtual machine was showing Windows Server 2003 R2. I could log in but could not join the domain ("The domain name [DOMAIN] might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS. ..." or "The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain domain.fqdn: The error was: "This operation returned because the timeout period expired."...").
I logged in and did some cleanup. Some installed services didn't start as the programs weren't there. Some programs in Add/Remove Programs weren't there. For this, I used the Windows Installer Cleanup Utility, the sc delete command, CCleaner, and some altering of the registry. For Microsoft.NET, I had to do some ugly ripping from the registry (Microsoft cringe #2). I updated the server. I demoted the other domain controllers forcibly using Active Directory Sites and Services (delete the replication partners in NTDS Settings, delete NTDS Settings and delete the Server) (Microsoft cringe #3).
I removed the other DCs from Active Directory Sites and Services and DNS. Where possible, I tried to use the GUI but had to delete some DNS entries manually. When satisfied, I backed up the system state, saved it out. I shut down this first server. I created another a second "typical first server" Active Directory, DNS, and DHCP adding WINS up to date with Windows Updates and with VMWare tools. I copied the backup down, rebooted into DS RM, restored the system state and rebooted.
Along side of this more civilized and cleaner DC, I brought up a Windows Server 2003 server without roles but with updates and VMWare Tools. I installed the Active Directory role on this server as a second server on the domain to the cleaner first server on the domain. I added the DNS role and WINS. I made WINS a replication partner on both servers, replicated the data, deleted the replication servers and removed WINS from the other server. I added the DHCP role (initially unactivated), copied over the settings, deactivated the original DHCP server, activated the new DHCP server, and removed the DHCP server role from the original DHCP server. I removed the original DNS server from responding to requests, made the new DNS server the primary on zones, removed it from the zones, and removed the role from the first server. I transferred over the roles (PDC emulator, RID master, Infrastructure master, schema master, and domain naming master) using the interface. Finally, I removed the Active Directory role (demoting the server) and got rid of every server except the new AD, DNS, DHCP, and WINS server.

To summarize, the steps were as follows:
1) Backup the system state using NTBackup from the DC holding most master roles.
2) Create the virtual machine server (with updates and VM tools) in isolated environment. Use dcpromo or Add or remove server roles to add the domain controller role as a typical first server, configuring to mirror the environment to be restored. Restart at the end of the installation wizard.
3) Copy over the system state backup. Restart and start in Directory Services Recovery Mode. Restore the system state using NTBackup.
4) Insert the Windows Server installation media. Restart and boot to the installation media. Repair the installation (past the recovery console, a repair installation).
5) Clean up the wreckage. Forcibly demote the servers that will not be restored. Use Windows Installer Cleanup Utility, CCleaner's Add/Remove Programs entry deleter, CCleaner's registry cleaner, sc delete command, and regedit (to remove some services, drivers, and programs manually)
6) Backup the virtual domain controller's system state using NTBackup. Copy the backup file out and shut down this server.
7) Create a second virtual machine server (with updates and VM tools) in isolated environment. Use dcpromo or Add or remove server roles to add the domain controller role as a typical first server, configuring to mirror the environment to be restored. Restart at the end of the installation wizard.
8) Copy over the system state backup. Restart and start in Directory Services Recovery Mode. Restore the system state using NTBackup.
9) Create a third virtual machine server (with updates and VM tools) in isolated environment. Use dcpromo or Add or remove server roles to add the domain controller role. Add this domain controller to the second server's existing domain. Restart when complete.
10) Add the DNS and WINS rules. Add but do not configure the DHCP role.
11) In WINS on the second server, add the third server as a replication partner. On the third server, add the second server as a replication partner. Initiate replication from either or both servers.
12) Duplicate the DHCP settings from the second server (changing, where necessary, to reflect the third server's planned role). Unactivate DHCP from the second server and activate DHCP on the third server. Remove the DHCP role from the second server. If WINS has finished replication, remove the WINS role from the second server.
13) Configure the third server's DNS with the intention of it being the DNS server (make the third server the primary server in the zones). Remove the second server from the third server's DNS. Remove the DNS role from the second server.
14) Transfer roles. RID, PDC, and Infrastructure can be transferred from Active Directory Users and Computers from the second server by connecting to the third server domain controller. Transfer Domain Naming Master can be done in Active Directory Sites and Trusts from the second server connecting to the third. Schema Master can be transferred from Active Directory Schema, but you may need to register it (regsvr32 schmmgmt.dll) and open it from mmc (Microsoft Management Console). This all can be done from the command line using ntdsutil.
15) Remove the Domain Controller role from the second server (using Add or Remove Roles or dcpromo), demoting it.
16) Now you can get rid of the first and second servers.