App-V 4.6: Configuration when Using Proxy Servers with HTTP Streaming
How App-V uses proxy settings will vary depending on configuration values. The values related to proxy configuration can be found under the HTTP subkey of the App-V networking configuration in the registry here:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\ Client\Network\Http or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\ Client\Network\Http
Simply put, you can sum up the options into this simple table below:
| Value | ForceProxyAutoDetect | SkipProxyDetection |
| Use IE Proxy Settings | 0 | 0 |
| Auto-Detect Proxy Settings | 1 | 0 |
| Use No Proxy | Does not matter | 1 |
Specific registry entries related to HTTP proxy configuration and their descriptions are below:
ForceProxyAutoDetect
Data Type: REG_DWORD
Default Value: 0
Possible Values: 0-1
When this value is set to 1, it forces auto proxy detection instead of using IE proxy settings. Requires a restart of the App-V client service.
ConcurrentRequests
Data Type: REG_DWORD
Default Value: 4
Possible Values: 1 - infinite
If the value is greater than 1, divides the Http streaming request into concurrent sub-requests for parallel streaming. Value must be greater than zero. Recommended setting is 4 (default). Requires a restart of the App-V client service.
SkipProxyDetection
Data Type: REG_DWORD
Default Value: 0
Possible Values: 0 or 1
If the value is set to 1, App-V will not use IE proxy configuration. If 1, it overrides ForceProxyAutoDetect flag. Requires a restart of the App-V client service.
FailedProxyAutoDetectRetryTimeout
Data Type: REG_DWORD
Default Value: 60
Possible Values: varies
Don’t try auto-proxy-detection if it failed in last ‘x’ seconds for the current user. Where ‘x’ is the value of this flag. Requires a restart of the App-V client service.
ProxyCacheLife
Data Type: REG_DWORD
Default Value: 60
Possible Values: varies
The number of seconds the http proxy info is cached by App-V in memory for a user Requires a restart of the App-V client service.
You can get more specific information by enabling the SFTLIST.log file which helps with File/HTTP Streaming troubleshooting
Path : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration
(KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration if x64)
Value Name: TRAN DWORD
Value data: 0 to 6
0 : NEVER (Does not open/create log file)
1: ALWAYS, (Info that should always be emitted)
2: FATAL, (Serious system-wide errors )
3: ERROR, (Serious errors related to one user or app)
4: WARN, ( Print a Warning & keep on going)
5: INFO, (Informational stuff)
6: VERBOSE, ( Heavy-duty output for users)
7: DEBUG ( Even more output )
Logging for individual sub-modules can be handled by creating a dword value instead for each of the following Sub-Modules:
TRAN_HTTP - HTTP streaming traffic
TRAN_FILE - File streaming
TRAN_ASYN - requesting asynchronoze pacakge info such as FB2
TRAN_OOSR - Data header information
TRAN_CONF - configuration information
TRAN_PLCY - Policy information
TRAN_PACK - Package information
TRAN_MAIN - Main transport stream
The name of the log is SFTlist.log and its located under the install path of APPV (Ex: c:\Program Files\Microsoft Application Virtualization Client\sftlist.log)
This might help shed light on what specifically in the HTTP proxy communication is failing.