Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Push updates using SCCM to servers

maxwell.2k19

Member
Messages
8
Reaction score
0
Points
1
Hi experts

i am beginner to SCCM, i have around 100 servers(This is first time we are using SCCM to push updates so i have selected non critical servers), which consists of windows 2016, windows 2012 R2, windows 2008R2. Below procedure i would like to go head please guide me if i am wrong

I will create custom collections for Windows 2016, Windows 2012 R2, Windows 2008 R2

But first I will create one Test Collection(I will put one windows server 2012R2 server in it)
ADR--
I will create ADR and assign it to my TEST collection
Collection: TEST (This Test collection have one windows 2012 R2 Server), will use below settings
1.jpg
search criteria i will use the below as i will not miss any critical updates
2.jpg

Evaluation Schedule i will put second Tuesday

Deployment package:
Create a new deployment package:
Name: Windows Server 2012 R2
Source: \\mysccmserver\Sources\Windows Server2012R2


2. I will create second ADR for Windows Server 2016 but i will use the same collection which i have used earlier TEST (This Test collection have one windows 2012 R2 Server)

in search criteria i will select windows server 2016(same as above but product i will select 2016)

Evaluation Schedule i will put second Tuesday

Deployment package:
Create a new deployment package:
Name: Windows Server 2016
Source: \\mysccmserver\Sources\Windows Server2016


Now i will have two ADR's and two deployment deployment packages one for Windows Server 2016 and Windows Server 2012 R2

From all software updates i will use Manage Searches for Current Node- i will select all critical updates, i will add criteria and select the product(Windows server 2012R2), create software update group and deployment package i will use existing Windows Server 2012R2 and will deploy the updates.
Can i go head with this

What i see is i will have only one ADR for Windows Server 2012 R2 and Windows 2016 and one deployment package for Windows Server 2012 R2 and one for Windows Server 2016.
 
Last edited:
Hi All

Just correct me if i am wrong.
First i will create one ADR for Windows Server 2016, Windows Server 2012 R2, Windows Server 2008R2 and then i will remove the collection for this ADR (i.e from deployment settings), if i remove the collection from the ADR's will the ADR's get updated?
I will go to All Software Updates--With the help of search criteria- i will create a new software update group. let says-TEST, when i right click this software update group- download-i can select existing windows server 2012R2 deployment package.
I want to keep ADRs and deployment packages as simple, i can deploy the updates this month and delete the Software update group and after 2 months i can create another software update group and assign it to existing deployment package.
===================================
What are the important updates requiredfor OS, other than security and critical updates anything else required
can i go with the below search criteria, do i require severity-important
1417488
 

Forum statistics

Threads
7,165
Messages
27,965
Members
18,262
Latest member
ChaseMcFadden

Trending content

Back
Top