A GUID is shared when two or more Symantec Management Platform (SMP) agents use the GUID at the same time. This can cause some odd behavior.
Shared GUIDs causes inaccurate inventory reporting, so, for instance, you will not know which computers have which software installed. In addition, Shared GUIDs prevents properly managing computers, because computers might receive policies intended for other computers, and so might receive a policy that it should not; or might not receive a policy that it should.
In order for the SMP Server (Server) to manage each SMP Agent (Agent) properly, the Server must be able to identify each Agent uniquely. To do this, the Server assigns each Agent a unique GUID (Global Unique Identifier), and each Agent uses its assigned GUID in all subsequent communication with the Server.
When the Agent is installed, it does not have a GUID until the Agent requests and receives a GUID from the Server. When the Agent requests a GUID, the Agent supplies several identifying key values, including the computer’s "name.domain" value. Then the Server checks whether a GUID has been associated with the values supplied by the Agent, if found the Server returns the existing GUID to the Agent, otherwise the Server creates a new GUID, associates the new GUID with the key values supplied by the Agent and returns the new GUID to the Agent.
Note: in order for the SMP system to work properly,
Note: UNIX, Linux and Macintosh agents are handled in a similar but slightly different manner.
Preventing Shared GUIDs
To ensure that each SMP agent receives a unique GUID, we suggest the following:
Detecting Shared GUIDs
Detecting computer with Shared GUIDs
Correcting Shared GUIDs
Shared GUID cleanup script
Concerning the re-use of computer names
A computer name is re-used when one name is assigned first to one computer and later assigned to a different computer, but the name is not assigned to both computers at the same time.
Symantec Technical Support strongly discourages the re-use of computer names - as this is known to lead a variety of issues. If historical data must be retained, then computer names should not be reused.
The following suggestions are offered in the unlikely event that computers names must be re-used to corporate policy. While these suggestions may be helpful in some situations, their use is strongly discouraged.
Note: These suggested steps involve the deletion of all data about the previous computer from the database. This deletion is necessary to prevent data inconsistencies caused when the information about two different computers is merged. If historical data must be retained, then computer names should not be reused.