/build/static/layout/Breadcrumb_cap_w.png

kace update agents (how does this work)

  • need some clarification on K1000 update agents
  •  

    we have 5+ domians in our network, i need some clarification on how does UPDATE AGENTS in Provisining option work..

    when we enable the Update Agent Settings in Provisioning it starts to push the agents to all the machines which have old agents, my doubt is which credentials or what kinda credentials does it take when pushing these agents to multiple domains/single domain, we dont supply any credentials when deploying using UPDATE AGENT OPTIONS. we have 5+ domains and each domain having different account and ADMIN credentialsYzMvsS.jpeg

1 Comment   [ + ] Show comment
  • thanks both for your reply, but when i manually install on remote machines, its asking for credentials to install.. when i run the msi installer, it should install without any credentials rite? - rahimpal 9 years ago
    • Just like any other installer it should run with the credentials that you are logged into the computer. If you aren't logged in as administrator then you might get prompted depending on the UAC settings. - chucksteel 9 years ago

Answers (2)

Posted by: chucksteel 9 years ago
Red Belt
0
Since the agent is already installed on the system and running with local credentials it will use those to install the update.
Posted by: SMal.tmcc 9 years ago
Red Belt
0
Update runs like a MI as system via the current installed agent.  If you create provisioning schedules those use credentials.

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