RM Ones (with RM pre-installed XP) do not appear in WSUS

[PiqueABoo]

it is intriguing that these machines which aren't controlled by CC3 don't just work as you say

 

It is, but could be something as simple as which hotfixes have or haven't been pre-installed i.e. nothing especially Machiavellian or stupid on RM's part.

[Michael]

I didn't think WSUS was hotfix dependant, so long as Automatic Updates is enabled, a WSUS server has been specified in a GPO (easy way) and you're using Windows 2000 SP3 or later, then you're good to go.

 

RM's official position is that they do not support WSUS, however at the one school I support, their admin workstations are HP - so I haven't had the problem meastaugh1 has.

I do suspect it's the RM image the machines come with, as RM of course want you to use CC3. It wouldn't surprise me if it is some reg hack which has been implemented, which is why I suggested formatting.

[meastaugh1]

No, not yet. I've had a quick look through the client and server logs again.

 

Although they have SP2, I wanted to try and re-install the WSUS client. It's WUAU22.msi isn't it? Is that in the main WSUS server installation download as I can't seem to find it.

 

I'll try and give the netmon and enable any verbose server logging tomorrow. Thanks

[PiqueABoo]

To get the latest, greatest WUA v3 (31st-Jul-2007) read here:

 

msdn2.microsoft.com/en-us/library/aa387285.aspx

 

And if that fixes a test box you might want to compare the versions of say "wuauclt.exe" with an unpatched RM box.

[meastaugh1]

Success at last! As suspected, the RM image is to blame. Downloading the client from http://download.windowsupdate.com/v6/windowsupdate/redist/standalone/WindowsUpdateAgent20-x86.exe as mentioned in http://msdn2.microsoft.com/en-us/library/aa387285.aspx does the trick.

 

Thanks all for your advice.

[Michael]

Great stuff, glad this has been solved.

 

meastaugh1 1-0 RM

[PiqueABoo]

the RM image is to blame

 

Well yes.. but we won't know that's really RM's fault without knowing more about the WUA on the image. Could be WUA was perfectly fine when they made an image, but it simply doesn't get along with a subsequently released WSUS server. Was it looking for something on your WSUS server to upgrade the client perhaps?

 

Not that I'd especially tempted to stop and do the forensics once I'd got it working.