Supporting Windows Updates for Windows 10 LTSB
Hello folks,
For Windows 7, we're looking at just downloading and installing the Convienence Updates provided by Microsoft that are effectively rollups. However, Windows 10 doesn't appear to have any mechanism for this.
Running into a bit of a trouble here.
We are a OEM/MSP group that utilize the K1000 to support 1000+ machines out in the field that are machine controllers for robotics. The K1000 has worked out great for us, but we are now looking to have a way of supporting the push/install of Windows Updates on the devices in the field.
For Windows 7, we're looking at just downloading and installing the Convienence Updates provided by Microsoft that are effectively rollups. However, Windows 10 doesn't appear to have any mechanism for this.
From what I'm told about the K1000 and updates, it installs updates one at a time, and reboots if an update requires this. From my understanding, that means if I have 15 updates, and 10 of them require a reboot, KACE will reboot this machine 10 times.
We don't really have the option to just have Windows Updates run nightly, as we need time to test out updates with our current level of software running on the equipment - so we were looking more at having updates performed on a quarterly basis. The fact that KACE could potentially reboot so often on updates would make things difficult on some of the older machines in the field.
Am I correct on my knowledge of how KACE process Windows updates, and if so, does anyone have any suggestions on how I can manage Windows 10 updates?
In my perfect world, a convenience type update for Windows 10 (or even a way to do the major updates, like 1151 and the upcoming anniversary update) would be a major improvement over the current method, which is none.
Any assistance or advice is greatly appreciated. Thanks!
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
JasonEgg
8 years ago
Firstly, I don't know if you would get the restart problem, KACE is usually good about patching everything it can before requiring a reboot. But don't trust me: test test test!
My one idea for managing this is to have a small patch window with timeout settings. So, even if ten restarts will be required, it can process that across ten nights.
