WSUS policy

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We had a server configured with SUS years ago and when it stopped working we
did not mess with it. When WSUS came out we installed it on this server but
could not get it to work so we left it alone. We eventually added another
server and installed WSUS using port 8530 successfully. I created a GPO and
set Microsoft update service location to http://server3:8530. Clients never
reported to WSUS so I started to troubleshoot. I found that on each pc and
server the following registry settings were set as follows:
wuserver=http://server1 and wustatusserver=http://server1. I manually change
this to reflect http://server3:8530 on the servers and 1 workstation. These
machines started to report to WSUS. (servers and workstations are windows
2000) I then ran secedit /refreshpolicy machine_policy on this machines and
the registry settings changed back to wuserver=http://server1 and
wustatusserver=http://server1. I ran gpresult to see what policies were being
applied I even deleted and recreate my WSUS policy and could not find any
policy that may be applying this registry setting. Does any body have any
suggestions on how I can pin point the problem
 
Howdie!
We had a server configured with SUS years ago and when it stopped working we
did not mess with it. When WSUS came out we installed it on this server but
could not get it to work so we left it alone. We eventually added another
server and installed WSUS using port 8530 successfully. I created a GPO and
set Microsoft update service location to http://server3:8530. Clients never
reported to WSUS so I started to troubleshoot. I found that on each pc and
server the following registry settings were set as follows:
wuserver=http://server1 and wustatusserver=http://server1. I manually change
this to reflect http://server3:8530 on the servers and 1 workstation. These
machines started to report to WSUS. (servers and workstations are windows
2000) I then ran secedit /refreshpolicy machine_policy on this machines and
the registry settings changed back to wuserver=http://server1 and
wustatusserver=http://server1. I ran gpresult to see what policies were being
applied I even deleted and recreate my WSUS policy and could not find any
policy that may be applying this registry setting. Does any body have any
suggestions on how I can pin point the problem
Click to expand...

There obviously is a problem with your policy processing. As of my
understanding of your issue, you have two possible causes for this error:
(i) You have a (although you looked at gpresult) policy defined, which
sets the (old) SUS server as the default update server. This policy has
higher "priority" than the WSUS policy (maybe a policy linked at the
domain level?) Check rsop.msc to see, what policies are applied!

(ii) the clients/users do not get the policy you defined, at all. Check
whether they are in the scope of the policy (reside in a OU/SubOU)?
There should be computer accounts in there since Windows Update policies
are Computer Configuration...

cheers,

Florian
 
Thanks for the reply. I ran rosp.msc on a workstation and under
computer-administrative template there was entry that said extra registry
settings and in there there were the gpo settings that keep pointing to the
wrong wsus server. I have only 1 gpo which is the domain default policy. If
I look at \sysvol\domain\policies I have 3 guid's. Is this part of the
problem. Can these be removed or fixed.
 
Back
Top