Score:0

Windows patch management infrastructure (expert opinion)

pl flag

Is using WSUS alone sufficient for an organization's patch management, or is it more beneficial to integrate SCCM with WSUS for a comprehensive solution?

cn flag
No, WSUS alone is not sufficient. It may be sufficient for many scenarios of patching Microsoft products. You also need to have a solution for measuring what is missing, and typically that gap is addressed by the Config Mgmt solution. SCCM is one, there are other solutions that are more capable.
Score:0
cz flag

WSUS is used to patch Windows servers and machines. For this task alone, yes it is sufficent.

However, SCCM does a lot more, it is primarily used to install software and keep them up to date. So they server different purposes.

Some examples: WSUS patches the Windows OS AND some Microsoft products. However, if you wanted to install Adobe Reader on all machines in the fleet, WSUS won't help you; for this you would need SCCM. Essentially if you want to patch/maintain any other software on machines other than Windows OS patches, you should go with SCCM. If you are new to all of this I'd recommend just WSUS to get you started, then move onto SCCM when you've learnt more.

Source: 20 years as IT admin/architect for large Enterprise companies with over 5000 users.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.