Hi Foggy,- do you mean you're seeing the "domain couldn't be contacted" message while trying to log in to the restored DC?
I restore the VM, the server starts until the login page, then does its " VEEAM AD restoration stuff ", and restarts. Then, I login. If I try to open the Users & Computers in example, I get " Naming information cannot be located because:
The specified domain either does not exist or could not be contacted. "- what do you mean by "AD opens"?
Sorry if I wasn't clear, I meant " AD Sites & Services ", " Users & Computers " ...- how many DC's do you have in this domain?
I have 3 DC's, I only restored a single VM " alone ", the AD VM holding the FSMO roles. The others weren't restored, I was just trying this VM.- are some (all) of them also serve as DNS servers holding DNS zone of this domain?
2 are DNS servers, this one, and another one. This server has the other DNS server as its primary DNS, and its own IP address as secondary DNS.Also, I strongly recommend opening a support case for a closer look at the log files.
I'll do this right now, thanks foggy
I found some similar case ( vmware-vsphere-f24/restored-dc-fails-to-start-ad-t11365-15.html
), but out of manipulating the registry (Tried, but it was a pain at many other levels to get the domain back on rails, I guess things should go on without such manipulations ?
PS : To avoid a VMware mistake or something specific out of VEEAM, I've just cloned this AD server from the production esxi, and copied it on the old esxi, in the private vlan, everything works fine.