About the Server Upgrade

All systems in your environment must use the same version of the server. Therefore, when you decide to upgrade your legacy server to the latest version, you must upgrade all systems that comprise your environment. This includes Remote Administrators, Remote Composers, Remote Connectors for DMS Libraries, Remote Embedded Directive Managers and Remote Modem Servers.

Note: Once you upgrade the server, all Remote Composers go off-line until you upgrade them.

If you are planning to set up and use ObjectArchive, verify that the system where you will install ObjectArchive meets the following hardware and software requirements.

• Windows NT domain computer that always runs in the same domain as the server
• Dual core processor; 2 GHz; 4GB of RAM; RAID 5W with 100 GB of disk space; DVD-ROM drive; and Microsoft mouse or compatible pointing device
• Windows 2012 64-bit, Windows 2008 R2 64 bit
• Microsoft SQL Server 2012 or MS SQL Server 2008

Note: ObjectArchive must be installed on a system remote from the server. The SQL Server does not have to be the same one used for the server databases.

When you upgrade your server, you must upgrade all instances of the remote Intelligent Device Client in your environment. See Installing Intelligent Device Client for more information.

When you install the server as a new install, it creates one General Composer and one OCR Composer. This allows for the OCR Composer to be off-loaded more easily, freeing up valuable system resources.

However, when you upgrade from a legacy server to the latest server version, you may have only one instance of the Composer since the upgrade will not change your Composer configuration. You can add additional Composers, and configure a Composer to handle only OCR jobs.

Some prior versions of the Universal Output connector (the XML Output connector) are neither supported nor updated by this release. If you were previously using the XML Output connector, then after installing the upgrade you will need to manually enable the Universal Output connector and update any existing rules.

The installation setup files for the clients are located in the Clients directory of the server. After you have finished installing the server, you must configure the Clients folder within the HP CR directory. This is necessary because remote Desktop and other clients must have access to this folder containing the setup files. For instructions on how to configure the share, see Configuring the client install directory share.

Note: The Desktop Clients are supported by the server for one release back. Therefore, if you have Desktop Clients from the prior release deployed in your environment, upgrading them is not a requirement. However, HP CR recommends that you upgrade to the latest version of Desktop Client to take advantage of the latest features.

HP CR is a cluster-aware application. If you plan to use the server cluster functionality after the upgrade, consult Setting up a Server Cluster section for an overview of the clustering functionality and instructions on setting up the cluster.

For Administrators planning an upgrade

Significant enhancements were made to RuleSets in the server upgrade v5.1. The following RuleSets issues have been reported after an upgrade.

• Empty rulesets, rules no longer exist
• Disabled rulesets are enabled
• Deleted rulesets reappear
• Rules moved to different rulesets
• Action items missing from rules

During the upgrade there is a conflict between the previous and current RuleSets tables and migrations that result in the issues listed above.

Note: Backup your server and database before upgrading.

Truncate Table RoutingRules Resolution

See the table below before using the Truncate Table Routing Rules resolution.

HP CR recommends that you complete the following procedure before you upgrade.

1. Open Microsoft SQL Server Management Studio and connect to the SQL server hosting the database.
2. Click New Query on the toolbar.
3. On the toolbar, change the database name on the drop-down list from Master to the Server’s Core Database.
4. Type the following query into the query window: Truncate Table RoutingRules.
5. Click Execute on the toolbar. Command(s) completed successfully message appears.

Note: If you have additional questions or require assistance in upgrading, contact Technical Support.

Companies have to manage Administrator rights to their technology resources effectively. Giving everyone in an organization Administrator rights is risky and can potentially result in a huge IT security breach and other technical issues. Operating system and other software applications have mechanisms in place that allow organizations to determine who can execute full or limited Administrator rights.

The server platform and its services support limited Administrator rights. You can set up limited Administrator rights for user accounts that need to perform specific server-related services. User accounts with limited Administrator rights cannot install or upgrade the server.

See Running the Server with Limited Administrator Rights for more information.