locked
Stand-alone App-V question RRS feed

  • Question

  • Hi,

    We use App-V integrated with SCCM, but for the purposes of testing sequenced applications before they go into SCCM, I'm thinking creating an initial standalone app-v package would be a good idea. I've had a little play at generating an MSI App-V installation, got that to install, but when it's executed it errors saying:

    could not launch <app>

    the specified application virtualisation server could not be accessed.

    Error code: 4513CDC-19D02C0A-10000002

     

    I'm thinking this is because it's using the default package url of RTSPS://%SFT_SOFTGRIDSERVER%:322/<package> and obviously we don't use a App-V server anymore.

    So, what are you supposed to do when you want to install and run a standalone app-v package? I notice that I could use FILE:// in the sequencer instead. Is this what you do? Point it to a local location in the sequencer before you create the MSI? Where do you set it to? The cache?

    Thanks!

    Tuesday, March 30, 2010 3:11 PM

Answers