Jump to content

Recommended Posts

Posted

Hi,

WSUS is not working on some pcs (mainly W7) but some XP also.

 

These missing computers do not register themselves in WSUS.

 

I have tried

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v AccountDomainSid /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v PingID /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v SusClientId /f
cls
@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow

 

and

IF EXIST ("$tchpath\reglimit.tch")=0
 if InStr(@PRODUCTTYPE, "Windows 7") OR InStr(@PRODUCTTYPE, "Windows Vista")
   SHELL '%comspec% /c REG ADD "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control" /v "RegistrySizeLimit" /t REG_DWORD /d "4294967295" /f > NUL'
 endif
 Copy ("$launchpath\generic.tch") ("$tchpath\reglimit.tch") /H
endif

 

I have also installed the latest WindowsUpdateAgent.

 

Any advice

Posted

Hi

 

Can you describe your environment?

 

Which version of WSUS?

Core OS and SP Level?

Client machines including SP Level?

Using GPO's?

Using Upstream/Downstream WSUS?

 

Thanks

Sukh

Posted

Server 2003 (sp2)

WSUS v3.2.7600.226 (sp2)

XP sp3

win7

Not using gpo to control wsus apart from a gpo to get the update service to pick up from local server and not ms. Computers are assigned within WSUS.

No upstream/downstream servers.

 

WSUS is running fine on about 60% of the computers.

Posted (edited)

Hi

 

Can you find a problem machine and run wuauclt.exe /detectnow and locate the WindowsUpdate.log file and post here or PM me?

 

 

Thanks

Sukh

Edited by sukh
Posted
Sounds like a SID issue to me... I remember years ago I had the same issue and I found out the machines had the same SID (where built from ghost and not sysprep'ed)
Posted
Sounds like a SID issue to me

 

Some of the machines came from Stone and now I think about it Stone do clone before sending out to schools. I will see which other machines are causing an issue tomorrow.

Posted

The odd computer I've had which refuses to get updates I've had great success in tracking down the problem by reinstalling the Windows Update Agent from How to obtain the latest version of the Windows Update Agent to help manage updates on a computer

 

If it says it's already installed, run it with the switch /wuforce and it'll force the install over the top. If it fails for any reason atleast it will give you one (the common one I've had is the Windows Installer being out of date).

 

After it's install, reboot and then run a wuauclt /detectnow and you should be off (has sometimes still taken 20 mins or so to pick up updates properly)

Posted

Windowsupdate.log after /detect on windows7 client

 

2011-03-09 08:34:32:073 1012 8e0 DnldMgr Error 0x80072ee2 occurred while downloading update; notifying dependent calls.

2011-03-09 08:35:14:101 1012 4a8 DnldMgr Error 0x80072ee2 occurred while downloading update; notifying dependent calls.

2011-03-09 08:35:56:164 1012 4a8 DnldMgr Error 0x80072ee2 occurred while downloading update; notifying dependent calls.

2011-03-09 08:36:00:501 1012 1108 AU Triggering AU detection through DetectNow API

2011-03-09 08:36:00:501 1012 1108 AU Triggering Online detection (non-interactive)

2011-03-09 08:36:00:501 1012 914 AU #############

2011-03-09 08:36:00:501 1012 914 AU ## START ## AU: Search for updates

2011-03-09 08:36:00:501 1012 914 AU #########

2011-03-09 08:36:00:548 1012 914 AU <<## SUBMITTED ## AU: Search for updates [CallId = {07C7EB91-29A4-4E76-828A-43D65EF70E6B}]

2011-03-09 08:36:00:548 1012 5b0 Agent *************

2011-03-09 08:36:00:548 1012 5b0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]

2011-03-09 08:36:00:548 1012 5b0 Agent *********

2011-03-09 08:36:00:548 1012 5b0 Agent * Online = Yes; Ignore download priority = No

2011-03-09 08:36:00:548 1012 5b0 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"

2011-03-09 08:36:00:548 1012 5b0 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed

2011-03-09 08:36:00:548 1012 5b0 Agent * Search Scope = {Machine}

2011-03-09 08:36:00:548 1012 5b0 Setup Checking for agent SelfUpdate

2011-03-09 08:36:00:564 1012 5b0 Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226

2011-03-09 08:36:00:564 1012 5b0 Misc Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\wuident.cab:

2011-03-09 08:36:00:673 1012 5b0 Misc Microsoft signed: Yes

2011-03-09 08:36:00:673 1012 5b0 Misc Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\wuident.cab:

2011-03-09 08:36:00:689 1012 5b0 Misc Microsoft signed: Yes

2011-03-09 08:36:00:704 1012 5b0 Misc Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:

2011-03-09 08:36:00:704 1012 5b0 Misc Microsoft signed: Yes

2011-03-09 08:36:00:720 1012 5b0 Misc Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:

2011-03-09 08:36:00:720 1012 5b0 Misc Microsoft signed: Yes

2011-03-09 08:36:00:954 1012 5b0 Setup Determining whether a new setup handler needs to be downloaded

2011-03-09 08:36:00:954 1012 5b0 Misc Validating signature for C:\windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:

2011-03-09 08:36:00:969 1012 5b0 Misc Microsoft signed: Yes

2011-03-09 08:36:00:969 1012 5b0 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226

2011-03-09 08:36:00:969 1012 5b0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"

2011-03-09 08:36:02:202 1012 5b0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" is already installed.

2011-03-09 08:36:02:202 1012 5b0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226"

2011-03-09 08:36:02:217 1012 5b0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226" is already installed.

2011-03-09 08:36:02:217 1012 5b0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226"

2011-03-09 08:36:02:249 1012 5b0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226" is already installed.

2011-03-09 08:36:02:249 1012 5b0 Setup SelfUpdate check completed. SelfUpdate is NOT required.

2011-03-09 08:36:04:152 1012 5b0 PT +++++++++++ PT: Synchronizing server updates +++++++++++

2011-03-09 08:36:04:152 1012 5b0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://school-srv1/ClientWebService/client.asmx

2011-03-09 08:36:14:526 1012 5b0 Agent * Found 0 updates and 58 categories in search; evaluated appl. rules of 469 out of 1053 deployed entities

2011-03-09 08:36:14:557 1012 5b0 Agent *********

2011-03-09 08:36:14:557 1012 5b0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]

