I am having a hard time finding out info on this. I am looking for the command line to reset the Guid for a computer that has been renamed so I can see it in reports and resources.
You could use the ResetGuid switch for the AeXAgentUtil.exe. Default location is on the client systems in the C:\Program Files\Altiris\Altiris Agent directory. This switch deletes the following registry values, if they exist. HKLM\SOFTWARE\Altiris\eXpress\NS Client\MachineGuid HKLM\SOFTWARE\Computing Edge\Notification Server\Machine Guid HKLM\SOFTWARE\Altiris\eXpress\MachineGuid The ResetGuid switch clears the GUIDs. After the GUIDs are cleared, the managed systems will create new, unique GUIDs.
Looks too easy. i am scared seriously though thanks a bunch Nick. will test after hours tonight and see how it goes. Again Nick to the rescue. Bill
It seems there is mixed results with the switch. It looks like the official solution from the Altiris Forums is: Code: 'vbscript Change GUID then force client to update configuratin and send basic inventory Dim WshShell Set WshShell = WScript.CreateObject("WScript.Shell" ) Dim TypeLib, sNewGuid Set TypeLib = CreateObject("Scriptlet.TypeLib" ) sNewGUID = TypeLib.Guid Set TypeLib = Nothing sNewGuid = left(sNewGUID, len(sNewGUID)-2) ' wscript.echo " # Guid Generated " + sNewGuid WshShell.RegWrite "HKLM\Software\Altiris\Altiris Agent\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\Client Service\NSMachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\eXpress\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Altiris\eXpress\NS Client\MachineGuid" ,sNewGuid, "REG_SZ" WshShell.RegWrite "HKLM\SOFTWARE\Computing Edge\Notification Server\MachineGuid" ,sNewGuid, "REG_SZ" Dim client Set client=WScript.CreateObject ("Altiris.AeXNSClient" ) ignoreBlockouts=1 sendIfUnchanged = 1 client.SendBasicInventory sendIfUnchanged, ignoreBlockouts client.UpdatePolicies ignoreBlockouts
Just wanted to add my thanks for posting this script. Looks like it has resolved an issue I've had with several 'problem' machines that simply would not connect with the NS.
I know i have this issue by looking through my bad process fiels *.tmps in the NSCAP. is there a quick way to find out which machines have a duplicate GUID? jw
https://kb.altiris.com/article.asp?article=3848&p=1 Attached to the kb article is the XML to import the collections and report referenced in that .doc I also use this to help clean up after that tasks runs for about a month: http://www.altirigos.com/vbulletin/showthread.php?t=1627&page=2 (Duplicate Computers v2.4.xml)
Those both are awesome. Worked great in lab setup. Will try a small sample in production this weekend. Thank you very much! jw
