Ok I searched and read throug a few other topics here and got some good information.
A little bit of history with our use... We use Altiris to push software/patches/inventory, etc to a select 4k machines in our company of 36k machines. With that we have challenges where we cannot do an AD Import, cannot deploy agents via network discovery. We are currently going from Windows XP to Windows 7.
We image a new machine via USB or network (non DS - would love to but that is a seperate issue all together... )
During this process the machine is given a name, joined to the domain and at the end Altiris is installed.
We are starting to see more and more shared GUID's. While other posters have stated to read a few articles... this one stands out for us.
http://www.symantec.com/business/support/index?page=content&id=HOWTO93988
In there it states a few things:
at the bottom of the link it states...
This process will delete all previous data about each computer from the database; and 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.
We cannot have this. We keep all hardware inventory and software delivery for machines so we cannot delete.
Scripts are provided to blacklist guids, delete those guids, etc.. but to that you also loose historical data...
I have those scripts and they work but not going to work for us as we do not want to loose the information.
so I guess what I am trying to do is figure out how to not have shared guids appear while also not doing an AD Import.
Any thoughts? I am going to talk to the guys and make sure they are building the computers off the bat with the correct name and not renaming in the future possibly causing the shared guid.
I have an automation policy setup to run the report and email it to me and I can see the list growing...
slightly cleaned up but you can see in the attached pic..