I recently performed a P2V migration, moving our physical Windows Server 2012 domain controller into a VM on Proxmox. The physical server is still operational, but when I try to start the new VM, I receive a 'No Domain Controller Available' error at login. I suspect the issue might be with the network card driver since the VM is currently using the `E1000` model NIC. The driver may not be installed correctly, and since this is a domain controller, I can't log in with a local account. I'm aware of Directory Services Restore Mode (DSRM), but I don't have the DSRM password. The physical server still boots fine, so should I reset the DSRM password there, or do I have other options within Proxmox to resolve this?
5 Answers
You should also consider loading the VirtIO drivers; they might be necessary for proper networking post-migration. If you can get those installed, it might resolve your issues!
If your disk is not encrypted, consider swapping the CMD accessibility for command prompt. This gives you a backdoor to access and potentially fix the NIC issues you're having. There's info about this on Reddit. Just be cautious!
You might want to check if the NIC is even configured correctly. Your DHCP server should point to a DNS server hosting another domain controller. If you have an outdated version of Windows, switching to a different NIC model like RTL8139 might help the situation too. Remember that virtual NICs can lose IP information, especially if you’re lacking a DHCP server in your test setup.
Also, if you can access the built-in admin account, that may help you. Just a reminder, those accounts are disabled once AD is set up. You'll need to remove AD to enable it again, but it's worth checking if that's an option for you.
I can't access the built-in admin since the AD role is active. But thanks for the tip!
It's generally advised not to virtualize a DC like this. A better approach would be to set up a new DC in your hypervisor, transfer the roles from the old 2012 DC, and then decommission the physical box. It's a cleaner solution and less risky. You can do it in under an hour too!
Agreed, that's the safest route. Just spin up a fresh server and promote it to DC!
Good point! I lost all IP info during my previous migration, which caused more headaches.