Which is a non re-occuring MW a long time in the past. One suggestion thought up was to create a "bogus" maintenance window (say on the "All Systems" collection or a duplicate of it) Solution (so we can mitigate the time and affected number of servers should we have an accidental deployment). Obviously we are quite aware of the impact we could have of accidently missing the MW off the "Normal" server collections, or accidently targetting the "Delegated" servers and have looked into methodologies for a "Big Red Stop Button" We create also an "available" deployment which we point to "All Systems" which means any server at any time "Delegated" servers which have to be patched manually by the respective application owners.
One which is the collection our "Required" security update deployment is targetted to.Ģ. "Normal" servers where our central CMDB holds a weekly maintenance window which we create a unique collection with this time/date on it per machine, and use the "Includes Collection" methodology to add this collection to a central Our monthly patching strategy consists of two types of servers:ġ. Clients are hosted and managed within a different SCCM hiearchy. In my company, we have an unique situation whereby we manage a single SCCM environment for Windows Servers, containing over 6000 windows servers worldwide.
0 kommentar(er)
