After using WDS machines won't apply computer group policy

[marsdenprimary]

Hi,

 

I've successfully managed to image some of our machines but they're getting stuck as they are not applying the Computer Config settings. Checked in gpupdate and they're getting the user settings but not the computer ones from AD. Why?

 

Checked DNS and the forward addresses are there but nothing in reverse lookup. Could this be it?

 

What can i do? Do i need to re-join them to the domain?

[jamesreedersmith]

Have they been sysprepped correctly?

[marsdenprimary]

Have they been sysprepped correctly?

 

Now then. I don't know what that means. :/ I did do the sysprep thing on the pc getting imaged... did i need to sysprep all the others too that were having the image applied??

[Guest Guest]

Network not coming up in time? Search this forum for mediasense

It's a reg key

[marsdenprimary]

Getting this from gpupdate /r:

 

The processing of Group Policy failed. Windows could not resolve the computer na

me. 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 co

ntroller has not replicated to the current domain controller).

[m25man]

Check your DNS/DHCP and clean it up.

Depending how you have it setup machines can register themselves with DHCP/DNS with random-minint names.

Your reverse DNS becomes polluted with ambiguous IP/NetBios names then GPs all go pear shaped until the DNS gets scavenged.

Check this 1st clean up the DNS reboot the PC see what happens.

[marsdenprimary]

Check your DNS/DHCP and clean it up.

Depending how you have it setup machines can register themselves with DHCP/DNS with random-minint names.

Your reverse DNS becomes polluted with ambiguous IP/NetBios names then GPs all go pear shaped until the DNS gets scavenged.

Check this 1st clean up the DNS reboot the PC see what happens.

 

Giving it a go now...

[marsdenprimary]

...didn't seem to work. Still getting the same message. How frustrating! So close but no cigar!! Any other ideas?

[marsdenprimary]

These are Windows 7 machines by the way with a 2008 server

[Ergo]

Daft question maybe, but is the client machine being given the IP address' of your internal DNS servers for name resolution? Have you tested that your AD domain name, and DC server names resolve correctly using these DNS servers?

 

nslookup domainname.tld

nslookup DCname.domainname.tld

 

Should both resolve correctly, almost instantly and with no errors

 

Dave

[marsdenprimary]

Daft question maybe, but is the client machine being given the IP address' of your internal DNS servers for name resolution? Have you tested that your AD domain name, and DC server names resolve correctly using these DNS servers?

 

nslookup domainname.tld

nslookup DCname.domainname.tld

 

Should both resolve correctly, almost instantly and with no errors

 

Dave

 

Yep resolving no problem... I have a sneaking suspicion it is something to do with the way the PC has joined to the domain... Just checking it now. Removed / rejoined to see if that sorts it.

[marsdenprimary]

Okay. Removed and rejoined- STILL NO JOY!? This makes me sad. I thought it would be much less time consuming and simpler than this to deploy an image... Do you recommend changing the computer name?

[Ergo]

That would be a good investigative approach. Before you do, is there anything in the event log relating to authentication errors on the domain before the error about accessing the DC for GP refresh?

 

Dave

[marsdenprimary]

That would be a good investigative approach. Before you do, is there anything in the event log relating to authentication errors on the domain before the error about accessing the DC for GP refresh?

 

Dave

nothing I can see

 

What do you suggest now? Total rebuild??

[Ergo]

I would; remove the machine from the domain, reboot, rename it, reboot, add to the domain, reboot, test for problem.

 

Yes that is tedious but the reboots will make sure nothing strange is going on.

 

If after the above it works, the problem probably relates to a computer account already in the domain of the original name, or part of the process of renaming and adding to the domain you have configured in WDS.

 

If after the above it does not work you probably have a slightly more complicated problem with your image which is preventing networking or domain operations from working correctly. I would go back to your image and see if that works.

 

Hope that helps.

 

Dave

[marsdenprimary]

I would; remove the machine from the domain, reboot, rename it, reboot, add to the domain, reboot, test for problem.

 

Yes that is tedious but the reboots will make sure nothing strange is going on.

 

If after the above it works, the problem probably relates to a computer account already in the domain of the original name, or part of the process of renaming and adding to the domain you have configured in WDS.

 

If after the above it does not work you probably have a slightly more complicated problem with your image which is preventing networking or domain operations from working correctly. I would go back to your image and see if that works.

 

Hope that helps.

 

Dave

 

Sadly- the above doesn't work so it must be the image. Harumph! Thankyou for your help on this. It's the first time i've ever used WDS to capture / deploy an image so i must have mucked it up somewhere.

[MatthewL]

What OS is this as it doesn't say.

[marsdenprimary]

What OS is this as it doesn't say.

 

See post #9

[MatthewL]

Sorry my bad.

[sonic1485]

When the imaged machines were rejoined to the network were they put in the correct OU in AD?

[Tsonga]

If you have time, add MDT 2012 to the server for deployment. Best deployment/capture tool on the planet, plenty of documentation, from Microsoft and free

[ricki]

Hi

 

Is the nic card in the client a 1 gig card.

see http://support.microsoft.com/kb/2421599

create a notepad doc and put this in it

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

 

"GpNetworkStartTimeoutPolicyValue"=dword:0000003c

 

save it a gpodelay.reg

 

log onto the client as administrator and double click the file and insert it into the registry.

 

then reboot and see if that fixes the error,

 

If this does not work it might be a corrupt image. When you installed this machine you did wipe it and all the partitions before you started and installed from original disk and not the manufactures install. Some companies like dell put extra partitions on the machine for restore and I have had problems either taking an image or group policies not applying.

 

Richard

Edited January 10, 2013 by ricki

[marsdenprimary]

CRACKED IT!!!

 

Turns out the original image I captured must have been corrupt or something. I decided to follow these guides again:

 

SYSPREP: how can I sysprep Windows Vista ? - Deploying Windows XP, Vista, Server and more... - www.windows-noob.com

 

CAPTURE: how can I CAPTURE an Image using WDS - Windows Deployment Services (WDS) - www.windows-noob.com

 

DEPLOY: how can I DEPLOY an image captured using WDS ? - Windows Deployment Services (WDS) - www.windows-noob.com

 

It feels like such a faff doing all this, many, many forums and technical tips for this and that and at the end of the day- it was just a corrupt image. Thanks for all your help everyone. Not sure why the image was corrupt or not working properly as i've been round the houses and back on this one and can't tell my backside from my elbow now.

 

If only there were some script or ANYTHING that did all this for you... You put in everything you want installing, domain joining, where etc... (in really basic, simple language) into a visual display and then press GO. x