Pretty much as the title say. This would save us a fair bit of hassle. I've fiddled around with sftmime LOAD APP and LOAD PACKAGE but haven't gotten anywhere and I haven'y found anything to say that it can't be done so I'm not sure it its just me. We are using 4.6 SP1.
Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1
Have you had a look at 'sftmime /add package?'

Details can be found here: http://technet.microsoft.com/en-us/library/cc817098.aspx

Alternatively you can select the option in the sequencer to generate an MSI installer for the package and then you can run the MSI to 'install' the App-V sequence locally. Bear in mind that you'll have to configure your App-V client for stand-alone mode.

Hope that helps,

Dunnpy
Answered 03/26/2012 by: dunnpy
Red Belt

  • Looking into this! Seems I just picked the wrong command to focus on.
  • Try ACDC from Login Consultants
Please log in to comment
1
fi you have App-V package files locally on the machine, you can change the paths in the OSD file and run it using the command

sfttray.exe /launch "path to OSD file"

If that's what you're looking for..
Answered 03/26/2012 by: pjgeutjens
Red Belt

  • This requires a little more fiddling than I wanted. I'm trying to create a simple script / gui for our packagers to use to test locally before publishing so simplicity is key (to make my code writing easier!)
    • In that case generate the MSI from the sequencer, your packagers will just need to copy it to the local machine and launch it to 'install' the app.

      No scripts required then.
      • Almost too simple! Will the MSI just behave like an AppV package with Local Interaction allowed?
  • Replied to wrong bit.
  • The MSI is just a wrapper that launches a custom action with the sftmime commands to add the package - it will behave exactly as it would in a published state.
Please log in to comment
Answer this question or Comment on this question for clarity