/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Deploying Kace Agent 7.1 using GPO Provisionning Tool

06/27/2017 2707 views
Hi,

I am trying to create a GPO to deploy the Kace agent. The GPO is correctly applied (checked with gpresult and presence of the registry keys) but the agent is not installed.

The GPO tool report that the kace server is inaccessible although it is. I can access the web interface from the DC as well as access the samba share.

There are no error in event viewer.

The domain controller is a Windows Server 2012 R2 essential and the Kace GPO tool is executed on it.
The client i use to troobleshoot is a Windows Server 2012R2 standard.
The msi is on a public share on the network and the K1000 server is off site but correctly accessible

Manually executing the msi does work correctly.

Is there some gotcha's in this procedure that i am missing ?

Thanks.

Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • We renamed our MSI file to include the server address. We seem to have more success with it.

    So instead of the file named ampagent-7.1.62-x86.msi, it is named ampagent-7.1.62-x86_MYKACESERVER.Company.COM.msi. we associated that with the GPO and set it to assigned and it seems to be working great.
    • Hi,
      Thanks for you reply.
      The file is already renamed with the kace server address. I also tried to add the .msi as a software package to the GPO as assigned but, same issue.
      • Do you have you GPO set as Computer or User based? We do computer.

        Anther thing that might help is we deploy DNS suffixes that include our domain to each joined PC.

Answer Chosen by the Author

0
 I managed to get it to work.
2 main things i changed was :
- Use a share located on the DC instead of an other fileserver (centos based but still correctly accessible, and joined to the domain)
- Use the full hostname (with domain suffixe) in the UNC share path

To do this i had to re-create the gpo using the Kace GPO Tool . When i executed the GPupdate /force in a cmd, it did not work, but executing in a cmd as admin did work directly, no reboot required.
Answered 06/28/2017 by: Uniwan Etienne
White 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