How to regenerate the agent GUIDs from the client side
Last Updated January 26, 2007
Question For many reasons (see various forums posted under "duplicate GUID", "Duplicate MachineGUID" or article
3848), it is possible that multiple agents (that is, different managed computers) share the same GUID.
Article 3848 provides a method for correcting this problem but in some cases this doesn't always work as it should (based on the customer environment) or the customer cannot use the recommended method.
How can this problem be resolved then?
Answer If the AeXAgentUtility /resetguid switch cannot be used or doesn't perform as expected, the following Visual Basic script will replace the Altiris Agent GUID directly:
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)
Dim client Set client=WScript.CreateObject ("Altiris.AeXNSClient" ) ignoreBlockouts=1 sendIfUnchanged = 1 client.SendBasicInventory sendIfUnchanged, ignoreBlockouts client.UpdatePolicies ignoreBlockouts
Create a SWD Package that contains this VBS file, and use CScript.exe within its Programs command line to run it. Assign the Package's Task to the Collection containing the duplicated Guids that is provided via the KBA3848 toolkit.
Imported Document ID: HOWTO6538
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe