Jump to content

Recommended Posts

Posted

Hi folks,

 

I'm switching over from a standalone WSUS server to SCCM and SUP.

 

I've followed a couple of guides and think I understand the setup: I have added SUP to the site, created Software Update Groups, downloaded the updates which I will deploy, and will setup relevant ADRs. I have created device collections to target the necessary PCs.

 

Are there any tips or things to watch out for?

 

We are using the Office 365 apps, so I have enabled updates for that in the SUP and client settings.

I will remove the GPO that's pointing the clients at the old standalone WSUS server.

I'm aware that I need to add Win 1903 and later as a product, otherwise I get no 1903+ updates.

 

Thanks

Posted

The main thing that I would say is that because SCCM clients don’t use WSUS to download their updates (they get them from a DP instead), WSUS doesn’t need to be set to store updates on the WSUS host. Therefore, if you’re still using WSUS outside of a software update point, I would have a separate installation of WSUS to manage the outliers.

 

The other thing to say is that outside of setting things like the Application Pool recycling settings, WSUS should be left well alone and that any setting changes to it should be made through SCCM.

  • Thanks 1

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...