Can't deploy Software Update Group - but can deploy single Software Update

Hi,

I've a very strange problem after i performed a disaster recovery of my site (switched from OS 2008 to OS 2012R2).
I can't deploy Software Update Groups. They arrive at the client, and the client is checking if it needs to be installed, but afterwards nothing happens. (nothing displayed in Software Center)
I can deploy single software updates and they show up in Software Center and get installed without issues.

What i've done:

- reinstalled SUP/WSUS
- deleted SoftwareDistribution Folder
- Installed a new Machine with SUP/WSUS
- Reduced my Software Update Groups to ~30 Updates per group
- Reindex WSUS DB
- Switched to HTTPS and back
- Verified IIS Permissions on VirtualDirectories and Pools
- took another client to test
- modified deadline / scheduling / maintenance window behaviour

Still the same.
I'm still unable to deploy SUG's but single Software Updates.

Any ideas someone?

August 4th, 2015 8:31am

Have you validated that the update package(s) that contain the updates are properly distributed to your DP(s) and that those DPs are within the boundary groups for the clients?
Free Windows Admin Tool Kit Click here and download it now
August 4th, 2015 9:34am

Hi Jason,

yes. I can even deploy a single software update which is contained in the same SUG / Update package.
Only the SUG Deployment does never show up.

August 5th, 2015 7:52am

"Only the SUG Deployment does never show up."

Can you expand on this? The client will never show the update group itself in Software Center, only the updates it contains.

Free Windows Admin Tool Kit Click here and download it now
August 5th, 2015 9:51am

if you deploy a sug with lets say four updates in, are the four updates visible and listed in the software center on the client?
August 5th, 2015 10:56am

"Only the SUG Deployment does never show up."

Can you expand on this? The client will never show the update group itself in Software Center, only the updates it con

Free Windows Admin Tool Kit Click here and download it now
August 6th, 2015 5:33am

If you can reproduce this, then you should open a case with Microsoft Customer Support Services. I can't tell if you are simply missing something, it perhaps you have a policy "stuck" somewhere, or you've uncovered some weird bug -- it's very difficult to troubleshoot this type of thing in the forums.
August 6th, 2015 9:52am

Examine LocationServices.log. You will most likely see that the client is searching for WSUS catalog version 897 (which is the WSUS catalog version state from the time before the server was restored, ymmv), but the catalog version currently is 10 (or to whatever it is set to after the recovery)? Your version numbers will differ for sure... Right?

Free Windows Admin Tool Kit Click here and download it now
August 6th, 2015 10:57am

Hi,

we've done the same thing and run into the same error. Software deployments would work but no updated. Count that I couldn't even deploy a single update up to 30 minutes ago.

Then we found an article elsewhere, I don't remember what it was (stack overflow perhaps?) and we solved it like this:

Go on the old server which we still had and connected to HKLM\software\microsoft\sms\components\sms_wsus_sync_manager

Identify these three keys:

ContentVersion
LastAttemptVersion
SyncToVersion

In our case they were 165, 164 and 165. We went on the new server, set these up to 170 and then restarted SMS_Executive. It didn't work right away so we did perform a reboot but i think if we had patience it might have worked. After about 30/40 minutes and after triggering the correct actions from the client's console that we were testing we got the updates and are currently installing.

Hope it helps.

August 7th, 2015 10:41am

Examine LocationServices.log. You will most likely see that the client is searching for WSUS catalog version 897 (which is the WSUS catalog version state from the time before the server was restored, ymmv), but the catalog version currently is 10 (or to whatever it is set to after the recovery)? Your version numbers will differ for sure...

Free Windows Admin Tool Kit Click here and download it now
August 11th, 2015 10:28am

i checked the LocationServices.log on my clients and i don't see any information regarding a Catalog Version.


Sure?

Don't you see something like

Calling back with the following WSUS locations
WSUS Path='http://SUP:8530', Server='SUP.domain.tld', Version='999'

August 11th, 2015 11:04am

i searched for catalog.. sorry.

yes i do see something:

Calling back with the following WSUS locations LocationServices
WSUS Path='http://SUPSERVER.FQDN.LOCAL:8530', Server='DEBES131.FRITZ.LOCAL', Version='17'

I just created two SUG's
1x with all Office 13 updates from last month: containing 5 Updates
1x with all Win7 Updates from last month: containing 12 Updates

Deployed both to my test client and all updates are shown on my test client.
I disabled the deployment of the 2x SUG's.

