Migrating ITM 6.1 Agents from one TEMS to another "semi-automatically"

Migrating Agents from one TEMS to another could be a tedious job especially if you have lot of agents to migrate. Many of the steps involved in migrating the agents could be easily automated in a script. This article describes the steps involved in migrating the agents from one TEMS to another.

Disclaimer: Always test it fully in your environment before using this in production.

Migrating the agents manually.

1) Open Manage Tivoli Enterprise Monitoring Services
2) Right click the agent and select reconfigure
3) Click OK for Protocol specification and specify the new TEMS IP address in the next window.
4) Stop and Start the agent.
5) In TEPS, right click Enterprise -> Managed System Status and remove the offline entry from the managed system list.

Migrating the Windows OS agent "semi-automatically"

The steps to semi-automatically migrate the agents are given below. Please note that these steps can easily be scripted in your favorite language except the last step.

1) Open Regedit and locate the following key HKLM\Software\Candle\KNT\Ver610\Primary\Environment and specify the new TEMS IP address in CT_CMSLIST string value.
2) Net stop kntcma_primary
3) Net start kntcma_primary
4) Manual Step: Open up TEPS, right click Enterprise->Managed System Status and remove the offline entry for the agent from the managed system list.

Migrating the Universal agent "semi-automatically" in Windows

1) Open \tmaitm6\KUMENV file and change the line CT_CMSLIST to point to the right IP address.
2) Net stop kumcma_primary
3) Net start kumcma_primary
4) Manual step: Open up TEPS, right click Enterprise->Managed System Status and remove the offline entry for the agent from the managed system list.

If you are looking for a script to automate these steps, please indicate so in your comments.

Hope you find it useful.