Hey all,

So I installed the latest Windows 10 build, which is version 1607, build 14393.10. We have made distributions for all the software our colleagues uses, so we simply install the kace agent and let it do its work. With the new build Kace doesn't push the software to the client machine. Scripts however are still succesfully deployed. 

Things i've done so far,

Disabled Windows firewall
Disabled Windows defender
Opend cmd as admin and navigated to Program Files (x86)\Dell\KACE and used the commands runkbot 4 0 and runkbot 6 0
Reinstalled the kace agent. 
Rebooted Kace and did a database check. 

So far i'm clueless on what to do next. I'm reinstalling the client with a earlier build of Windows 10 and try to see if software is being pushed. 

Have you guys experienced anything like this with the latest build of Windows 10?

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


check the amp.conf file and see if your kbox name is short or normal
Answered 08/05/2016 by: SMal.tmcc
Red Belt

  • It's normal. "host=kbox.companyname.nl"
    • it's not the bug I have found then. If the name is short files will not copy to the clients. Have you gone back to the software items the distributions are tied to and check windows 10 in the supported operating systems?
      • I have checked all the windows operating systems. It's Windows 10 Pro 64-bit version, earlier builds have successfully deployed our software.
      • I would submlit a ticket on this. I bet the Anniversary Update added some new security features that is blocking the copying of the files to to programdata area.
      • put the client in debug mode to get more answers by issuing an "amptools debug=true" command on the client workstation

  • Our sysadmin pointed out that with every new Windows 10 build, Kace sees it as a whole new OS. So now we have 3 times Windows 10 Pro x64 OS in the list, with 2 of the 3 OS selected. Therefor the software wasn't being pushed since the latest build of Windows wasn't selected in the list. Shake my head for this stupid mistake :) Anyway thank you for helping me with this matter!
    • On a related note, has anybody found an easy way to update the Supported OS lists? I have a lot of MIs and software in the inventory. It's a huge hassle to go into every item to add the new build.
      • if you have a system with all the software installed on it that the MI push and update to the newest os then force an inventory it will add that OS to all the MI's via the software items
      • you can add that idea to the uservoice if it is not already out there

Please log in to comment