How to move the Password Manager database
Password Manager uses the database to store user information for statistics and reporting. This is assuming that the database will move to another SQL Server with a new instance of SQL Reporting Services.
How to move the Password Manager Database:
- Open SQL Management Studio on the existing SQL Server and detach the database
- Move the Database files to the new SQL Server (both the MDF and LDF files are required)
- Attach to the database on the new SQL Server
- Open the Password Manager Admin site and browse to the Reports tab
- Select Edit Connection and follow the Wizard inputting the new server name and credentials to re-attach the database and to redeploy the SQL Reporting Services Reports to the new SQL Reporting Services Server.
Also see Solution 87872:
Changing the Password Manager service account
Password Manager has two main sections where a password must be changed. The Password Manager service and the Application Pool identity.
To change the Password Manager Service account:
- On the Password Manager server open Windows Services (Run | services.msc)
- Find Password Manager Service
- Right-click and select Properties
- Click the Logon tab
- Change the password
- Restart Password Manager Service to ensure it starts
To change the Password Manager Application Pool account:
- Launch IIS (Internet Information Server)
- Select Application Pools
- Right-click PMAdmin
- Select Advanced settings
- Select Identity
- Within the Application Pool identity select “Set…”
- Then set the new credentials
- Restart the application pool to make sure it starts
- Repeat Steps 4-8 for the Helpdesk and Self-Service Application pools
Workflow design considerations
A Workflow is the set of options available to Users and Helpdesk staff on the Self Service and Helpdesk sites. Each of these options are also comprised of various actions that will be performed. For instance, if a user chooses Forgot My Password, you can add in options to authenticate the user using the Question and Answer profiles and send an email upon completion.
Each Workflow contains specific user scopes to which the Workflow will be applied. As such, it is recommended to keep the number of Workflows to a minimum. For instance, if you have two domains but the rules are the same for each, you can simply add in both domains for the Workflow.
When to use one Workflow
- Same Question & Answer profiles for all users in all Domains
- Same email notification requirements (languages, logos, same text)