Jump to content

Recommended Posts

Posted

Hello,

 

I've just installed Windows 7 64-bit and applied all updates (took me an eternity) including SP1. Joined it to our domain using the Network ID wizard. Restarted. Computer boots up and is joined to domain. Computer appears in our All Computers OU properly named. I log on and all drives are mapped...

 

...but when i run a gpupdate /force from the command line it tells me:

 

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 not replicated to the current Domain controller)

 

We don't have another domain controller.

 

Does anyone know why the Computer Configuration settings from Group Policy aren't being applied? It's applying the User Config settings...

 

We are running 2008 R2 as our Domain Controller

Posted
This seems like a DNS related problem to me, but then again you joined the domain OK. Did there used to be more than one Domain Controller?
  • Thanks 1
Posted
This seems like a DNS related problem to me, but then again you joined the domain OK. Did there used to be more than one Domain Controller?

 

I've been joining new computers to the domain no problem for quite a while now- I just seem to be having issues all of a sudden. The PC has an SSD in it so it boots up mega fast- don't know if this could have anything to do with it?

Posted
remove from domain / rejoin to domain make sure there is not duplicate names in AD if you have already tried this.

 

Thanks for the tip. I've tried this a few time already with no joy.

Posted
The SSD should make no difference - as you say, just makes loading/processing data quicker. Are you running a gpupdate via wired or wireless?
  • Thanks 1
Posted
The SSD should make no difference - as you say, just makes loading/processing data quicker. Are you running a gpupdate via wired or wireless?

 

Wired. I did have to Sysprep this machine a few times (not catching it on boot up...!) :/ so I'm wondering if that may have affected it?

 

I'm going to try removing the computer from the domain, removing the computer object from AD, sysprep with generalise and then re-add it. Think this could work?

Posted
You can Sysprep with generalize up to 3 times on Win 7. If you switched off a computer during the middle of Sysprep, this can ruin an image completely. It's better to let it run and lose one rearm.
  • Thanks 1
Posted
is it hard wires with an intel network card if so try setting to cards properties to 100mb half duplex rather than auto detec see if that helps
  • Thanks 1
Posted
You can Sysprep with generalize up to 3 times on Win 7. If you switched off a computer during the middle of Sysprep, this can ruin an image completely. It's better to let it run and lose one rearm.

 

I didn't switch it off during the Sysprep so that can be ruled out... Looks like this will be the last time i can do it! Fingers crossed...

Posted
is it hard wires with an intel network card if so try setting to cards properties to 100mb half duplex rather than auto detec see if that helps

 

Thanks for the suggestion. I gave that a try but it didn't work.

Posted
Thanks for the suggestion. I gave that a try but it didn't work.

 

try 10mb. Sometimes ive found auto negotiate can take longer that the pc gives it

  • Thanks 1
Posted
try 10mb. Sometimes ive found auto negotiate can take longer that the pc gives it

 

Okay I shall give that a whirl and see if it helps.

 

If this doesn't have any effect- what else could it be? I'd be mortified if i had to re-install Windows all over again.

 

Could the fact it isn't activated yet make a difference to Machine Group Policy settings?

Posted

shouldngt make any difference not being activated.

 

It looks like its not waiting long enough for the network card/network to be ready you could also try setting always wait for network at startup in local gpo (there is also a reg key that does slightly more than this BUt ive had mixed issues using it on win 7 so on your own head be it lol

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"GpNetworkStartTimeoutPolicyValue"=dword:

  • Thanks 1
Posted
shouldngt make any difference not being activated.

 

It looks like its not waiting long enough for the network card/network to be ready you could also try setting always wait for network at startup in local gpo (there is also a reg key that does slightly more than this BUt ive had mixed issues using it on win 7 so on your own head be it lol

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"GpNetworkStartTimeoutPolicyValue"=dword:

 

I did already try this to no avail...

Posted

SOLVED!!

 

After attempting ALL the suggestions provided by the lovely folk here at Edugeek to no avail I reformatted the machine and it's working.

 

I believe the culprit MUST have been the updates...possibly SP1.

 

My suggestion would be to anyone doing this- apply the updates AFTER joining the domain

 

Thanks for all your help everyone- I'm just glad it's all working now!

 

I'll let you know if it blows up after doing the updates again...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...