I'm doing some pilot testing on KACE patching, and though, (hopefully) the plan is to deploy patches at night, I need some machines where I can deploy patches during the day, to see the impact in general, as usual, you're the guinea pigs :)
I have been doing some tests on accessible VMs with not much RAM in them (about 512Mb), and there hasn't been much impact, even though the CPU usage is noticeable.
The good news, is that all the CPU usage is from the patch installation itself, and non of it is from the KACE agent causing slowness. So, by this, I mean that the patching process, during the day, through the KACE box would be no different than triggering the Microsoft Updates from within Windows (or GPO, or Deepfreeze)
Depending on the number of patches needed on your computer, you may be asked for multiple reboots. Please treat it as you would during a normal day. If you're too busy to reboot, then, go ahead and snooze it. (I have the reminder to reboot set to pop up only twice a day -- every 4 hours), and the snooze button will timeout in 5 minutes, and will NOT force your machine to reboot if you don't hit anything.
For night schedules for the reboots, the snooze button may not be there at all, and will definitely force the reboot.
Please watch out for any really unusual behavior from your machine. (aside from the KACE notification asking for a reboot -- which you should probably get used to :) )
By the end of the process, and the required reboots, all your Windows OS security criticals should be taken care of.
This particular push will not include Flash, Java, or Adobe updates. It will also not install a service pack if your computer needs that. (This info is just so that you know what to look for, in case you're curious)
The target group for this pilot is only those of you whose machines fall in the 10.40.52.1-254 IP range. If you had never given me your Mac address, then you will not be affected by this pilot. (and will also potentially, not have the access you need as an admin later on).
For any questions, please talk to me.
I have been doing some tests on accessible VMs with not much RAM in them (about 512Mb), and there hasn't been much impact, even though the CPU usage is noticeable.
The good news, is that all the CPU usage is from the patch installation itself, and non of it is from the KACE agent causing slowness. So, by this, I mean that the patching process, during the day, through the KACE box would be no different than triggering the Microsoft Updates from within Windows (or GPO, or Deepfreeze)
Depending on the number of patches needed on your computer, you may be asked for multiple reboots. Please treat it as you would during a normal day. If you're too busy to reboot, then, go ahead and snooze it. (I have the reminder to reboot set to pop up only twice a day -- every 4 hours), and the snooze button will timeout in 5 minutes, and will NOT force your machine to reboot if you don't hit anything.
For night schedules for the reboots, the snooze button may not be there at all, and will definitely force the reboot.
Please watch out for any really unusual behavior from your machine. (aside from the KACE notification asking for a reboot -- which you should probably get used to :) )
By the end of the process, and the required reboots, all your Windows OS security criticals should be taken care of.
This particular push will not include Flash, Java, or Adobe updates. It will also not install a service pack if your computer needs that. (This info is just so that you know what to look for, in case you're curious)
The target group for this pilot is only those of you whose machines fall in the 10.40.52.1-254 IP range. If you had never given me your Mac address, then you will not be affected by this pilot. (and will also potentially, not have the access you need as an admin later on).
For any questions, please talk to me.
No comments:
Post a Comment
Please make your comment. (GMK)
Note: Only a member of this blog may post a comment.