Enable Notification in a Windows Endpoint During Application Change

Using EnableAppChangeNotification, an svservice parameter, notifications can be presented to an end user in the Windows endpoint when the state of an application delivery (unassign or uninstall and change in CURRENT marker or swap) changes. These notifications give end users time to save work and prepare for the change thus improving user experience.

EnableAppChangeNotification is of type REG_DWORD and must be addded to HKLM\SYSTEM\CurrentControlSet\Services\svservice\Parameters in the Windows endpoint.

In the local copy mode where App Volumes Manager is used to manage the application lifecycle, changes in application delivery for the end user at the Windows endpoint occur when an application is unassigned or when the package CURRENT marker changes. In the standalone mode, where device management tools are used instead of App Volumes Manager, changes in application delivery for the end user occur during an application uninstall or swap. This parameter can be used for such changes and help the end user prepare for the change.

When the parameter is enabled and the application remains launched for any of the delivery changes then notifications are displayed to the end user. If the application is not actively used, then no notifications are displayed even when the parameter is enabled.

For more information about application delivery to Windows endpoints, see Deliver App Volumes Applications to Windows Endpoints.

Parameter behavior during application unassign or uninstall

When the parameter value is 0 or the parameter is not added:

• No notifications are presented to the end user.

• When a delivered application is unassigned in App Volumes Manager, the Windows endpoint in local copy mode retrieves these changes after a periodic synchronization with App Volumes Manager. After the change in assignments are retrieved, the application becomes unavailable to the user at the subsequent login.

  In the Standalone mode, after the command to uninstall is run, the application is unavailable to the user at the subsequent user login.

When the parameter value is 1:

If the application remains launched during unassign or uninstall, then one of the following occurs:

• An Application Removal dialog box is displayed. The end user can either save the work and close the application or allow the application to automatically close after the timer has elapsed. In either case, the application is removed from the Windows endpoint.


• Sometimes during uninstall, a system reboot might be required. The end user is presented with A System Reboot Required dialog box. Similar to application removal, the end user can either save the work and immediately restart the system or wait for the system to automatically restart after the timer has elapsed. After the system restart, the application is uninstalled.

Parameter behavior during application swap or change in package CURRENT marker

When the parameter value is 0 or the parameter is not added:

• No notifications are presented to the end user.

• When the CURRENT marker of the package changes in App Volumes Manager, the Windows endpoint in local copy mode retrieves these changes after a periodic synchronization with App Volumes Manager. After the changes are retrieved, the new application package is available to the user at the subsequent login.

  In the Standalone mode, when commands are run to deliver a new application replacing the existing application (swapped), the new application is available to the user at the subsequent user login.

When the parameter value is 1:

If the application remains launched during swap or CURRENT marker change, then one of the following occurs:

• An Application Removal dialog box is displayed. The end user can either save the work and close the application or allow the application to automatically close after the timer has elapsed. In either case, the existing application is removed from the Windows endpoint and the new application is delivered.


• Sometimes during the swap, a system reboot might be required. The end user is presented with A System Reboot Required dialog box. Similar to application removal, the end user can either save the work and immediately restart or wait for the system to automatically restart after the timer has elapsed. After the restart, the existing application is uninstalled and the new application is installed.