{"id":970,"date":"2013-01-15T11:23:25","date_gmt":"2013-01-15T11:23:25","guid":{"rendered":"http:\/\/pariswells.com\/blog\/?p=970"},"modified":"2013-01-15T11:23:25","modified_gmt":"2013-01-15T11:23:25","slug":"domain-and-dns-not-working-after-vmware-conversion-booting-a-domain-controller-dc-standalone","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/fixes\/domain-and-dns-not-working-after-vmware-conversion-booting-a-domain-controller-dc-standalone","title":{"rendered":"Domain and DNS not working after VMware conversion – Booting a domain controller (DC) standalone"},"content":{"rendered":"\r\n


\"IC101558[1]\"I would like to thank Dan Furse from Response IT<\/a>\u00a0for this little trick bit!<\/p>\r\n

When virtulising a domain controller from Physical to Virtual, it is recommended to\u00a0segregate\u00a0it from any other domain controllers on the network in-case replication occurs during the convert. Usually servers will be offsite so you can disable the site to site VPN’s during the conversion, onsite you will need to swap the host to a different unroutable subnet \u00a0and assign the virtual host an ip on that network for the management port.<\/p>\r\n

After migration you might find that the server’s DNS and DC functionality has stopped working.<\/p>\r\n

If you have a DC that is:<\/p>\r\n

a)\u00a0\u00a0\u00a0\u00a0\u00a0 A FSMO role holder<\/p>\r\n

b)\u00a0\u00a0\u00a0\u00a0\u00a0 NOT the only DC in a domain<\/p>\r\n

c)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Booted standalone (ie it can\u2019t contact any other DCs in the domain)<\/p>\r\n

If the FSMO role holder can\u2019t talk to at least one of its inbound replication partners after a reboot, it won\u2019t advertise itself as either a DC or a DNS server.\u00a0This is a precaution in case the\u00a0FSMO roles may have been changed on other DCs while this one was down, so it has to do an initial sync to check that it is still the FSMO holder before it allows DNS\/DC connections<\/p>\r\n

You will need to add the following Registry Key and Reboot the machine, then it will skip initial replication and boot standalone.<\/p>\r\n

[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\NTDS\\Parameters]<\/span><\/span><\/strong><\/p>\r\n

“Repl Perform Initial Synchronizations”=dword:00000000<\/span><\/span><\/strong><\/p>\r\n","protected":false},"excerpt":{"rendered":"

I would like to thank Dan Furse from Response IT\u00a0for this little trick bit! When virtulising a domain controller from Physical to Virtual, it is recommended to\u00a0segregate\u00a0it […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[542,541,544,543],"class_list":["post-970","post","type-post","status-publish","format-standard","hentry","category-fixes","tag-booting-a-dc-standalone","tag-booting-a-domain-controller-standalone","tag-dns-not-working-on-domain-controller-after-convert","tag-domain-not-working-after-virtual-convert"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t