Hi All,

I'm hoping someone out there can help me or provide some additional direction/feedback to aid in our investigations.

We are installing WSUS using Server Manager on Windows Server 2012 Server, the database is on another server with SQL Server 2012 SP1 and has a pre-created contained database in a SQL AO-AG but during the WSUS install, it keeps failing, the exact error message is as per below.

 .... Log File to be added soon ....

When letting Server Manager create the database as opposed to pre-creating it, it works fine therefore implying that it is either the pre-creation or the containment type that is causing it to get upset.

Has anyone seen this before and/or know what the stance is in terms of support with the above as information seems to be somewhat scarce :-(

After March 13th updates to servers I noticed WSUS 3.0 SP2 (on w2k8R2) is no longer able to sync for updates. It actually shows the last successfull attempt on March 13th and then no more (all failed), not really sure what did it.

here is the error in from WSUS console:

TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 400: Bad Request.
at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceProxyInternal(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper, Boolean useCompressionProxy)
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceCompressionProxy(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.RetrieveSubscriptionData()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

in firewall both WSUS related rules are allowed, all clients can connect for updates (over SSL) without trouble, same goes for remote admin consoles (working in plain and SSL mode both).

It sounds like it sends a bad HTTP request (error 400), but why? what am I missing here?

I tried installing KB2734608, but it didn't help in resolving the sync fail problem. it still persists.

just to rule out Firewall issues, I disabled it and it still fails, so re-enabled it back on since it is unrelated.

any ideas?

EDIT:

last server updates installed on March 13th were:

KB2791765

KB2806748

KB2809289

KB2807986

KB890830

Rajnish

Hello,

I have a few Windows Server 2012 servers that are unable to communicate with our WSUS server.  Doug

I One of my customers is running Windows 2008 Small Business Server. Windows Update Contant folders had been correctly moved away from C drive soon after installation of the server (WSUS Content). That folder is about 8 GB big (small network, 8 computers). The susdb.mdf file however, is still on the C drive and is a whopping 15.1 GB big. I believe this is not according to plan. I have done some server cleanup through the specific WSUS interface, but the biggest chunk just hangs. What can I do? None of the suggestions I found have worked.

Kind regards,

Wouter Pinkhof

Wouter Pinkhof PINKH bvba, PC-Hulp.com

Hi All,

I have just inherited some existing issues in my new Sys Admin position, as i have never used WSUS before i thought i would ask you fine people for some input!

All servers are 2008R2, 2 physical servers running Hyper-V and these run 8 Virtual machines, each physical has one domain controller on it.

One of the virtual domain controllers is not taking MS Updates, a few months ago it did then something happened and it changed, so WSUS is not updating it and when i try it manually i am getting Error code: 8000FFFF, the other DC is updating fine

When i check C:Windows windowsupdate

Setup    Downloading setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"

Setup    Downloading setup package WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.cab from http://.local:/selfupdate/WSUS3/x64/Vista

Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.cab:

Misc     Microsoft signed: Yes

ABOVE IS JUST ONE EXAMPLE UPDATE, THERE ARE A FEW

WARNING: LoadLibrary failed for srclient.dll with hr:8007007E
Setup    Staging setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
Setup    WARNING: CBS staging operation failed, error = 0x8000FFFF
Setup    FATAL: Failed to stage setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256", error = 0x8000FFFF
Setup    WARNING: Failed to stage applicable setup packages, error = 0x8000FFFF
Setup    FATAL: Downloading binaries for SelfUpdate failed, err = 0x8000FFFF
Agent      * WARNING: Skipping scan, self-update check returned 0x8000FFFF
Agent      * WARNING: Exit code = 0x8000FFFF

I have also looked at the group policy and when i check the settings, im getting An error has occured while collecting data for administrative templates

namespace 'Microsoft policies........' is already defined as the target namespace for another file in the store

I have also checked the permissions on the C: if the problem server and some sub folders and they do not seem to be a problem!

Any help would be greatly appreciated,

Cheers

Hi,

I have a wsus master running 3.0 SP2 (with KB2720211) running on 2003 Server R2 X64 which services about 40 downstream servers.  4 servers consistently are showing 0% in installed/not applicable.  Please note that the master server was until recently a replica server.  I had run the wsusmigration tool to copy from the old master server and checked settings were the same from the old master.

I have read many threads about similar issues that other people have had and this is what I have tried so far to no avail:

Uninstall wsus on downstream server and reinstalled

Uninstall iis and wsus on downstream server and reinstalled

Reset the pw on the anonymous IUSR_xxxxx account

Added the IUSR_XXX account to the security on \program files\selfupdate with read/execute etc

Uninstalled WSUS on the master server and reinstalled

Uninstalled report viewer and reinstalled on the master server.

Sync's from the downstream to the upstream say they have succeeded but I am seeing an error on the master server event viewer saying the report web service isn't working.  This same error originally was coming up on the downstream server but after reinstalling wsus and iis that has gone. Now, all the other 30+ servers have %'s in that column but they don't seem to have changed much over the last few days.  So, maybe they are bogus too.  I can't figure out what else could be wrong so hoping someone here might have an answer.  Thanks very much.

Hello,

I have read in several locations some troubleshooting steps to take to make sure that a WSUS server instance can download files, including firewall problems, and even this interesting thread where an expired thread cause a downstream server to not properly reconcile it's files to it's DB.

I have several updates that I have approved, but have not downloaded.

I have attempted to perform a reconcile of downloaded files against the DB using `wsusutil.exe reset` and have had no luck.  I am using bitsadmin.exe to monitor the download queue, and nothing is populating.

A good example of this is KB943729; it is approved, not superseded, and I can verify that the file is not located on the drive.

I have also retried downloads of all updates that aren't superseded through the UI ("cancel download"> "retry download").

I see the following error in bitsadmin output, but have concluded that it is irrelevant:

2013-03-13	21:11:42:796	 832	1324	DnldMgr	Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update BD5A51BA-2106-46F1-BC87-347294901FDF is "PerUpdate" regulated and can NOT download. Sequence 1020 vs AcceptRate 0.
2013-03-13	21:11:42:796	 832	1324	DnldMgr	  * Update is not allowed to download due to regulation.
2013-03-13	21:11:42:796	 832	1324	DnldMgr	Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update BD5A51BA-2106-46F1-BC87-347294901FDF is "PerUpdate" regulated and can NOT download. Sequence 1020 vs AcceptRate 0.
2013-03-13	21:11:42:796	 832	1324	DnldMgr	***********  DnldMgr: New download job [UpdateId = {744F9366-C308-44B2-8542-CA31C229179D}.200]  ***********
2013-03-13	21:11:42:796	 832	1324	DnldMgr	Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update 744F9366-C308-44B2-8542-CA31C229179D is "Priority" regulated and can NOT download. Sequence 8249 vs AcceptRate 7828.
2013-03-13	21:11:42:796	 832	1324	DnldMgr	  * Update is not allowed to download due to regulation.
2013-03-13	21:11:42:796	 832	1324	DnldMgr	Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update 744F9366-C308-44B2-8542-CA31C229179D is "Priority" regulated and can NOT download. Sequence 8249 vs AcceptRate 7828.

I will perform a server cleanup now (cleanup: unneeded update files, expired updates, superseded updates), then reattempt `wsusutil.exe reset` again.

What else could be the problem?  What else can I look into?

Thanks,

Matt

[update]

declined expired updates: 0
Declined superseded updates: 102

[update 2]

After allowing WSUS to hang out by itself for the night, it appears to have downloaded any updates that are not superseded.  I verified this by right-clicking on the example target update KB943729> file information> located the filename and patch in the file URI, and located it on the local disk  ..\wsuscontent\WsusContent\e0\E174C41CE3DCBD5C8922D6D1C39DF1BE425A70E0.exe.

I think we're good here.

PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \\WSUS\UpdateServicesPackages\de80c836-6549-40e8-b408-1a525f51ea26\d3624167-2f9d-48e4-99d5-0cdbfb5d9259_1.cab$$<Updates Publisher><Tue Mar 5 22:25:28.431 2013.6><thread=6>
Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.$$<Updates Publisher><Tue Mar 5 22:25:28.435 2013.6><thread=6>
Publish: Background processing completed.$$<Updates Publisher><Tue Mar 5 22:25:28.436 2013.1><thread=1>

Under the category of - I wish it would just bloody well work.

I have uninstalled and resinstalled WSUS 3.0 SP1 and SCUP 2011.

WSUS has the following updates installed on it:

   WinSE368126
   KB2734608
   KB2720211

Server OS is 2007 R2 Stadard, 64-bit OS.

Now updates needed from either Microsoft or itsself.

I have created a new self-signed certificate
I have checked Options/Advanced Add timestop and I've unchecked Add timestamp.
On the SCUP/WSUS server the certificate has been imported in to two trusted areas.

The UpdateServicesPackages share is empty.

SCUP and WSUS are on the same server, and pointing towards SCCM 2012 CU2.

This is becoming very frustrating.

Hi,

we are having an environment having nearly 2000+ wsus clients(XP) . Ot of these many are getting updates successufully from wsus server but not showing up in the report as updated.

Please let me know how to trouble shoot this issue.

Our organization of roughly 2000 endpoints has only recently started rolling out Windows 7 SP1 (KB976932) via WSUS.  To make sure we don't break anything we're rolling it out slowly to one office each week.  Its been a few weeks now and we're nearing the end so I'm running reports, via WSUS, to see what machines were missed, failed, etc.  I can understand a margin of error to some extent, but I feel what I'm seeing is significant enough to warrant a deeper investigation.  What am I seeing?  The WSUS report says ~800 machines need to be updated, but upon further inspection, ~400 of them have SP1.  Why is there such a difference?

The clients are all Windows 7 x86
Server is Windows Server 2003 R2 x64 running WSUS 3.2.7600.226
Although the 'Automatic Updates detection frequency' has been enabled for some time (via GPO), about a month ago I set the interval to '2' hours thinking maybe the numbers I were seeing were just delayed because of that 20% variance.
The WSUS report query configuration is as follows:

• Report View: Detailed
• Report is specifically for Windows SP1 (KB976932)
• Include computers from specific [target] groups (all of our offices; not servers)
• Include computers that have a status of: any
• Include status from replica downstream servers: All replica downstream servers (there are 4)

The status summary tells us that 807 machines (8+610+118) don't have SP1 for whatever reason so we'll need to look into what's going on.  (Note: The numbers used in this posting are fresh, created today, 3/27/13, at the time of writing.)

I save the report as an Excel document, massage the data little so I can create a pivot table for office specific reporting. Then I subtract the 'Installed' number from the 'Grand Total' which gives me 808.

But that number includes:

• Machines with a status of 'Not Applicable', 2 - presumably these assets don't need SP1; maybe wrong OS or system/server in wrong OU?
• Machines with a status of 'Pending Reboot', also 2 - presumably these assets have installed SP1 but haven't rebooted?

So, subtract 4 from the total and I'm at 804.  This gives us a difference of 3 (807-804); less than 1% of our assets - not enough of a difference to warrant a huge investigation.

Now I'm going to check each of the 804 machines that don't have a status of 'Installed' via a basic batch script I slapped together specifically for this:

for %%i in (machine1 machine2 ... machine803 machine804) do (
	set system=%%i

	if exist "\\!system!\c$\windows\system32\cmd.exe" (
		for /F "usebackq tokens=1" %%k in (`wmic /node:!system! os get version ^| find /i "6.1.76"`) do (
			set systemVersion=%%k

			if [!systemVersion!] NEQ [6.1.7601] (
				echo !system! not pached: !systemVersion!
			) else (
				echo !system! pached: !systemVersion!
			)
		)
	) else (
		echo !system! offline
	)
)

Those results are logged to a file so I can import into Excel where I report on machines with SP1, without SP1 and Offline/inaccessible machines.  The results are quite a bit different than what WSUS is reporting.

For instance, referencing the chart above, of the 31 machines in Office o1, 30 are patched, not 7 as WSUS shows.  I worked with our local resource to visit each machine in that office to confirm what my script reported, and the one that's not patched is out the office.  What WSUS is 'seeing' is wildy different, and I'm seeing similar results for other offices.

Up until now I've been using real, current numbers, but because today's manual 'scan' is still running, I don't have fresh numbers.  So for the bullets below I'm using results from a scan I did last week.

• WSUS said 784 machines needed SP1
• 379 actually had SP1
• 108 actually needed SP1
• The rest were inaccessible

Why are the WSUS report results off by so much?

Short of resetting the ID's, I'm not sure what to do.

echo. & echo Stopping Services...
For %%i in (wuauserv) do (
	echo.  Stopping %%i
	net stop %%i >nul
)

echo. & echo Clearing Registry Data
For %%j in (AccountDomainSID PingID SusClientIdValidataion SusClientID) do (
	echo.  Removing %%j
	reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v %%j /f >nul
)

echo. & echo Restarting Services...
For %%i in (wuauserv) do (
	echo.  Starting %%i
	net start %%i >nul
)

echo. & echo Forcing AU Discovery
wuauclt.exe /resetauthorization /detectnow

Hi

I‘ve installed a security update on windows server 2003.

After 8 months I’m unable to locate the installed KB in appwiz.cpl. checked in System and application event, event logs are cleared through GPO.

If I search the KB in widow’s registry I’m locate the KB number only.

However registry displays KB number but it is not telling the KB article installed.

Can we confirm using registry entry that respective article was installed?

Otherwise please help me to generate an installed patch report on a particular server.

We have a WSUS server in the main office (Windows Server 2008 R2 Standard).

We have a branch office with Windows 7 Professional clients and Windows Server 2008 R2 Standard and Enterprise servers, which means these computers are using BITS 4.0 (http://msdn.microsoft.com/en-us/library/bb968799(VS.85).aspx).

To save on disk space, we prefer not to set up a WSUS downstream replica server in the branch office if we can use BITS 4.0 with BranchCache.

Researching WSUS and BITS Versions and Peer Caching and BranchCache and Windows Editions has been confusing. Some questions…

These pages in the BITS section of MSDN all say: “Starting with Windows 7, the BITS 3.0 peer caching model is deprecated. If BITS 4.0 is installed, the BITS 3.0 peer caching model is unavailable.” However, these pages also say: “BITS (4.0) uses the Windows BranchCache for peer caching,” and “Starting with Background Intelligent Transfer Service (BITS) 4.0, the BITS service was extended to allow subnet-level peer caching for downloaded URL data by using Windows BranchCache.”
   http://msdn.microsoft.com/en-us/library/aa362708(v=vs.85).aspx
   http://msdn.microsoft.com/en-us/library/aa964314(v=vs.85).aspx
   http://msdn.microsoft.com/en-us/library/aa964240(v=vs.85).aspx
And this page says: “(BITS 4.0 New Feature) Peer caching now uses Windows BranchCache. This new peer caching model replaces the model used for BITS version 3.0.”
   http://msdn.microsoft.com/en-us/library/aa363167(VS.85).aspx

Okay, fine. BITS 3.0 peer caching is unavailable for Win7/2008 R2, but BITS 4.0 “peer caching” does work by using BranchCache. Got it. So, do we understand correctly that the various “peer caching” group policy settings under Computer Configuration – Policies – Administrative Templates – Network – Background Intelligent Transfer Service have no effect at all for BITS 4.0 clients?
http://msdn.microsoft.com/en-us/library/aa362844(v=vs.85).aspx

Next, the link at the end of this paragraph says: “Windows BranchCache must be enabled on the client through a group policy or local configuration settings.” Okay, fine. We followed the instructions at the second link to enable BranchCache for our Windows 7 clients. Interestingly, the description in the Turn on BranchCache group policy setting (under Computer Configuration – Policies – Administrative Templates – Network – BranchCache) says: “For this policy setting to take effect, you must install the BranchCache feature on the client computer.” However, it seems that the BranchCache feature is already installed by default (although not enabled) on Windows 7, because there’s no option to add BranchCache in Control Panel – Programs and Features – Turn Windows features on or off, and there’s already a BranchCache service on Windows 7. So, does this statement actually not apply to Windows 7 (and only Windows Server 2008 R2)?
   http://msdn.microsoft.com/en-us/library/aa964314(v=vs.85).aspx
   http://technet.microsoft.com/en-us/library/dd637820.aspx

Next, the link below says: “The Windows BranchCache feature is an optional component that must be installed on the server,” and “The server must also enable the Windows BranchCache feature though group policy.” Okay, fine. We followed the instructions at the second link to enable it for our Windows Server 2008 R2 servers. However, we would like one of our servers in the branch office to be the “Hosted Cache” server, and the remaining Win7/2008 R2 computers to just be “clients” that use the Hosted Cache server (for the WSUS updates). So, in this case, does only the Configuring a Web server or a BITS application server to use BranchCache section at this link apply to our Hosted Cache server, meaning no other steps are necessary beyond just installing the BranchCache feature? Or, do we have to go through theConfiguring a file server to use BranchCache section?
Likewise, does the Computer Configuration – Policies - Administrative Templates – Network - Lanman Server - Hash Publication for BranchCache group policy setting apply to us if we’re just looking to use BranchCache for WSUS updates and nothing else?
   http://msdn.microsoft.com/en-us/library/aa964314(v=vs.85).aspx
   http://technet.microsoft.com/en-us/library/dd637785.aspx

In doing more research I believe that, for Hosted Cache mode, the BranchCache feature must be installed onboth the WSUS server at the main site and on a server at the branch office. Is this correct?

Next, we want to configure the BranchCache Hosted Cache mode group policy setting. However, this setting says: “This address must match the Fully Qualified Domain Name (FQDN) of the server specified in the certificate for the BranchCache server's certificate,” and “the certificate root for the BranchCache server's certificate must be in the client computer's trusted root store.” Since our BranchCache clients will only be using BITS for WSUS updates (via HTTP), is it still necessary to install a certificate on the Hosted Cache server? (If Yes, that's too bad, because it really complicates BranchCache deployments, especially when all of the computers are within your Active Directory domain).

Next, there’s the Configure BranchCache for network files group policy setting. Since this setting uses SMB, we’re assuming this does not apply to BranchCache used by BITS clients, and so we don't need to configure it. Is this correct?

So, in Summary: We just want to use BITS with BranchCache for the computers in our branch office to access WSUS updates on a local server that’s acting as a BranchCache Hosted Cache server. And we’d prefer not to have to deal with certificates to make this happen, if possible.

Sorry for the long post, but there’s just no clear, one-stop place that informs us how to configure all of this.

Oh, and is all of the above completely irrelevantfor us since this TechNet page says BranchCache requires the Enterprise Editions of Windows 7 and Windows Server 2008 R2? I sure hope not…   :o)
   http://social.technet.microsoft.com/wiki/contents/articles/2342.branchcache-settings-for-windows-server-2008-r2-windows-7-enterprise-and-windows-7-ultimate.aspx

-Taylorbox

NOTE: I’ve already read these posts:
   http://www.windowsnetworking.com/articles-tutorials/windows-7/Introduction-BranchCache-Part1.html
   http://www.windowsnetworking.com/articles-tutorials/windows-7/Deploying-Hosted-Mode-BranchCache-Server-Part2.html
   http://www.windowsnetworking.com/articles-tutorials/windows-7/Deploying-Hosted-Mode-BranchCache-Server-Part3.html

Hi,

Last week (Wednesday) we were trying to do a export of the metadata from a WSUS instance we have connected to the Internet before we transfered it to a disconnected network. Unfortunitly it was not working and was giving us a 0KB cab file and a 100MB log file.

We decided that we should do a clean up, and instead of running the cleanup wizard, we ran the command wsusutil.exe reset.

On the Thursday, one of our admins tried to use WSUS, and as it was still going with the reset, he restarted the Update Services service and when it came back, it started doing the reset command all over again. We have since left it, and it is now Tuesday (5 days since the services was started again, 6 since the command was run) and it is still going.

Our database is about 6.3GB (On a seperate Database server - SQL 2008 R2), and our WsusContent folder is about 212GB (51,438 files) in size.

We have so many updates, as this data is imported to a number of disconnected systems that contain systems from Server 2000 all the way up to Server 2012, and most of the other Microsoft products. We do decline updates that are superseeded, but that is about all.

Is there anyway we can check on the progress of the reset command, or stop WSUS and then clear the flag that tells it to run again when the service is restarted?

Thanking you in advance.

Byron

I've been all over the forums on this but have yet to find a solution. I have a downstream WSUS server running WSUS version 3.2.7600.226 with 64 clients connected (both Win 7 and Win XP).The server is not in a load balanced cluster, but clients were redirected to another server via Group Policy before this server was in place.

I was getting local WSUS error logs like this:

2013-01-24                    04:00:06:727                596             150c            PT                    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.75.77.8/ClientWebService/client.asmx

2013-01-24                    04:00:06:773                596             150c            PT                  WARNING: Cached cookie has expired or new PID is available

2013-01-24                    04:00:06:773                596             150c            PT                  Initializing simple targeting cookie, clientId = ff2ef028-3216-4ba5-ba37-a0e582f574be, target group = WSUS-BH-283, DNS name = smcd02.corp.uhsinc.biz

2013-01-24                    04:00:06:773                596             150c            PT                    Server URL = http://10.75.77.8/SimpleAuthWebService/SimpleAuth.asmx

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING: SOAP Fault: 0x00012c

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING:     faultstring:Fault occurred

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING:     ErrorCode:ConfigChanged(2)

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING:     Message:(null)

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"

2013-01-24                    04:00:06:805                596             150c            PT                  WARNING:     ID:32fed988-78fb-4734-9930-475c76b4d418

2013-01-24                    04:00:07:023                596             150c            PT                  WARNING: Cached cookie has expired or new PID is available

When I deleted the WSUS object from the WSUS console and reset the SUS ID on the local PC, I'd then get this on the local log:

2013-01-25         07:42:23:258       1164      fe4         AU           # Detection frequency: 6

2013-01-25         07:42:23:258       1164      fe4         AU           # Target group: WSUS-BH-283

2013-01-25         07:42:23:258       1164      fe4         AU          # Approval type: Scheduled (Policy)

2013-01-25         07:42:23:258       1164      fe4         AU           # Scheduled install day/time: Every day at 18:00

2013-01-25         07:42:23:258       1164      fe4         AU           # Auto-install minor updates: Yes (Policy)

2013-01-25         07:42:23:258       1164      fe4         AU           # Will interact with non-admins (Non-admins are elevated (Policy))

2013-01-25         07:42:23:258       1164      fe4         AU         Setting AU scheduled install time to 2013-01-26 02:00:00

2013-01-25         07:42:23:258       1164      fe4         AU         Initializing featured updates

2013-01-25         07:42:23:258       1164      fe4         AU         Found 0 cached featured updates

2013-01-25         07:42:23:258       1164      fe4         AU         WARNING: ISusInternal::CanInstallNow failed, error = 0x80070005

2013-01-25         07:42:23:258       1164      fe4         AU         AU finished delayed initialization

2013-01-25         07:42:23:258       1164      fe4         AU         Triggering AU detection through DetectNow API

2013-01-25         07:42:23:258       1164      fe4         AU         Triggering Online detection (non-interactive)

2013-01-25         07:42:23:289       1164      1d8         Agent   Created new random SusClientId efad077d-cdf7-409e-bf40-d623ac06bf69. Old Id: none.

Thus far I have tried attacking this from the client and server angles:

To recap from the client side I've done:

- I have stopped the AU service, deleted the C:\Windows\SoftwareDistribution folder then restarted the AU service (which recreated the SoftwareDistribution folder) and ran wuauclt /resetauthorization /detectnow
- I have stopped the Windows Management Instrumentation Service, renamed the REPOSITORY to REPOSITORY.OLD in C:\Windows\system32\wbem and restarted the service which recreated the REPOSITORY folder
- I have stopped the AU service, deleted the SUSID from the registry:
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
Reg Delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIdValidation /f
- then restarted AU service and ran wuauclt /resetauthorization /detectnow
- as some blogs indicated a change in local permissions on the C:\ drive I compared the local C:\ drive permissions with a working PC connected to a different WSUS server and saw no difference
- some blogs indicated a services permission issue using a custom account
   - Automatic Update Service, Background Intelligent Transfer Service were both using the Local System account
   - dependent service (on the XP box) Remote Procedure Call was using Network Service account

Clients could then always talk to the WSUS server, update their "Reported" status, and get metadata approvals, but would never download updates (would stay at status "Not Installed" and never move to "Downloaded")

As some blogs indicated an issue with IIS, from the server side:
- I uninstalled the IIS role, all dependent roles and services and WSUS
- I removed all files and local DB's during the WSUS uninstallation
- Rebooted, then again after the IIS removal was complete after that reboot
- reinstalled IIS and WSUS, re-setup the server as a downstream (no SSL no proxy - as before)

Now all clients (Win 7 and Win XP) hit the WSUS server and hang indefinitely in a "Not Yet Reported" status unless I run a wuauclt /resetauthorization /detectnow  command where they will at least register a status, but when they do, same issue as before. Metadata on approvals shows ok, but client does not download any updates.

Wanting to verify the PCs needed updates so while I was on one I had it hit Windows Update via IE. PC needed 9 updates. I was able to successfully download and install one update as a test, then rebooted the PC, so the AU client is working when connected to Windows Update directly.

Then after stopping and starting the service net stop/start wuauserv  and re-registering with  wuauclt /resetauthorization /detectnow
this is how the log looks now:
2013-01-30    06:13:56:312    1108    230    Service    ** START **  Service: Service startup
2013-01-30    06:13:56:312    1108    230    Service    *********
2013-01-30    06:13:56:656    1108    230    Agent      * WU client version 7.6.7600.256
2013-01-30    06:13:56:656    1108    230    Agent      * Base directory: C:\WINDOWS\SoftwareDistribution
2013-01-30    06:13:56:656    1108    230    Agent      * Access type: No proxy
2013-01-30    06:13:56:671    1108    230    Agent      * Network state: Connected
2013-01-30    06:14:05:296    1108    b2c    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
2013-01-30    06:14:05:328    1108    b2c    Agent    ***********  Agent: Initializing global settings cache  ***********
2013-01-30    06:14:05:328    1108    b2c    Agent      * WSUS server: http://10.75.77.8
2013-01-30    06:14:05:328    1108    b2c    Agent      * WSUS status server: http://10.75.77.8
2013-01-30    06:14:05:328    1108    b2c    Agent      * Target group: WSUS-BH-283
2013-01-30    06:14:05:328    1108    b2c    Agent      * Windows Update access disabled: No
2013-01-30    06:14:05:359    1108    b2c    DnldMgr    Download manager restoring 0 downloads
2013-01-30    06:14:05:750    1264    8c0    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0800)  ===========
2013-01-30    06:14:05:750    1264    8c0    Misc      = Process: C:\Program Files\LogMeIn\x86\LogMeIn.exe
2013-01-30    06:14:05:750    1264    8c0    Misc      = Module: C:\WINDOWS\system32\wuapi.dll
2013-01-30    06:14:05:750    1264    8c0    COMAPI    -------------
2013-01-30    06:14:05:750    1264    8c0    COMAPI    -- START --  COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:14:05:796    1264    8c0    COMAPI    ---------
2013-01-30    06:14:05:968    1264    8c0    COMAPI    <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:14:08:203    1108    230    Report    ***********  Report: Initializing static reporting data  ***********
2013-01-30    06:14:08:203    1108    230    Report      * OS Version = 5.1.2600.3.0.65792
2013-01-30    06:14:08:328    1108    230    Report      * Computer Brand = Dell Computer Corporation
2013-01-30    06:14:08:328    1108    230    Report      * Computer Model = Dell DE051                  
2013-01-30    06:14:08:343    1108    230    Report      * Bios Revision = A01
2013-01-30    06:14:08:343    1108    230    Report      * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A01
2013-01-30    06:14:08:343    1108    230    Report      * Bios Release Date = 2006-01-03T00:00:00
2013-01-30    06:14:08:343    1108    230    Report      * Locale ID = 1033
2013-01-30    06:14:08:343    1108    db0    Agent    *************
2013-01-30    06:14:08:343    1108    db0    Agent    ** START **  Agent: Finding updates [CallerId = ]
2013-01-30    06:14:08:343    1108    db0    Agent    *********
2013-01-30    06:14:08:343    1108    db0    Agent      * Online = Yes; Ignore download priority = No
2013-01-30    06:14:08:343    1108    db0    Agent      * Criteria = "IsInstalled = 0 AND IsHidden = 0"
2013-01-30    06:14:08:343    1108    db0    Agent      * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2013-01-30    06:14:08:343    1108    db0    Agent      * Search Scope = {Machine}
2013-01-30    06:14:49:180    1108    230    AU    ###########  AU: Initializing Automatic Updates  ###########
2013-01-30    06:14:49:211    1108    230    AU    AU setting next sqm report timeout to 2013-01-30 14:14:49
2013-01-30    06:15:07:727    1108    230    AU      # WSUS server: http://10.75.77.8
2013-01-30    06:15:07:727    1108    230    AU      # Detection frequency: 6
2013-01-30    06:15:07:774    1108    230    AU      # Target group: WSUS-BH-283
2013-01-30    06:15:07:774    1108    230    AU      # Approval type: Scheduled (Policy)
2013-01-30    06:15:07:774    1108    230    AU      # Scheduled install day/time: Every day at 18:00
2013-01-30    06:15:07:774    1108    230    AU      # Auto-install minor updates: Yes (Policy)
2013-01-30    06:15:07:774    1108    230    AU      # Will interact with non-admins (Non-admins are elevated (Policy))
2013-01-30    06:15:07:976    1108    230    AU    Setting AU scheduled install time to 2013-01-31 02:00:00
2013-01-30    06:15:07:991    1108    230    AU    Initializing featured updates
2013-01-30    06:15:08:053    1108    230    AU    Found 0 cached featured updates
2013-01-30    06:15:08:410    1108    230    AU    AU finished delayed initialization
2013-01-30    06:15:08:504    1108    230    AU    #############
2013-01-30    06:15:08:504    1108    230    AU    ## START ##  AU: Search for updates
2013-01-30    06:15:08:504    1108    230    AU    #########
2013-01-30    06:15:08:566    1108    230    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {B62EA1DA-327C-4B0D-9858-F4E0E80A4661}]
2013-01-30    06:15:08:721    1108    db0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
2013-01-30    06:15:08:721    1108    db0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.75.77.8/ClientWebService/client.asmx
2013-01-30    06:17:37:983    1108    db0    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
2013-01-30    06:17:37:983    1108    db0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.75.77.8/ClientWebService/client.asmx
2013-01-30    06:19:01:376    1108    db0    Agent      * Found 0 updates and 64 categories in search; evaluated appl. rules of 1128 out of 2354 deployed entities
2013-01-30    06:19:05:287    1108    db0    Agent    *********
2013-01-30    06:19:05:287    1108    db0    Agent    **  END  **  Agent: Finding updates [CallerId = ]
2013-01-30    06:19:05:287    1108    db0    Agent    *************
2013-01-30    06:19:05:303    1108    db0    Agent    *************
2013-01-30    06:19:05:303    1108    db0    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-01-30    06:19:05:303    1108    db0    Agent    *********
2013-01-30    06:19:05:303    1108    db0    Agent      * Online = No; Ignore download priority = No
2013-01-30    06:19:05:303    1108    db0    Agent      * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2013-01-30    06:19:05:303    1108    db0    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-01-30    06:19:05:303    1108    db0    Agent      * Search Scope = {Machine}
2013-01-30    06:19:05:380    1264    c50    COMAPI    >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:19:05:380    1264    c50    COMAPI      - Updates found = 0
2013-01-30    06:19:05:380    1264    c50    COMAPI    ---------
2013-01-30    06:19:05:380    1264    c50    COMAPI    --  END  --  COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:19:05:380    1264    c50    COMAPI    -------------
2013-01-30    06:19:11:123    1264    8c0    COMAPI    -------------
2013-01-30    06:19:11:123    1264    8c0    COMAPI    -- START --  COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:19:11:154    1264    8c0    COMAPI    ---------
2013-01-30    06:19:11:341    1264    8c0    COMAPI    <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:19:17:950    1108    db0    Agent      * Found 0 updates and 64 categories in search; evaluated appl. rules of 248 out of 2354 deployed entities
2013-01-30    06:19:22:065    1108    db0    Agent    *********
2013-01-30    06:19:22:065    1108    db0    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-01-30    06:19:22:065    1108    db0    Agent    *************
2013-01-30    06:19:22:096    1108    9c0    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {B62EA1DA-327C-4B0D-9858-F4E0E80A4661}]
2013-01-30    06:19:22:096    1108    db0    Agent    *************
2013-01-30    06:19:22:096    1108    db0    Agent    ** START **  Agent: Finding updates [CallerId = ]
2013-01-30    06:19:22:096    1108    db0    Agent    *********
2013-01-30    06:19:22:096    1108    db0    Agent      * Online = Yes; Ignore download priority = No
2013-01-30    06:19:22:096    1108    db0    Agent      * Criteria = "IsInstalled = 0 AND IsHidden = 0"
2013-01-30    06:19:22:096    1108    db0    Agent      * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2013-01-30    06:19:22:096    1108    db0    Agent      * Search Scope = {Machine}
2013-01-30    06:19:22:096    1108    9c0    AU      # 0 updates detected
2013-01-30    06:19:22:127    1108    9c0    AU    #########
2013-01-30    06:19:22:127    1108    9c0    AU    ##  END  ##  AU: Search for updates [CallId = {B62EA1DA-327C-4B0D-9858-F4E0E80A4661}]
2013-01-30    06:19:22:127    1108    9c0    AU    #############
2013-01-30    06:19:22:127    1108    9c0    AU    Featured notifications is disabled.
2013-01-30    06:19:22:127    1108    9c0    AU    Setting AU scheduled install time to 2013-01-31 02:00:00
2013-01-30    06:19:24:060    1108    db0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
2013-01-30    06:19:24:060    1108    db0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.75.77.8/ClientWebService/client.asmx
2013-01-30    06:19:49:358    1108    db0    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
2013-01-30    06:19:49:358    1108    db0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.75.77.8/ClientWebService/client.asmx
2013-01-30    06:19:52:040    1108    db0    Agent      * Found 0 updates and 64 categories in search; evaluated appl. rules of 1128 out of 2354 deployed entities
2013-01-30    06:19:52:055    1108    db0    Agent    *********
2013-01-30    06:19:52:055    1108    db0    Agent    **  END  **  Agent: Finding updates [CallerId = ]
2013-01-30    06:19:52:055    1108    db0    Agent    *************
2013-01-30    06:19:52:102    1264    9b8    COMAPI    >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:19:52:102    1264    9b8    COMAPI      - Updates found = 0
2013-01-30    06:19:52:102    1264    9b8    COMAPI    ---------
2013-01-30    06:19:52:102    1264    9b8    COMAPI    --  END  --  COMAPI: Search [ClientId = <NULL>]
2013-01-30    06:19:52:102    1264    9b8    COMAPI    -------------
2013-01-30    06:19:52:523    1108    db0    Report    REPORT EVENT: {A8F91037-C426-46F1-88BC-66F4C2A1CC34}    2013-01-30 06:15:08:053-0800    1   202    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Content Install    Reboot completed.
2013-01-30    06:19:52:570    1108    db0    Report    REPORT EVENT: {A2D0D939-D68D-4E11-A548-56B3D6084738}    2013-01-30 06:19:05:194-0800    1   147    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
2013-01-30    06:19:52:570    1108    db0    Report    REPORT EVENT: {5E052410-7766-4F15-AF6E-F0342D680532}    2013-01-30 06:19:05:287-0800    1   156    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Pre-Deployment Check    Reporting client status.
2013-01-30    06:19:57:059    1108    db0    Report    REPORT EVENT: {33FE34C6-1B74-4306-9F56-DDEF64B2060A}    2013-01-30 06:19:52:055-0800    1   147    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
2013-01-30    06:19:57:074    1108    db0    Report    REPORT EVENT: {9E7CC8EE-F9B2-4A00-8438-6502AB3079DF}    2013-01-30 06:19:52:055-0800    1   156    101    {00000000-0000-0000-0000-000000000000}    0    0        Success    Pre-Deployment Check    Reporting client status.
2013-01-30    06:32:40:415    1108    db0    Report    Uploading 5 events using cached cookie, reporting URL = http://10.75.77.8/ReportingWebService/ReportingWebService.asmx
2013-01-30    06:32:40:461    1108    db0    Report    Reporter successfully uploaded 5 events.

The WSUS client now seems to think it needs zero updates when talking to the WSUS server. What gives?

Having looked at 15 or 16 blogs on this subject over the last week or so and having done everything I can think of from a client and server side - I am at a loss to understand where issue lies. Can anyone help?

Hello,

How can I export a list of computers and their respective groups from WSUS? I can get a report of all computers but their groups are not listed in the report.  Thank you.