locked
Sequencing for Standalone installation RRS feed

  • Question

  • I've a question regarding using "standalone" model .
    If we sequence an application for "standalone" use how can we prevent users to "pass" the msi created to other people outside the company ?
    Is there a way to tie the use of the sequenced application to the membership of groups in AD ?
    thanks
    stefano
    Tuesday, July 28, 2009 2:11 PM

Answers

  • Hello,

    MSI has, as the only, a prereq of the app-v client.

    Unless you modify the MSI by yourself, there is no check possible based on any condition to prevent an end-user to install it if they have gotten their hands on it.

    /Znack
    • Proposed as answer by znack Tuesday, July 28, 2009 2:14 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 3:25 PM
    Tuesday, July 28, 2009 2:14 PM
  • There are several ways to achieve this with App-V 4.5.  The real question is what do you want out of "standalone" model and how do you want to implement it. 

    There are some options with standalone and an MSI that are presented in the following documentation.

    I would look at Application Publishing and Client Interaction for sure and possibly Extensibility Today before the SDK.  Really all of them are good, but those focus on some different ways of publishing applications to a client.

    They are avaialble at:  http://go.microsoft.com/fwlink/?LinkId=127120

    Another good source would be to look at the App-V Planning and Deployment Guide available at: 

    http://go.microsoft.com/fwlink/?LinkId=122063.

    mattmcdermott
    Tuesday, July 28, 2009 3:33 PM
    Moderator

All replies

  • Hello,

    MSI has, as the only, a prereq of the app-v client.

    Unless you modify the MSI by yourself, there is no check possible based on any condition to prevent an end-user to install it if they have gotten their hands on it.

    /Znack
    • Proposed as answer by znack Tuesday, July 28, 2009 2:14 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 3:25 PM
    Tuesday, July 28, 2009 2:14 PM
  • Using GPo to deploy such MSI could solve the problem ( as we won't give the MSI to the final user ) ?
    Tuesday, July 28, 2009 2:44 PM
  • Hello,

    As with any MSI, this could be one way to not directly reveal the location of the msi.

    /Znack
    Tuesday, July 28, 2009 2:48 PM
  • There are several ways to achieve this with App-V 4.5.  The real question is what do you want out of "standalone" model and how do you want to implement it. 

    There are some options with standalone and an MSI that are presented in the following documentation.

    I would look at Application Publishing and Client Interaction for sure and possibly Extensibility Today before the SDK.  Really all of them are good, but those focus on some different ways of publishing applications to a client.

    They are avaialble at:  http://go.microsoft.com/fwlink/?LinkId=127120

    Another good source would be to look at the App-V Planning and Deployment Guide available at: 

    http://go.microsoft.com/fwlink/?LinkId=122063.

    mattmcdermott
    Tuesday, July 28, 2009 3:33 PM
    Moderator