/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Update Kace Agent with GPO

02/11/2015 3574 views
What is the best method do update agents from 6.2.1020 to 1025 with GPO and not using provisioning?
0 Comments   [ + ] Show comments

Comments

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

All Answers

0
If you are updating from one version to another you shouldn't have to use GPO. You can do that under Settings > Provisioning > Update Agents (link)

This is where you upload a new version of the agent (bottom of page) and then using the top portion of the page, enable the update and tell the system who you want to update. (all devices, label or select a few machines)

The systems will update themselves on their next inventory cycle, if they were selected for the update. 
Answered 02/16/2015 by: nshah
Red Belt

0
Use this GPO tool:
https://support.software.dell.com/k1000-systems-management-appliance/kb/133776
You can get it here:
https://support.software.dell.com/download-install-detail/5717701?prodjid=1-DCAQNA
Answered 02/11/2015 by: Hrkljus
Orange Belt

  • I used this tool for the original deployment, buy when I changed the package to the new agent, the new agent is not installed.
    • Same thing for me... If someone have a solution...
0
I get a copy of the new agent, modify the language (to English), append the .msi to use my K1000 FQDN, and deploy via GPO. That catches the new machines. I do that after letting the K1000 update my existing agents. As machines check-in they are updated automatically via the K1000.
Answered 02/12/2015 by: rockhead44
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