Display client-side notification area battery status in desktop sessions

Display client-side notification area battery status in desktop sessions

book

Article ID: CTX235140

calendar_today

Updated On:

Description

Feature Description
In previous versions of XenApp & XenDesktop, users working from a laptop and in a full-screen desktop session would not be aware of the laptop’s battery status or remaining battery level.
This could lead to a loss of work/productivity for users when the laptop unexpectedly shuts down or goes into hibernation.
Changes introduced in 7.18 version VDAs and Receiver for Windows 4.12 support the redirection of the client-side battery status into the Notification Area (System Tray) of the desktop session.

Feature Limitation
The battery status will not be displayed in sessions where Local App Access is enabled.

Feature Requirements

  • Minimum: XenApp & XenDesktop 7.18 VDAs
  • Minimum: Receiver for Windows 4.12
  • A client device that can display battery status in the Notification Area
  • This feature is enabled by default.


Feature Architecture and Workflow
On a supported client system (e.g. RfWin 4.12 installed on a latop), Receiver subscribes to the device’s battery status. When a battery status event is triggered (for either BatteryState or BatteryCharge), the update is sent to the VDA over the MRVC. The VDA receives the status update and displays the event as a custom Notification Area icon or popup in the desktop session.

User-added image

Feature Troubleshooting
Both Client and Host need to have the capability to transmit battery state changes and respectively receive the changes. An old host with new client will not handshake the capability and won’t transmit data.

Client-side troubleshooting
Feature activity is tracked on the client-side using CDFControl. Filter on vdmrvc in client-side CDF traces.

VDA-side troubleshooting
Feature activity is tracked on the VDA-side using CDFControl & Windows Event viewer.
CDF traces:
Filter on cmp, mrvc, and wfshell. Look for initialization in wfshell, and handshake in mrvccapabilities.
Windows Event logging:
Search for mrvcsession and vdoevents events sources.
Make sure that Local App Access is not enabled for the Citrix session. Traces where LAA is enabled, you will see HPC_ICA_Engine: "Reverse Seamless is enabled in ICA Engine."