COB wrote:
> I have wsus 3.0 installed and working for my network computers. I have group
> policy updating pointing to the wsus server.
>
> Yesterday I created a new group in AD (win2003) and then created the group
> in WSUS.
Do you really mean an AD group or was it an OU? (Did you move the servers into
an OU or add them to a group?)
> Yesterday both servers showed up in wsus under member server group
> and updates started generating. On each server in the Automatic updates, the
> Auto Update was grayed out indicating it was pulling from group policy and
> the wsus server. Upon rebooting the servers, the updates stopped populating.
> On the non-wsus server the auto updates indicate they are set to No Auto
> Updates and they are NOT grayed out anymore which tells me that something has
> failed - but only for the member servers not the user workstations which
> still appears to be fine.
Sounds as if the servers are no longer receiving group policy. Is the relevant
group policy object liked to the new OU (if it was an OU) or (if it was a group)
is the group policy object filtered by group membership?
Try the Client Diagnostics Tool:
<http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
http://technet.microsoft.com/en-us/wsus/bb466192.aspx
Harry.
>
> I tried gpupdate /force a couple of times. I ran wuauctl /detectnow from
> both servers and nothing is happening.
>
> The non-wsus server log indicates it still needs 48 updates and says
> "Pending Reboot". I have rebooted this server 2 times now and its like wsus
> has lost contact and is not responding. Is this an issue with Member
> Servers? Why would it work once initially and then fail? any ideas?