Manual v11 Agent Install Using Tokens
Is there any way to bypass creating a token to install the v11 Agent manually? Right now I have to create a token to enter into the install prompt because it wont install without entering a token. I would think you can bypass this and the agent goes into quarantine until an Admin approves the Agent?
1 Comment
[ + ] Show comment
-
We have done what you suggest and it works for us. It only works if you allow legacy agents to connect. That was a setting when we upgraded to 11 and we left it open because we were pushing the v10 agent with GPO at the time and it allowed us time to work on the agent deployment after the sma upgrade to 11 with no legacy issues. - EFCNinja 3 years ago
Answers (1)
Answer Summary:
Please log in to answer
Posted by:
Nico_K
4 years ago
Top Answer
no, there is no way to bypass the token.
You can enter a "virtual" token, but there needs to be one.
You have the opportunity to give the token also with the name of the agent file.
ampagent-11.0.119-x86_SMANAME+TOKEN.msi (or deb or whatever your platform is)
or as argument: ampagent.msi HOST=SMANAME TOKEN=TOKEN
Comments:
-
I'm trying to find the equivalent Mac installer arguments. I don't think I've ever gotten it to work by adding server name in the filename like on Windows, instead I had to have a script that would edit/create the amp.conf file. Has this changed in 11.0? Or is there a line to add in the conf file for the agent token? - jtremblay 4 years ago
-
So this is what I had for our mac Kace deployment,
export KACE_SERVER=yourserver
/usr/sbin/installer -pkg /path to file/AMPAgent.pkg -target /
For the new token part I added
export KACE_TOKEN=mytoken - th3v01c3s 3 years ago
