/build/static/layout/Breadcrumb_cap_w.png

patching label

Hi Guys,

have a number of machines that are missing patches. I've looked at the report Machines not compliant by patch and it gives me a list of machine missing what patches but how do I translate that into a machine label that I can use? Is there way to hit only the machines that haven't gotten patched?

Thanks,

Mike

0 Comments   [ + ] Show comments

Answers (3)

Posted by: GillySpy 12 years ago
7th Degree Black Belt
0
Why would you want to? The kbox will not deploy patches to machines that do not need it -- the machines that were patched will not redo the same patches. Are you trying to super streamline the patching process by adding redundancy into the detect process with labels?
Posted by: ms01ak 12 years ago
10th Degree Black Belt
0
Yes, I have over 3000 plus machines and I don't want to bother all of them in one night. I'm looking for a clean way of determining only the machines that need the patches. Plus if I did a detect on all the machines I think it would cause network/kbox performance issues.
Posted by: GillySpy 12 years ago
7th Degree Black Belt
0
You won't cause a performance issue because of built-in scheduling:
see http://itninja.com/question/recommended-number-of-machines-per-patch-schedule?&mpage=1&key=throughput&#86550

Only machines that need the patch would get it. The others would pass and move on. If you have already done a detect then consider just a deploy schedule.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