Detecting patches
Hi All,
I am new to Dell Kace, just having a play with things at the moment. How long does it usually take for Kace to complete a detection of patches on a client? i know that it is obviously difficult to tell how long it would take to deploy patches. i have set just the one machine to detect but i would liketo do this to quite a lot of pc's, up to 300 at a time. Will it have a big impact on network bandwidth for both detecting and deploying??
Thanks
I am new to Dell Kace, just having a play with things at the moment. How long does it usually take for Kace to complete a detection of patches on a client? i know that it is obviously difficult to tell how long it would take to deploy patches. i have set just the one machine to detect but i would liketo do this to quite a lot of pc's, up to 300 at a time. Will it have a big impact on network bandwidth for both detecting and deploying??
Thanks
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
GillySpy
13 years ago
That is going to vary A LOT. A patch detection checks the machine against certain critiera which might be the existence of a file or reg key. So each detect interaction is fairly quick, but it depends on how many patches are in the label, etc.
(FTR, even if I had a specific answer I would still do the following). I would test how long it takes in your network under the conditions you are going to run it (e.g. after hours? across the LAN? etc) and get a baseline from that.
Another thing that affects a detection is task schedulding. The KBOX will chew through tasks as quickly as it can up the limit of the task throughput (see docs). If Y machines are scheduled the kbox is doing patching (or other tasks) on X machines where X <=Y. The left over machines wait in the queue. This is why one should ALWAYS set the option Suspend pending tasks after N minutes from scheduled start that is available in a patch schedule (e.g. a detect).
This throughput is a good thing for the resources on the kbox and your network. We want to be able to do other things on the kbox so this governor will allow the kbox to allocate a certain amount of capacity to those tasks. With only N running at a given time your network usage by kbox communication will be stretech over time as well.
What I woudl do
(FTR, even if I had a specific answer I would still do the following). I would test how long it takes in your network under the conditions you are going to run it (e.g. after hours? across the LAN? etc) and get a baseline from that.
Another thing that affects a detection is task schedulding. The KBOX will chew through tasks as quickly as it can up the limit of the task throughput (see docs). If Y machines are scheduled the kbox is doing patching (or other tasks) on X machines where X <=Y. The left over machines wait in the queue. This is why one should ALWAYS set the option Suspend pending tasks after N minutes from scheduled start that is available in a patch schedule (e.g. a detect).
This throughput is a good thing for the resources on the kbox and your network. We want to be able to do other things on the kbox so this governor will allow the kbox to allocate a certain amount of capacity to those tasks. With only N running at a given time your network usage by kbox communication will be stretech over time as well.
What I woudl do
Comments:
-
hi GillySpy
how are you doing
i too am new in patching
our Kace environment is divided in to 14 different Ou's
eg: Russells, Barnetts ect............
we have been doing patching (windows sp 1)
the issue i am having is that when i detect and deploy over 2000 pc's in one Ou only ( Russells)
some of my client machines will patch and most of the other will display a message on the client machine ( Dell Kace Updating please wait) and this could take an hour up to the whole day running the update which is frustrating as i get it on most of my machines
your help is highly appreciated
thanks
regards Chuck - burtono 11 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
