Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WSUS 3.0 cannot show new computer

15 views
Skip to first unread message

GUSN2005

unread,
Dec 7, 2007, 7:55:01 AM12/7/07
to
My WSUS system was upgraded from 2.0 to 3.0 two month ago.

The WSUS 3.0 works well; the entire client computers can get updates from
WSUS.
There are several computer groups in the WSUS which keep computers, the
computer groups was migrated while WSUS upgrade.

I noticed when I add new computer in the AD, it can get updates from WSUS,
but I cannot find it in the computer groups of the WSUS.

Please tell me how to fix this problem.

Thanks

John R

unread,
Dec 7, 2007, 8:04:24 AM12/7/07
to

"GUSN2005" <GUSN...@discussions.microsoft.com> wrote in message
news:A43F5DB1-C01A-4D01...@microsoft.com...

It's funny, I just posted this in another thread almost word for word...

Were the new machines created using an Image? If so, were the images
Sysprep'd? If they were not, See Microsoft KB 903262. The client needs to
re-register under a new SusClientID. Also, the original machines that were
used to create the image may also need to re-register.

I implemented this using a .BAT file as follows that I run on problem
clients...

>>net stop wuauserv
>>REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
>>PingID /f
>>REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
>>AccountDomainSid /f
>>REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
>>SusClientID /f
>>net start wuauserv
>>wuauclt.exe /resetauthorization /detectnow

(Note, there are 5 lines to that bat file, because some news readers
automatically wrap lines, each begins with a ">>", remove the ">>" prior to
executing)

John R


John R

unread,
Dec 7, 2007, 8:55:56 AM12/7/07
to

"John R" <jsr^^^813@zoom^^^internet.net> wrote in message
news:eF3DcGNO...@TK2MSFTNGP02.phx.gbl...

Well, I guess that was a bad choice, lol..

Here it is again with "&&" instead of ">>"

&&net stop wuauserv
&&REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
PingID /f
&&REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
AccountDomainSid /f
&&REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
SusClientID /f
&&net start wuauserv
&&wuauclt.exe /resetauthorization /detectnow

John R
>
>


GUSN2005

unread,
Dec 7, 2007, 12:20:00 PM12/7/07
to
Hi John,

Thanks for your reply.

But my new machines were not created using an Image, some new machines are
running windows XP professional with SP2, some running windows server 2003
with SP2.

GU

John R

unread,
Dec 7, 2007, 2:02:00 PM12/7/07
to

"GUSN2005" <GUSN...@discussions.microsoft.com> wrote in message
news:028534EC-23D2-4958...@microsoft.com...

> Hi John,
>
> Thanks for your reply.
>
> But my new machines were not created using an Image, some new machines are
> running windows XP professional with SP2, some running windows server 2003
> with SP2.
>

And you've checked the default 'Unassigned Computers' group as well I
assume. (Also assuming that the computers are in fact in an OU where the
GPO is deployed, or have been manually assigned to the WSUS server. In the
case of a GPO, you can do a 'gpresult' command to see if the gpo is applied
or not on the workstation.)

Normally, the reason you don't find computers is that two or more have
registered using the same ID which comes from loading multiple machines from
an image that was not Sysprep'd. It won't hurt to go ahead and run that
script on those particular computers. My suggestion would be to try that.

John R


Phil Darveau

unread,
Mar 6, 2011, 3:45:49 PM3/6/11
to
I had a similar issue and the problem was the url link I gave in the GPO. The first time I went by the FQN like this : ? http://wsusservername.domain.local ? and I only 1 out of 10 machines showing in the WSUS manager. I then changed the link in the GPO to go like this :
? http://wsusservername ? and after a gpupdate, all the machines were there.

Hope this helps

> On Friday, December 07, 2007 7:55 AM GUSN200 wrote:

> My WSUS system was upgraded from 2.0 to 3.0 two month ago.
>
> The WSUS 3.0 works well; the entire client computers can get updates from
> WSUS.
> There are several computer groups in the WSUS which keep computers, the
> computer groups was migrated while WSUS upgrade.
>
> I noticed when I add new computer in the AD, it can get updates from WSUS,
> but I cannot find it in the computer groups of the WSUS.
>
> Please tell me how to fix this problem.
>
> Thanks


>> On Friday, December 07, 2007 8:04 AM John R wrote:

>> "GUSN2005" <GUSN...@discussions.microsoft.com> wrote in message

>> news:A43F5DB1-C01A-4D01...@microsoft.com...


>>
>> It's funny, I just posted this in another thread almost word for word...
>>
>> Were the new machines created using an Image? If so, were the images
>> Sysprep'd? If they were not, See Microsoft KB 903262. The client needs to
>> re-register under a new SusClientID. Also, the original machines that were
>> used to create the image may also need to re-register.
>>
>> I implemented this using a .BAT file as follows that I run on problem
>> clients...
>>
>>

>> (Note, there are 5 lines to that bat file, because some news readers
>> automatically wrap lines, each begins with a ">>", remove the ">>" prior to
>> executing)
>>
>> John R


>>> On Friday, December 07, 2007 8:55 AM John R wrote:

>>> "John R" <jsr^^^813@zoom^^^internet.net> wrote in message
>>> news:eF3DcGNO...@TK2MSFTNGP02.phx.gbl...
>>>

>>> Well, I guess that was a bad choice, lol..
>>>
>>> Here it is again with "&&" instead of ">>"
>>>
>>> &&net stop wuauserv

>>> &&REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
>>> PingID /f
>>> &&REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
>>> AccountDomainSid /f
>>> &&REG DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v
>>> SusClientID /f


>>> &&net start wuauserv
>>> &&wuauclt.exe /resetauthorization /detectnow
>>>
>>> John R


>>>> On Friday, December 07, 2007 12:20 PM GUSN200 wrote:

>>>> Hi John,
>>>>
>>>> Thanks for your reply.
>>>>
>>>> But my new machines were not created using an Image, some new machines are
>>>> running windows XP professional with SP2, some running windows server 2003
>>>> with SP2.
>>>>

>>>> GU
>>>>
>>>> "John R" wrote:


>>>>> On Friday, December 07, 2007 2:02 PM John R wrote:

>>>>> "GUSN2005" <GUSN...@discussions.microsoft.com> wrote in message
>>>>> news:028534EC-23D2-4958...@microsoft.com...
>>>>>

>>>>> And you've checked the default 'Unassigned Computers' group as well I
>>>>> assume. (Also assuming that the computers are in fact in an OU where the
>>>>> GPO is deployed, or have been manually assigned to the WSUS server. In the
>>>>> case of a GPO, you can do a 'gpresult' command to see if the gpo is applied
>>>>> or not on the workstation.)
>>>>>
>>>>> Normally, the reason you don't find computers is that two or more have
>>>>> registered using the same ID which comes from loading multiple machines from
>>>>> an image that was not Sysprep'd. It won't hurt to go ahead and run that
>>>>> script on those particular computers. My suggestion would be to try that.
>>>>>
>>>>> John R


>>>>> Submitted via EggHeadCafe
>>>>> Install Windows Updates using C# & WUAPI
>>>>> http://www.eggheadcafe.com/tutorials/aspnet/0e46f5cb-9c67-41fb-b362-4981543fd24b/install-windows-updates-using-c--wuapi.aspx

0 new messages