40 new desktops - some show up in Unassigned some don't show up at

I have a WSUS 3.0 SP1 machine that is controlling the updates to machines in
our domain. I have just rolled out 40 computers, all with different names, as
new desktops for our users. The computers are sitting within different OUs,
that have Group Policies attached to point them towards the WSUS server. All
of the computers are correctly showing the greyed out options in Automatic
Updates on the client, and they're definitely contacting the local server.
What's odd is that some of the new computers (in different OUs), are showing
up in the Update Services console under Unassigned Computers, but most of
them are not anywhere.

Are there logs or anywhere on the server/clients that I should be looking
for errors? This is a little confusing to say the least. We're using the same
Administrative template that we were using before in our Group Policy.

Thank you,

Eric

Eric wrote:
> I have a WSUS 3.0 SP1 machine that is controlling the updates to
> machines in our domain. I have just rolled out 40 computers, all
> with different names, as new desktops for our users. The computers
> are sitting within different OUs, that have Group Policies attached
> to point them towards the WSUS server. All of the computers are
> correctly showing the greyed out options in Automatic Updates on
> the client, and they're definitely contacting the local server.
> What's odd is that some of the new computers (in different OUs),
> are showing up in the Update Services console under Unassigned
> Computers, but most of them are not anywhere.
>
> Are there logs or anywhere on the server/clients that I should be
> looking for errors? This is a little confusing to say the least.
> We're using the same Administrative template that we were using
> before in our Group Policy.

Perhaps ask in the SUS related newsgroups?

From the web:
http://www.microsoft.com/communities...pdate_services

Inside your newsreader:
news://msnews.microsoft.com/microsof...pdate_services

Cross-posted for convenience.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

I've had this problem when the desktops have duplicate SIDs. Did you image
the Desktops? Did you you run sysprep or newsid afterwards?

"Shenan Stanley" wrote:

> Eric wrote:
> > I have a WSUS 3.0 SP1 machine that is controlling the updates to
> > machines in our domain. I have just rolled out 40 computers, all
> > with different names, as new desktops for our users. The computers
> > are sitting within different OUs, that have Group Policies attached
> > to point them towards the WSUS server. All of the computers are
> > correctly showing the greyed out options in Automatic Updates on
> > the client, and they're definitely contacting the local server.
> > What's odd is that some of the new computers (in different OUs),
> > are showing up in the Update Services console under Unassigned
> > Computers, but most of them are not anywhere.
> >
> > Are there logs or anywhere on the server/clients that I should be
> > looking for errors? This is a little confusing to say the least.
> > We're using the same Administrative template that we were using
> > before in our Group Policy.
>
> Perhaps ask in the SUS related newsgroups?
>
> From the web:
> http://www.microsoft.com/communities...pdate_services
>
> Inside your newsreader:
> news://msnews.microsoft.com/microsof...pdate_services
>
> Cross-posted for convenience.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

The logfile is %windir%\WindowsUpdate.log.

It sounds like the new GPO's are not specifying the correct group name or that
the groups specified has not been created in the WSUS console.



On Tue, 17 Mar 2009 11:53:30 -0500, "Shenan Stanley" <>
wrote:

>Eric wrote:
>> I have a WSUS 3.0 SP1 machine that is controlling the updates to
>> machines in our domain. I have just rolled out 40 computers, all
>> with different names, as new desktops for our users. The computers
>> are sitting within different OUs, that have Group Policies attached
>> to point them towards the WSUS server. All of the computers are
>> correctly showing the greyed out options in Automatic Updates on
>> the client, and they're definitely contacting the local server.
>> What's odd is that some of the new computers (in different OUs),
>> are showing up in the Update Services console under Unassigned
>> Computers, but most of them are not anywhere.
>>
>> Are there logs or anywhere on the server/clients that I should be
>> looking for errors? This is a little confusing to say the least.
>> We're using the same Administrative template that we were using
>> before in our Group Policy.
>
>Perhaps ask in the SUS related newsgroups?
>
>From the web:
>http://www.microsoft.com/communities...pdate_services
>
>Inside your newsreader:
>news://msnews.microsoft.com/microsof...pdate_services
>
>Cross-posted for convenience.
>
>--
>Shenan Stanley
> MS-MVP
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.