Vault and remote access

[flu]

Hi,

I used CVSNT/TortoiseCVS for some time in my office. While I did like the fact that any of my users could right-click from within the windows file explorer and checkout stuff, I don't like the edit/merge idea since im working with a lot of binary files. I need a check-in check-out LOCKED source control. If one user has a file, nobody can check it out. So I heard about Vault.

I have a few questions regarding your product:

1. Can I install it on Windows 2003 Server?
2. After I install Vault on the server, what do I need to remotely access that server? Is it a module that I get with Vault?
3. How many users can install that remote access for that server, per license?
4. I would rather manage the user/password/permissions myself. Is there any option like that on Vault?

Thanks for your time.

P.S. I would suggest making a pre-sale forum, so people with pre-sale questions won't interfere the support forum.

[lbauer]

1. Can I install it on Windows 2003 Server?

Yes. We recommend the Vault Server be installed on a server class machine.

2. After I install Vault on the server, what do I need to remotely access that server? Is it a module that I get with Vault?

Download and install the Vault GUI Client on the remote machine. You can connect to the Vault Server though this client. Enter the IP address or fully qualified domain name of the Vault Servr machine in the connect to server dialog.

The Vault GUI Client installation also has the Vault command line client and integration with Visual Studio.

3. How many users can install that remote access for that server, per license?

Licensing is per client. You need a client license for each named Vault user. There is no additional licensing for the Vault Server.

4. I would rather manage the user/password/permissions myself. Is there any option like that on Vault?

You can create user accounts and passwords and enable and manage folder security. Users can change their passwords though. A option is to use Active Directory authentication, where the Vault username would be the same as the user's network name, and passwords would be managed in Active Directory.

[flu]

So lets just clarify - each remote login application needs a license?

So if I got 5 remote users to a vault installation I need 5 licenses of vault?

[lbauer]

Yes, 5 users would need 5 licenses.

[flu]

As it stands, for small businesses of 5-10 people, Vault is simply too expensive. I guess I'll have to use CVSNT or Subversion, even if Vault does look better.

Just a comment tho, adding a shell (context menu) to check in/out files like tortoise would be tremendously beneficial to you.

[rshillington]

I would disagree that vault is too expensive. One has to wonder what signal management is sending to it's devlopers when they will not spend a dime on providing a robust infrastructure for the product of their developers work.

Per user how much are we talking about as function of the developers annual billing rate, 1/10th of 1 percent? If management can't afford that then I think it speaks more to their business cost model, than to the price of Vault.

just my 2 cents worth (all puns intended)

Ralph Shillington