The svservice component of App Volumes agent is used for communicating system events, such as computer startup, login, logout, and shutdown, with the App Volumes Manager. You can configure this component with registry values at HKLM\SYSTEM\CurrentControlSet\Services\svservice\Parameters.
Policy rules for backup svservice log files
If a backup svservice log file meets either of these policy rules, the log file is deleted:
-
If the aggregate size of all the backup log files is greater than a designated number, then svservice starts the deletion from the oldest backup log file until the aggregate size is lower than the designated number.
To set the designated aggregate size of all backup log files, you can use the
BackupLogFileSizeInKBparameter. -
If a backup log file is older than the designated number of days, the log file is deleted.
To designate the number of days for the log deletion policy, you can use the
BackupLogFileDaysparameter.
| Parameter | Type | Description |
|---|---|---|
| BackupLogFileSizeInKB | REG_DWORD | The aggregate size of all svservice backup log files.
If the aggregate size of all backup log files is greater than the value of this parameter, svservice starts the deletion from the oldest backup log file until the aggregate size is lesser than the value of this parameter.
The default value of this parameter is 768000 (750MB) and the maximum value is 3584000 (3500MB).Note: If the parameter is set to 0 or greater than the maximum value, svservice uses the default value as the value of this parameter. |
| BackupLogFileDays | REG_DWORD | The maximum age of svservice backup log files.
If an svservice backup log file is older than the value of this parameter, the backup log file is deleted.
The default value of this parameter is 15 days. |
| CaptureFTA | REG_DWORD | When this parameter is activated, file type association metadata is captured during packaging the application.
To deactivate the capture of metadata, value of this parameter must be set to 0 in the packaging virtual machine before packaging the application.
By default, this parameter is activated and file type association metadata is captured. |
| CleanSystemWritable | REG_DWORD | Use this parameter to either allow svservice to clear any changes made on the system Writable Volume or retain the changes after a restart.
If set to 1, system Writable Volume is cleared after a restart.
If set to 0, system Writable Volume is not cleared after a restart and the changes are retained.
By default, the value of this parameter is 0.
Location of the system Writable Volume is C:\{00000000-0000-0000-0000-000000000000}. |
| CommandLineAppDelivery | REG_DWORD | This parameter can be used to allow real time delivery of an application package to an end user using command line options in App Volumes agent.
Supported values of this parameter are 0 and 1. By default, the value of the key is 1 (enabled).For an understanding of the command line delivery behavior, see command line Delivery of Applications in App Volumes. |
| ConnectTimeOutMs | REG_DWORD | Defined in milliseconds for server connection requests. If a connection request takes longer than this timeout value, the request is canceled. The default is 10 seconds. |
| DelayVirtualizationType | REG_DWORD | Defers application virtualization at end user login and helps in improving the user login time.
Values of this parameter are as follows:
2. |
| DeliverAppsAtLogin | REG_DWORD | Use this parameter to skip delivery of applications at login. This parameter can be used on computers that receive on demand delivery when user assignments already exist for other computers on the same App Volumes Manager.
By default, this parameter defaults to 1 and applications are delivered to the end user during login.
To use this parameter, an administrator must manually add this parameter to svservice. If the value of this parameter is set as 0, applications are not delivered to the end user at login.
If the parameter has a non-zero value, then applications are delivered to the user at login.For more information about the package delivery modes, see Understanding Package Delivery Modes in App Volumes. For information about published applications on demand delivery, see Configure Horizon 8 for Published Applications on Demand Delivery section in the Windows Desktops and Applications in Horizon 8. |
| Direct | REG_DWORD | Use this parameter to install Omnissa App Volumes agent directly on Windows endpoints when you want to deliver applications in the Standalone mode. In this mode, Windows endpoints such as physical desktops, laptops, and cloud desktops (Windows 365 Cloud PC) can be used. The values of this parameter are as follows:
For more information about the Standalone mode, see Choose Your App Volumes Deployment Model section in the Omnissa App Volumes Installation Guide, version 2509 and later at Omnissa Product Documentation. |
| DisableAutoStartServices | REG_DWORD | Use this parameter to not start services automatically when application virtualization starts.
If set to 1, when application virtualization starts, services belonging to the application do not start automatically.
By default, the value of this parameter is 0. |
| DisableRunKeys | REG_DWORD | Use this parameter to deactivate Run key execution.
If set to 1, the application's Run key entries do not start automatically.
By default, the value of this parameter is 0. |
| DisableAppServicesList | REG_DWORD | Application services added to this multi-string registry value are not started when the application package is virtualized.
This parameter is located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svservice\Parameters. |
| DriveLetter | REG_SZ | To assign a specific drive letter to a Writable Volume, use this parameter. Note: To use this parameter, ensure that you have configured DriveLetterSettings to DRIVELETTER_ASSIGN_WRITABLE. DriveLetterSettings is an svdriver parameter. For more information about the registry value, see the Driver Letter Settings in Configuration of svdriver.
A Writable Volume can have any drive letter from C: to Z:. The allowed formats for a drive letter are as follows: "E", "E:", "e", or "e:".
The drive letter of a Writable Volume can be updated. For example: A Writable Volume is assigned a drive letter, D:. Use this parameter to assign the drive letter, E:. As a result, the drive letter for the Writable Volume is updated from D: to E:.
If no drive letter is assigned, App Volumes assigns any available drive letter to the Writable Volume, starting from C:. |
| DomainNameWaitTimeOut | REG_DWORD | Defined in seconds how long to wait for the computer during startup to resolve from the registered domain name. On machines that are not joined to any domain, you can set the value to 1 for faster login. The default is 60. |
| EnableAppChangeNotification | REG_DWORD | This parameter controls whether end users receive notifications when the state of an application delivery (unassign or uninstall and change in CURRENT marker or swap) changes at a Windows endpoint. Providing notifications improves the user experience by giving end users time to save work and prepare for the change.When the parameter value is 1 or not added, notifications are presented to the user at the Windows endpoint. When the parameter value is 0, no notifications are presented to the end user. By default, the parameter value is 1.For more information about parameter behavior, see Enable Notification in a Windows Endpoint During Application Change. The other related svservice parameters which can be used with this parameter to enhance user experience when presenting notifications in the Windows endpoint are: EnableAppChangeTimer, EnableAppChangeAutoClose, and EnableAppChangeTimerDuration. For information about these parameters, see the other rows in this table. |
| EnableAppChangeTimer | REG_DWORD | This parameter controls whether notifications display a countdown timer. When enabled, the timer is also displayed in the notification and indicates to the end users how much time remains before the change in state of application delivery takes effect. As a result, end users get time to plan their work accordingly. When this parameter is set to 1, a countdown timer is displayed in the notification. When set to 0 or not added, the notification appears without a timer. By default, the value of this parameter is 0.To use this parameter, configure the parameter in the Windows endpoint before application delivery state changes and ensure that the EnableAppChangeNotification parameter is enabled. The duration of the countdown is controlled by the EnableAppChangeTimerDuration parameter. |
| EnableAppChangeAutoClose | REG_DWORD | This parameter controls whether applications automatically close when the application notification timer expires. When enabled, the affected applications are automatically closed without user intervention after the countdown reaches zero. This ensures that application delivery state changes can proceed without waiting for end user action. When this parameter is set to 1, applications close automatically when the timer expires. When set to 0 or not added, applications remain open even after the timer expires, and end users must manually close them. By default, the value of this parameter is 0.To use this parameter, configure the parameter in the Windows endpoint and ensure that both EnableAppChangeNotification and EnableAppChangeTimer are enabled. |
| EnableAppChangeTimerDuration | REG_DWORD | This parameter specifies the duration of the countdown timer displayed in the application notification. The value indicates how much time end users have to save their work and prepare before the change of state in application delivery occurs. Setting an appropriate duration ensures end users have sufficient time to complete their work while maintaining timely application updates. Configure this parameter on the Windows endpoint to adjust the notification duration based on your organization's policies and end user requirements. The value of this parameter is specified in minutes. By default, the value is 90 minutes. The maximum allowed value is 120 minutes. This parameter takes effect only when configured in the Windows endpoint and EnableAppChangeTimer is enabled (1).Note:
|
| EnablePIILogging | REG_DWORD | Use this parameter to control data obfuscation in logs for App Volumes agent and Application Capture command line Program. When this parameter is set to 0, PII data is obfuscated in the logs and when the parameter is set to 1, all PII data is visible in the logs. By default, the value of this parameter is 1. This means that data obfuscation is turned off and all PII data is visible in the logs.This parameter can be provided only as a command line option at the time of install or upgrade. For more information about how to use this parameter, see the Obfuscate PII Data in App Volumes section in the App Volumes Install Guide at Omnissa Product Documentation. |
| HidePopups | REG_DWORD | Use this parameter to hide pop-up messages displayed by svservice.
If set to 1, svservice.exe does not display pop-up messages.
By default, the value of this parameter 0. |
| LogFileSizeInKB | REG_DWORD | The size of the log file before rotating the log file.
The default value of this parameter is 15360MB (15MB) and the maximum value of this parameter is 51200 (50MB).
Note: If the parameter is set to a value greater than the maximum value or 0, svservice uses the default value as the value of this parameter. |
| LogLevel | REG_DWORD | Use this parameter to control the logging of entries in the logs for App Volumes agent and Application Capture command line Program. When this parameter is set to 0, no entries are logged in the log files but continue getting logged in the console. When the parameter is set to 1, all entries are logged in the log files and console. By default, the value of this parameter is 1. This means that logging is turned on and all entries are logged in the log files and console.This parameter can be provided only as a command line option at the time of install or upgrade. For more information about how to use this parameter, see the Obfuscate PII Data in App Volumes section in the App Volumes Install Guide at Omnissa Product Documentation. |
| MaxDelayTimeOutS | REG_DWORD | The maximum wait for a response from the App Volumes Manager, in seconds. If set to 0, the wait for response is forever. The default is 300 seconds (5 minutes). |
| MSIXMgrToolPath | REG_SZ | appcapture.exe packagemsix is the command used for generating an App Volumes package for an MSIX application. To generate the package, the executable of the MSIX Manager tool must be placed in the capture virtual machine. appcapture.exe runs the executable of the MSIXMGR tool to unpack the MSIX application into a VHD or any of the specified formats. When the command runs for the first time, the location of the MSIX Manager tool executable is stored in this registry value. When the command is run a subsequent time:
For more information about the appcapture.exe packagemsix command, see Windows Command-Line Arguments for the App Volumes Application Capture Command-Line Program. |
| NoRebootAfterCapture | REG_DWORD | Use this parameter to prevent the agent machine from rebooting during finalizing the packaging of an application. This parameter can be used only when packaging applications into VHD format. The parameter must be added to the agent machine prior to packaging, and the value must be configured to 1. After adding the parameter, the agent machine must be rebooted.As a result, at the time of finalizing the packaging, the agent machine does not reboot and continues to complete the packaging process successfully. If the application getting captured has a requirement for machine reboot during the installation process, this reboot is not affected. Adding and configuring the parameter is optional as skipping the agent machine reboot depends on your packaging requirements. By default, the parameter does not exist. The current behavior continues where the agent machine reboots to complete the packaging process. For more information about the packaging process, see Package an App Volumes Application. |
| OnDemandLaunchDelayedTimeout | REG_DWORD | This parameter can be used to control the time at which a specific pop-up message is displayed when delivering an App Volumes on-demand application to the end user.
When an end user clicks a shortcut, App Volumes agent communicates with App Volumes Manager for application delivery, and the following message is displayed to the end user: App delivery in progress. Please wait while your application is delivered.. If this parameter does not exist and the application delivery takes more than 3 seconds, this message is displayed to the end user.
To avoid showing this message to the end user, you can add this parameter and configure the value of the parameter to 180 seconds or higher. Note: By default, the timeout for application delivery is 180 seconds.
After application delivery, when the application is getting launched for the first time, the following message is displayed: App delivery in progress. Your application is starting.. This message display stops as soon as the application is launched. |
| PackageModeLocal | REG_DWORD | Use this parameter to install App Volumes agent in the Local Copy package access mode. When the Windows endpoint is in this mode, MSI-wrapped VHD packages are downloaded on the endpoint, locally cached, virtualized, and the application is delivered to the end user. The user can access applications even when the endpoint goes offline. The Windows endpoint connects with App Volumes Manager, which is used for application management. Setting this parameter to 1 installs the agent in Local Copy package access mode.By default, the value of this parameter is 0 and App Volumes agent is installed in the Shared Storage package access mode.For more information about the package access modes, see see the Application Delivery Modes with App Volumes Manager section in the Omnissa App Volumes Installation Guide, version 2509 and later, at Omnissa Product Documentation. |
| ProvisioningCompleteTimeOut | REG_DWORD | Defined in seconds to keep trying to contact the App Volumes Manager after provisioning is completed. The default is 120. |
| RebootAfterDetach | REG_DWORD | Use this parameter to automatically restart the agent computer after the end user logs out.
If set to 1, the agent computer restarts automatically after the end user log out.
By default, the value of this parameter is 0. |
| ResolveTimeOutMs | REG_DWORD | Defined in milliseconds for name resolution. If resolution takes longer than the timeout value, the action is canceled. The default is 0, which waits for completion. |
| ReceiveTimeOutMs | REG_DWORD | Defined in milliseconds to receive a response to a request. If a response takes longer than this timeout value, the request is canceled. The default is 5 minutes. |
| SendTimeOutMs | REG_DWORD | Defined in milliseconds for sending requests. If sending a request takes longer than this timeout value, the request is canceled. The default is 30 seconds. |
| VolumeExpansionTimeoutInMs | REG_DWORD | Specifies the maximum time, in milliseconds, svservice waits for the diskpart command to expand a Writable Volume and then times out.
The default value of this parameter is 60000ms and this parameter can be configured to override the default value. |
| WaitInstallFonts | REG_DWORD | Defines how long to wait in seconds for fonts to be installed. The default is to not wait for completion. |
| WaitUninstallFonts | REG_DWORD | Defines how long to wait in seconds for fonts to be removed. The default is to not wait for completion. |
| WaitForFirstVolumeOnly | REG_DWORD | Defined in seconds, only hold logon for the first volume. After the first volume is complete, the remaining are handled in the background, and the logon process is allowed to proceed. To wait for all volumes to load before releasing the logon process, set this value to 0. The default is 1. Note: When WaitForFirstVolumeOnly parameter is set to 0, svservice implicitly sets the DelayVirtualizationType parameter value to 0. |
Was this page helpful?