Changing server name (v 3.0.6)

Guest · Post by **Guest** » Fri Apr 15, 2005 6:33 am

At the time that we installed the trial version we were not aware that the server name gets its name from the domain user specified during installation time (http:\\username\vaultservice). We then created a domain user to be used for this purpose and re-installed vault. The problem now is that the server name is still that original one. Also, we are not able to connect to the server using the new user or the original one.

What do we need to do to update the server name and be able to connect to it.

TIA

Ingrid

lbauer · Post by **lbauer** » Fri Apr 15, 2005 8:01 am

There seems to be a little confusion here. The Vault servername is always the network name or IP address of the machine were Vault is installed. So if your machine is named "ServerOne" then when you connect to Vault you'd connect to ServerOne in the GUI Client or via the web client it would be "http://ServerOne/VaultService/VaultWeb/login.aspx?".

You may be thinking of the IIS Process model selection during installation. This is usually the account that runs the aspnet process, Machine\Aspnet or NT Authority\Network Service (IIS6), or you can create a custom account, as you did.

http://www.sourcegear.com/vault/support ... orial.html

We can help get this sorted out for you. Send me a copy of the vault_install.log file from the %temp% directory of the user who installed Vault. This will give us info on your current configuration. Email it to linda at SourceGear.com.

lbauer · Post by **lbauer** » Fri Apr 15, 2005 3:08 pm

Follow-up:

The user was attempting to install Vault server on a server machine on the LAN, but was running the Vault installer from her own workstation. This caused Vault to be partially installed on her workstation instead of the target machine.

The Vault installer should always be run from the C:\ drive of the machine where you wish to install Vault.