SourceGear - tools for small and midsize teams
  Vault Server Installation Guide - Vault 3.5.x

Upgrade Vault

If you are upgrading an existing Vault server, first backup your Vault database before beginning the installation. You can do the backup via SQL Server backup, or from the Vault Admin Tool, in the Backup pane. Then run the Vault upgrade over your current installation. The Vault installer will upgrade Vault and the sgvault database in MS SQL Server.

Overview

Before installing the Vault Server, verify that your system meets the following requirements:

  • Server class machine with 1 GB RAM or greater.
    Disk space requirements depend on size of your source code tree.
  • Operating system of Windows 2000 (Service Pack 3) or above.
  • IIS 5 or above with ASP.Net
  • The .Net Framework 1.1 or 2.0 (For information on the system requirements and installation for .Net Framework, please refer to Microsoft.) - .Net Framework 1.1 - .Net Framework 2.0
  • SQL Server 2000, MSDE 2000, SQL Server 2005 or SQL Server 2005 Express. (SQL Server or MSDE does not have to be on the Vault Server machine)

Guidelines for specific operating systems:

Windows 2000 and Windows XP: IIS must be installed before the .NET Framework to ensure the proper IIS mappings exist for ASP.NET file extensions. If there is a problem with the mappings, they can be repaired: http://support.microsoft.com/default.aspx?scid=kb;en-us;q306005

Windows  2003 Server: Verify that IIS is installed and that ASP.NET is allowed: http://support.sourcegear.com/viewtopic.php?t=185

Windows Vista:  Vault supports Vista Business and Vista Ultimate.

To install Vault on Windows Vista, you may need to install the .msi file as an administrator. Due to the new User Account Control (UAC) feature of Windows Vista, you may encounter problems installing the Vault .msi files which require elevated system privileges.

The following is a work-around used to launch the Vault installation files with elevated rights:

From the Start menu, [All Programs] -> [Accessories].

Invoke the context menu on “Command Prompt.”

Select “Run as administrator.”

Continue through the User Account Control dialog.

From the command line, start the Vault installation. For example: C:\> c:\dir_location\VaultServer_3_5_2.msi

The next step is to enable IIS meta-base and IIS 6 configuration compatibility.  This setting is in Start->Control Panel->Programs and Features-> Turn Windows Features On or off-> IIS Web Management Tools->IIS Meta-base and IIS 6 Configuration Compatibility.

Special configuration for 64-bit Operating Systems: Win 2003 Server, Windows XP Professional, Vista:

The Vault server is supported on 64-bit operating systems only if IIS/ASP.NET is in 32-bit mode. See this Microsoft KB article for how to enable 32-bit  ASP.NET for IIS.

http://support.microsoft.com/kb/894435

The Vault Client is supported on 64-bit operating systems with no additional configuration.

Once these requirements are satisfied, you may proceed with the installation.

What the Installer does:

During the installation, the Vault installer will:

  • create the VaultService directory on the local hard drive.
  • create the sgvault database in SQL Server.
  • if required, create a SQL Server login and database user for the sgvault database.
  • create the Server's web.config file for IIS.
  • ask for permission to give the Microsoft .Net Process account access to certain directories on the Vault Server Machine.
  • create the VaultService and VaultShadowFolder directories on the hard drive and VaultService and VaultShadowFolder virtual directories in IIS.

Checklist before you begin installation:

Is Microsoft Sharepoint installed on the Vault Server machine? Sharepoint and Vault cannot successfully co-exist on the same server machine without special configuration.

You must be logged in as a domain or machine Administrator. Be sure SQL Server or MSDE is running.

During the installation you will be asked to choose certain options.

You will choose to install Vault to the default IIS Default website or to a secondary website configured on the machine you are installing to.

You will decide which user/login will have access to the Vault virtual directory. Your choices are the ASPNET or Network Service account (Win2003) (default), the machine account, or you can create a custom account. In most cases you will pick the account that the .Net Process model is using.

To determine which account the .Net Process model is using:

  • In IIS 5.0, examine %windir%\Microsoft.NET\Framework\v.YYY\Config\machine.config. Search for the "processModel" element.
  • In IIS 6.0, open up the Internet Information Administrator. Examine the properties for the "application pool". Look for the account used to run the process model

You will decide whether to use Windows Authentication or SQL Server authentication for access to the Vault database by the Vault process. Be sure your SQL Server is set up to accept the type of authentication you choose.

The options you select in the IIS Process model and SQL Server Setup screens determine what user has access to the Vault database. Examples:

Using Windows Authentication:

This describes using the Machine\ASPNET account, but applies to any of the IIS Process model choices.

If you select Windows Authentication during the SQL Server Setup portion of the installation, the installer will use your credentials to log into SQL Server. The installer will create the sgvault database, the SQL Server login for the Machine\ASPNET account, and create the user Machine\ASPNET within the sgvault database.

Using SQL Server Authentication:

If you choose to use SQL Server Authentication in the SQL Server Setup portion of the installation, then the installer will use the user/password you supply in the SQL Server Setup page to log into SQL Server. That username you supply must have SQL Server administrative privileges (the SA account, for example). The Server installation will then create the sgvault database, plus create a SQL login named 'sgvaultuser', and grant it access to the sgvault database.

IF SQL Server/MSDE is on another machine:

The easiest way to install the Vault Server when SQL Server is located on a different machine is to use SQL Server authentication.

However, If your SQL Server is on a different machine, and you would like to use Windows Authentication, then the account you choose for the IIS Process Model should not be the ASP.Net account, as that only exists on the local machine. In this case, choose the DOMAIN\MACHINE account, or a custom account. The custom account needs to be a Windows account which has access to both the SQL Server and the IIS Server, usually a DOMAIN\USER account.

1. Welcome to the Vault Server Installer

For best results, run the Vault Installer from the C:\ drive of the Vault Server machine. Double click the Vault Install icon to launch the Vault Server Installation Wizard.

Click Next to continue.

2. Software License Agreement

Please read the license agreement. Select "I accept this agreement."

3. Read Me

Please read the notes concerning the version of Vault being installed.

Click Next to continue

Next page

 

• product features

• screen shot gallery

• documentation

• support forum

• downloads

• demo

• pricing

Buy Now!


Copyright 1997-2008 SourceGear LLC. All Rights Reserved.

SourceGear and SourceOffSite are registered trademarks of SourceGear LLC. Fortress, Vault and DiffMerge are trademarks of SourceGear LLC.

Microsoft, SourceSafe, Visual Studio and .NET are trademarks of Microsoft Corporation.