1) Some time ago, a colleague did a clean install of Windows Server 2008 R2, promoted it to Domain Controller from an old Windows Server 2003, and life seemed to be good. In the meantime, a bunch of software was installed the on server.
2) He asked me to take a look because of a seeming annoyance: the Active Directory for Users and Computers (dsa.msc) fails with this error:
ERROR: Naming information cannot be located because: The specified domain either does not exist or could not be contacted.
3) Looking further: - There is no SYSVOL and no NETLOGON - dcdiag passes most tests, but flags this error:
... Running enterprise tests on : myserver.local Starting test: LocatorCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down.
4) Most things seem to work. Active Directory exists, users can log in, the databases and 3rd-party enterprise software installed on the server all work.
But we seem to have a domain without a PDC.
It is not practical to reinstall from scratch.
Q: Is there any chance I can somehow create a Global Catalog, SYSVOL and NETLOGON and turn our Domain Controller into a viable PDC?
1) When I try to seize the relevant FSMO roles, ntdsutil reports "FSMO transferred successfully - seizure not required." So this is not the problem.
2) Both dsa.msc (Active Directory for Users & Computers) and dssite.msc (Active Directory Sites and Services) snap-ins fail with
Naming information cannot be located.