XA Client speed optimization

If your XA Client is not performing as fast as expected, there are some tips to increase the speed of the client performance.

Tip 1

Remove unneeded notification plugins. XA Client installs the most common notifications by default and removing unused plugins from the notifications registry key can speed up loading of the XA Client.

The following is a list of entries you may find in HKLM\Software\HealthCast\eXactACCESS\notification. If you are not using the feature or using a mode where the feature would not apply, delete the entire value from the registry. Changes will take affect upon the next reboot.

• XADriveMapping.clsXALoginNotification- XA Drive mapping for Kiosk Mode. This is an optional feature that required specific configuration to be leveraged. If you are not using XA Drive Mapping in Kiosk Mode or are using Standard Mode (this feature only applied to Kiosk Mode) remove this value.
• xaMoTD.clsNotify - XA Message Of the Day. If you do not wish to configure a message of the day, this value can be safely removed.
• XAAutoLaunch.clsAutoLaunch- XA AutoLaunch. If you do not wish to configure any autolaunch applications, you can safely remove this. Removing this will not impact TFA autolaunching Epic.
• logoffCleanup.clsEventNotify - XA Logoff Cleanup. If you do not wish to use Logoff Cleanup or the watchlist, you can safely remove this value.

Tip 2

For Kiosk Mode systems, to speed up the time between the kiosk user login until the ExactAccess Privacy Shield appears, modify the following registry settings:

Remove any references to any HealthCast software from the Windows Run key, including:
[HKLM\Software\Microsoft\Windows\CurrentVersion\Run]
"xahid_kiosk.exe"="C:\Program Files (x86)\HealthCast\eXactACCESS\xahid_kiosk.exe"
"hciNetStatus.exe"=""C:\Program Files (x86)\HealthCast\eXactACCESS\hciNetStatus.exe" hcikmlock"
"watchforlogoff.exe"="C:\Program Files (x86)\HealthCast\eXactACCESS\watchforlogoff.exe"
"usernotification.exe"="C:\Program Files (x86)\HealthCast\eXactACCESS\usernotification.exe"

Modify the Windows Userinit value to include xaClientStarter.exe. This will start the ExactAccess Client immediately after login instead of waiting for Windows logon to process the contents of the 'Run' key.
[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Userinit"=""C:\Windows\system32\userinit.exe,C:\Program Files (x86)\HealthCast\eXactACCESS\xaclientstarter.exe"

Tip 3

If you are not using the XA Toolbar Desktop, modify the registry key:
[HKLM\Software\HealthCast\eXactACCESS\override]
"AutoLaunchTBDesktop"=dword:00000000

This setting is independant of the xaAutoLaunch from the 'notification' registry key.

Tip 4

Removing the XA status messages can increase performance when autolaunching Epic. Status messages are the semi-transparent message boxes displayed as after logging into ExactAccess as user context is loaded.

To hide these message boxes, change this registry value:
[HLKM\Software\HealthCast\eXactACCESS]
"ShowXAStatusMessages"=dword:00000000