WSUS doesn't see any computers

We has WSUS running on Windows Server 2003.  That crashed.  I installed WSUS 3.0 SP2 on a new server running 2008 Server R2.  The new installation seems to be working fine - updates downloaded etc - however it sees no computers.  I have change the Group Policy to point to the new server.

I believe the problem is the registry settings on the PC are still pointing to the old server.  The old server still exists just the WSUS is not running.  I have ran the commands to try to force the detection however no change - still looking at the old server.

Any thoughts?
magarnerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
magarnerConnect With a Mentor Author Commented:
I changed the enforced flag to a yes and now they are starting to come through.  I really do not understand why this is - the old server that had the GPO on it is no longer running active directory - we demoted that server - therefore the GPO the should not be a GPO to overwrite - or atleast I would think that the AD users would not be looking to that server for GPO's.  
0
 
Stelian StanNetwork AdministratorCommented:
0
 
magarnerAuthor Commented:
I tried all of those options - the only way I was able to get it to work was to edit the registry - that is not a good option for over 200 computers - plus what is going to happen when I add new computers.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
magarnerAuthor Commented:
On the client side I ran gpupdate /force - and then ran gpresult /v - it says The following GPO's were not applied becuase they were filtered out

WSUS
   Filtering:   Not Applied (Empty)

What does that mean?  That seems to be why my clients are not picking up the change?
0
 
magarnerAuthor Commented:
Disregard my last comment it is not relevent since that GPO was part of the computer group and not the user group - so I am still in a position where my changes to my GPO will not apply to the client computers?

Thought?
0
 
Donald StewartNetwork AdministratorCommented:
Are the client computers in the OU that the GPO is applied to ?

Do you have "Authenticated Users" in the security filtering ? <<<Computers are members of that group FYI
0
 
magarnerAuthor Commented:
Yes Authenticated users is in the security filtering - and computers are members of the OU.
0
 
Donald StewartNetwork AdministratorCommented:
Are the computers in the default "Computers" container ?
0
 
Donald StewartNetwork AdministratorCommented:
You can check by running from the command prompt:


Set
0
 
magarnerAuthor Commented:
What exaclty am i looking for - my logonserver is the correct one?
0
 
Donald StewartNetwork AdministratorCommented:
I would also run rsop.msc
0
 
magarnerAuthor Commented:
What am I looking for on rsop.msc
0
 
Donald StewartNetwork AdministratorCommented:
Computer configuration>>>Administrative templates>>>Windows Components>>>Windows Update>>> is the correct GPO listed under GPO name(Far right) ?
0
 
magarnerAuthor Commented:
Well now they are again - after setting the enforced flag - they all appear to have come through.  Turn that flag off and they stopped almost immediately.
0
 
Donald StewartNetwork AdministratorCommented:
Rsop will show you the GPO that is overriding
0
 
magarnerAuthor Commented:
This is what fixed the problem.
0
All Courses

From novice to tech pro — start learning today.