Vault 3.0.1 Release Notes

[dan]

The following features and changes have been included in the 3.0.1 release:
<UL>
<b>Installer</b>
<LI>Installation to a server account that uses NT AUTHORITY\NETWORK SERVICE will now install correctly on non-english versions of Windows

<b>Server and Client</b>
<LI>Authentication from non-interactive users, such as Vault shadow folders or using Vault to authenticate Dragnet users, now works without having to use impersonation to access the Vault service.
<LI>Get by label to a working folder on multiple files will now be retrieved without errors about baselines being incorrect

<b>Client Only Changes</b>
<LI>External Merge apps like P4WinMerge that fail on arguments they don’t recognize should now be invoked properly.
<LI>Filename searches now report the correct status for each found file.
<LI>Sorting in the Remote Date column now always sorts by date. Some configurations would sort this alphabetically

<b>Admin Tool</b>
<LI>Help button in Email settings dialog now goes to correct place in help files.
<LI>Bug Tracking URL field now only enabled when Bug Tracking Application has a value.

<b>Command Line Client</b>
<LI>CLC now does not use chunked encoding by default, allowing file transfers from the CLC over a proxy server.

</UL>

<b>Client/Server Version Compatibility</b>
It is always recommended that your client and server versions match exactly (e.g., a 3.0.1 client should be connecting to a 3.0.1 server). 3.0.x clients should be able to communicate with any 3.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.0.x clients and servers are <b>not</b> compatible with 1.x or 2.x clients and servers.

<b>Upgrading From Previous Versions</b>
It is recommended that you backup your Vault database prior to an upgrade. This can be done from either the Vault Admin tool, or the SQL Enterprise Manager tool.

To upgrade from a previous installation of Vault, simply invoke the new installer, and choose the same options that were selected when Vault was previously installed. Program files and configuration settings will be automatically updated to reflect the upgrade. Note that the server installation will not delete your database unless you explicitly tell it to.

You may also safely uninstall Vault first, and then install the upgrade. As with installation, an uninstall will not delete your database unless you explicitly tell it to.