Solution Intelligence
Active Roles supports Solution Intelligence to monitor the web application and detect performance issues. Active Roles administrators can enable or disable the Solution Intelligence feature that supports intelligent collection for Active Roles solution usage data.
The telemetry data that is captured for Active Roles is sent to the Azure portal and can be accessed by the development team for analysis. In addition to the general telemetry data that is collected by Microsoft Azure, Solution Intelligence in Active Roles helps captures data about the Active Roles Language Pack usage by customers, referred to as Language Pack telemetry and the area of bugs and issues referred to as the diagnostic telemetry.
The Language Pack telemetry provides insights for the following:
You can enable or disable Solution Intelligence by using Configuration Center. For information on managing Solution Intelligence for Active Roles, see Enabling or disabling Solution Intelligence.
Enabling or disabling Solution Intelligence
After installing Active Roles on a computer, the Solution Intelligence setting is not enabled by default. To allow the Solution Intelligence to retrieve telemetry data of Active Roles, you can use Configuration Center to enable the Active Roles Solution Intelligence.
NOTE: Active Roles Service must be installed and running on the system for the Solution Intelligence feature to be.
To manage the Solution Intelligence settings
-
On the Dashboard page in the Configuration Settings main window, click Solution Intelligence.
-
On the Solution Intelligence page, select Enable Solution Intelligence.
-
Click Save.
The Solution Intelligence settings are configured successfully and a success message is displayed.
NOTE: The changed status may take approximately up to 30 minutes to reflect during which, the telemetry may still be sent until new setting is applied to the website. You may reset IIS if you want the settings to be applied immediately.
Configuring gMSA as an Active Roles Service account
Active Roles Configuration Center enables you to configure the gMSA as a service account. Before you configure a gMSA as an Active Roles Service account, the following prerequisites must be met:
-
The Key Distribution Services (KDS) Root Key must be available in the KDS service on the Domain controller.
-
The computers and groups that have servers with Active Roles Service installed on them, must be added to the gMSA.
-
The gMSA must be available in the Local Administrators group where the Active Roles service is installed and in the built-in Administrators group of the domain.
-
The gMSA must have an SQL login with db_Owner permission for Active Roles database.
-
The gMSA account name must be unique across domains.
NOTE: Exchange operations cannot be performed on the on-premises Exchange Server environment using the gMSA. For example, Remote mailbox, User mailbox, or Contact.
For information on creating a new database see Configuring the Active Roles Service account to use a gMSA.
For more information on managing gMSA accounts see Managing Group Managed Service Accounts in the Active Roles User Guide.
Configuring the Active Roles Service account to use a gMSA
After completion of Active Roles Setup, the Configuration Center enables you to create an instance of the Administration Service to get the Administration Service ready for use.
To configure the Administration Service account to use a gMSA as the service account during initial configuration
-
Start Configuration Center on the computer running the Administration Service.
You can start Configuration Center by selecting Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For more information, see Running Configuration Center.
-
In the Configuration Center main window, under Administration Service, click Configure.
-
On the Administration Service page, in the Service Account area, click Browse.
-
In the Select User or Service Account dialog, click Object Types.
-
In the Object Types dialog, select the Service Accounts object type along with the Users object type and click OK.
-
In the Service User or Service Account dialog, click Check Names to select the required gMSA, and click OK.
The Configure Administration Service dialog displays the new login name for the gMSA. The Password field is disabled.
-
Click Next to complete the service account configuration.
If the system running the Active Roles Service is not linked to the gMSA, then an error is displayed prompting you to check if the system is permitted to use the provided gMSA.
If the gMSA is not part of the Local Administrators group, then an error is displayed prompting you to check if the gMSA is a member of the Local Administrators group on the system.
-
If all the prerequisites are met, you can proceed to the next step. Provide the name of the group or user account that will have full access to all Active Roles features and functions through this Administration Service instance (Active Roles Admin). Click Next.
-
Provide the details for the database in which this Administration Service instance will store the configuration data and management history data.
You have the option to create a new database or use an existing database of the current Active Roles version. It is possible to have multiple Administration Service instances that use the same database.
NOTE: When you create a new database, you can add the DB_owner permission to the gMSA for the new database only after the Administration Service is configured.
Based on the authentication mode that the Administration Service instance uses when connecting to the database, the Administration Service uses the relevant credentials:
-
With the Windows authentication option, the Administration Service will use the credentials of the service account.
-
With the SQL Server authentication option, the Administration Service will use the SQL login name and password you supply in the wizard.
-
After all steps are complete, review the settings on the Ready to Configure summary page and click Configure to save the configuration.
The Active Roles Admin setting is specific to the instance of the Administration Service. If you have multiple Administration Service instances deployed in your environment, then you need to apply the changes on each computer running the Administration Service.