2011-03-09 08:36:14:557 1012 5b0 Agent *************

2011-03-09 08:36:14:588 1012 1070 AU >>## RESUMED ## AU: Search for updates [CallId = {07C7EB91-29A4-4E76-828A-43D65EF70E6B}]

2011-03-09 08:36:14:588 1012 1070 AU # 0 updates detected

2011-03-09 08:36:14:588 1012 1070 AU #########

2011-03-09 08:36:14:588 1012 1070 AU ## END ## AU: Search for updates [CallId = {07C7EB91-29A4-4E76-828A-43D65EF70E6B}]

2011-03-09 08:36:14:588 1012 1070 AU #############

2011-03-09 08:36:14:588 1012 1070 AU Successfully wrote event for AU health state:0

2011-03-09 08:36:14:588 1012 1070 AU Featured notifications is disabled.

2011-03-09 08:36:14:588 1012 1070 AU AU setting next detection timeout to 2011-03-09 09:31:46

2011-03-09 08:36:14:588 1012 1070 AU Setting AU scheduled install time to 2011-03-09 10:00:00

2011-03-09 08:36:14:588 1012 1070 AU Successfully wrote event for AU health state:0

2011-03-09 08:36:14:588 1012 1070 AU Successfully wrote event for AU health state:0

2011-03-09 08:36:19:565 1012 5b0 Report REPORT EVENT: {A4C7A8B4-7C08-4684-A2FC-EFD1795C7F14} 2011-03-09 08:36:14:557-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.

2011-03-09 08:36:19:565 1012 5b0 Report REPORT EVENT: {E7F692BC-B3AD-41CF-ACF0-74B6E622A448} 2011-03-09 08:36:14:557-0000 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.

2011-03-09 08:36:19:565 1012 5b0 Report CWERReporter finishing event handling. (00000000)

2011-03-09 08:36:38:364 1012 ed4 DnldMgr Error 0x80072ee2 occurred while downloading update; notifying dependent calls.

Posted

We've had the same issue with our systems - that was a SID issue because they had been ghosted without being sysprepped first.

 

Apparently, WSUS still works with those machines, it's just that WSUS Console only gets one entry per SID - so if multiple machines have the same SID, only one of them will appear in the list.

 

HTH

Posted
OK that probably sorts out the xp machines but I thought (probably wrong) that Win7 used a new sid system based on user sids. Also newsid will not work on win7. That would leave me with sysprep. Can sysprep run on a live machine without changing any user accounts/settings?
Posted

Hi

 

Can you post the exact command as you have typed it, maybe save the contents of the cmd window.

 

To confirm/rule out the duplicate SID, can you continue with the steps ignoring NTDSUTIL command.

 

Thanks

Sukh

Posted

Hello sukh,

As requested I have pm you the cmd output window.

 

The code on the 'Delete Duplicate SUS Client IDs' page is the same as the code I have used in my first post, although I did run this one just in case.

 

Any other ideas?

Posted

Hi

 

Please use PsGetSid and download PSGetSid. Just run the command and note down the computer SID.

 

The run sysprep and select (OOBE) with the generalise option. After a reboot, you may have to enter some configs again suvch as keyboard layout etc..

 

After the reboot, run PSGetSid again and confirm you have a different Computer SID. Once confirmed, then go back to previous step and run the script, then run wuauclt /detectnow.

 

Thanks

Sukh

Posted

Sukh, thanks for all your time and help. All working on the W7 test box. Just need to do the same on other machines around the school. One odd thing to note, after doing the sysprep and running the script both the old & new computer name got listed in WSUS.

 

Thanks again.

Posted
I'm not fully convinced by the SID/sysprep argument. I had problems with WSUS, the desktop machines I had cloned didn't show up until I changed their SIDs, but I also had a set of 30 netbooks, again, cloned, that all showed themselves in the WSUS list first time, no problems.
Posted

Hi not sure if you still have issue - however I would try running this batchfile on a client machine with the wsus issue - as I feel problem could be related to the machines susclientid.

 

rem Fixes problem with client machines not showing up on the server due to imaging method

 

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...