If you have recently received your serial licenses keys, please refer to the Getting Started topic.
For more information about any of the features in the deploy wizard, please consult their respective topic under the Server Settings chapter.
Multiple Devolutions Password Server instances can be hosted on the same server. Each instance resides in its own Web Application within IIS. The following steps are carried out using the Devolutions Password Server Console.
1.Install Devolutions Password Server Console on the web server. It is available from the Download page
2.Execute Devolutions Password Server Console with elevated privileges (run as administrator). This is performed by right-clicking on the application, and selecting Run as administrator.
All operations performed through the console are done with the credentials used to launch Devolutions Password Server Console. If you must use other credentials, you will need to launch another Windows session. The RunAs command does not offer the option of starting a process with elevated privileges.
Run Devolutions Password Server Console as administrator
3.In the Devolutions Password Server Console, click on the button to deploy a new server instance.
Deploy a new Devolutions Password Server
4.The first dialog diagnostics the server to verify if the IIS Server has all the necessary Web Roles prerequisites installed, and is ready to run Devolutions Password Server. Missing features are marked with an . The Install Prerequisites button will install all missing features using a PowerShell script.
IIS Features Diagnostic dialog
5.The License Agreement needs to be accepted to continue to create a new server.
Devolutions Password Server License Agreement dialog
6.Under , enter a custom and . Under , provide a license serial that has been received by email upon buying the product.
If you did not buy any Devolutions Password Server license yet, you may Request a 30-days trial.
General and Registration dialog
7.Under , select to either , or .
Under , select the destination folder, and an IIS virtual directory name. The process to run Web sites has been granted the proper permissions under c:\inetpub\wwwroot. We recommend to create a new folder beneath it, and create the Devolutions Password Server instance within this folder.
We do not recommend to set the installation folder to C:\Program Files or C:\Program Files (x86). Devolutions Password Server is a web application and this could result to unwanted behavior and issues because IIS do not have enough permissions to run web applications that are located under those folders.
Source and Destination dialog
Create and select folder
8.Under , enter the server and database information, then create the database using the button.
The user account used to create the database must have privileges in the SQL Server instance. Consult the Database topic for more information.
To use to connect to the database, it is important to change the Application Pool Identity in the IIS Manager and set the proper permission of the service account on the SQL database. Please consult How to Configure Devolutions Server to use integrated security.
9.On the creation of the database, some options can be enabled. For a simple installation, the default selection must be kept. For more information about these options, refer to the Database topic for further information.
Create database dialog
Database creation successful dialog
10.Under Authentication Modes, select the modes which users authenticate with.
For the initial setup, we recommend enabling Authenticate with Devolutions Password Server custom user. This guarantees connectivity for the first steps and can be disabled later. If you are connected to a domain, refer to the Authentication server settings topic for further information.
Authentication Modes dialog
10.Under IIS Settings, select the website used to host the Devolutions Password Server instance.
Make sure the Internet Information Services (IIS) is installed in order to proceed with the installation of Devolutions Password Server.
IIS Settings dialog
11.Under , configure the email settings for the notification system. This feature is optional and can be left disabled if desired.
SMTP Configuration dialog
12.Under Scheduler, when enabling the Install Scheduler service option, please set the proper Service Account. The following features depend on the Scheduler : Backup manager, Domain Users and Roles cache, Office365 Users and Roles cache, Email notifications.
13.Choosing to not install the Scheduler, you will get the following warning message.
14.Under , validate the configuration and click Install.
14.The last step is to save the Encryption Keys file in a folder.
We recommend to protect the Encryption Keys in a safe to avoid data loss if Devolutions Password Server has to be restored.
Backup Encryption Keys dialog
15.Once the installation is complete, a summary indicates if the Devolutions Password Server has been deployed correctly.
Progress installation dialog
Create at least one administrator user account.
You must create an administrator account if you've enabled the Devolutions Password Server Authentication mode. In other cases, the account name must match with the chosen authentication mode. If you are unsure of the result, also enable Devolutions Password Server authentication, create an administrator account and grant the Administration privilege to the account. Please refer to User Management for further information about creating user accounts.
After the successful authentication with the other model, the Devolutions Password Server user account will have been created and you will be able to see how to format your account names. You can then disable the Devolutions Password Server authentication model. Please see Automatic User Account Creation section in the topic Authentication.
To test the server installation, navigate to the instance URL (e.g.: http://<Machine_Name>/<InstanceName>) with any web browser or click on the button in the Devolutions Password Server Console.
Devolutions Password Server Console
To test the connection from a client by creating a data source in Remote Desktop Manager. Please consult the How to Configure Client Data Source for more information.