6. Ready to Install/Updating System

The Vault installation program will now update your system. A Vault Server Configuration Status dialog appears on top of Updating System. This dialog shows the status of the configuration, step by step.

6a. Vault Administration

Create a password for the Admin user. If using SQL Server authentication, this password will also be used for the SQL Server login, 'sgvaultuser'. This value is encrypted in the Vault Server's web.config file.

Be sure to remember this password. If you decide to move the Vault server or database, life is much easier if you use the same password for the Vault Admin when you reinstall.

Vault can accept a blank password, but this is not recommended for security concerns.

Click Next to continue.

6b. SQL Server Setup

Specify the location of the SQL Server which will store the Vault database, and the authentication method the Vault Server should use to connect to the database. Vault can create a database on SQL Server if it has been set up on the local machine, or you can use a SQL Server on a different machine on the network. Please verify SQL Server is running before you complete this step.

The Vault Server can connect to SQL Server via Windows Authentication or SQL Server Authentication. If you choose SQL Server Authentication, please verify SQL Server is set up to use SQL Server Authentication

When installing Vault Server with SQL Server 2005 Express, use .\sqlexpress instead of (local) or use machinename\sqlexpress, since SQL Express is installed as an instance.

Note for MSDE users: By default, MSDE uses Windows Authentication only.

If you select Windows Authentication:

It is very important that before you install Vault on your machine, you login to the machine with full administrative rights and full access to the master database of SQL Server. During this phase, the installation script use your credentials to create the database, modify the database to set options and create the entire schema.

Vault installer will grant database access to the user specified in the IIS Process Model screen, Step 5.

If you select SQL Server authentication,

If you choose SQL Server authentication, then you should use the sa account or another account that can modify the database to create logins and users to establish the connection between the Vault Service and the sgvault database.

Note that the SA account is only used once during installation to create the appropriate users and logins for the Vault database.

The Vault Installation creates a SQL Server login named 'sgvaultuser', and grants this account access to the 'sgvault' database. Sgvaultuser will have db roles of public and db_owner. Vault is set up so that only sgvaultuser can access the Vault database.

Click Next to continue.

6c. Database Collation

Choose Collation for Database (on a new database only). Collation is how the database sorts text strings in the database based on the language used. The Vault installer chooses a collation that is appropriate based on the language settings of the machine. If you wish to choose a different collation than the default, click Collations and select the one you want.

6d. Updating System Status - if reinstalling and database exists

The Vault installation program will check to see if a Vault database exists.

If you re-install Vault and there already is a database, you will be asked to use the existing database or drop the database and create a new one. If you choose to drop the database, a confirmation box will appear.

6e. Granting Directory Access

The installer will grant permissions to the account you chose in the IIS Process Model dialog. Vault installer will request that read/write access be granted to the following folders:

• the local directory containing the server installation files (by default, InetPub\wwwroot\VaultService).
  
• the directory where the log files are written (by default, WINNT\Temp). The log file location can be changed after installation, in the Vault Admin Tool under Server Options.
  
• the IIS process account's %userprofile%\Application Data \Microsoft\Crypto\RSA\MachineKeys or to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys if the IIS process account does not have a user profile.
  
• the Vault Shadow Folder directory.
  
• Windows\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files.

7. Updating System - Web Site

The final step is installing the Vault virtual directory. By default, Vault is installed to the IIS default website. However, the Vault installation program will detect whether you have more than one website configured, and if you want the virtual directory installed to a different site, make your selection from the entries in the combo box.

8. Installation Complete

The server installation is complete when the status message says "Your Vault Server has been successfully configured." If you wish to install the Vault GUI Client and Admin Tool, press OK. No further input is needed on your part.

Installation Files

A SourceGear Vault folder will be created in the server’s Programs menu. The folder contains:

• Vault Admin Tool (if installed)
  
• Vault Admin Tool Help (if Admin Tool installed)
  
• Vault Client (if installed)
  
• Vault Client Help (if Client is installed)

A Vault Home web page will also be created. To access this page, you should go to http://<vaultservername>/VaultService/serverinstall.html. This page will contain links to the Admin Tool and Client installers that were copied as part of the Server installation.

A desktop icon for the Vault Client will also be created if the Client was installed.

9. Testing the Installation

To log in to Vault for the first time, use the username "admin" and the admin password you created during the Vault Server installation. For the Vaultserver name, use the hostname of the machine where Vault is installed, for instance: myserver.mydomain.com. Use the SSL option only if IIS is configured to use SSL.

If you receive an error, open a web browser and connect to

http://yourvaultservername/VaultService

and

http://yourvaultservername/VaultService/VaultService.asmx

If either of these generates an error message, then there is a problem with the installation. For solutions, see Vault troubleshooting information.

10. Configure Server Options

If your installation is successful, log in to Vault with the Admin tool and configure the Vault Server options.

• product features

• screen shot gallery

• documentation

• support forum

• downloads

• demo

• pricing

• Buy Now!