moving to 2.0.4

[luther_miller]

I just noticed that 2.0.4 now exists.
What I couldn't find, however, are answers to some basic questions:

1. What is the upgrade process for 2.0.3 to 2.0.4 server? Can I simply install 2.0.4 msi on the server where 2.0.3 is, and Vault will take of the rest? Do need to do anything special before or after?

2. What the interoperability between clients/servers? Can 2.0.3 client communicate with 2.0.4 server and/or vice versa?

We have ten people using Vault, so I need to manage any upgrades we do. It would be great if you could include this kind of information somewhere for future releases, too. Thanks!

-Luther

[jclausius]

I just noticed that 2.0.4 now exists.
What I couldn't find, however, are answers to some basic questions:

1. What is the upgrade process for 2.0.3 to 2.0.4 server? Can I simply install 2.0.4 msi on the server where 2.0.3 is, and Vault will take of the rest? Do need to do anything special before or after?

I believe most people are just running the 2.0.4 msi, and doing an upgrade against both the client and servers. Personally, I like to keep things fresh, so I've been known to Uninstall entire suites (Office), and install to the newer version. "To each their own."

2. What the interoperability between clients/servers? Can 2.0.3 client communicate with 2.0.4 server and/or vice versa?

We've tried to maintain compatiblity between the client and server within the same Version family (2.0.x). The only thing that might not be compatible will be the Vault 2.0.4 Admin Tool when used against a Vault 2.0.3 (and less) server. Basically, the Admin Tool is an extension of the server's settings, so it needs to be in sync with the server.

We have ten people using Vault, so I need to manage any upgrades we do. It would be great if you could include this kind of information somewhere for future releases, too. Thanks!
-Luther

Most info like this can be found in the Knowledge Base. See http://support.sourcegear.com/viewtopic.php?t=1417 for more info.

[bluestone]

Luther, thanks for your post - I was wondering exactly the same things. It never seems like a good time to upgrade when you have a large team, and I'm afraid of doing something wrong in the upgrade that will interrupt the team's work.

Jeff, your instructions for the client upgrade seemed more like a suggestion than a stated process.

1. Can you please tell us exactly how SourceGear recommends that we upgrade the Admin, Server and Client software?

2. In particular, what is the recommended sequencing? Do we have to upgrade the clients at the same time as the server?

3. Are the MSI's cumulative? Can v2.0.2 be upgraded using the 2.0.4 MSI? (i.e., skipping the 2.0.3 MSI?)

A dedicated KB article called "How to Upgrade SourceGear Vault Admin, Server and Client" would be great.

Thank you -

Jeffrey Hasan
Bluestone Partners, Inc.
jeffh@bluestonepartners.com

[jclausius]

Jeff, your instructions for the client upgrade seemed more like a suggestion than a stated process.

1. Can you please tell us exactly how SourceGear recommends that we upgrade the Admin, Server and Client software?

SG Support should respond for the "official recommendation" on Vault upgrades.

However, I can share how I upgraded my own machine to Vault 2.0.4 client:

• Control Panel - Add / Remove Programs
• SourceGear Vault client -> Remove
• Installed Vault client from Vault Client 2.0.4 msi file, which was copied/launched from a local folder.

2. In particular, what is the recommended sequencing? Do we have to upgrade the clients at the same time as the server?

No. As I mentioned earlier in this thread, all servers / clients within the same versioning family can talk to each other. (However, the Vault Admin Tool 2.0.4 should only be used against a Vault 2.0.4 server). For example, a Vault 2.0.4 client works with a Vault 2.0.3 server, and a Vault 2.0.2 client works with a Vault 2.0.4 server.

Again, SG Support should give you the official line here. However, I don't see any harm in upgrading the Vault Server as soon as possible. You should then be able to upgrade clients according to your schedule.

3. Are the MSI's cumulative? Can v2.0.2 be upgraded using the 2.0.4 MSI? (i.e., skipping the 2.0.3 MSI?)

Yes. This goes for both Vault Client and Vault Server.

A dedicated KB article called "How to Upgrade SourceGear Vault Admin, Server and Client" would be great.

I'll bug the Support team about this next week.

Your questions should go a long way in getting information available to help others.

Thanks for the feedback.

[jclausius]

bluestone, I should pay more attention to SourceGear's main web site.

Support has already posted information related to Vault Server upgrades:
http://www.sourcegear.com/vault/support ... torial.asp. The information found in that tutorial covers all Vault 2.0.x server upgrades / installations.

As for rolling out the Vault 2.0.4 client, a Vault client can be upgraded at any time when upgrading within the same version family. This should give you complete control over scheduling / managing the upgrade process.

Jeff