After imaging a PC, a duplicate PC or at least a PC with the same name/ip address appears in the console. This only happens when imaging a PC with a Windows 7 image. If you were to image that same PC again, but with our XP image, the duplicate PC goes away and the XP PC remains in the console. If you reimage the Windows 7 PC with a windows 7 image, another duplicate PC appears.
The Altiris Agent is in the image, but it was manually installed on the reference PC with no network access and the service was stopped, prior to any network connection to that PC in the image building process, so it did not get a GUID.
It has been brought to my attention that it could be our answer file. For new PCs (unknown to Altiris) we have a custom answer file with a computer name of BASEIMAGE. While still in WinPE we run a script to prompt for computer name and OU that then edits the unattend.xml file, replacing BASEIMAGE with the computer name we enter. For Existing PCs (known to Altiris) we also use a custom answer file with @compName for the computer name. I found this token/variable in an unattend.xml file on the NS. I have opened the unattend.xml file in the Panther folder on a imaged PC still in WinPE and the proper computer name is replacing @compName.
As well as duplicate computers appearing, our Duplicate GUID report shows newly Windows 7 imaged PCs as having the same GUID as a PC named
"Win-*********" which does not exist in the console. These PCs have the same GUID as the same Win-********** PC, yet they have different GUIDs from each other.