This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

How does SAM Agent create it's SID/UID?

I am curious how the Orion/SAM 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?

  • The GUID is generated at time of Agent installation and should be globally unique, even if everything else about the system is identical. The only way to duplicate the GUID across multiple systems would be to image the machine after the Agent is already installed.

  • aLTeReGo​ thanks for the super fast response.  So, if a system with the agent already installed is being replicated (essentially cloned) then when it comes on it will have the same GUID and report as the exact same system?  If that is the case would you have any suggestions on how to make it report in as a different system or is that essentially just uninstall/re-install of the agent to create a different GUID?

  • Yes, you would utilize the Gold Master Image option for the Agent deployment. This installs the agent but does not provision it with a GUID or register it with an Orion instance until the server is rebooted. This can be further postponed by disabling the Agent Windows service until such time as you're ready to snapshot the image.