I am curious how the LEM agent generates it's SID/UID?
We are working with a client to develop a BC/DR solution and I am curious when the replica nodes comes online if it will check in as a new node or if it will appear as the same node?
Upon installation it connects to the manager and gets a certificate which is then associated with an id. If you are working on a DR type solution then you can copy the ContegoSPOP directory after it installs to the manager and that agent will get the same id and certificate.
I would suggest trying it out and if you need some help post to Thwack or give support a holler.
So, if a system that already has the agent is being replicated (essentially cloned) it will already have the certificate and an ID so how will LEM handle that system trying to connect; will it see it as the same system as before or will it see it as a different system? If the original (source) system is still online reporting to LEM and the clone comes online and also tries to talk to LEM what happens then?
Is there a way to force it to get a new certificate/id or is the only way to do that an agent uninstall/reinstall?
Just trying to understand all of the nuances so we can get a proper solution in place.
If it is the same cert it will see it as the same system. If the clone comes online you would get duplicate connection messages in your console saying there was a duplicate agent connection that is happening.
Well if you are trying to clear it out then you would do something similar to Include the LEM Agent in a Windows image - SolarWinds Worldwide, LLC. Help and Support which is very similar to an uninstall/reinstall
Definitely try it out to see what happens for you and if you are ok with it.
