Client Management Suite

 View Only
  • 1.  package software with a batch install

    Posted Jun 27, 2017 10:29 AM

    I'm trying to package a software called greenshot which is free screen print program, for it to have the settings I want after install I need two ini files to be placed in the install dir after the install is complete:

    1. I have the exe running like this "Greenshot-INSTALLER-1.2.9.129-RELEASE.exe" /sp /suppressmsgboxes /nocancel /norestart /closeapplications /verysilent 

    2. I know I did this once before but can't for the life of remember how, believe I would need to create a batch file for the install and after the above line runs have the xcopy command run to copy those two ini files in the "c:\program files\greenshot' but do I need to upload the those ini files into software resources or is there a step when i first load greenshot.exe into the software resources that I attach those files?

     

     



  • 2.  RE: package software with a batch install

    Posted Jun 28, 2017 04:52 AM

    Hi Cody,

    You have two options, one easy and second more complex with compliance check.

    Easy one is to import your files to separate software package and create Package Delivery task which will deliver package content to specific folder without specific command line (Quick Delivery task don't have such option). https://www.symantec.com/connect/forums/altiris-task-copy-file-unc-local After that you may Create Quick Delivery task for Greenshot installation and combine them both into one Job. 

    Second one: First of all you should create detection check for Greenshot software release. 

    1-st option is to use same Package Delivery. But now you should combine Installation of the Greenshot and Package Delivery with files under Managed Delivery Policy (MDP in future).

    2-nd option in case if your software can be installed into Program Files (x86) for x64 bit machines you should create 2 similar software releases for ini files and custom command line: cmd /c "exit 0"(this command line will do nothing). Add Applicability check to both of them them. For one for x86 bit machines and for second for x64 bit machines. Add both software release to the MDP with Greenshot, specify custom download location in advanced options for both software releases in this MDP (C:\Program Files for x86 bit machines and C:\Program Files (x86) for x64 bit machines). 

    In this case your policy will install Greenshot, after that in case x86 bit machine it will download ini files from one package in proper location. In case of x64 bit machine it will be skipped and ini files will be downloaded from another package.

    Regards,
    Dmitri