- 1. When you ran the installer, which windows login did you use on the machine?
Future admins may need to find the Vault_install.log file. That file is saved in C:\Users\<your login name>\appdata\local\temp. If this location is not being kept, it might be useful to save the vault_install.log file along with your other documentation.
2. Setup Type: Typical or Custom.
This determines the path where it will be installed. Typical will use C:\inetpub\wwwroot. Custom will allow you to specify a path. If you choose Custom, then document the path.
3. IIS Process Model - Machine or Custom.
The process model will determine which account under which Vault will run. If Custom is chosen, include the account in your documentation. Be aware that future admins may not know the password for that user. Older versions of Vault also had the option of System.
This window only appears if you have more than one website available on the machine. If there is only Default, then it will choose that automatically and not offer this popup.
5. Admin password
If the admin password is lost, the only way to reset it is to perform a reinstall.
6. Connect to SQL Server - SQL Server and authentication information.
Windows authentication will use the account specified in the IIS Process Model. SQL authentication will require you to enter in a SQL sysadmin account such as sa, but Vault will create its own user called sgvaultuser that it will use after the installation.
After the server is installed, the users will install their clients, which could possibly be the Vault Windows GUI client, the Cross-Platform client, the Command-Line client, and so on. If the users use Vault integrated with Visual Studio, then document whether they are using the Vault Visual Studio Enhanced Client or the Vault Visual Studio Classic Client. Both of these clients are installed automatically with the client, unless the user is running the beta of VS 2017.