HealthCast

Install the server certificate or verify that the certificate is present. (The certificate must have the Fully Qualified Domain Name as the subject field.)

User and Admin Groups should be created on the AD and users added.

Execute the PowerShell script (C:\Program Files (x86)\HealthCast\SSO Audit Monitor\Config\SsoAuditMonitorSetup.ps1) on the server that will be hosting the SSO Audit Monitor application. This must be run as an administrator. (The PowerShell script sets up the administration tools using the FQDN from the Certificate subject field. It also opens ports 5000 on the server firewall to allow access.)

Locate the Audit Database for your installation of ExactAccess on the SQL server and note the name:

1. Before executing the provided SQL script (C:\Program Files (x86)\HealthCast\SSO Audit Monitor\Config\CreateDb.sql), change the name of the database in the first line to the name of your Audit database. (The line you will be changing is “USE [AUDIT]” – change the word “AUDIT” to the name of your actual Audit Database, whatever you configured it to be.)

Using the SQL Server Manager, grant permissions to the AD user account selected (ExactAccess Active Directory user account) or the account created for the Environment Prerequisites.

1. Select the Security Folder right click>New>Login

2. Fill in the Login Name. It will be the Active directory user requested in the Environment Prerequisites or the account created for the Environment Prerequisites.

3. Select User Mapping. Select the Audit Database and the roles will be db_datareader db_datawriter. (If using Windows Authentication the db_owner permission should be set with the ExactACCESS configuration. The account will not require the additional permissions.)

Using File Explorer, browse to C:\Program Files (x86)\HealthCast\SSO Audit Monitor

1. Locate the appsettings.json

2. Open with a text editor.

3. Change the Server=servername

4. Change the Database=databasename

5. Save the changes and close.

In Services, set the Log On As to the AD user who has permission to access the SQL database.

Start the service.