Networks

Ask something
Question Locked

WSUS 3.0: Can't view my network computers

0 helpful
9 replies

by mrpunjab

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When I click the computers section of my WSUS 3.0 administration console, my detail pane does not show any computers. I tried with "Any" in the "Status" drop down and clicked "refresh". Nothing appears in the detail pane. On the top it shows "All Computers (0 computers of 0 shown, 0 total). Can some one help me troubleshoot this???

Further when we set GPO's do we set them on the Domain Controller or the Server we installed WSUS on??

9 replies

by churdoo

The question you asked about setting GPO's makes me think it's your GPO's that are not set up correctly.

Typically, you'll create a new GPO with the appropriate WSUS settings and link it to an OU which contains your computer objects. Generally I'll create one GPO configured for nightly updates for my workstations and link it to my workstations OU, another for servers configured for weekly updates linked to my servers OU, and then any other special cases.

Give us more information relative to your GPO configuration for your WSUS.

by mrpunjab

1. WSUS is installed on Storage Server not on DC.
2. Setup info on GPO settings on DC:
a. Configure automatic updates: enabled
Configure automatic updating: auto download and notify for install.

b. Specify intranet Microsoft update service location: enabled
Both the entries below are http://:80/

Then went to command prompt of the DC and executed command:
"wuauclt.exe /detectnow"
Which i think may be wrong. Is there a command that i can run from the DC so all the clients can redetect for WSUS.

BTW my DC is visible in WSUS management console now. I executed the same command from my workstation on the network but it did has not shown up in that list so far.

by churdoo

Sounds like you've only modified the GPO of the local computer on your DC -- this will not have the results that you're expecting.

What you want to do, well first is to download the GPMC (Group Policy Management Console), free download from MS, as it makes GP management much simpler.
http://www.microsoft.com/DownLoads/details.aspx?FamilyID=0a6d4c24-8cbd-4b35-9272-dd3cbfc81887&displaylang=en

Next, create an OU into which you'll eventually move all of your generic workstations' computer objects. Create and link a new GPO to that OU and configure the automatic updates as you have above. Finally, move a test workstation computer object in ADUC from the built in Computers OU to the new OU you've created here. Go to the test workstation and execute "gpupdate /force" at a CMD prompt. On the test workstation, you may also want to stop the "Automatic Updates" service and delete the "windowsupdate.log" in %systemroot% (C:\windows by default), restart the Automatic Updates service, and finally execute "wuauclt /detectnow" from CMD prompt. By deleting the windowsupdate.log, a new one will be created and it will be available and easier to use for further troubleshooting if necessary. Make yourself familiar with this log.

Once confirmed on your test workstation and it shows up on your WSUS management console, you can move additional computer objects to the new OU as applicable. I know of no way to automatically and globally execute either the GPUPDATE or WUAUCLT commands except by login scripts -- both of these processes happen automatically at timed intervals and if left alone, will happen automatically at some point, without you having to touch each workstation. So once your test is confirmed on your test workstations, you can simply move the rest of your workstations to the applicable OU and monitor your WSUS server and watch as the rest of the workstations appear over the next several to 24 hours as they perform their typical automatic gpupdate and wuauclt processes.

As I indicated in my last post, I will typically create an OU for my generic workstation objects which is configured to install updates nightly, then a separate Server OU and Server GPO configured to apply updates only once weekly. The GPMC makes this easy.

edited: just a couple things, clarity mostly

by mrpunjab

i think you are right I tried changing GP on my workstation and run the gpupdate and wuauclt commands. My work station populated the list. Thanks heaps for your patience. Well now I want to know If i can run a script to change the GPO's. say If i can combine that script with the gpupdate and wuauclt and run it at startup (just a thought). Or do I have to make an OU and the rest of it???

Further if I have to make a new OU and link a GPO with it, could you be a bit more descriptive as to where to go and what to do..? Thanks

by churdoo

Download the GPMC that I told you about and install it on one of your servers, whichever server you typically run Active Directory Users and Computers from.

There is no way, at least that I know of, to batch edit each individual local computer GPO, besides, doing so defeats the purpose of GP processing in active directory.

Yes create the OU using Active Directory Users and Computers, then open the GPMC and create and link a new GPO to that OU and give it an appropriate name. Edit the GPO and add the settings that you want for your WSUS Server, i.e. the same settings you applied to the individual local GP's that you edited. Once you have the settings in place, just move a different workstation into that OU, go to the workstation and run the GPUPDATE /FORCE and the WUAUCLT /DETECTNOW. Check the WSUS server for the new workstation.

Once done and tested, note that applying those settings to other computers doesn't involve scripts, batch files, nothing, just go to Active Directory Users and Computers and move the computer object into the OU that you set up.

by mrpunjab

Thanks

Can't I link the new GPO to existing OU??

by mrpunjab

Your way is working but there are a few anomalies occuring in the network now that I can't explain. I'll try figuring them out and see how i go...

by churdoo

Yes you can link the new GPO to an existing OU. I don't think you can link a GPO to the built in Computers OU, but if your computer objects are already in the non built in OU, then yes you can simply link your GPO there.

This discussion is closed to new replies.