Discussion:
wsus can only see 16 machines
(too old to reply)
f***@gmail.com
2013-10-03 22:20:16 UTC
Permalink
This is really weird, but we have three standalone wsus servers distributed geographically.

On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.

So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.

That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.

This is on win 2008 r2 enterprise and wsus 3.2.7600.256.

The other two servers have the same wsus version and work fine.
Special Access
2013-10-04 00:01:54 UTC
Permalink
Post by f***@gmail.com
This is really weird, but we have three standalone wsus servers distributed geographically.
On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.
So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.
That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.
This is on win 2008 r2 enterprise and wsus 3.2.7600.256.
The other two servers have the same wsus version and work fine.
We saw something similar when our 'cloning' process didn't create a
new SID on the cloned PC. Drove us crazy for about a week before
someone cloned a new computer and we watched the entire process.

Just a thought
Mike
f***@gmail.com
2013-10-04 21:03:16 UTC
Permalink
Post by Special Access
Post by f***@gmail.com
This is really weird, but we have three standalone wsus servers distributed geographically.
On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.
So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.
That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.
This is on win 2008 r2 enterprise and wsus 3.2.7600.256.
The other two servers have the same wsus version and work fine.
We saw something similar when our 'cloning' process didn't create a
new SID on the cloned PC. Drove us crazy for about a week before
someone cloned a new computer and we watched the entire process.
Just a thought
Mike
We don't clone computers, so sadly this isn't our case.
Special Access
2013-10-05 02:00:37 UTC
Permalink
Post by f***@gmail.com
Post by Special Access
Post by f***@gmail.com
This is really weird, but we have three standalone wsus servers distributed geographically.
On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.
So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.
That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.
This is on win 2008 r2 enterprise and wsus 3.2.7600.256.
The other two servers have the same wsus version and work fine.
We saw something similar when our 'cloning' process didn't create a
new SID on the cloned PC. Drove us crazy for about a week before
someone cloned a new computer and we watched the entire process.
Just a thought
Mike
We don't clone computers, so sadly this isn't our case.
If you are using any type of imaging platform, this could be the
problem. Unless you are building them all from the DVD, then I have
no more ideas for you.
f***@gmail.com
2013-10-09 21:10:44 UTC
Permalink
Post by Special Access
Post by f***@gmail.com
Post by Special Access
Post by f***@gmail.com
This is really weird, but we have three standalone wsus servers distributed geographically.
On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.
So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.
That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.
This is on win 2008 r2 enterprise and wsus 3.2.7600.256.
The other two servers have the same wsus version and work fine.
We saw something similar when our 'cloning' process didn't create a
new SID on the cloned PC. Drove us crazy for about a week before
someone cloned a new computer and we watched the entire process.
Just a thought
Mike
We don't clone computers, so sadly this isn't our case.
If you are using any type of imaging platform, this could be the
problem. Unless you are building them all from the DVD, then I have
no more ideas for you.
The irony is that we use WDS / sysprep on our main branch and it works fine. Machines on the branch with the problem were prepared by normal DVD.

Since the problem is just with one branch i am guessing there is some network/server issue but i don't know how to properly diagnose.

Is there some server side log i can check?
Special Access
2013-10-10 00:42:28 UTC
Permalink
Post by f***@gmail.com
The irony is that we use WDS / sysprep on our main branch and it works fine. Machines on the branch with the problem were prepared by normal DVD.
Since the problem is just with one branch i am guessing there is some network/server issue but i don't know how to properly diagnose.
Is there some server side log i can check?
What WSUS version are you running? 3 sp2 (3.2.7600.226 is what I'm
running)

You can also check the problem computers and delete the "SusClientID"
and "SusClientIDValidation" registry values in the key
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
and then restart the Automatic Updates service. Then run "wuauclt
/resetauthorization /detectnow" to have the computer recreate the
registry entries you just deleted. Then you should see them in the
WSUS console.

There is also a client diagnostic tool that you can get from MS
(http://technet.microsoft.com/en-us/windowsserver/bb466192.aspx, 2nd
from the bottom) that may help you see if the problem is network,
computer or WSUS related.

Good luck!
Mike
John Stark
2014-03-12 01:29:20 UTC
Permalink
http://windowsenterprise.blogspot.com/
Post by f***@gmail.com
This is really weird, but we have three standalone wsus servers distributed geographically.
On one branch, the wsus server shows 16 clients , but i have over 30 machines on the branch.
So, i go to one of them and type wuauclt /detectnow and wuauclt /reportnow.
That machine appears in the wsus console, but one previosly listed machine now disappears! If i retry with another non listed machine, it appears and the previous one that appeared also dissapears. Repeat and it happens the same.
This is on win 2008 r2 enterprise and wsus 3.2.7600.256.
The other two servers have the same wsus version and work fine.
Loading...