Home » Groups » Asset & CMDB

Installing AClient as Part of Sysprep

Installing AClient as Part of Sysprep
Filed under: Deployment Solution Automation, Scripting
vortex0007's picture
Submitted by vortex0007 on 15 May, 2008 - 13:02.

The best way to install the Altiris AClient as part of the base imaging task, is to have the Deployment Server copy the most recent version of the AClient to the local drive, followed by a call from the Windows XP Cmdlines.txt file to run the installation.

This method ensures your clients always have the latest version of the agent and ensures freshly imaged computers still can be properly managed.

Unfortunately the command line options available for the aclient install are not as wide-spread as they should be.

Here's what the cmdlines.txt should look like to make this successful. And yes, the quotes are required:

[Commands]
"c:\altiris\aclient\altiris-aclient-6.9.164.X86.exe c:\altiris\aclient\aclient.inp -silent -install -scriptedinstall"
3.5283
Average: 3.5 (53 votes)

not bad..

dfnkt_'s picture
Submitted by dfnkt_ on 15 May, 2008 - 13:52.

I prefer to copy the latest version of the aclient from eXpress\agents and place it in the eXpress folder named "aclient.exe" and then as part of my driver injection I copy "eXpress\aclient.exe" to the "prod:\" (c:\). This way when a new aclient comes out, I simply replace the aclient.exe in the eXpress share with the newest version keeping the same name, and I don't have to adjust my cmdlines txt file.

Our Solution

Submitted by dkerr on 16 May, 2008 - 12:43.

We actually prefer to embed the Aclient within the image itself. As our image is actually a VM (makes HAL and driver prep a bit easier plus the ability to snapshot before and after the sysprep really helps us keep a consistent image) and we keep the AClient loaded within there. Any update to the AClient will be done when our VM is brought online. This ensures our AClient is always there and is also available immediately after the OS is done. Since it is in the image we have one less thing to worry about.

Question

DeborahAlbrecht's picture
Submitted by DeborahAlbrecht on 20 May, 2008 - 13:41.

Do you have the cmd for a server OS or would it be the same, what about a Linux box?

-d

The settings

trb48's picture
Submitted by trb48 on 21 May, 2008 - 17:35.

All of the settings for the scripted install are in the .inp file. This file lets you specify your DS server name and ip address, the install path, the clients password, and more.

Here is some more info on this subject:
https://kb.altiris.com/article.asp?article=24368&p...

Aclient in Image not working

Submitted by remco.smit on 22 May, 2008 - 01:05.

We are working on our new XP image and I need to have the Aclient in the image. this way the new host reports to the DS after image deployment. In the 'Golden-PC' installation I installed the Aclient using initial settings: Use Multicast to report to the nearest DS. This is needed because our network has multiple sites with multiple Altiris servers in different subnets. When the new client reports to the DS, another job pushes the final INP file with the site dependent settings.
The multicast settings does not work proper. When I copy the image to another site and deploy it with that local DS, it reports back to our DS in the Netherlands (I always thought multicast did not go through routers??).
What am I missing here?
The important lines from the initial.inp file are:
MCastAddr=225.1.2.3
MCastPort=402
and these disabled lines
;TcpAddr=172.16.10.108
;TcpPort=402

Any suggestions anyone?
Thanks.