Embed of /exe-parameter in osd file? RRS feed

  • Question

  • We are using the PuTTY Suite (Plink, Pscp, PSFTP, PuTTY, etc...) as an app-v package.

    For starting and using plink and pscp we need the parameter /exe cmd.exe in the shortcut like this

    "C:\Program Files (x86)\Microsoft Application Virtualization Client\sfttray.exe" /exe cmd.exe /launch "Plink"

    to start cmd which opens a promt in the correct q-directory and than we can start plink.exe manually within the cmd window by typing plink (or pscp).

    The shortcuts are changed manually.

    Now there is the question if it is possible to saying via the osd file to use the /exe-parameter automatically to not change afterwards manually the shortcuts?

    Tuesday, August 13, 2013 4:12 PM


All replies

  • Hello,

    Change the FILENAME in CODEBASE to your desired .EXE-file;


    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, August 13, 2013 4:43 PM
  • or more gracefull

    With MS native tools:

    Modify the pacakge again on the Sequencer with the Add Application wizard, make sure that you use to follow the 'customize package' during that wizardsteps. There you can add additional shortcuts/applications for your package.

    Saving the package ensures that 'all' deplyoment methods (App-V Manmagement Server, Stand-Alone MSI, ConfigManager) can leverage that new shortcuts.

    With 3rd Party Tools:

    Gridmetric's (older) Application Virtualization Explorer offers a GUI to accomplish that (and more). Note that for modifying App-V 4 packages you have to use AVE v2 or AVE v3_ProfessionalEdition

    Changing just the FILENAME indeed would work as well, but it'll 'break' your original shortcut (so you still can only launch one application and not every application of that package) and it might be confusing for users to click on like 'Plink' and actually launch PSCP or so.

    You may create copies of the original OSDs and modify the FILENAME in these copies, but then you have to adjust the NAME element in there, you definitevely should adjust the applications GUID in there, you should update the SPRJ file to include these new OSDs... and still you don't have the new OSDs in the MSI... I'm not saying that Nicke's advice would not work (I never would say that ;-) ) but fixing the package with ApplicationVirtualizationExplorer or the Sequencer is _always_ the more solid and consitent method.


    Twitter @kirk_tn   |  Blog kirxblog   |  Web kirx.org

    Wednesday, August 14, 2013 6:40 AM
  • Thanks, I changed filename to "%SFT_SYSTEM32_X64%\cmd.exe" within the Sequencer. Now on doubleclick of the Shortcut a cmd-promt is opening in the directory of the virtual putty file.

    Wednesday, August 14, 2013 2:34 PM