/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


GPO Provisioning, does this look right?

11/18/2016 1330 views
Hi everyone. We are attempting to deploy our agent via gpo using the tool provided. We ran the tool successfully, linked the gpo, and saw these registry entries get created on the machine in our test OU. Unfortunately, it is not installing the agent, though. Do these registry keys look correct?



4 Comments   [ + ] Show comments

Comments

  • Did you use the GPO Provisioning Tool to prepare the MSI? https://support.software.dell.com/kb/133776
  • Not sure what you mean by "Prepare" the msi. We did use the tool and selected the msi from the tool. I got the msi from the kace server.

    I will try to attach a screenshot of the folder where the group policy pulls from into the original question, maybe there is something missing?
  • Have you put the "dll files" and the ampagent" in the SYSVOL folder. I believe that is where they are supposed to be on the DC.
  • Hi AK, thanks for the reply. We have the files on a share on our fileserver that everyone has read/execute access to and pointed the GPO provisioning tool to that. In the screenshot above, those are the files that are in that share.

    I have a ticket open with the kace support team and they remoted in to look at everything, but still have not been able to figure out why it is not working yet.

All Answers

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
0
The share needed to have authenticated users with modify permissions instead of domain users.
Answered 12/19/2016 by: piratecalvin
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