Kerberos Configuration Manager was released back in May of 2013. It initially released with only SQL Server support . This was followed up with support for Reporting Services in November 2013. You can download the latest release from the following link:
Microsoft® Kerberos Configuration Manager for SQL Server®
http://www.microsoft.com/en-us/download/details.aspx?id=39046
This month we have released Version 3 of the Kerberos Configuration Manager which provides support for Analysis Services. This will work with Analysis Services 2005 and later (including 2014).
This release also includes support for SQL 2014 services .
Logging
If you happen to encounter something that I didn’t highlight above, you may be able to find additional information. Each time you run the tool, we will create a log file. The default location for this is the following: C:\Users\<user>\AppData\Roaming\Microsoft\KerberosConfigMgr.
The details of the log file will be flushed when you close the program. So, if it is blank, just close the tool and the log should populate. You may also find some details in the Event Log under the Source “Kerberos Configuration Manager”. If we encounter an error, it should be logged in the Application Event Log as well as the tool’s log file.
Limitations DelegationFor Analysis Services, there is no Delegation check at this time. The scenarios for that are limited and may be looked at in a future release.
SQL Browser DISCO SPNThis also does not do a validation on the SQL Browser SPN.
Multiple DomainsRight now, the tool will only work in a single domain scenario. So, if you have the service installed in Domain A, but want to use a Service Account from Domain B, we won’t be able to discover and correct the issue appropriately. As long as the machine the instance is in and the Service Account are in the same domain, you should be good to go. This is true for Reporting Services and the SQL Server discovery.
Adam W. Saxton | Microsoft SQL Server Escalation Services
https://twitter.com/awsaxton