Hello everyone,

I'm new to the pacthing part of the dell product line. It appears that my company is using both WSUS as KBOX patching:
  • Installs are still done using Windows Updates
  • Dell KACE agent prompts me to reboot after installing updates

As you probably know, Windows 10 will treat feature upgrades as patches. This means that new builds of Windows 10 will be released using Windows Update.
I want more control over these feature upgrades (+ also drivers) and would like to use the K1000 as a tool to manage this.

When I look in the catalog in the K1000, I can't seem to find these feature upgrades. Also no Windows 10 drivers can be found.

My question: Is it possible to use the K1000 to install new builds of Windows 10 in a controlled manner? This way, I would be able to communicate this to our end-users before they just click install update and need to wait over one hour to install it. Also if I would like to skip one build, I don't want a possibility that end-users could install it themselves.

Thanks in advance!!



0 Comments   [ + ] Show Comments


Please log in to comment


With the patching engine of the K1000 we have the ability to deploy patches and Software installer patches, which are designed to install complete products as a patch i.e. Adobe Reader. we could assume that updates to Windows 10 that actually upgrade the software will be included as this style of patch, but I am not sure that is the case.

If we therefore assume that any Windows 10 update will be released as a patch, then to capture and control the distribution of those updates we will need to create a label to gather the patches so that they can be deployed in a controlled manner.

So first make sure that your KACE patching Deployments are not marked to deploy all patches on any schedule.

Next go to your Subscriptions and make sure you have Windows 10 marked for Download

When the Windows 10 patches appear, we assume that they will say "Windows 10" in the title or will be marked for the Windows 10 platform, so create a label that groups all of these patches together.

You can now set up a controlled deployment of this patch label, hopefully preventing any isses.
Answered 01/27/2016 by: Hobbsy
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.