Logging Overrides - Server
For components utilizing the client logging service, and being configured with an application XML and INI file pair, these logging configurations can now be overridden by adding keys to the registry. This allows logging to be configured by group policy per machine, or by using remote registry edit on a specific workstation to aid in troubleshooting issues in an organization.
Overrides will appear as keys for each application under the following registry:
HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\Logging
The information present in any given INI file may be added to the registry.
Create the application registry name:
HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\Logging\example.exe
Create a debug and event log key under this parent:
HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\Logging\example.exe\debug HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\Logging\example.exe\eventlog
Then, create the settings for each key:
HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\Logging\example.exe\debug LogFileSizeInMeg=dword:00000003 MaxMemoryCacheLogLines=dword:000003e8 critical=dword:00000001 information=dword:00000000 methodEntryExit=dword:00000000 warning=dword:00000001
HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\Logging\example.exe\eventlog auditSuccessFail=dword:00000001 critical=dword:00000001 warning=dword:00000001 information=dword:00000001
Presently, the following applications may be configured:
Tip
The server may also contain registry keys for client components.
HealthCastAuditServer.exe
ExactAccessServer.exe
hcideploy.exe
hchidserver.exe
hcremotesessiondirectory.exe
HCServerUpService.exe