/build/static/layout/Breadcrumb_cap_w.png
11/20/2018 194 views

I have four new PC's that I deployed windows to.  KACE has yet to pick up the new PC's so I can distribute software from my catalog to them.  I have done a force inventory and they have been connected and running for about 16 hours now.  Is there a way to get KACE to pick up the new PC's faster?

2 Comments   [ + ] Show comments

Comments

  • Do you use the KACE SDA to deploy windows? Also how do you deploy the agent? Through Provisioning or GPO?
  • Yes we do use the KACE SDA to deply windows. We boot into KACE using a USB script. I believe it is through provisioning and not GPO.

All Answers

1

For deploying using the SDA why don't you just add the KACE Agent as a Post Install task?

Library > Post Install > Choose Action - Add KACE SMA Agent Installer. Upload your agent and change the command line to be your host name. 

msiexec /i ampagent-5.5.25198-x86.msi HOST=your.kace.server.com /qn

For getting the agent out in general, I'd advise doing it through GPO using the GPO Provisioning tool provided by quest. 

https://support.quest.com/kb/217592/group-policy-object-gpo-provisioning-wizard-tool-step-by-step

Answered 11/20/2018 by: Ziggi
Yellow Belt

  • Which I did for future images, but it was overlooked on the initial installs. So the first four machines that were imaged are needing it pushed out. But every machine there after will have it in the post install. Thanks Ziggi.
    • Oh right, I understand now ;). I would advise just setting up the GPO then and those machines will get it after GPUpdate. It should be quicker. Hope it helps. If you get stuck with it, drop me a message.
      • Thank you, I'll see what I can figure out. :)
    • Dustin, Go to Provisioning > Provision Agents > Create a new Install and Select the IP Address of the Machines, Make sure the credential is correct. I just tested and it ran almost instantly. You can also check as well under your provisioning schedules the log, i'm sure it will show your errors.
      • Thanks Ziggi, for some reason the provisioning failed on step 3. But I was able to manually move the files from kace server to the PC and install it, at which point kace picked it up almost immediately...