SAS PCE Windows Services Startup Recommendations
The following section describes the recommended configuration for various SAS PCE Windows services. Some of the below mentioned SAS services are recommended to run on a single instance only to avoid conflict among multiple instances.
| Windows Service Name and Description | Primary Server | Secondary Server | DR Server |
|---|---|---|---|
| *BlackShield ID Auto Provisioning - Self-Enroll token(s) to user(s) based on rule(s) created within Auto-Provisioning. Occurs at configured interval | Running (Automatic) | Stopped (Manual) | Stopped (Manual) |
| *BlackShield ID Monitor - Checks SAS every 5 minutes to determine if any alerts are configured, user/token association integrity, and performs archiving functionality | Running (Automatic) | Stopped (Manual) | Stopped (Manual) |
| BlackShield ID Proxied Source Server - Listens for incoming connections from SAS LDAP Sync agent(s) to maintain a local copy of remote user sources (LDAP/SQL) | Running (Automatic) | Running (Automatic) | Running (Automatic) |
| BlackShield ID Remote Logging Service - Dispatches logging events to listening logging agents | Running (Automatic) | Running (Automatic) | Running (Automatic) |
| *BlackShield ID Reporting Service - Processes all reports scheduled to run in the SAS management console | Running (Automatic) | Stopped (Manual) | Stopped (Manual) |
| BlackShield ID SIM Service - Manages Token provisioning to mobile devices | Stopped (Disabled) | Stopped (Disabled) | Stopped (Disabled) |
| *SAS HA Controller Service - Provides high availability support to MySQL database | Stopped (Disabled) | Stopped (Disabled) | Stopped (Disabled) |
| *SAS LDAP Integrator - Integrates LDAP users from configured LDAP directories into the local database | Stopped (Disabled) | Stopped (Disabled) | Stopped (Disabled) |
*: Only single instance can run at a time. To improve performance, these services can be disabled when not in use.
Note
All SAS services are installed on the server via Local System account.
