Hi Casey,

 

You either do it manually, do some complex thing with multiple collections
and maintenance windows and task sequences with some logic or you do some
orchestration.

I've just done the latter for a SQL Always On cluster (which I might blog
about soon), where I enumerate all the nodes, disable failover and so on,
and then put them into a collection, force the patching, reboot the
machines, check if everything is ok and after that move on to the next
cluster node.

That's all Powershell!

 

ConfigMgr can't really do it on its own.

 

Cheers

David

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Casey Robertson
Sent: Saturday, 22 November 2014 4:26 AM
To: [email protected]
Subject: [mssms] Patching web servers behind F5

 

Morning all,

 

Done lots of patching with SCCM before but not in an environment of lots of
web servers load balanced behind  F5's.  I see an old-ish Orchestrator
integration for F5 to do things like enumerate servers in the pool, take
servers in and out etc.  But in reality, how do you folks handle this in
production environments?  We can't just have the web servers all bouncing at
once and have to take the F5 into account.  

 

Any thoughts, tools or processes you've used would be great.  Right now our
NOC literally uses WSUS and logs into each server individually, removes it
from the F5, patches it, reboots and then adds to F5.take forever.

 

Thanks,

 

Casey Robertson

Systems Engineer

W 619.878.9099

E [email protected]
<mailto:[email protected]> 

 

MINDBODY, Inc.

4051 Broad Street, Suite 220

San Luis Obispo, CA 93401

 

   <http://www.mindbodyonline.com/> 

 

 



Reply via email to