Deployment Solution

Advice please. I am trying to create a software package that contains an exe and a lot of files and reg files that need to copied to certain locations as part of the install and then running the reg file as well as installing the exe. I do not have an option of an MSI package as the install I have is only exe. what will be the best action to complete this?

The easiest way will be to create an "install.cmd" with all your "copy" and "reg add" commands and executing the exe.

How many error handling you want to build inside (effort) is up to you.

 

If you are not able to run the exe silent/unattended you have a problem.

You either have to automize it (f.e. autoit), or repackage the application (MSI).

Thanks, I was currently looking at creating tasks and then a job from the tasks but an install.cmd seems more logical approach. The exe will not install silently as I need to copy a file to a directory that allows it to run with a silent switch. Our counter parts had created the exe and sub files using wise, why they didn't create a msi package I do not know as I am not too familiar with WISE studio and packaging and why the exe doesn't tell the installer to do this as part of the install. The package it seems was created for SMS/SCCM deployment it appears.

I have successfully managed to get the exe to install manually using command line witht he silent switch once the relevant file was copied to the directory by myself.

If you need to run setup.exe -f c:\support\myapp\installer.properties or similar you can put the installer.properties file and the setup.exe in the same folder on your software share and specify c:\support\myapp in the "Location on destination computer:" section of the Download tab in the Advanced options of a Managed Software Delivery Policy. I create any required reg settings and other updates as a separate Software Resource, usually a Software Update. If you write an install.bat file to do the whole lot you risk losing error codes or having it report success even if the install fails but the reg writes succeed.

Andy is right, but creates some dependencies, that might also cause the package installation to fail.

What happens if someone doesn't check to install the patch in the policy?

What happens if someone forgets to "fix" the download location in the policy?

 

I like my software "standalone". No admin can forget settings, or needs to read a documentation ... just call install.cmd.

Yes, you have to care for the errors in the install.cmd yourself... you probably have to anyway.

 

Both solutions will work ... your choice.

Thanks Andy,

I will give this a try first, i am new to Altiris and been learning as i go a long. Ideally I want to keep any error codes for troubleshooting as the package will be distributed worldwide

 

Yes, it does depend on your admin model. I recommend trying to only have the one Policy per software with a daily compliance check and corresponding Filter so once it's done and tested it's left working - you get to know the error codes if you've forgotten pretty quickly (-2147213312 or -8 for InstallShield iss files). I also put the alternate download location in the Description field of the Software Release/Update/Service Pack so it's visible in the Policy

So a plain package ... all for nothing.

Nice discussion, though ^^

Our solutions team who created the package have advised the exe copies and runs all the reg files similar to vendor setup.exe. They advised I need to be in the Alitiris Cache so the exe will install all the files.

 

 

If i just package the exe it will not work, I not sure how to create the job with all the files. They mentioned the folder needs to be in the Altiris cache but I'm not sure where this is.

Just Import all the files to your package in the software release and execute the exe with the needed parameters (Default install command line).

It will automatically be downloaded to the client (into the agent cache) and be executed there, using the current directory (don't use absolute paths).

You don't even have to know where it is ;)

 

Psst:

C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\<Package GUID>\cache

There is a set of articles that might help:

https://www-secure.symantec.com/connect/articles/symantec-software-management-75-troubleshooting-and-best-practices-part-4-process-flows

 

Brilliant, thats helped a lot. I created a software product and imported all the folders an exe etc and just planning to test now but confident it will now work.