Name
Type
Valid Range
Default Value (hex/dec), additional info
ConnectTimeoutSec
Dword
0 – 32,767
0000003c/60. The time that an inactive client connection is allowed to remain idle. In other words, how long it can stay connected without a session.
CoreTimeoutSec-
0 –65,535
0000000a/10. How long the dispatcher should wait for a core process to accept a client connection.
EnableAuthentication
0-1
1 - If enabled, all client connection requests are authenticated
EnableAuthorization
1 - If enabled, all client streaming requests are authorized by comparing the client’s Windows credential with the ACL applied to the virtual application package
FcBlockSizeKb
64-16383
00000200/512, must be < FcMaxSizeMb. 0 means file cache is disabled
FcMaxSizeMb
128-16384
00000200/512, must be > FcBlockSizeKb. . 0 means file cache is disabled. The File Cache Maximum is the maximum amount of memory that each core process will allocate to stream files. Each client sessions uses at least File Cache Block Size while the file is streaming. When the client finishes streaming, the server eventually releases this memory. So a session can exist that is using no memory from the file cache. Additionally, each session may use more than the File Cache Block Size worth of file cache. The Metadata block in a sequencing may be very large (note that the Metadata block name is not related the server’s File Cache Block name) and the server always reads the entire block from the file before it sends it to the client (not a good idea). So if the server sees that a block in the sequencing is larger than the current File Cache Block Size, it will get more memory from the file cache and after it is done with the block shrink the file cache block back down the File Cache Block Size. So theoretically, the maximum number of clients a core process can support actively streaming is: (File Cache Maximum Size)/(File Cache Block Size) – (something for clients going over their File Cache Maximum Size).
LogFile
Reg_Sz
C:\Program Files\Microsoft App Virt Streaming Server\logs\sft-server.log
LogLevel
0 -5
3 (Warning) 0=transactions, 1=Fatal errors, 2=Errors, 3=Warnings, 4=Information, 5=Debug
MaxConnections
1-32767
000003E8/1000 - Server can support ~500 connections per Core process. 0=unlimited connections
NumCores
1-128
5 – The number of core processes that the dispatcher process should spawn on startup. The LWS is the maximum number of connections per core process. The HWS is the maximum number of connections for that instance of the SoftGrid system (that is the HWS divides the number of connections by the number of core processes)
PackageRoot
Reg_SZ
C:\Program Files\Microsoft App Virt Streaming Server\content\Server\content\
Absolute path to the root of the directory tree from which the server will read package files.
PackageDetectionIntervalSec
0 – 2,147,483,647
00000708/1800. 0=package detection is disabled. Time between new package detection searches down the packageRoot, measured from the completion of the previous search.
RtpTcpMinPort
1,025 – 65,535
0000c000/49152. Must be < RtpTcpMaxPort. Minimum TCP port number to use for client RTP and RTCP connections.
RtpTcpMaxPort
0000ffff/65535. Must be > RtpTcpMinPort. - Maximum TCP port number to use for client RTP and RTCP connections
RtspTimeoutSec-
1-60
0000003C/60. - timeout value for RTSP connections
ThreadPoolSize
1-255
00000032/50 - – The size of the thread pool (i.e. the number of threads) used to process client requests.
X509CertHash
No default value. – Identifies the certificate used for device authentication
Version
<version number>
Danny van Dam edited Revision 7. Comment: corrected type error
Danny van Dam edited Revision 6. Comment: added App-V version to tags
Steve TH - MSFT edited Revision 3. Comment: Added Location
Steve TH - MSFT edited Revision 1. Comment: Filled in value description for CoreTimeOutSec
Danny van Dam edited Revision 5. Comment: added note about that has changed in App-V v5
Re-edited. Please don't put 4.x here. These refer specifically to version 4.5. There is no Streaming Server (LWS) in 4.1.