KACE Product Support Question

Provisioning fails after version 8 upgrade

04/03/2018 3245 views
I usually will uninstall/reinstall an agent that doesn't connect via provisioning. It has always worked in the past with a few exceptions (machine off, fixable things). Now everytime I try to do this I get "NETWORK/Unable to establish a WinRM connection." Every once in awhile I will get "NETWORK/CreateProcessAsUser," but not as much as the WinRM error. I have tried this on multiple machines, even my test machine sitting next to me. All are on the network with Windows 10 Build 1703. Never had this issue until the 8 upgrade. Seems like 8 killed it. Any help would be appreciated.
Answer Summary:
1 Comment   [ + ] Show comment


  • KACE removed the option to uncheck the box "Use WinRM" under provisioning detail page. Thanks. Now it really doesnt work.

Answer Chosen by the Author

In 8.0, K1000 server made provisioning using WinRM as a default method. Hence, if your client systems don't have WinRM enabled by default or the port is blocked, provisioning will fail. To not use WinRM, you may simply uncheck the box "Use WinRM" under provisioning detail page and it will use the old way.
Answered 04/03/2018 by: AbhayR
Red Belt

  • KACE removed the box to uncheck the "Use WinRM" under provisioning detail page

All Answers

As far as the CreateProcessAsUser error is concerned, that happens when the client machine cannot resolve the K1000 webserver name. Please check if the clients can resolve the K1000 DNS name
Answered 04/03/2018 by: AbhayR
Red Belt

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