/build/static/layout/Breadcrumb_cap_w.png

Windows 10 Feature Updates

Hello,

Anyone using the K1000/K2000 to deploy Windows 10 feature updates? If so, could you give me some points on how you have it implemented? 

Thank you.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Christian1616 3 years ago
White Belt
0
Hi,

I packed the installation files in a .zip file and connected it to the build in the Software Inventory (not the Software-catalouge). 
Then I created a Softwaredeployment for this build. The Installationoption is set to overwrite the default installation and has the following commands: "setup.exe /auto upgrade /quiet".
Check the box, to not put msiexec.exe first.

I don't have a plan running to upgrade it automatically. I manually start this deployment, when a new build is released, to upgrade all clients that are the newest build -2. 

Comments:
  • So you zip the iso for the version such as 1709 into the software inventory and script it out? We currently use WSUS, I wanted to see if the K1000 would make it easier to manage. Thanks. - agahlbeck 3 years ago
  • Also the file size is about 4gb and I believe there is a limit on upload in the K1000. - agahlbeck 3 years ago
    • Yes, I mount the iso of the latest build and then I zip those files.I never used WSUS for this, but once I had created the Softwaredeployment, it was easy, to upgrade the clients. However, I don't have the comparison. Regarding the upload limit, you move the file to a location in the explorer, to have it available in KACE. I don't remember the configuration, maybe it's set by default. You have to type the IP or DNS Name of your K1000 into the Windows Explorer and open the folder "clientdrop" with a administrator login. When you copy your files to this location (\\yourk1000\clientdrop) you can access them in the webinterface of the k1000 as well. - Christian1616 3 years ago
Posted by: mcnaugha 3 years ago
Senior Yellow Belt
0
Do you mean Features On-Demand (FoD)? I used to slipstream (using NTLite) in the bits we needed (.NET 3.5) but we no longer require them and I've stopped doing it. It worked well when we did.
 
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