Introduction
Kepion Service Identity (SI) is a credential that determines the web server's running context. You can update it to a different credential in an existing environment. We recommend using a dedicated domain account as the Kepion SI.
This article outlines the steps to update the Kepion SI.
Before you start
-
Make sure the new Kepion SI is a valid domain account.
-
If your environment requires Active Directory (AD) synchronization, the SI must be an Active Directory account rather than a local domain account.
Step 1. Create a login for the new Kepion SI
In the relational SQL database, create a login for the new Kepion SI. For more details, refer to Kepion SI - Ceate login.
Step 2. Configure permissions for the new Kepion SI
Grant the new SI the necessary permissions at both the server and application database levels. For more details, refer to Kepion SI - Set permissions.
Step 3. Add the new Kepion SI to SSAS
In the SQL Server Analysis Services (SSAS), replace the old SI with the new SI as the server administrator. For more details, refer to Add Kepion SI to SSAS.
Step 4. Update Kepion SI in IIS
In Internet Information Services (IIS) Manager:
- Go to Application Pools.
- Right-click on Kepion Planning and select Advanced Settings.
- Update the Identity value to the new Kepion SI.
Step 5. Verify Kepion is running
After updating the SI:
- Ensure the Kepion Planning application is running in IIS.
- Try launching Kepion in your browser to confirm functionality.
Step 6. Clean up the old Kepion SI
Once Kepion is successfully running under the new SI, remove any references to the old SI in the relational database, SSAS, and Active Directory.