Here’s a new App-V Knowledge Base article we published today. This one covers the %SFT_SOFTGRIDSERVER% environmental variable:
After modifying the %SFT_SOFTGRIDSERVER% environment variable, Microsoft Application Virtualization (App-V) packages may fail to load or may connect to an incorrect server. In some cases, you may receive a 0A-10000002 error ("The specified Application Virtualization Server could not be accessed. Try again in a few minutes. If the problem persists, report the following error code to your System Administrator") if the system variable references a non-existent or inaccessible server.
This is most common in scenarios where the intent is to test packages located on a development server with the intention of later copying the package to the production environment. In this case, changes to either the user or system environmental variable %SFT_SOFTGRIDSERVER% will not be used by the App-V client.
In the case of user variables (that is, adding a variable called SFT_SOFTGRIDSERVER under Control Panel\System\Advanced System Settings\Advanced tab\Environmental Variables...\User variables for username), App-V does not read the %SFT_SOFTGRIDSERVER% for individual users. Only the system variable is honored.
In the case of system variables, this setting is only reflected after a system reboot. This is necessary for the App-V client services and drivers to properly and consistently read these variables. Any changes made to the %SFT_SOFTGRIDSERVER% variable are not reflected until either the Application Virtualization client service is restarted or the client operating system is rebooted.
This behavior is by design.
There are several possible workarounds to enable this scenario:
User environmental variables override system environmental variables in Windows. Executables (including services and drivers) read environmental variables when they first launch, but do not subsequently re-read values.
For the most current information please see the following KB:
KB2552111 - Understanding the %SFT_SOFTGRIDSERVER% environmental variable in Microsoft App-V
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
The link in item 4 cannot be accessed without an an account and password.
We'll get that fixed, Rick.
Thanks for the heads up, should be fixed now.
I'd rate "Application Source Root / ASR" first in the list of workarounds, because it offers the most flexible usage. Because it does not require a machine nor service restart it can be configured quite dynamic (like: Notebook: Resume action in a branch office). Keep in mind that SFT_SOFTGRIDSERVER and ApplicationSourceRoot are machine-wide settings (not user specific)
A common misconcept is trying to use SFT_SOFTGRIDSERVER in the Publishing Server URL. That doesn't work
I'll second kirk_tn's comment - ApplicationSourceRoot should be the primary method of directing clients to the streaming source.
I'll go as far as to recommend avoiding the use of SFT_SOFTGRIDSERVER whereever possible.
Interesting article but I usually use boxedapp for it....