Before you perform the upgrade from ZENworks 11 SP2 to ZENworks 11 SP3, consider the following guidelines:
If you are using an external database, you need to upgrade or migrate the external database to the supported latest version before upgrading the Primary Server.
NOTE:If you have MS SQL 2008 R2 running in compatibility mode on the device, you must manually turn off the compatibility mode before you upgrade to ZENworks 11 SP3.
For more information about the supported database versions, see Database Requirements
, in the ZENworks 11 SP3 System Requirements Guide.
If you are using Remote OEM Sybase on a 32-bit device, ensure that you migrate the database to a 64-bit OEM Sybase device before you upgrade. For more information, see Section 1.5, Upgrading the Remote OEM Sybase SQL Anywhere Database.
(Recommended) Select the type of database based on the number of devices in the environment:
For environments with up to 3,000 devices, use Embedded Sybase or Remote Sybase.
For environments with up to 40,000 devices, use MS SQL or Oracle.
For environments with more than 40,000 devices, use Oracle Enterprise Edition (with partitioning). For information about partitioning, see Oracle Enterprise with Partitioning, in the ZENworks 11 SP3 Server Installation Guide.
If the existing database does not meet the recommendation, migrate the existing database after the upgrade is complete.
ZENworks 11 SP3 introduces the Audit Management feature. Because the amount of data that audit can generate is significant, ZENworks 11 SP3 requires that this data be stored in a separate database. This prevents the large amount of data stored in the audit tables from degrading the performance of the overall ZENworks system. Therefore, ZENworks 11 SP3 requires two databases: a ZENworks database and an Audit database. For more information on the Audit Management feature, see the ZENworks 11 SP3 Audit Management Reference.
During the upgrade from an older version of ZENworks to ZENworks 11 SP3, the Audit database must be created. There are two ways to create the Audit database:
The upgrade installer can create the Audit database during the ZENworks upgrade process.
Use the setup.exe -c command to create the Audit database before the upgrade. During the ZENworks upgrade process, opt to use an existing database as the Audit database and point to the database created using the setup.exe -c command.
If you are using an Oracle database, ensure that you have the database administrator credentials to create an audit database and user. Ensure that the administrator has the required rights with the Grant option enabled. For the list of rights to create the database, refer to Prerequisites for Oracle
in the ZENworks 11 SP3 Server Installation Guide.
Ensure that you note of the new database details. You will be prompted for this information during the ZENworks 11 SP3 upgrade.
For upgrading database, you can either upgrade the database on the same device where it is running or you can migrate the database using a third-party upgrade installer.
If you are using an embedded Sybase database, the ZENworks Upgrade installer will upgrade and rebuild the database.
NOTE:On a server that hosts an embedded Sybase database, ensure that you have the required free space, equal to the size of the database file.
OEM Sybase SQL Anywhere 12 is supported by ZENworks 11 SP3. Therefore, if you are using a remote OEM Sybase SQL Anywhere database, ensure that you upgrade it to OEM Sybase SQL Anywhere 12.
For more information on how to upgrade the remote OEM Sybase SQL Anywhere database, see Section 1.5, Upgrading the Remote OEM Sybase SQL Anywhere Database.
You can only upgrade to a higher version of the same database. You cannot migrate from one database to another using the Upgrade installer.
For all external databases, stop the ZENworks services before performing the database upgrade.
If the upgrade has failed in the previous attempts, ensure that the Audit database administrator user name does not exist in the database. If the user name exists in the database, ensure that you delete the user name or provide a different user name for the Audit database administrator user when you re-run the upgrade installer.
Ensure that the access user name is unique when you create Audit database while using MS SQL with SQL authentication or OEM Sybase.