Why do some machines retain old group policy data?
I have a handful of machines that retain old group policy data, specifically incorrect information for the Windows Update settings. In particular, these machines point to an old intranet WSUS address. All policies have been updated to reflect the new server address but these machines have not accepted the updated information. I have scoured all GPO's to make sure there is nothing that still points to the old address and there is not. I have removed and created new GPO's to get a fresh start, but no luck.
The machines are desktops and laptops running XP Pro SP3 and all servers are 2008 R2 SP1.
So far I have tried the following to no avail:
-gpupdate /force...no change
-updating the GP info manually on the machine, but it reverts to the old info.
-deleting the reg keys for the info and running gpupdate /force - but it returns the old info
-deleting the entire Group Policy data from HKLM\Software\Microsoft\Wi
-remove PC from domain and re-join...no change
-I have been through all of the Windows Update troubleshooting information and everything tests fine (can reach the server, can download the wuident.cab file, have done all the client self update troubleshooting and resets...all to no avail
-I have run gpresult and all the data is correct, the right GPO's are applying
-I have checked to make sure both User and Computer Configurations are set to apply
-there are no GP restrictions in place, nothing is configured to keep the policy from applying
-I have modified other group policy settings to make sure the GPO's are applying and discovered that only part of the Computer Configuration is applied...specifically anything within Windows Settings is applied, however I can't find any settings from within Administrative Templates that are being applied.
I have found one 'Extra Registry Setting' in the Administrative Templates which no longer has a category in the GPOE, so I've been wondering if I need to update the ADMX files to fix this? If so, how do I do that?
I'm a little lost at this point...I'm self taught, so to have gotten here has been a lot of work and I have exhausted Google for anything that might help me, I've read all the posts on this info and tried anything and everything suggested to those who have had similar problems, but have not gained any ground. Any input will be appreciated.
Thanks!
The machines are desktops and laptops running XP Pro SP3 and all servers are 2008 R2 SP1.
So far I have tried the following to no avail:
-gpupdate /force...no change
-updating the GP info manually on the machine, but it reverts to the old info.
-deleting the reg keys for the info and running gpupdate /force - but it returns the old info
-deleting the entire Group Policy data from HKLM\Software\Microsoft\Wi
-remove PC from domain and re-join...no change
-I have been through all of the Windows Update troubleshooting information and everything tests fine (can reach the server, can download the wuident.cab file, have done all the client self update troubleshooting and resets...all to no avail
-I have run gpresult and all the data is correct, the right GPO's are applying
-I have checked to make sure both User and Computer Configurations are set to apply
-there are no GP restrictions in place, nothing is configured to keep the policy from applying
-I have modified other group policy settings to make sure the GPO's are applying and discovered that only part of the Computer Configuration is applied...specifically anything within Windows Settings is applied, however I can't find any settings from within Administrative Templates that are being applied.
I have found one 'Extra Registry Setting' in the Administrative Templates which no longer has a category in the GPOE, so I've been wondering if I need to update the ADMX files to fix this? If so, how do I do that?
I'm a little lost at this point...I'm self taught, so to have gotten here has been a lot of work and I have exhausted Google for anything that might help me, I've read all the posts on this info and tried anything and everything suggested to those who have had similar problems, but have not gained any ground. Any input will be appreciated.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The new server is a different name, so it should be obvious when/if the change takes effect.
I had not tried clearing the cache, but I have now. I ran gpupdate /force following that and the settings changed instantly! I think the problem is solved.
Could you explain this situation to me? I'd like to understand what was wrong and why this fixed it.
Thanks!
I had not tried clearing the cache, but I have now. I ran gpupdate /force following that and the settings changed instantly! I think the problem is solved.
Could you explain this situation to me? I'd like to understand what was wrong and why this fixed it.
Thanks!
ASKER
Yes, I had run "wuauclt /resetauthorization /detectnow" and it worked in one case only.
I wish I could answer your question as to why... however I tell my friends this:
"If you want me to fix the problem it will take a few minutes. If you want me to figure out how it broke it will take a few days."
"If you want me to fix the problem it will take a few minutes. If you want me to figure out how it broke it will take a few days."
ASKER
Well, thanks for the solution nonetheless. I have spent days getting to this point, I'll take an easy fix.
ASKER
Sorry to come back to this question again...it would appear the solution was only temporary. Many of my machines have reverted to their old settings after some time. Any ideas why this would be happening? After receiving new info from Group Policy and applying it successfully for some time (days/weeks), why would the settings change, where would the machines get this info from?
I have the same problem. I do a gpupdate /force update and the policy applies, however, after the reboot it reverts back to the old GPO. Any ideas?
@davidjuste
This question has been long since answered and probably not even monitored anymore...You will need to open a fresh question to get any responses.
This question has been long since answered and probably not even monitored anymore...You will need to open a fresh question to get any responses.
wuauclt /resetauthorization /detectnow