Network ID/ Change...

[Mr_Jiminy]

Has anyone ever experienced computers losing connection to the domain on mass?

 

We have a batch of Windows 7 and XP laptops which have seemingly lost connection, with the Network ID and Change button are both greyed out.

 

The only way to re-connect is to remove to a local workgroup and then re-connect to the domain.

 

The only common denominator is having used WDS to have imaged them.

 

Any ideas?

[MatthewL]

Have you sysprep'd the machines?

[Mr_Jiminy]

Have you sysprep'd the machines?

 

Yep sysprep ran prior to capturing each image.

[Garacesh]

We get the same problem here. I read somewhere (helpful, I know!) that Startup Repair can often try to 'roll back' a machine in a similar manner to System Restore, which results in a failure with AD. We have to do the same with ours, drop them into a workgroup, then back onto the domain. Although we do that via the 'Change' button, so if that's greyed out for you, I'm not sure how much use this would be.

 

The following commands from an administrative command prompt disable startup repair:

bcdedit /set {default} recoveryenabled no

bcdedit /set {default} bootstatuspolicy ignoreallfailures

 

We haven't rolled it out to the site yet, though, so I can't confirm it works (I can confirm that disables startup repair, but not that it stops things losing their connection)

[Mr_Jiminy]

Brilliant will give that a whirl, thanks

Typically because this has been an image, we're suffering from this on mass in one of our areas... Fortunately we already had a new unattended image compiled and ready, so that took the bite out of it.

It was more of a curiosity thing for us.