/build/static/layout/Breadcrumb_cap_w.png

Provisioning fails after version 8 upgrade

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.

1 Comment   [ + ] Show comment
  • KACE removed the option to uncheck the box "Use WinRM" under provisioning detail page. Thanks. Now it really doesnt work. - lama01 2 years ago

Answers (2)

Answer Summary:
Posted by: AbhayR 3 years ago
Red Belt
1

Top Answer

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.

Comments:
  • KACE removed the box to uncheck the "Use WinRM" under provisioning detail page - lama01 2 years ago
Posted by: AbhayR 3 years ago
Red Belt
0
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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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