Installing Vault Server 4.1 on Vista/IIS7 (x86 or x64)

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear

Post Reply
ian_sg
Posts: 787
Joined: Wed May 04, 2005 10:55 am
Location: SourceGear
Contact:

Installing Vault Server 4.1 on Vista/IIS7 (x86 or x64)

Post by ian_sg » Thu Mar 13, 2008 12:40 pm

Installing Versions 4.1.x of the Vault Server

NOTE: Vault 5.x is fully supported on newer operating systems suchs as Vista, Windows 2008 and Windows 7, both 32- and 64-bit. Choose the appropriate installer (32 or 64 bit) for the system you have. In most cases, no further configuration is needed. For earlier versions of Vault, see below:

There are 32-bit and 64-bit versions of the Vault Server. If you are currently running the 32-bit version of Vault on a 64-bit OS and want to change to the 64-bit version, you will need to uninstall the 32-bit version of Vault (choose to KEEP your database when prompted during the uninstall) before installing the 64-bit server. It is always recommended that you backup your Vault databases before you upgrade or uninstall Vault.

The Vault Server requires IIS, which is only available in Vista Business and Vista Ultimate

1) Install IIS

In Windows Features, install the necessary IIS features by clicking the following nodes:

a) Internet Information Services
b) ASP.NET

If you are running the 64-bit version of the Server on a 64-bit OS, there should be no other IIS configuration changes required. Vault Server versions 4.1.2 and greater will work with or without IIS 6 compatability turned on.

If you're running the 32-bit version of the Server on a 64-bit OS, you need to enable 32-bit applications in the IIS Application Pool that runs Vault. This can be changed in the Advanced Settings for the application pool:

Image

2) Install SQL Server

If the Vista machine will also host the Vault databases, install SQL Server 2005+SP2. Only SQL Server 2005 with Service Pack 2 is supported on Windows Vista. All editions (x86/x64, Express, Developer, Standard, Enterprise) are supported by Vault.


3)Install The Vault Server

See the install guide for general information about the Vault server installation.

4)Allow Vault Traffic through Vista's Firewall

You'll need to enable the HTTP exception to access the server from other machines:

Image

Note that you may also need to enable the Network Discovery exception, depending on your network configuration. Consult your network administrator for settings appropriate to your network.

Installing Older Versions of the Vault Server

0) Compatibility

Image
Note: servers compatible with x64 require IIS 6 management compatibility to be installed and run only in 32-bit mode.

The Vault Server requires IIS, which is only available in Vista Business and Vista Ultimate. The client is supported on all editions of Vista except for Starter.

1) Install IIS

In Windows Features, install the necessary IIS features by clicking the following nodes:

a) Internet Information Services
b) IIS Metabase and IIS 6 configuration compatibility
c) ASP.NET

Image

2) Install SQL Server

If the Vista machine will also host the Vault databases, install SQL Server 2005+SP2. Only SQL Server 2005 with Service Pack 2 is supported on Windows Vista. All editions (x86/x64, Express, Developer, Standard, Enterprise) are supported by Vault.

Install The Vault Server

NOTE: For versions prior to 4.1.0, you need to run the MSI from an elevated command prompt, as follows:
From the Start menu, [All Programs] -> [Accessories].
Right-click 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:\temp\VaultClient_3_5_2.msi
For Vault 4.1.0 or newer, you can run the MSI normally and it will elevate permissions itself.

See the install guide for general information about the Vault server installation.

3)Tweak IIS 7 (NOTE: this step is no longer necessary, as of Vault 4.1.1 and Fortress 1.1.1)
The server must run in an IIS Application Pool in Classic Managed Pipeline mode (not integrated). The easiest way to do this (and what you should do, unless you have custom pools set up and generally know what you're doing) is to move the VaultService, VaultShadowFolder (and Fortress, if you're using Fortress) applications into the Classic.Net application pool. This can be changed in the Basic Settings for each IIS application:

Image

If you're running a 64-bit OS, you need to enable 32-bit applications in the IIS Application Pool that runs Vault. This can be changed in the Advanced Settings for the application pool:

Image

4)Allow Vault Traffic through Vista's Firewall

You'll need to enable the HTTP exception to access the server from other machines:

Image

Note that you may also need to enable the Network Discovery exception, depending on your network configuration. Consult your network administrator for settings appropriate to your network.

That's it! Your Vista Vault server is up and running.

Post Reply