Those error messages (and similar) plague me from time to time. Once it was to do with a missing GPO folder in the sysvol share. Another time it was due to Symantec scanning the sysvol share. I have a new-ish one now which I have yet to fathom out. My DCs are virtualised too.
2009/3/11 David Lum <[email protected]> > I have a recently virtualized DC with the following entries in the * > Application* Event log (entries did not appear before VM-ing to Hyper-V): > > > > Event Type: Error > > Event Source: Userenv > > Event Category: None > > Event ID: 1054 > > Date: 3/11/2009 > > Time: 6:37:02 AM > > User: NT AUTHORITY\SYSTEM > > Computer: COC-SBS1 > > Description: > > Windows cannot obtain the domain controller name for your computer network. > (An unexpected network error occurred. ). Group Policy processing aborted. > > What I have already tried: > > DCDIAG: Comes up clean > NETDIAG: passes all test > Replication with another DC works > This DC is also a DNS server, and for DNS it points to itself > No related errors in this servers System Event log > When logged in, \\mydomain.com\sysvol\mydomain.com works > I can get to the DC with ADUC snap in, etc > > EventID.NET has an entry about an AMD processor driver, which I haven’t > tried yet but the VM’s DC is on an quad-core AMD Opteron system > > *David Lum** **// *SYSTEMS ENGINEER > NORTHWEST EVALUATION ASSOCIATION > (Desk) 971.222.1025 *// *(Cell) 503.267.9764 > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
