How to test App-V packages locally?

All replies

• 

  

  1

  Sign in to vote

  Could you explain what you would like to do further? If you wanted to just test on a local machine without SCCM you could install the generated MSI on your Client machine or use an SFTMIME command to cache the application to the machine.

  Are you trying to ask how to make it available to your machine through SCCM?? Or do you just want to test it locally no matter method? If you don't care about the how, use the generated MSI on a machine with the App-V Client

  ---

  PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

  • Proposed as answer by RorymonMVP Tuesday, November 20, 2012 2:21 PM
  • Unproposed as answer by Aaron.ParkerModerator Tuesday, November 20, 2012 2:24 PM
  • Proposed as answer by Aaron.ParkerModerator Tuesday, November 20, 2012 2:24 PM

  Tuesday, November 20, 2012 2:05 PM
• 

  

  0

  Sign in to vote

  Hello,
  
  You can publish them using Powershell or the provided MSI.
  
  See this as an example;

  http://blog.stealthpuppy.com/virtualisation/app-v-5-powershell-one-liners-adding-and-publishing-app-v-client-packages/

  ---

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

  • Proposed as answer by RorymonMVP Tuesday, November 20, 2012 2:21 PM
  • Unproposed as answer by Aaron.ParkerModerator Tuesday, November 20, 2012 2:24 PM

  Tuesday, November 20, 2012 2:06 PM
• 

  

  0

  Sign in to vote

  Hi weedee,

  Let me make it clear, are you going to test the application in standalone or do you any issues when deployed the application using SCCM.

  Regards

  ---

  Raghavendra Rao V

  Tuesday, November 20, 2012 2:12 PM
• 

  

  0

  Sign in to vote

  Further to Rorymon's suggestion, here's how to use SFTMIME ADD PACKAGE command to add and test packages locally: http://technet.microsoft.com/en-us/library/cc817181.aspx

  ---

  
  

  Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.

  
  

  This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

  • Proposed as answer by RorymonMVP Tuesday, November 20, 2012 2:21 PM

  Tuesday, November 20, 2012 2:12 PM

  Moderator
• 

  

  0

  Sign in to vote

  Hello Rorymon,

  many thanks for quick response!

  What I'm trying to achieve, is to quick test my App-V packages on virtual workstation, before adding them to SCCM server.

  • Proposed as answer by VRaghu Tuesday, November 20, 2012 3:32 PM
  • Unproposed as answer by VRaghu Tuesday, November 20, 2012 3:32 PM

  Tuesday, November 20, 2012 2:15 PM
• 

  

  0

  Sign in to vote

  Also see these articles:

  • http://blog.stealthpuppy.com/deployment/app-v-faq-20-what-are-the-deployment-methods-for-app-v/
  • http://blog.stealthpuppy.com/deployment/app-v-faq-13-how-do-i-configure-the-app-v-client-in-stand-alone-mode/
  • http://blog.stealthpuppy.com/virtualisation/app-v-errors-00000006-and-000d3002-when-adding-packages/

  ---

  
  

  Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.

  
  

  This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

  • Proposed as answer by VRaghu Tuesday, November 20, 2012 3:32 PM
  • Marked as answer by weedee Monday, November 26, 2012 8:09 AM

  Tuesday, November 20, 2012 2:19 PM

  Moderator
• 

  

  0

  Sign in to vote

  Cool. I think you've got your answer than. MSI if you have generated your MSI during sequencing (you'll see it in the same directory as your .sft, .sprj, .osd etc.) Just install that on your VM that has the App-V Client.

  Alternatively use the SFTMIME command that Aaron just provided a link to.

  ---

  PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

  • Proposed as answer by RorymonMVP Tuesday, November 20, 2012 2:21 PM
  • Unproposed as answer by Aaron.ParkerModerator Tuesday, November 20, 2012 2:28 PM
  • Proposed as answer by Aaron.ParkerModerator Tuesday, November 20, 2012 2:28 PM

  Tuesday, November 20, 2012 2:21 PM
• 

  

  0

  Sign in to vote

  You can install the generated MSI on your client VM workstation to test. But if you are deploying via SCCM and you have a client on that VM machine you will need to switch it to launch the installed MSI app via the sfttray, otherwise you will receive the error "Unable to initialize package information"
  
  
  There is a good technet article on this: http://support.microsoft.com/kb/2622617?wa=wsignin1.0

  You can use it for the configuration of launching of the app deployed via SCCM (ConfigMgr client) and an app installed via the msi (VAS client). Just create reg files for each and then use them to switch between the two environments to do your testing.

  • Proposed as answer by Never4saken Friday, December 14, 2012 10:31 PM
  • Unproposed as answer by Never4saken Friday, December 14, 2012 10:31 PM

  Wednesday, November 21, 2012 12:32 PM
• 

  

  0

  Sign in to vote

  Also see these articles:

  • http://blog.stealthpuppy.com/deployment/app-v-faq-20-what-are-the-deployment-methods-for-app-v/
  • http://blog.stealthpuppy.com/deployment/app-v-faq-13-how-do-i-configure-the-app-v-client-in-stand-alone-mode/
  • http://blog.stealthpuppy.com/virtualisation/app-v-errors-00000006-and-000d3002-when-adding-packages/

  ---

  
  

  Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.

  
  

  This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

  Thank you everybody for helping me out with this. Aaron: great articles and links.

  Monday, November 26, 2012 8:10 AM
• 

  

  0

  Sign in to vote

  I just open the package in the seq on my vm and copy down the .osd.

  Just remember don't run a 'Save As' or save the package once the testing is complete. Just reset you VM or revert back to a previous snapshot.

  You can install the generated MSI on your client VM workstation to test. But if you are deploying via SCCM and you have a client on that VM machine you will need to switch it to launch the installed MSI app via the sfttray, otherwise you will receive the error "Unable to initialize package information"
  
  
  There is a good technet article on this: http://support.microsoft.com/kb/2622617?wa=wsignin1.0

  You can use it for the configuration of launching of the app deployed via SCCM (ConfigMgr client) and an app installed via the msi (VAS client). Just create reg files for each and then use them to switch between the two environments to do your testing.

  
  
  

  • Edited by Never4saken Friday, December 14, 2012 10:34 PM

  Friday, December 14, 2012 10:33 PM