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 former is recommended, that is to simply uninstall the Altiris Agent.2
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.
|
The information contained in the Altiris Knowledgebase is subject to the Terms of Use as outlined at http://www.altiris.com/legal/termsofuse.asp.