Clients not listing in WSUS
Showing all messages in thread #1194037726
Windows Server 2003 Annoyances Discussion Forum
The following are all of the messages in this thread (5 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
|
Clients not listing in WSUS
Friday, November 2, 2007 at 2:08 pm
Posted by Jared Harder
(11 messages posted)
I'm having a problem with 2 clients in my network. I have a WSUS server that distributes
all updates to computers in this local area. There are 39 computers that are served
by this server, and only 37 of them are showing up.
Recently, these two computers that are having troubles were ghosted. I have recently
built the ghost images that were placed on them (two seperate images for two different
builds). During the ghost construction, I was able to add the computers to my domain
and WSUS server and properly install all available updates. I then finished preparation
of the images and cast them to the computers and placed them in the network. Since
then, they have shown up only in Active Directory, and not WSUS.
I've verified they are placed properly in my organizational structure so they receive
the commands to update, and they are. I've checked the logs (%systemroot%\WindowsUpdate.log)
and both appear to be contacting my WSUS server correctly, yet they aren't showing
up in my console.
How can I go about re-establishing their presence in the console?
Thank you,
Jared
[Reply or follow-up to this message]
|
re: Clients not listing in WSUS
Tuesday, November 6, 2007 at 5:50 pm
Posted by dsennich
(2 messages posted)
This is usually resolved by one of the following things on my network
the computers do not inherit the group policy that is directing them to the correct
WSUS server. The policy is under Computer configuration -> Administrative Templates
-> Windows Components -> Windows Update
- gpresult.exe will show you which policies are currently applied on that workstation).
-
gpupdate should re-apply the policy (or gpupdate /force)
finally wuauclt.exe /updatenow /resetauthorization asks windows update to contact
the server. (or you can manually edit the registry keys that control which windows
update server is used.)
Also SP2 needs to be installed.
One other thing to check - did sysprep create a new guid?
Also see MS KB903262
[Reply or follow-up to this message]
|
re: Clients not listing in WSUS
Wednesday, November 7, 2007 at 1:23 pm
Posted by Jared Harder
(11 messages posted)
Thanks, that KB article got WSUS showing one of the clients. The other client is
still not showing up for some reason. Is there any way to reset a GUID on a computer,
or do I need to reghost it?
[Reply or follow-up to this message]
|
re: Clients not listing in WSUS
Thursday, November 8, 2007 at 1:12 pm
Posted by Jared Harder
(11 messages posted)
Actually, it turns out this worked for the second computer. It just took a while
for it to show up (I waited over night and it showed up).
Thanks, this worked wonderfully!
[Reply or follow-up to this message]
|
re: Clients not listing in WSUS
Friday, November 9, 2007 at 10:02 am
Posted by dsennich
(2 messages posted)
Correction:
should be wuauclt.exe /detectnow /resetauthorization
That probably explains your delay.
[Reply or follow-up to this message]
|
|
Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
|
|
Return to the Windows Server 2003 Discussion Forum
|
