Notification Plug-in Configuration

Notification Plug-in Configuration

eXactaccess has several plug-ins that can be enabled for handling special cases. Each of these plug-ins must be configured manually to provide the desired results.

Asynchronous Notification plug-in

Adding the plug-in to the registry requires adding a new name/value pair to the following location.

HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\ExactAccess\notification

HCIAsyncNotify.clsNotify = "eXactACESS Asynchronous Event Notification"

In addition, any plug-in that should be run by this plug-in should be configured in (or moved to) this location

HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\ExactAccess\notification\async

There are specific plug-ins that should only be run synchronously:

• xaDriveMapping
• HCIAsyncNotify
• vcState
• webConnect

Other plug-ins that can be run asynchronously are:

• XAAutoLaunch
• HCINotifyappSense
• psNotify
• xaMoTD
• RIRunOnce

Run-Once Notification plug-in

Adding the plug-in to the registry requires adding a new name/value pair to the following location.

HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\ExactAccess\notification

RIRunOnce.clsNotify = "Run a list of applications after login of the XA client"

To run this plug-in asynchronously, remove it from notification, and add a new name/value pair to the following location.

HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\ExactAccess\notification\async

RIRunOnce.clsNotify = "Run a list of applications after login of the XA client"

Configuring the list of applications to run one time

Features

• Supports environment variable expansion in app path, and parameters
• Supports app path surrounded by single or double quotes
• If no quotes, the first space will delineate parameters to be passed to the app
• App launch order is not guaranteed and may be based on registry value create order
• App is deleted from the list after it is launched, so subsequent user logins will not trigger a new launch of the app

Create the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\ExactAccess\RunOnce
Bitmask value meanings

• 0x80 is use shell execute (default if value not present) - will search path environment to launch app if no path specified
• 0x40 is use create process
• 0x02 is launch hidden
• 0x01 is wait for program terminate (use with caution - if not in async mode, XA will be blocked launching the app)

Examples

• 01: reg_sz = 40,%windir%\notepad.exe %username%
• 02: reg_sz = 40,"%windir%\notepad.exe" %username%
• 03: reg_sz = 40,'%windir%\notepad.exe' %username%
• 04: reg_sz = 80,%windir%\notepad.exe %username%
• 05: reg_sz = 80,"%windir%\notepad.exe" %username%
• 06: reg_sz = 80,'%windir%\notepad.exe' %username%
• 07: reg_az = notepad.exe

As shown for 07 above, default to using Shell Execute with app visible, and not waiting for app close before launching another