Deployment Solution

We have a few machines that are being difficult accepting the AClient being pushed out from the server(s).   I was wondering if there was nice easy way I could copy off the install file and embedd the settings so when it is istalled it will just take the settings and not have to go through the advanced set tabs to set the server info and other settings.

You can do a silent install by creating an aclient.inp file that has all of your settings saved in it.

Depending on what version of the aclient you are using, the install command line would look something like:
AClient.exe AClientConfig.inp -install -silent
(note: the inp file can be named whatever you want)

You could put that command-line in a batch file and run it on-demand.

I was hoping to make it into a self contained EXE or something.  The problem I have is I would like to make this easy as I have tech staff that I would like to do this but they are not computer saavy so to speak.    So far it only has been a few machines that have been tempermental so maybe it won't be so bad.   I was trying to avoid making a step by step install process with screen shots to guide them through the options.

If I make this inp file and put it all in a folder that they can put on a flash drive or run off the network they can probably run the command so I will try that method.  Thanks

I created a .bat file for our techs here.  This is all that you have to put in it.  As George said above you can name the .inp file whatever you would like.

\\yourservername\express\aclient.exe \\yourservername\express\aclient.inp

Not sure how you go about your PC build process, but you can automate this into the build (and therefore always getting the latest version and updated .inp file).

In our case, after imaging we have a few FIRM commands that copy the aclient and inp file into a specific directory.  Upon reboot, it runs through sysprep (of course...this is Windows XP we're talking about here...)

Within our sysprep file, the last command is to do the exact same command line above, pointing of course to the aclient.exe and aclient.inp files.

Hope this helps, but if it's redundant, sorry  :-)