DocAve Upgrade Guide. From Version to 4.5.3

Transcription

1 DocAve Upgrade Guide From Version to 4.5.

2 About This Guide This guide is intended for those who wish to update their DocAve platforms from version and above to the latest version (DocAve 4.5.). To ensure a successful upgrade for this patch, as well as all future patches for DocAve, please follow the steps detailed below. *Note: All servers and agents must be upgraded to version or above to perform this upgrade! Please contact AvePoint s Technical Support team to obtain links to the build if you are running an earlier version of 4.5. Upgrading DocAve Pre-requisites Before performing the steps below, be sure to check the status of all Remote Media Services and DocAve Agent Services. You can use the Server and Agent monitors in the DocAve Control Panel to check that their status is up. Also, make sure that the server is currently running DocAve version or higher. Https Configuration In order to update the Patch System, https will need to be temporarily disabled on the DocAve Servers. Please perform the following steps on all DocAve servers (Media, Web): Navigate to Start -> All Programs -> AvePoint DocAve 4.5 -> DocAve 4.5 Server Tools on the DocAve Server. 2 Open the Server Configuration Tool and uncheck the Enable https box. Click the Confirm button. Installing the DocAve Patch In order to apply 4.5., download the patch manually (using links from the AvePoint Support Team) and upload it directly to the DocAve Patch Manager. You can also use the Check Now button in the DocAve

3 Patch Manager, but be sure to complete the sections below before completing the upgrade. The DocAve Patch Manager allows you to update the current version of DocAve directly from the DocAve GUI. *Note: The Client and Server Patches must be renamed from.zip to.ave before proceeding to load the patch. Download the DocAve 4.5 Client and Server patches as a zip file to the machine on which the DocAve Server is located. *Note: Do not decompress this file. 2 Change the extension from.zip to.ave by renaming the file. In the DocAve Manager GUI, navigate to Control Panel -> License Management -> Patch Manager. Depending on whether you are applying the patch to the Agent or to the Manager, please follow the steps below. 4 If DocAve Manager DocAve Agent Then. On the top of the GUI, select the Server radio button. 2. Browse for the Server Patch (.ave file) and select Load.. On the top of the GUI, select the Client radio button. 2. Browse for the Client Patch (.ave file) and select Load.. Choose a client machine from the drop-down list under the Agent Host section to install the upgrade. Select Apply to load the patch. 6 *Note: To install this patch across multiple agents, you must perform the previous step multiple times.

4 Upgrade for Patch System After using the upgrade tool, a patch must be applied to the DocAve Media and Web servers to ensure all future patches use the proper protocol. Please follow the instructions below to ensure that all future patches occur normally. This setup takes place on the DocAve 4.5 Server and Remote Media Servers and will replace the files docave-xml.jar, docave-util.jar, and docave-patch.jar : Navigate to \AvePoint\DocAve4\VaultServer\Tools\ExchangePatchFileTool\bin under the DocAve installation directory for each server. 2 Run ExchangePatchFile.bat. After the tool completes, the following screen appears. Press any key to close this tool. *Note: If you wish to enable https support again, you can now do so in the Server Configuration Tool under the start menu of the Web and Remote Media server. Check the Enable https option, and note the corresponding change to the Web Service Port. The Web Service port should match on both the Web and Media server. (The recommended port setting is 8090.) You have now successfully upgraded to DocAve 4.5.!

5 SharePoint 200 to 2007 Migration Upgrade Configuration File For users who are currently using DocAve s SharePoint Migrator.cfg files to map permissions and content metadata, a new master.xml mapping file must be built in order to use plans created before This is especially true for scheduled plans after upgrading to On each destination Agent for the 200 to 2007 migrator, navigate to \AvePoint\DocAve4\VaultClient\bin under the DocAve installation directory. Run the tool SP200To2007MigrationConfigurationMergeTool.exe. This will condense all.cfg files into a single.xml entitled SP200To2007MigrationConfiguration.xml. 2 *Note: When running this tool, you can rename this file using the command prompt. Type the name of the tool SP200To2007MigrationConfigurationMergeTool.exe followed by a space, and the desired name of the new file (without the.xml extension). Log on to the DocAve Manager and go to the SharePoint 200 to 2007 Migration tab in the GUI. Click the Config button and browse for this new file to Upload. 4 5 *Note: This file should be uploaded directly. Do not rename this file or make any additional edits while a migration job is running. If a migration job has already run in 4.5. prior to performing this upgrade, please run this job again. Otherwise, this plan can be saved and run at a later time. To make any additional edits to the mapping functions, either edit the original.cfg files and repeat the steps above, or simply edit the new.xml file directly. *Note: For more information on this section, please refer to the updated User Guide, accessible from the AvePoint website or the Help button in the DocAve Manager GUI. Congratulations, you have now upgraded to DocAve 4.5.! Please visit to learn about the new modules and enhancements included in this version, or contact your AvePoint account representative for any further questions or information.