As part of a routine check, I found that one of our servers had an instance of Analysis Services (SSAS) running under a local service account. As many of our solution pull data from various sources, on other servers, there is almost always a need to do a double hop. To enable that, the service needs to run under a domain service account.
This being a simple task and only a small part of the bigger Kerberos puzzle, I filed a ticket with our support, for them to change the service account to one already existing. The reply I got is the cause of this blog post. I needed to provide the individual steps for the change. A quick googlebing turned up rather empty on specific SSAS guides, to my surprise, so I decided to create on myself (I had to anyhow).
Type [Windows] + [r], in the promt type ‘SQLServerManagerXX.msc’ (depending on the edition XX, 12 for 2014, 11 for 2012, 10 for 2008) – i.e ‘SQLServerManager12.msc’ for SQL Server 2014
Depending on your security settings, you may encounter this next dialog:
Clicking ‘Yes’ will bring you to the SQL Server Configuration Manager:
Here you can select (double click) the particular instance you would like to re-configure. Doing so will open this Dialog, where you can edit the login information:
Change the login information and provide the corresponding password:
Click OK/Apply and the Service will need a restart for the changes to be applied.
This guide will be for Windows 2012 R2, but will be applicable on other Windows versions.
Type [Windows] + [r], in the prompt type ‘services.msc’
This will open up the Services Dialog, where you can scroll to the SQL Server services listed
Double click the Analysis Services Service, and the following Dialog will appear:
Click the ‘Log on’ tab
Change the account to the desired domain account and type the corresponding password
Click OK/Apply and the Service will need a restart, before the changes are applied.