Optimize XA Client Speed

Prev Next

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

Tip 1 - Remove Unnecessary Notification Plugins

XA Client installs the most common notifications by default and removing unused plugins from the notification registry key can speed up loading of the XA Client. The following is a list of entries you may find. If you are not using the feature or using a mode where the feature would not apply, delete the entire value from the registry. Each value can safely be removed individually as needed.

ℹ️ All Changes will take affect upon the next reboot.

Registry Path

HKLM\Software\HealthCast\eXactACCESS\notification

Values Under this Path

Registry Value Name Notification Feature Purpose
logoffCleanup.clsEventNotify XA Logoff Cleanup If you do not wish to use Logoff Cleanup or the watchlist, you can safely remove this value.
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.
XADriveMapping.clsXALoginNotification XA Drive mapping for Kiosk Mode This is an optional feature that requires specific configuration to be leveraged. If you are not using XA Drive Mapping in Kiosk Mode or are using Standard Mode, remove this value. This feature only applies to Kiosk Mode.
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.

Tip 2 - Windows Run References (Kiosk Mode)

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.

Registry Path

[HKLM\Software\Microsoft\Windows\CurrentVersion\Run]

Values Under this Path

Value Name Type Value Data
xahid_kiosk.exe STRING "C:\Program Files (x86)\HealthCast\eXactACCESS\xahid_kiosk.exe"
hciNetStatus.exe STRING ""C:\Program Files (x86)\HealthCast\eXactACCESS\hciNetStatus.exe" hcikmlock"
watchforlogoff.exe STRING "C:\Program Files (x86)\HealthCast\eXactACCESS\watchforlogoff.exe"
usernotification.exe STRING "C:\Program Files (x86)\HealthCast\eXactACCESS\usernotification.exe"

Additional Setting

Modify the Windows Userinit value to include xaClientStarter.exe. This will start the XA Client immediately after login instead of waiting for Windows logon and process the contents of the 'Run' key.

Registry Path

[HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]

Value Under this Path

Value Name Type Value Data
Userinit STRING "C:\Windows\system32\userinit.exe,C:\Program Files (x86)\HealthCast\eXactACCESS\xaclientstarter.exe"

Tip 3 - Disable XA Toolbar

If you are not using the XA Toolbar Desktop mode, you can disable it. This setting is independent of the xaAutoLaunch from the 'notification' registry key.

Registry Path

[HKLM\Software\HealthCast\eXactACCESS\override]

Value Under this Path

Value Name Type Value Data
AutoLaunchTBDesktop DWORD 0

Tip 4 - Remove XA Status Messages

Removing the XA status messages can increase performance when auto-launching Epic. Status messages are the semi-transparent message boxes displayed after logging into ExactAccess as the user context is loaded. To hide these message boxes, update the following registry value:

Registry Path

[HLKM\Software\HealthCast\eXactACCESS]

Value Under this Path

Value Name Type Value Data
ShowXAStatusMessages DWORD 0