WSUS Not Working on Some Stone Machines

[garethEds]

We have some Stone machines here that have been rebuilt - around half of them are not updating using WSUS. It's really strange as the other half are.

 

We are having to reinstall the Windows Update Agent manually on the machines which are not working. This has the effect of fixing them and they then get their updates.

 

However, can anyone advise on why this would be happening? All of the machines were RIS built so there should be no issues and they were all built on the same day.

 

Gareth

[ZeroHour]

I take it that only you/techs have admin rights on the pc?

What firewall do you have also as I have found some issues with WUA updates delivered from the net before WSUS gets in there.

[garethEds]

I take it that only you/techs have admin rights on the pc?

What firewall do you have also as I have found some issues with WUA updates delivered from the net before WSUS gets in there.

 

Hi ZH,

 

I've made sure the firewall is off across the network via GPO to test the machines.

 

LIke I say - installing the Windows Update Agent manually on the troublesome computers has worked and the two machines I tested this on are now showing 100% updated.

 

GJE

[dwhyte85]

Hello,

 

Have you tried:

 

WUAUCLT /detectnow

 

on the machines from the cmd prompt instead of re-install? Also have you checked the C:\windows\WindowsUpdate.log - might give you some insight

[garethEds]

Hello,

 

Have you tried:

 

WUAUCLT /detectnow

 

on the machines from the cmd prompt instead of re-install? Also have you checked the C:\windows\WindowsUpdate.log - might give you some insight

 

Yes - I run that command but it was giving me an error in the Event Viewer - like the one shown below:

 

DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service wuauserv with arguments "" in order to run the server:

{E60687F7-01A1-40AA-86AC-DB1CBF673334}

 

 

[ricki]

Hi

 

Try this in a bat file and then run the bat file on the client pc.

 

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f

cls

@echo Triggering detection after resetting WSUS client identity

net stop wuauserv

net start wuauserv

wuauclt /resetauthorization /detectnow

 

Richard

[dwhyte85]

You would need the service to be running, go to services.msc from run and check if 'Automatic Updates' is set to enabled and running; i don't know why it'd stop though

[ricki]

If that does not work download the clientdiag.exe and try running that and it might give you a clue whats wrong.

 

http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE

 

Richard

[ZeroHour]

I've made sure the firewall is off across the network via GPO to test the machines.

 

Hi

I was actually meaning external net firewall/proxy rather then local pc firewalls as allows are normally in already for WUA.

[alan-d]

We had this problem on a few machines and deleted the following registry entry

 

HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

 

Rebooted the PC and 99% of them connected within 24 hours.

[Dos_Box]

We had this problem on a few machines and deleted the following registry entry

 

HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

 

Rebooted the PC and 99% of them connected within 24 hours.

 

 

That's exactly what I do after reimaging machines using RIS\WDS Legacy mode. Apparently sysprep is supposed to reset this value as it will be set for the original machine you imaged from, but experience tells me that this often does not happen. A little script to delete this entry does the job once the imaging process finishes. Once you reboot again the entry is recreated with the correct settings.