Group Managed Service Account as a feature provides automatic password management within a domain and simplifies service principal maintenance. The periodically changed password will be automatically updated and retrieved from the domain controller, which adds to security techniques that are commonly followed nowadays.
To completely utilize this feature to run ApexSQL Audit components, requires both central and audited service to run under the specific gMSA account. In below text we will distinctively describe how to configure each service to run under gMSA principal.
To configure central process using gMSA account, the application installation has to be performed.
ApexSQL Audit installer can be instantiated either:
No matter the choice, ApexSQL Audit central configuration dialog will prompt for the setup input.
To complete the installation:
Shortly after the installation processing, the central background process will be started and running under the used account:
Audited (distributed) agent configuration is much likely easier and faster to configure through the application interface.
To complete the process:
The same dialogue will be available if the Add server option is clicked to configure new instances for auditing.
Right after the newly created process “ApexSQL Audit Processor Distributed” will run under the configured account:
With the explained easy setup, the gMSA account will be utilized to run auditing processes which, in long term, will prevent interruptions of those processes due to password changes for regular accounts.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center