When using duplicate computer names and/or GUIDs, various issues occur. For example, duplicate or shared GUIDs can occur, inventory being added to the wrong computer, the wrong computers being processed in tasks or policies, etc.
Altiris matches up computers based on their Name.Domain. It can also check for existing GUIDs that match up to computers. If computer names are reused or shared between multiple computers such as being pushed out by an image, this will result in severe issues such as duplicate or shared GUIDs, which prevents Altiris from uniquely identifying which computer is being referenced correctly. This situation can become further complicated if a hierarchy or stand-alone replication rules are used. Because of these requirements, using duplicate computer names is not supported by Altiris*.
(1) When the computer name is duplicate but belongs to a different domain than its duplicate.
(2) When setting up staging (unmanaged) computers that are later to be merged with managed computers. For example, a common process for many customers is the following on how they bring in new computers to their environment:
Depending on what's happened, there may be little to no solution. The following possible solutions can be attempted, but which may result in data loss, which may be unavoidable.
The resource history of an asset can shed light on what may have changed it. The following instruction describe how to check this:
Duplicate Computer Merge not merging all duplicates
Does Asset Management or CMDB Solutions support hierarchy and stand-alone replication rules?
Any version of the Altiris Notification Server and its products that leverage computer data.