Return
-
Title
How to redirect the Agent to another KACE SMA -
Description
How to redirect the Client to another KACE SMA -
Cause
There are scenarios when needs to redirect the KACE SMA clients from "KBOX A" to now check in to "KBOX B" server.For more information about "AMPTOOLS.EXE" Command Switches, see the reference here. -
Resolution
To achieve this goal one of the client components "AMPTOOLS.EXE" can be used along with the script created on the "KBOX A" server.Please Note:- Script's execution is silent and a system reboot is not required;
- Replacing the "K1B.com" with the hostname of "KBOX B";
KACE Agent 13.2 or below:- C:\Program Files (x86)\Quest\KACE\AMPTools.exe resetconf host=K1B.com token=agent_token
KACE Agent 14.0 or newer:- C:\Program Files\Quest\KACE\AMPTools.exe resetconf host=K1B.com token=agent_token
Mac OS X:- /Library/Application\ Support/Quest/KACE/bin/amptools resetconf host=K1B.com token=agent_token
Linux:- /opt/Quest/Kace/bin/amptools resetconf host=K1B.com token=agent_token
About the TOKEN: Device Security including auto-assignment to organizations based on tokens. For more information about this topic, please see the reference here.Follow these notes for creating a script to push the changes from the “KBOX A” server:- Select "Run As Local System"
- Check box next to "Allow Run While Logged Off"
- In the "Verify" step select "Launch a program…"
- Directory: $(KACE_APP_DIR)
- File: AMPTOOLS.EXE
- Wait For Startup box UNCHECKED
- Parameters: resetconf host=K1B.com token=agent_token
NOTE: Replace "K1B.com" with the actual name and the "agent_token" created on the Agent Tokens page.
Important Notes:
- Test this script first on a small target e.g. 1-2 agents and verify expected results. Make sure that agents are not left orphaned.
- Please note if agents cannot connect to “K1 B” after script distributed due to networking problem (e.g. router, firewall, DNS and etc.) the connectivity to “K1 B” will be resumed as soon as network problem resolved. It is strongly recommended to distribute this script in small batches per subnet, if applied, to make sure that each “K1 A” clients subnet of the network is properly routs to “K1 B” server.
- If you only want to change your Webservername you do not need to follow this advise but creating an alias from the old webserver name to the new one. All systems which connect then will grab the new webserver name.