How to prepare a workstation for imaging that includes the NS Agent

Article ID: 19323

How to prepare a workstation for imaging that includes the NS Agent

---

Applies To
	• Deployment Solution 6.0, 6.1, 6.5 • Notification Server 6.0

 

 

---

Problem/Symptoms
	How can I image a computer with the Altiris Agent on it? What is needed to prepare the NS Agent when distributed as part of an image?

 

---

Environment
	Any imaging engine and any version of Notification Server. Note:  If imaging with DS 6.5 using the built-in methods, DS 6.5 will now do this automatically.

 

---

Cause

The Altiris Agent has a unique GUID for each workstation. If done incorrectly, when a new workstation is started with the same GUID as another, Notification Server will begin to manage it. Inventory from the multiple computers will keep over-writing each other, Software Delivery will be broken, and there are many other problems that become very difficult to clear. Because Notification Server identifies a workstation by its Machine Name and/or GUID, both must be different by the time the Altiris Agent connects to the Notification Server. If the GUID is in place but the Machine name changes, NS still thinks it is the same. If the GUID is missing but the Machine Name is the same, NS still recognizes the computer, and re-applies the old GUID to the computer.

 

---

Resolution

To prevent problems, one of two things must be done: The Altiris Agent must be completely removed and then re-applied post-imaging1, or The GUID for the Altiris Agent must be removed and the Altiris Agent must be prevented from communicating with the Notification Server prior to the computer being renamed. The former is recommended, that is to simply uninstall the Altiris Agent.2 However, some may want to pre-stage the Altiris Agent and Packages for bandwidth considerations. For those who do, do the following: Stop the NS client service and the client transport service. Leave them set to autostart. Remove the three Altiris MachineGUID entries from the registry3: HKEY_LOCAL_MACHINE/SOFTWARE/Altiris/eXpress/MachineGUID HKEY_LOCAL_MACHINE/SOFTWARE/Altiris/eXpress/NS Client/MachineGUID HKEY_LOCAL_MACHINE/SOFTWARE/Altiris/Altiris Agent/MachineGUID Take steps to ensure that there will be no communication between the operating system and the NS Server until after the computer is renamed4. Shut the computer down and image it without restarting the NS Client Services. Alternative Method using AexAgentUtil.exe /ResetGUID   The Altiris Agent now has a ResetGuid switch added to the AeXAgentUtil.exe. This switch deletes the following registry values, if they exist:   •   SOFTWARE/Altiris/Altiris Agent/MachineGuid  SOFTWARE/Altiris/eXpress/MachineGuid • SOFTWARE/Altiris/eXpress/NS Client/MachineGuid • This setting is useful if you have imaged several computers with the NS Client or only the MachineGuid already on them. Each NS Agent needs to have a unique MachineGuid. The ResetGuid switch clears the GUIDs. You can run AeXNSCUtil.exe from a logon script or by setting an AT command and the GUIDs will be cleared. After the GUIDs are cleared, computers create all new, individual, GUIDs. Prepare the client computer with the Altiris Agent. Once the agent is configured how you want it, remove it from the wire so that it can no longer communicate with the Notification Server. Open a command window and run AeXAgentUtil.exe /resetguid. The guid will be removed from the client.     1Some methods of deploying the Altiris Agent can include (but are not limited to) having a script in the image to connect to the Notification Server and run the install, having a post-deployment task in DS to push the Altiris Agent, using Active Directory to push the Agent to all new computers, using a login-script, or using the Notification Server policies to automatically push the Agent to all computers detected either via AD Import, or by some other method. 2There are a number of manual steps that can be taken to "clean up" the Altiris Agent from a computer. The simplest method is simply to uninstall all of its sub-components and then the Agent itself from Add or Remove Programs in Windows. This process is well documented in other articles. 3There have been rumors that various other files and registry entries must be removed from the Altiris Agent installation. These are not correct. Any XML files will be updated when the Agent checks in, gets a new GUID, and then receives new policies. Old packages will automatically expire. Only the Registry Key entries above are necessary for a pre-staged NS Agent to work, along with prevention of the Agent from connecting too soon. 4Using DS 6.5 to image a computer with the NS Altiris Agent on it If using Deployment Solution 6.5 to image the computer via the AClient, the above steps are automatic. Deployment Solution has always stopped all network services as part of its imaging jobs using AClient to rename the computer. Thus, the computer gets renamed prior to any opportunity for the Altiris Agent to communicate with Notification Server. Prior to DS 6.5 though, the step to remove those Registry keys was not included, and thus had to be performed manually. If using any other imaging engine, it will be the responsibility of the user to ensure that their process renames the computer prior to the workstation having a chance to connect to the Notification Server. DS will also remove an additional key as part of its imaging process: HKEY_LOCAL_MACHINE/SOFTWARE/Altiris/Client Service/NsMachineGUID. This stores the AClient location. There are some key considerations to make this process work: In order for the removal of the GUID to occur, the workstation must have the DS 6.5 AClient installed prior to the creation of the image. A scripted create image event will not trigger the wiping of the GUID. The "Do not boot to Windows" option must remain unchecked in the task. SOFTWARE/Computing Edge/Notification Server/MachineGuid

 

---

The information contained in the Altiris Knowledgebase is subject to the Terms of Use as outlined at http://www.altiris.com/legal/termsofuse.asp.