Altiris Agent 7.x on Image
Updated: 09 Oct 2010 | 7 comments
This issue has been solved. See solution.
Does anyone have the information on how to place the Altiris Agent on an image for 7.x? There are a couple KB articles that define what registry keys and files to delete so that a new GUID is automatically generated but I am unable to find the equivalent information for 7. Am I just missing it or is the process different for 7?
thanks,
Discussion Filed Under:
Comments
You would probably be better
You would probably be better off installing it post-imaging than pre.
That way you won't have to worry about the GUID issue, and you'll always be deploying your most current agent to newly imaged machines.
Agree
I have to agree with Mr. Swenson.
There's the theoretical effectiveness of including the agent on your image and then cleaning it up properly (99.8% effective), and then there's the actual effectiveness of including the agent on your image and cleaning it up properly (40% effective). Don't play with fire.
Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
Summary + Applicable KBs
You can avoid the duplicate GUID issue by following these steps:
Note: These steps work for NS 6 or NS 7
...HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent\Machineguid
...HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\MachineGuid
...HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\NS Client\MachineGuid
...HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Client Service\LastUpdateComputerInfo (Note: This will exist when the AClient is installed.)
The above information was taken from KB 16846 (https://kb.altiris.com/article.asp?article=16846&p=1)
You can find similar information in KB 193232 (https://kb.altiris.com/article.asp?article=19323&p=1)
Please let me know if you have any questions
On image
I include the agent on images because, hopefully, it ensures the system will become managed immediately and it doesn’t rely on staff pushing the agent to the PC subsequently or figuring on some mechanism to automatically install the agent post image.
I install the agent at the end of the image creation just prior to sysprep, unplugging the network cable first, so the agent can’t contact the NS server at all, assigning a GUID etc, I don’t know if that is the best way to do this but it seems to work ok.
We use a script after the
We use a script after the modify configuration task on DS 6.9 with the agent install file injected into the image to kick off the agent installation.
msiexec /i c:\source\AeXNSCInstSvc.msi NS="NS-ServerName" /qn
Works well - hope this helps.
I was under the impression
I was under the impression that the prepare computer for sysprep task takes care of this automatically.
(NS 7.x user here).
I too use a
I too use a firstlogoncommands script to install the agent post imaging. I had many problems when including the Agent in our Windows 7 image. To be fair, I was using the "AeXAgentUtil.exe /resetguid" command to prepare it, so that may have been the issue.
I also script the install of the Software Management Solution Plug-in make the machines able to get pushed software immediately.
Would you like to reply?
Login or Register to post your comment.