Go to All Forums

Cloning a server

We have many servers that are cloned from images: install the software (including monitoring) then save to image.  As needs dictate, new servers are spawned from this image, given a new hostname and they're in business.

We've seen some funky issues with the agents during this process.

Does the monitoring agent need any special attention - variables or config files modified to account for a new hostname or IP address?
Like (3) Reply
Replies (5)

We recommend you to follow the steps given below, so the agent will consider it as a new server and add it for monitoring.


1. Go to Run -> regedit.exe
2. Navigate to the below key:
3. Change the above registry key value to "SITE24X7NEW" and click 'OK'
4. After performing the above change, open Windows services -> restart the 'Site24x7 Windows Agent' service once. 


1 Edit the configuration file "/opt/site24x7/monagent/conf/monagent.cfg".
2 Change the [PRODUCT_REGISTRATION_KEY] from: site24x7 = SITE24X7 to: site24x7 = SITE24X7NEW
3 Change the [AGENT_INFO] from: agent_key = "AGENT_KEY" to: agent_key = 0
4. Restart the agent using "sudo /etc/init.d/site24x7monagent restart"

Like (0) Reply

This should be a knowledge base article. 
Like (0) Reply

I tried the same thing but It didn't work. What do I need to do?

Like (0) Reply

but if I do this workarround, can I except that the historical reporting works for this cloned server? You wrote after adding this regkey it will consider that this is a new server.
Like (0) Reply

Hi p.pfeffer,

Yes, data collection and reporting will start from the time the new server monitors are created for the cloned server. Hence, Historical reports can be generated for this new server monitor from the time the new server monitor was added to Site24x7. 

Please let us know if you require any further clarifications and I would be glad to assist further. 
Like (0) Reply

Was this post helpful?