Answered by:
App-V 4.6: Run Client in Standalone mode

Question
-
Hi Guys,
Running client 4.6 SP2 on XenApp 6 on 2008 R2 with Sp1. Basically, my application estate is pretty static. Currently deploy applications that are sequenced by publishing an application in Citrix with the following command line example:
- sfttray \\unc to share\content\app\app.osd
This basically allows me to make changes to the .OSDs on the fly without having to do anything client side. our .OSD files generally launch scripts hence the reason for doing this. Basically, I had an issue where the App-V management server stopped accepting connections on port 554. All our .OSD files tell the client to look for the .SFT files on this port and hence we could not launch anything. Thing is, I pre-cache all these .SFT packages client side when the client boots up (which is every day). IS there any way to run the client and launch the applications without contacting the App-V management server ? Accessing the UNC to the OSD file is fine as this is outside of App-V and a pure CIFS access which was fine. It appears to me that the client checks back for newer versions of the .SFT and checks against what's in the cache. Thing is, i don't really need the client to do that as I ensure the cache is up to date with a server startup/scheduled scripts which runs and does the same.
Any ideas?
- Edited by Aaron.ParkerModerator Saturday, April 13, 2013 8:14 AM added App-V version to title
Wednesday, March 27, 2013 9:21 AM
Answers
-
It might be the case that you don't need any App-V Management Server (RTSP:554) communication at all, because you handle the publication via XenApp - so you may be able to configure all your RDS Servers as in "stand-alone" mode from an App-V perspective.
You may check Tim Mangan's DeployNPublish and/or his XenApp PublishinExtension tools at http://www.tmurgent.com/Tools/AppV4Tools.aspx
Falko
- Proposed as answer by znack Saturday, March 30, 2013 10:16 PM
- Marked as answer by Aaron.ParkerModerator Saturday, April 13, 2013 8:15 AM
Wednesday, March 27, 2013 9:49 AMModerator -
AaronParker has a blog post about that: http://blog.stealthpuppy.com/deployment/app-v-faq-13-how-do-i-configure-the-app-v-client-in-stand-alone-mode/ also linking some other articles (including a sample with GPOs which indicates the Registry settings)
Falko
- Marked as answer by Aaron.ParkerModerator Saturday, April 13, 2013 8:15 AM
Tuesday, April 2, 2013 11:02 AMModerator
All replies
-
It might be the case that you don't need any App-V Management Server (RTSP:554) communication at all, because you handle the publication via XenApp - so you may be able to configure all your RDS Servers as in "stand-alone" mode from an App-V perspective.
You may check Tim Mangan's DeployNPublish and/or his XenApp PublishinExtension tools at http://www.tmurgent.com/Tools/AppV4Tools.aspx
Falko
- Proposed as answer by znack Saturday, March 30, 2013 10:16 PM
- Marked as answer by Aaron.ParkerModerator Saturday, April 13, 2013 8:15 AM
Wednesday, March 27, 2013 9:49 AMModerator -
Thanks for the advice ;)
It seems that to run standalone mode you need to re-install the client with some options. Is it possible to leave my existing config in place yet somehow instruct the client not to look back at the App-V management server at all ?
Monday, April 1, 2013 11:42 AM -
Hello,
All those settings can be set via the registry.
Nicke Källén | The Knack| Twitter: @Znackattack
Monday, April 1, 2013 12:02 PM -
AaronParker has a blog post about that: http://blog.stealthpuppy.com/deployment/app-v-faq-13-how-do-i-configure-the-app-v-client-in-stand-alone-mode/ also linking some other articles (including a sample with GPOs which indicates the Registry settings)
Falko
- Marked as answer by Aaron.ParkerModerator Saturday, April 13, 2013 8:15 AM
Tuesday, April 2, 2013 11:02 AMModerator