WSUS is a real life saver on a Windows network of any size, it more
than pays off its huge initial download size when it serves computers on
the network and saves internet bandwidth. However, like any other
software, it can be temperamental and have tough to troubleshoot
problems.
I recently came across a problem during the migration at my work. We
set up the client XP SP3 workstation, ran sysprep and then cloned the
box. However, after the deployment, only 1 or 2 computers were appearing
in the WSUS console when there should have been 38.
Puzzled by this, and by the fact that computers were still getting
updates despite not showing up in the console, I decided to investigate.
After a lot of internet searching, I narrowed down the seeming culprit
to a setting in the registry.
It turns out that for whatever reason, sysprep is not removing these
entries in the registry, so the computers after cloning will receive
updates but won’t report to the console. It may have been some change
Microsoft made with SP3, or it may be the updated Automatic Update
client, no one really knows.