Hello Joseph,
What I'm looking for is more in-depth understanding of Server patching with 
SCCM. Trying to improve my processes.

@ Kent I saw that class and I was thinking of that, I have enjoy the other 
classes you taught...great stuff thank you!

All,
I have about 3k servers, I have them broken down into 4 major areas, pilot, 
development, test, and Production. 80% of these are automated patch/reboot 
scenario.
The other 20% is a manual reboot by me of other SME's.

A SharePoint site for two purposes,
1. Every server across the enterprise (as it is built) gets a code identifier 
(patch code) which tells all when it is schedule for patch reboot etc. {this 
lives in our CMDB}
2. Calendar on the SharePoint site shows a visual of patch codes so any SME can 
know when said server patch code is schedule for this process.

Again, trying to make my process better, we have begun to use Orchestrator to 
build out the run books so as to automate the rest of the 20%

I hope this helps you understand the goal~

Thank you all for your comments
Phil
From: [email protected] [mailto:[email protected]] On 
Behalf Of Heaton, Joseph@Wildlife
Sent: Friday, February 24, 2017 07:21 AM
To: [email protected]
Subject: [EXTERNAL] [mssms] RE: Microsoft Server patching training

What exactly are you asking?

Server patching is pretty straight-forward.  Have a test collection, apply the 
patches there first, if everything goes well, deploy to your production 
environment.  We suppress the reboots here, and I do reboots manually, SQL 
boxes first, then web, then apps, etc.  We've historically had issues with apps 
not reconnecting to their databases if we don't reboot in order.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Phil Hanly
Sent: Wednesday, February 22, 2017 5:21 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Microsoft Server patching training

Hello,
What was/in the best training you found for Microsoft Server patching training?

Using SCCM (Current Branch) ~

Thank you,
PhilH







Reply via email to