Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-8734: How to use MSA (Managed Service Account) to run Reporting Service?

Authentication Service ,  

19 May,17 at 01:45 PM

Question:

How to use MSA (Managed Service Account) to run Reporting Service?
 
Workaround:

Currently, using MSA to run Reporting Service is not supported in the User Interface. (RFE has been filed and accepted)
 
However, we use the following workarounds:
If you hadn't deployed the Report Services, please firstly deploy it by using a domain account / built-in account as service account.
  1. Create SQL login and user for the target MSA:
  • Open SQL Server Management Studio (SSMS) and connect to the instance which the Report Services is deployed to
  • Use SQL command to create SQL login for the target MSA, e.g. 
create login [{MSA account} from Windows]
  • Create DB user for this SQL login under the DB which the Report Services is deployed to, and grant it as the role: SnapshotService
  1. If you're using domain mode, make sure you've delegated the 'Replicate Directory Changes' permission to the target MSA
  2. Start > Run > Services.msc > Locate Centrify Report Services and change it's service account to the target MSA > Restart the Report Services
  3. Open Report Services Control panel > Troubleshooting > Click Validate to verify if the MSA is configured correctly.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6041: How to show current license type in use by adclient article[HOWTO] Configure Centrify Authentication Service with an AWS Managed Microsoft Active Directory articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?