If i now deploy one single SUG containing all Win7 + Office 13 Updates from the last 3(!) months - 68 - no updates are shown in software center...

Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 8:46am

And what version of the catalog is displayed on the Monitoring node (SUP sync status)?
August 12th, 2015 9:39am

i searched for catalog.. sorry.

yes i do see something:

Calling back with the following WSUS locations LocationServices
WSUS Path='http://SUPSERVER.FQDN.LOCAL:8530', Server='SUPSERVER.FQDN.LOCAL', Version='17'

I just created two SUG's
1x with all Office 13 updates from last month: containing 5 Updates
1x with all Win7 Updates from last month: containing 12 Updates

Deployed both to my test client and all updates are shown on my test client.
I disabled the deployment of the 2x SUG's.

If i now deploy one single SUG containing all Win7 + Office 13 Updates from the last 3(!) months - 68 - no updates are shown in software center...


  • Edited by gnatkopf 21 hours 43 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 12:43pm

i searched for catalog.. sorry.

yes i do see something:

Calling back with the following WSUS locations LocationServices
WSUS Path='http://SUPSERVER.FQDN.LOCAL:8530', Server='SUPSERVER.FQDN.LOCAL', Version='17'

I just created two SUG's
1x with all Office 13 updates from last month: containing 5 Updates
1x with all Win7 Updates from last month: containing 12 Updates

Deployed both to my test client and all updates are shown on my test client.
I disabled the deployment of the 2x SUG's.

If i now deploy one single SUG containing all Win7 + Office 13 Updates from the last 3(!) months - 68 - no updates are shown in software center...


  • Edited by gnatkopf Wednesday, August 19, 2015 10:07 AM
August 12th, 2015 12:43pm

i searched for catalog.. sorry.

yes i do see something:

Calling back with the following WSUS locations LocationServices
WSUS Path='http://SUPSERVER.FQDN.LOCAL:8530', Server='SUPSERVER.FQDN.LOCAL', Version='17'

I just created two SUG's
1x with all Office 13 updates from last month: containing 5 Updates
1x with all Win7 Updates from last month: containing 12 Updates

Deployed both to my test client and all updates are shown on my test client.
I disabled the deployment of the 2x SUG's.

If i now deploy one single SUG containing all Win7 + Office 13 Updates from the last 3(!) months - 68 - no updates are shown in software center...


  • Edited by gnatkopf Wednesday, August 19, 2015 10:07 AM
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 12:43pm

Same, SUP Catalog Version is 17

August 19th, 2015 6:10am

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Free Windows Admin Tool Kit Click here and download it now
August 29th, 2015 1:15pm

nope... issue is still actual. working with CSS on it. I will update it with an Solution once i got it.

August 30th, 2015 3:59pm

hi

this is the solution:

1. We need to find the highest content version on the site. To do this, run the following query on the top level site in the hierarchy :

select * from CI_UpdateCIs order by MinSourceVersion desc

2. Look at the MinSourceVersion field to find the highest content version of the site. (Lets say the highest value is 1600)

3. On the site where the backup is restored, run the following query to see if the ContentVersion is less than the client's required version

select * from wsusserverlocations 

In my Case the Content Version was 20, should be 220. So adjust it:

  • Stop the SMS_Executive service
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER
  • Change the values of ContentVersion, Synctoversion and lastattemptversion to a value which is higher than the highest content version of the site. (to 220 if the highest value is 219 as per result from the query)
  •  Start the SMS_Executive service and run a sync on the top level site.

Tadaa!

Issue solved.

  • Marked as answer by gnatkopf 1 hour 43 minutes ago
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2015 2:07am

hi

this is the solution:

1. We need to find the highest content version on the site. To do this, run the following query on the top level site in the hierarchy :

select * from CI_UpdateCIs order by MinSourceVersion desc

2. Look at the MinSourceVersion field to find the highest content version of the site. (Lets say the highest value is 1600)

3. On the site where the backup is restored, run the following query to see if the ContentVersion is less than the client's required version

select * from wsusserverlocations 

In my Case the Content Version was 20, should be 220. So adjust it:

  • Stop the SMS_Executive service
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER
  • Change the values of ContentVersion, Synctoversion and lastattemptversion to a value which is higher than the highest content version of the site. (to 220 if the highest value is 219 as per result from the query)
  •  Start the SMS_Executive service and run a sync on the top level site.

Tadaa!

Issue solved.

  • Marked as answer by gnatkopf Wednesday, September 02, 2015 6:06 AM
September 2nd, 2015 6:06am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics