Sheridan Posted July 24, 2013 Posted July 24, 2013 I've imaged a room full of PCs to Windows 7 (from a clean sysprep'd image) and have discovered only about 1/3 of them are working properly. The rest fail to apply any computer GPO's - running RSOP shows the error: Group Policy Infrastructure failed due to the error listed below. The specified domain either does not exist or could not be contacted I've checked everything I can think of: - DNS is working fine - Updated/downgraded network drivers - Re-imaged again - Servers are ok and policies are ok Its odd as all the PCs are identical hardware, with the same image on, but it seems entirely random which ones work. Its not cabling as swapping them around doesn't make any difference. The system event shows an initial error: This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following: There are currently no logon servers available to service the logon request. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. Followed by another: The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has to the currennot replicated t domain controller). Anyone seen this before? I'm either about to throw these out of the window, or simply put them back to XP!
round2it Posted July 24, 2013 Posted July 24, 2013 Last time I had problems I had to w32tm /resync then a gp update fixed it. Sorry not much help Check date time and year on new pcs
burgemaster Posted July 24, 2013 Posted July 24, 2013 (edited) Check DNS, check date time, check NIC driver, test with different switch/hub, gpresult, take off the domain and add back on. I would defenitly look at checking domain controller replication. Also if i remember there is a regfix for nics that attempt to start too early, I think you add a delay? Edit. Just read you have tried most of the above! Good luck. Edited July 24, 2013 by burgemaster
Sheridan Posted July 25, 2013 Author Posted July 25, 2013 If anyone else has a similar problem try this: Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used It didn't fix the problem on all of them - but did seem to have an instant effect on a good few of them!
psydii Posted July 25, 2013 Posted July 25, 2013 If anyone else has a similar problem try this: Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used It didn't fix the problem on all of them - but did seem to have an instant effect on a good few of them! An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1 that includes the above hotfix should be rolled out to all Windows 7 SP1 machines in a domain environment.
mrstrong Posted February 28, 2014 Posted February 28, 2014 If anyone else has a similar problem try this: Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used It didn't fix the problem on all of them - but did seem to have an instant effect on a good few of them! Did you ever get to the bottom of this as I think I've got the same issue :-(
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now