locked
Adding Shortcuts after Sequencing the application. RRS feed

  • Question

  • Hi,

    I have a application which is already sequenced, now the user requested to add a shortcut to one of the exe's located in the application directory, is it posible to create shortcuts after completing the sequencing of the application, if yes can you guide me on this.
    Thursday, May 28, 2009 6:32 PM

Answers

  • Hello,

    Did I misunderstand this?

    Do you want to add a shortcut to a executable file which is not "advertised" previously?

    That includes a new OSD-file (and I would say an upgrade / repackage).

    If the executable is published (or advertised.. :) ) previously but you wish to add a shortcut to a new location - the above is correct (first of all - it depends on deployment method).

    /Znack
    • Marked as answer by Vinod Mukka Tuesday, June 2, 2009 8:16 PM
    Friday, May 29, 2009 4:42 AM
  • To expand on Znack's answer...

    It is possible to copy an existing OSD from the package, and edit it.  You would replace the "NAME=" and "FILENAME=" fields with the executable you now want to launch.  Assuming the Dedicated server (RTSP/S delivery), copy this into the content share next to the original OSD.  In the App-V server console you would import applications, change the file type from sprj to osd and pick the new OSD.  Assign to user, etc... 

    This, however is not a good practice, and Znack's suggestion to upgrade/repackage is.  The reason is that unless you edit the sprj and manifest.xml files to also handle these changes, you have set yourself up for a potential issue to loose this added application if you ever open the package for upgrade in the future.  While it is straightforward to make those edits - it is tedious and error prone.  Thus we usually recommend upgrading the package.

    If the app is deployed using SCCM or MSI, cracking open the sequencer to upgrade the app is nearly the only way.

    To do so, copy the content folder to a clean sequencer.  File "Open for Package Upgrade".  When prompted, pick the root of the secondary drive (Q:\  not Q:\8.3 ).  From the menu, select tools then sequencing wizard.  Run through the wizard - you don't have to start/stop monitoring.  On the Applications page of the wizard, use the add button to add the new shortcut.  Save off as a new version.  Copy to the content share and use the server management console to add the new version (under Packages, not applications).

    • Proposed as answer by znack Tuesday, June 2, 2009 7:19 PM
    • Marked as answer by Vinod Mukka Tuesday, June 2, 2009 8:16 PM
    Friday, May 29, 2009 2:25 PM
    Moderator

All replies

  • Hi,

    You can alway's do this trough the App-V client console, right-click the application and select "new shortcut"

    If you want to do this for more users, it depends on what kind of deployment of App-V you use.
    Native, MSI, SCCM etc.

    Kind regards,

    Jan van der Elst
    Login Consultants
    Thursday, May 28, 2009 8:04 PM
  • Hello,

    Did I misunderstand this?

    Do you want to add a shortcut to a executable file which is not "advertised" previously?

    That includes a new OSD-file (and I would say an upgrade / repackage).

    If the executable is published (or advertised.. :) ) previously but you wish to add a shortcut to a new location - the above is correct (first of all - it depends on deployment method).

    /Znack
    • Marked as answer by Vinod Mukka Tuesday, June 2, 2009 8:16 PM
    Friday, May 29, 2009 4:42 AM
  • To expand on Znack's answer...

    It is possible to copy an existing OSD from the package, and edit it.  You would replace the "NAME=" and "FILENAME=" fields with the executable you now want to launch.  Assuming the Dedicated server (RTSP/S delivery), copy this into the content share next to the original OSD.  In the App-V server console you would import applications, change the file type from sprj to osd and pick the new OSD.  Assign to user, etc... 

    This, however is not a good practice, and Znack's suggestion to upgrade/repackage is.  The reason is that unless you edit the sprj and manifest.xml files to also handle these changes, you have set yourself up for a potential issue to loose this added application if you ever open the package for upgrade in the future.  While it is straightforward to make those edits - it is tedious and error prone.  Thus we usually recommend upgrading the package.

    If the app is deployed using SCCM or MSI, cracking open the sequencer to upgrade the app is nearly the only way.

    To do so, copy the content folder to a clean sequencer.  File "Open for Package Upgrade".  When prompted, pick the root of the secondary drive (Q:\  not Q:\8.3 ).  From the menu, select tools then sequencing wizard.  Run through the wizard - you don't have to start/stop monitoring.  On the Applications page of the wizard, use the add button to add the new shortcut.  Save off as a new version.  Copy to the content share and use the server management console to add the new version (under Packages, not applications).

    • Proposed as answer by znack Tuesday, June 2, 2009 7:19 PM
    • Marked as answer by Vinod Mukka Tuesday, June 2, 2009 8:16 PM
    Friday, May 29, 2009 2:25 PM
    Moderator