lgallion
asked on
Window Server Update Service 3.0
Hi,
I have a WSUS server version 3.0 running on Windows 2003 and it has been automatically running updates on desktop pcs without users' intervention for serveral years. A couple of months ago, the new pcs I moved to OU I created for WSUS under the AD didnot received updates. I checked the all settings on GPO/IIS and they are all the same as it was before.
What I found out later is when I move the new pc to WSUS OU it usually goes to Unassigned Computer in WSUS Update Service All Computers folder I then move it to a group underneath called CCG I added and GPO points to this group too. ( By the way, the existing pcs under CCG group are still getting updates). For some reason the new pc does not show under the Unassigned Computers anymore so I cannot reassign it to CCG although it shows 63 total under the Unassigned Computer. Please see the screen shots attached. Can someone help me please?
Thanks a lot!
WSUS-Issue.docx
I have a WSUS server version 3.0 running on Windows 2003 and it has been automatically running updates on desktop pcs without users' intervention for serveral years. A couple of months ago, the new pcs I moved to OU I created for WSUS under the AD didnot received updates. I checked the all settings on GPO/IIS and they are all the same as it was before.
What I found out later is when I move the new pc to WSUS OU it usually goes to Unassigned Computer in WSUS Update Service All Computers folder I then move it to a group underneath called CCG I added and GPO points to this group too. ( By the way, the existing pcs under CCG group are still getting updates). For some reason the new pc does not show under the Unassigned Computers anymore so I cannot reassign it to CCG although it shows 63 total under the Unassigned Computer. Please see the screen shots attached. Can someone help me please?
Thanks a lot!
WSUS-Issue.docx
Your screenshot shows you're only displaying "failed" instead of status of "Any" for the Unassigned group.
ASKER
"Any" is the same result. see the screen shot please.
Unassigned-Computers.docx
Unassigned-Computers.docx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
They are missing. They are in WSUS OU but not in CCG. You are right, 63 machines in total in CCG, sorry. I missed about 20 pcs.
Can you download the WSUS Client Diagnostic Tool from this link below, run it on a PC that doesn't appear and post the results:
http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx
http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx
ASKER
ok. Will do!
ASKER
Here is the result. This is new pc I moved to WSUS OU serveral days ago.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes. Let me attach again.
ClientDiag-Result.docx
ClientDiag-Result.docx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok. Let me run it on 32 bit os and send you the result
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes. I use Acronis to create image and clone new pcs.
ASKER
I will create the batch file and will let you know if it is fixed.
Sounds good
Oh, I didn't know you were doing this on 64-bit systems. Are all the problematic machines 64-bit. If not, please run on 32-bit and post results. Do this AFTER you make sure your clients don't use the same SID from cloning via Acronis....that is definitely a problem. I run sysprep on my machines prior to taking an image. I use Acronis too.
The best collection of troubleshooting WSUS found here
http://social.technet.microsoft.com/wiki/contents/articles/2491.wsus-troubleshooting-survival-guide.aspx
http://social.technet.microsoft.com/wiki/contents/articles/2491.wsus-troubleshooting-survival-guide.aspx
ASKER
Ok. I will read. Thanks a lot!