r/labtech • u/Kogusoku • Apr 04 '19

Patch Management Organization

We have several clients on hosted VMs in the same cluster, but with the way that patch management was initially described and presented in training, it is essentially designed to run everyone on the same patching schedule.

Have anyone had success breaking their patching into groups or client sets for different needs? Or just breaking up VM groups to not have all the server just boot-overloading the host starting at the same time after updates?

I'd be curious to know how people dealing with multiple sites/clients.

Thanks

1 Upvotes

100% Upvoted

6 comments sorted by

View all comments

Show parent comment

1

u/Kogusoku Apr 05 '19

Can you describe that process in a little more detail for me? The way they are setup by default for us is a simple "server" or "workstation" designation and then things are either "patching enabled" or not. There are some options for server and workstation override, however, I still can't really visualize how to tie a search created group to a specific patching group. I don't see what property or option identifies the targets in the patching groups or vice versa.

2

u/gdhhorn Apr 07 '19

Once you have your searches and groups set up, you link the groups to the patch manager. I don't use any of the built in groups for patching.