Yikes... I have a reboot script that I deploy to all my collections for reboots. I'd find another way to automate that so I wouldn't be sitting there for 4 hours for 200+ servers.
From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Friday, February 24, 2017 11:32 AM To: [email protected] Subject: [mssms] RE: Microsoft Server patching training ***This is an EXTERNAL email. Please do not click on a link or open any attachments unless you are confident it is from a trusted source. ________________________________ No. I have a Server 2008 collection, and a Server 2012 collection. The reboots are literally manually done by me after work. I sit at my desk at home, starting at 7:00pm, with the status report from the deployment, and reboot. We're 99% virtualized, so I'll open up the console view for 14 servers at a time (because that's how many I can fit on my monitor and still have the actual view) and have VMWare do the recycle. When the console is back to the login screen, I close that window, open up the next and continue. It typically takes me about 3-4 hours to reboot the 200+ servers. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of HELMS, DAVID C Sent: Friday, February 24, 2017 8:12 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Microsoft Server patching training Do you have your sql boxes, web, and app servers in different collections and then rebooted at different times? How many collections do you have that you have to manually setup like this each month? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Friday, February 24, 2017 10:21 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Microsoft Server patching training ***This is an EXTERNAL email. Please do not click on a link or open any attachments unless you are confident it is from a trusted source. ________________________________ 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
