Jump to content


Chris404

Surface Drivers can not be supported in this hierarchy because some of the SUP are not on Windows Server 2016, resetting SyncCatalogDrivers"

Recommended Posts

Hi guys,

we have a SCCM Server, which has been inplace-upgraded from Server 2012R2 to Server2016 and SCCM Version was updated from 1610 to 1706. We activated the Pre-Release-Feature to get Surface-Updates through WSUS and checked the Box to Receive Surface Driver and Firmware-Updates. Everything is fine with the Server and WSUS, BUT in wsyncmgr.log we get the following Message: "Surface Drivers can not be supported in this hierarchy because some of the SUP are not on Windows Server 2016, resetting SyncCatalogDrivers"

So why does WSUS say this, when the Server has been updated to Server2016? The SUP of SCCM is on the same Server like WSUS-Console.

I also removed the only one SUP and readded it with no luck. In WCM.LOG everything is fine.

wsyncmgr.log says:

Found 1 SUPs

Found active SUP Servername.blabla.local from SCF File.

Surface Drivers can not be supported in this hierarchy because some of the SUP are not on Windows Server 2016, resetting SyncCatalogDrivers

Synchronizing WSUS server Servername.blabla.local

......

sync: Starting WSUS synchronization

Done synchronizing WSUS Server

 

I removed the whole WSUS-Role and readded ist with no luck either...

 

Thanks for a tip

 

Chris

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.