2.2 Upgrading the Primary Servers

You can upgrade by using a graphical user interface (GUI) program or a command line (Linux only).

NOTE:After upgrading the zone, ZooKeeper is enabled on the Primary Server that is first updated. For more information see, Post-Upgrade Configurations.

IMPORTANT:

  • Do not use the ZENworks System Update to upgrade the Primary Servers to ZENworks 2020Update 2.

    Before upgrading the ZENworks server on a Windows device, run the Windows Update on the device to ensure that all the available updates are installed on the device. Subsequently, disable the Windows Update to ensure that there are no further updates on the device when you upgrade the ZENworks server on the device. Windows Update can be enabled after upgrading ZENworks.

  • Disable the Linux Update to ensure that there are no further updates on the device when you upgrade the ZENworks server on the device.

2.2.1 Using the GUI to Upgrade Linux and Windows Servers

Perform the following procedure on the Primary Server that you want to upgrade to ZENworks 2020 Update 2, if all the prerequisites are met:

  1. To start the ZENworks upgrade program:

    • Linux: Do the following:

      1. Download the ZENworks upgrade ISO image from the Micro Focus Download site.

      2. Mount the ISO by running the command mount -o loop <ISO path including name> <mount_path>

      3. cd to the mounted location and run ./setup.sh.

    • Windows: Do one of the following:  

      1. Download the ZENworks upgrade ISO image from the Micro Focus Download site.

      2. Mount the ISO.

      3. Run setup.exe.

      4. Open a DOS window, browse to the root of the ZENworks 2020 Update 2 installation media, then enter the setup.exe command.

  2. During upgrade, see Table 2-1, Upgrade Information for details on the upgrade data.

    If you are using the GUI upgrade, you can also click the Help button for similar information.

  3. Do one of the following on the Windows device:

  4. After the upgrade, the ZENworks Server data will be copied from the old Novell file path to the new Micro Focus file path. However, the ZENworks Server data in the old file path is retained during the upgrade process. After verifying whether the upgraded version of the ZENworks Server is working as expected, you can run the cleanup utility provided with the build, to remove the retained server data. For more information, see Running the Cleanup Utility on a Linux or Appliance Server.

  5. To upgrade another Primary Server, repeat from Step 1.

    IMPORTANT:Repeat these steps until all Primary Servers in the Management Zone are upgraded.

NOTE:If you are using ZENworks Reporting, then after upgrading the zone to ZENworks 2020 Update 2, ensure that you reconfigure ZENworks reporting. For more information, see Reconfiguring ZENworks Reporting Appliance in the ZENworks Reporting Appliance Deployment and Administration Reference.

The Table 2-1 provides the upgrade information for upgrading from ZENworks 2020 to ZENworks 2020 Update 2.

Table 2-1 Upgrade Information

Upgrade Information

Explanation

License agreement

The Upgrade installer does not proceed if the license agreement is not accepted.

ZENworks Prerequisites

If the required prerequisites are not met, the upgrade procedure does not continue. The requirements that are not met are displayed (GUI) or listed (command line). For more information, see Prerequisites.

If the.NET prerequisite is not met, you can click the ZENworks link in the description to install the runtime version that is bundled with ZENworks. Ensure that you install Microsoft .NET 4.5 framework and all its latest updates. After .NET is installed, the ZENworks upgrade proceeds.

NOTE:You must reboot the device after the installation of .NET 4.5.

Upgrade Type

Select Yes if this is the first Primary Server in the Management Zone to be upgraded, else select No.

If you select Yes, you are prompted for the zone administrator credentials.

or

If you select No, perform the steps listed in Table 2-2, Upgrade Information - Upgrade of additional Primary Servers.

Database Purging

The time required to complete the upgrade of the first Primary Server depends on the size of the data present in the database. On Primary Servers that are using an Microsoft SQL or Oracle Enterprise database, the upgrade installer checks the size of unwanted inventory data that can be purged. If there are more than 200,000 records to be purged, the Upgrade installer gives an option to purge the database before upgrading the Primary Server. For other database types, if there are less than 200,000 records to be purged, this page does not open.

  • Purge the database now: If this option is selected, the wizard will continue with purging the database. After the database is purged, re-initiate the upgrade process.

    Configure the following settings for purging:

    • Remove the deleted products and components older than x day(s): Specify the number of days after which to purge deleted product and component data. The default value is 180 days.

    • Remove the inventory history data older than x day(s): Specify the number of days after which to purge the inventory history. The default value is 180 days.

    • Remove the Software Application Usage data older than x day(s): Specify the number of days after which to purge the software application usage data collected for Asset Management. The default value is 180 days.

    • Remove the Network Software Usage data older than x day(s): Specify the number of days after which to purge the network software usage data collected for Asset Management. The default value is 180 days.

    • Remove the Web Application Usage data older than x day(s): Specify the number of days after which to purge the Web application usage data collected for Asset Management. The default value is 180 days.

    IMPORTANT:If the purging process is interrupted, the database might become inconsistent.

  • Continue without purging the database: If this option is selected, the wizard continues with the upgrade process.

ZENworks Diagnostic Center

Verify the database using ZENworks Diagnostic Center. If any mismatches are found, then error are logged in the ZDC reports.

The error reports are available in the following location:

  • On Windows: %ZENSERVER_HOME%\logs\migration\zdc\reports

  • On Linux: /var/opt/microfocus/log/zenworks/migration/zdc/reports

NOTE:Verify the database before you upgrade the first Primary Server to ZENworks 2020 Update 2. You will not be prompted to verify the database for the subsequent server upgrades.

Pre-Upgrade Tasks

Ensure that you have stopped all ZENworks services on all other Primary Servers. If services are not stopped on other Primary Servers, then you cannot proceed with the upgrade.

For Linux servers, ensure that Docker and Docker Compose is installed and their services are enabled and running. For more information, see Prerequisites.

Ensure that you have taken complete backup of the ZENworks databases and other important data.

After performing the required actions, select the displayed checkboxes .

Pre-upgrade summary

The following fields are displayed in the summary:

Zone Name: Displays the name of the Management Zone to which this server belongs.

To make changes to any information, click Previous.

Upgrading process

The upgrade process takes several minutes, depending on the capabilities of the hardware and size of data in the database.

Upgrading errors

If there are errors during the upgrade, this page is displayed. For detailed information, see the log files in the following locations. Resolve the errors and restart the upgrade.

On Windows: You can check the logs in the old Novell file path. When the Upgrade process is re-initiated, then check the logs in the new Micro Focus file paths.

Novell File Path:

  • %ZENWORKS_HOME%\logs

    • %ZENWORKS_HOME%\logs\ZENworks_Upgrade_<TimeStamp>.log.xml

    • %ZENWORKS_HOME%\logs\loader-messages.log

    • %ZENWORKS_HOME%\logs\system-update-import.log

    • %ZENWORKS_HOME%\logs\system-update\<Update GUID>

    • %ZENWORKS_HOME%\logs\pre-global-actions.log

    • %WINDOWS_SYSTEM_DRIVE%\tmp\err.log

Micro Focus File Path:

  • %ZENSERVER_HOME%\logs

    • %ZENSERVER_HOME%\logs\ZENworks_Upgrade_<TimeStamp>.log.xml

    • %ZENSERVER_HOME%\logs\loader-messages.log

    • %ZENSERVER_HOME%\logs\system-update-import.log

 

On Linux: You can check the logs in the old Novell file path. When the Upgrade process is re-initiated, then check the logs in the new Micro Focus file paths.

Novell File Path

  • /var/opt/novell/log/zenworks

    • /var/opt/novell/log/zenworks/ZENworks_Upgrade_<TimeStamp>.log.xml

    • /var/opt/novell/log/zenworks/system-update/<Update GUID>

    • /var/opt/novell/log/zenworks/loader-messages.log

    • /var/opt/novell/log/zenworks/system-update-import.log

    • /var/opt/novell/log/zenworks/pre-global-actions.log

    • /tmp/err.log

Microfocus File path

  • /var/opt/microfocus/log/zenworks

    • /var/opt/microfocus/log/zenworks/ZENworks_Upgrade_<TimeStamp>.log.xml

Post-upgrade actions: Run the ZENworks System Status utility

Choose to run the ZENworks System Status utility to launch the ZENworks services heartbeat check before closing the upgrade program. The results are posted in the upgrade log file.

Post Upgrade actions: Run the cleanup Utility

After upgrade, the ZENworks server configuration will be copied from the old Novell file path to the new Micro Focus file path. However, the ZENworks server binaries and old configuration in the old file path is retained during the upgrade process. After verifying whether the upgraded version of the ZENworks Server is working as expected, you can run the cleanup utility provided with the build, to remove the retained server data. For more information, see Running the Cleanup Utility on a Linux or Appliance Server.

Restarting the Server (applicable only for Windows)

Upon a successful upgrade on a Windows Primary Server, you can select between rebooting immediately or later:

  • Yes, Restart the System: If you select this option, the server is rebooted to complete the upgrade process.

  • No, I Will Restart the System Myself: If you select this option, the upgrade process finishes when you reboot the server for the next time.

    IMPORTANT:Reboot the server to complete the upgrade process.

Upgrade completion

The actions you selected previously are performed, including:

  • Upgrading the ZENworks database (done when the first Primary Server is upgraded).

  • Upgrading all ZENworks components installed on the Primary Server.

  • Importing System Update into the zone so that you can upgrade the managed devices in the zone.

Table 2-2 Upgrade Information - Upgrade of additional Primary Servers

Installation Information

Explanation

Primary Server and Zone Credentials

You are prompted for the details of the Primary Server that is already upgraded, the Zone credentials, and the SSL port number.

ZENworks Database Details

(Conditional) If the device cannot connect to the database through the Primary Server that is already upgraded, you are prompted for the details to connect directly to the database.

Port Number

A few ports that might be blocked by your firewall need to be opened. You can open them now or you can manually open them later.

Pre-upgrade summary

WARNING:Before the Pre-upgrade summary page is displayed, the ZENworks services will be stopped on the server. If you cancel the upgrade at this time, you will need to restart the ZENworks services manually.

The following fields are displayed in the summary:

ZENworks Home Directory: Displays the location on the Primary Server where the ZENworks software that is being upgraded is installed.

Zone Name: Displays the name of the Management Zone to which this server belongs.

Upgrading process

The upgrade process takes several minutes, depending on the capabilities of the hardware.

Errors during upgrade

If there are errors during the upgrade, this page is displayed. You must resolve the errors and restart the upgrade. For detailed information, see the log files in the following locations:

On Windows: You can check the logs in both the old Novell and the new Micro Focus file paths:

Novell File Path

  • %ZENWORKS_HOME%\logs

    • %ZENWORKS_HOME%\logs\ZENworks_Upgrade_<TimeStamp>.log.xml

    • %ZENWORKS_HOME%\logs\loader-messages.log

    • %ZENWORKS_HOME%\logs\system-update-import.log

    • %ZENWORKS_HOME%\logs\system-update\<Update GUID>

    • %ZENWORKS_HOME%\logs\pre-global-actions.log

    • %WINDOWS_SYSTEM_DRIVE%\tmp\err.log

Micro Focus File Path

  • %ZENSERVER_HOME%\logs

    • %ZENSERVER_HOME%\logs\ZENworks_Upgrade_<TimeStamp>.log.xml

    • %ZENSERVER_HOME%\logs\loader-messages.log

    • %ZENSERVER_HOME%\logs\system-update-import.log

 

On Linux: You can check the logs in the following file paths

Novell File Path

  • /var/opt/novell/log/zenworks

    • /var/opt/novell/log/zenworks/ZENworks_Upgrade_<TimeStamp>.log.xml

    • /var/opt/novell/log/zenworks/system-update/<Update GUID>

    • /var/opt/novell/log/zenworks/loader-messages.log

    • /var/opt/novell/log/zenworks/system-update-import.log

    • /var/opt/novell/log/zenworks/pre-global-actions.log

    • /tmp/err.log

Microfocus File Path

  • /var/opt/microfocus/log/zenworks

    • /var/opt/microfocus/log/zenworks/ZENworks_Upgrade_<TimeStamp>.log.xml

Post-upgrade actions

Before closing the upgrade program, you can run the ZENworks System Status utility to launch a heartbeat check of the ZENworks services. The results are listed in the installation log.

Restarting the Server (applicable only for Windows)

After the upgrade on a Windows Primary Server, you can select either to reboot immediately or later:

  • Yes, Restart the System: Reboots the server to complete the upgrade process.

  • No, I Will Restart the System Myself: Completes the upgrade process, when you reboot the server the next time.

    IMPORTANT:You must reboot the server to complete the upgrade process.

Upgrade completion

The actions you selected previously are performed, including:

  • Upgrading the ZENworks database (done when the first Primary Server is upgraded).

  • Upgrading all ZENworks components installed on the Primary Server.

  • Importing System Update into the zone so that you can upgrade the managed devices in the zone.

2.2.2 Using a Command Line to Upgrade a Linux Server

Perform the following on the Primary Server that you want to upgrade from ZENworks 2020 to ZENworks 2020 Update 2:

  1. Ensure that the upgrade prerequisites are met.

  2. Start the ZENworks upgrade program, open a Linux terminal, browse to the root of the upgrade media, then enter the following command:

    ./setup.sh --console 

    or

    ./setup.sh -e 
  3. Select the language. English is the default language. Select the number corresponding to your language, then press Enter to continue.

  4. Review the introduction, then press Enter to continue.

    HINT:Type back and press Enter to return to a previous installation option to make the changes. Type quit to exit the wizard.

  5. To accept the end-user license agreement (EULA), type 1, then press Enter.

  6. To accept the license agreement, type 1, then press Enter.

    If you disagree, the upgrade wizard quits.

  7. The Prerequisite check page is displayed. If there are any warning or error messages, resolve the errors, then press Enter to continue.

  8. Type 1 if this is the first Primary Server to be upgraded; otherwise, type 2,then press Enter.

  9. (Conditional) If you typed 1 in the previous page, you will be prompted for the zone administrator credentials. Specify details, then press Enter and continue with Step 11.

  10. (Conditional) If you typed 2 in the previous page, you will be prompted for the details of the upgraded Primary Server and the zone administrator credentials. Specify the required details, then press Enter.

  11. At the end of the Enter the zone administrative user's name line, press Enter to accept the default (Administrator), or specify an administrator name, then press Enter.

  12. Specify a password for the administrator, then press Enter.

  13. In the ZENworks licensing page, you have an option to change the ZENworks licensing type. Specify the ZENworks 2020 Update 2 license, and then click Next.

  14. Stop the ZENworks services on all other Primary Servers, then press Enter to stop the services on the local server.

    Before the upgrade, you should stop the services on all other Primary Servers in the Management Zone. If services are not stopped on other Primary Servers, then you will not be able to proceed with the upgrade.

    Except for the database service, no ZENworks service should be running during the upgrade process.

  15. Review the pre-upgrade summary, then press Enter to continue.

    If you are upgrading the other Primary Servers in the Management Zone, the upgrade starts when you press Enter in this step.

  16. When Upgrade Complete is displayed, press Enter to continue.

    If errors are displayed, see the installation logs in the /var/opt/novell/log/zenworks or /var/opt/novell/log/zenworks/systemupdate/<Update GUID> file.

    If while re-running the upgrade process, errors are displayed, then you can also check the logs in the Micro Focus path. For example, /var/opt/microfocus/log/zenworks

  17. Do any of the following to verify that ZENworks 2020 Update 2 is running:

    • Check the Linux services by using the specific service commands

      For SLES 12, or later servers run the following commands:

      systemctl status microfocus-zenserver.service
      systemctl status microfocus-zenloade.service

      If the services are not running, run the following commands to start the ZENworks services:

      sysytemctl start microfocus-zenserver.service
      sysytemctl start microfocus-zenloader.service
    • Check the Linux services by using the configuration command

      On the server, run the following commands:

      microfocus-zenworks-configure ‑c SystemStatus

      ZENworks services and their status are listed.

      To start the services, run the following command:

      microfocus-zenworks-configure ‑c Start
    • Run ZENworks Control Center

      Use the following URL to open the ZENworks Control Center in a web browser on any device in your network:

      https://<DNS name of the Primary_Server>/zenworks

      or

      https://<IP address of the Primary_Server>/zenworks

  18. To upgrade another Primary Server, repeat from Step 2.

For information on the post-upgrade tasks, see Completing Post-Installation Tasks in the ZENworks Server Installation.

NOTE:If you are using ZENworks Reporting, then after upgrading the zone to ZENworks 2020 Update 2, ensure that you reconfigure ZENworks reporting. For more information, see Reconfiguring ZENworks Reporting Appliance in the ZENworks Reporting Appliance Deployment and Administration Reference.

2.2.3 Upgrading the ZENworks 2020 Update 2 Lighthouse build to ZENworks 2020 Update 2 FCS

If you have deployed ZENworks 2020 Update 2 Lighthouse build, and intend to upgrade the zone to ZENworks 2020 Update 2 FCS, then perform the following steps:

On Linux/Appliance

On Appliance: If you have deployed ZENworks 2020 Update 2 Lighthouse Appliance build on Microsoft Hyper-V, XEN on SLES, or Citrix XenServer and want to update to the ZENworks 2020 Update 2 FCS build, please contact Micro Focus Customer Support, and then perform the following steps.

  1. Create a temporary directory (mntdir) in the /var/tmp or /var/opt/microfocus/zenworks/tmp directory.

  2. Mount the ISO in the temporary directory that was created.

  3. After mounting the ISO, ensure that you restart the ZENloader service.

  4. Go to the mount directory (mntdir).

    Example:

    • If you have mounted to /var/tmp/ location then go to /var/tmp/mntdir.

    • If you have mounted to /var/opt/microfocus/zenworks/ location then go to /var/opt/microfocus/zenworks/mntdir

  5. Run the zman sui Common command.

    When prompted, specify the administrator credentials, and you will be prompted for the root password.

The system update will be imported to the zone, and to track the status in ZCC, go to Configuration > System Updates.

Next follow update deployment steps, see Deploying Updates in the ZENworks System Updates Reference.

On Windows

  1. Mount the ZENworks 2020 Update 2 ISO.

  2. After mounting the ISO restart the ZENloader service.

  3. Open the command prompt and go to the <mount_location>.

  4. Run the zman sui Common command.

    When prompted, specify the administrator credentials.

The system update will be imported to the zone, and to track the status in ZCC, go to Configuration > System Updates.

Next follow update deployment steps, see Deploying Updates in the ZENworks System Updates Reference.

2.2.4 Running ZENworks Diagnostic Center to Verify the Database Schema

The first time you upgrade any Primary Server to ZENworks 2020 Update 2, you must verify the database schema. Do not perform this procedure for the subsequent server upgrades.

Verifying an Embedded Database Schema

  1. At the Primary Server’s console prompt, run the following commands:

    • On Windows

      cd to MEDIA_ROOT\Common\tools\zdc

      zdc_verifyDB.bat

    • On Linux

      cd to MEDIA_PATH/Common/tools/zdc

      ./zdc_verifyDB

    ZENworks Diagnostic Center runs the diagnostic tests and generates the results in HTML format. On a Windows Primary Server, the reports are stored in the following location: %ZENSERVER_HOME%\logs\zdcreports\%SESSION%

    /var/opt/microfocus/log/zenworks/zdcreports

    On a Linux Primary Server the reports are stored in the following location:

    /var/opt/microfocus/log/zenworks/zdcreports

    To view the reports, open index.html, located in the report directory.

    The complete log of diagnostic tests is stored in the following locations:

    On Windows: %ZENSERVER_HOME%\logs\zdcreports\zdc_zen11_verify_%SESSION%.log

    On Linux: /var/opt/microfocus/log/zenworks/zdcreports

Verifying an External Database Schema

Perform the following steps to verify an external database schema such as external PostgreSQL, Microsoft SQL, or Oracle database schema:

  1. At the Primary Server’s console prompt, run the following commands:

    • On Windows

      cd to MEDIA_PATH/Common/tools/zdc

      zdc_verifyDB.bat -d check

    • On Linux

      cd to MEDIA_PATH/Common/tools/zdc

      ./zdc_verifyDB -d check

      NOTE:The -d check parameter must be used only when you migrate the database from one device to another. Do not use the -d check parameter if the database is upgraded on the same device.

  2. Specify the type of database. Type the relevant number based on the database type:

    • (1) PostgreSQL

    • (2) MS-SQL

    • (3) Oracle

  3. Specify the database details, based on the selected database (Microsoft SQL, PostgreSQL, or Oracle).

    NOTE:If you are using an Microsoft SQL database, based on the type of authentication you choose to log in, enter the user name in the relevant format:

    • Windows Authentication: <name>@<domain>

    • SQL Server Authentication: <name>

  4. (Conditional) If the database is Remote PostgreSQL, enter the Database Engine Name.

    ZENworks Diagnostic Center runs the diagnostic tests and generates the results in HTML format. On a Windows Primary Server the reports are stored in the following location: %ZENSERVER_HOME%\logs\zdcreports\%SESSION%

    On a Linux Primary Server the reports are stored in the following location:

    /var/opt/microfocus/log/zenworks/zdcreports

    To view the reports, open index.html, located in the report directory.

    The complete log of diagnostic tests is stored in the following locations:

    On Windows: %ZENSERVER_HOME%\logs\zdcreports\zdc_zen11_verify_%SESSION%.log

    On Linux: /var/opt/microfocus/log/zenworks/zdcreports

2.2.5 Running the Cleanup Utility

After upgrade, the ZENworks server configuration will be copied from the old Novell file path to the new Micro Focus file path. However, the ZENworks server binaries and old configuration in the old file path is retained during the upgrade process. After verifying whether the upgraded version of the ZENworks Server is working as expected, you can run the cleanup utility provided with the build, to remove the retained server data. The topics covered in this section are as follows:

Viewing the Renamed Services and File Locations on a Linux or Appliance Server

After a successful upgrade, you can now go ahead and view the changes introduced in this release:

New File Path for ZENworks Server Data

Example:

  • Log Files: The log files will now be available in the new Micro Focus path (/var/opt/microfocus/log/zenworks).

    The log files in the old Novell path (/var/opt/novell/log/zenworks) will also be retained. These files will not be deleted even after you run the cleanup utility.

    NOTE:All new server related log files that are generated after the upgrade, will be available only in the new Micro Focus file path and not in the old Novell file path.

  • Conf Files: The configuration files for only the ZENworks Server will now be available in the new Micro Focus path (/etc/opt/microfocus/zenworks).

    The configuration files for both the server and the agent will also be retained in the old Novell path (/etc/opt/novell/zenworks). When you run the cleanup utility, the configuration files related to the ZENworks Server will be deleted from the old path. However, the files related to the ZENworks agent will be retained in the old path.

  • Libraries: The libraries for only the ZENworks Server will now be available in the new Micro Focus path (/opt/microfocus/zenworks).

    The libraries for both the server and the agent will also be retained in the old Novell path (/opt/novell/zenworks). When you run the cleanup utility, the libraries related to the ZENworks Server will be deleted from the old path.

Renamed Configure Actions

Configure actions have been renamed from Novell to Micro Focus. For example, the configure action novell-zenworks-configure -c CalibrateMemoryConfigureAction is now renamed to microfocus-zenworks-configure -c CalibrateMemoryConfigureAction. Configure actions that follow the Novell naming convention have been deprecated in this release and will be available along with the Configure actions that follow the Micro Focus naming convention.

Renamed Services

ZENworks Server services have been renamed from Novell to Micro Focus. For example, novell-zenserver.service is renamed to microfocus-zenserver.service. Similarly, services such as novell-zenloader.service and novell-zenjoinproxy.service are renamed to microfocus-zenloader.service and microfocus-zenjoinproxy.service, respectively

However, the old service names will still be displayed but will be inactive. You can run the cleanup utility to remove the old server services.

Therefore, while using the systemctl commands to start or stop services, ensure that you use the renamed services in the command.

NOTE:Some services such as novell-zenworks-xplatzmd.service will not be renamed and will retain the old naming convention even after running the cleanup utility.

The service related to the embedded database for PostgreSQL will also retain the Novell naming convention, that is, the zenpostgresql.service will remain enabled and will not be removed during cleanup.

Running the Cleanup Utility on a Linux or Appliance Server

The cleanup utility enables you to remove the old ZENworks configuration data that is retained in the Novell file path and the old versions of the ZENworks Server services that are inactive. Run the cleanup utility only after verifying whether the upgraded server is working as expected. The following are retained after running the cleanup utility:

  • ZENworks agent related data such as the configuration files and libraries will be retained in the old Novell file path.

  • The ZENworks System Updater Service (ZeUS) folder will be retained in the /opt/novell/zenworks/ZeUS path.

  • The System Update and other log files will be retained in the /var/opt/novell/log/zenworks path.

  • Services related to the ZENworks agent, that is, novell-zenworks-xplatzmd.service, will be retained with the Novell naming convention.

  • The service related to embedded PostgreSQL, that is, zenpostgresql.service, will not be renamed.

To run the clean up utility, execute the following command as a root user and confirm whether you want to proceed with the cleanup:

/opt/microfocus/zenworks/bin/zen-legacy-cleanup.sh

To run the clean up utility silently without user interaction, add the -s flag into the command.

The logs for this cleanup utility can be found at the /var/opt/microfocus/log/zenworks/zen-legacy-cleanup_<timestamp>.log location.

After running the command, you can verify whether the files in the old file path /opt/novell/zenworks/ and old server services that follow the Novell naming convention, are removed from the server or not.

NOTE:When you run the cleanup utility, Sybase related files will be retained, which can be removed manually after verifying whether the upgraded ZENworks Server is working as expected.

If you have migrated the Sybase database to any other database using the database migration tool, the database files, services, and Sybase packages might be retained in the Primary Server. To clean-up the data, run the following scripts on the Primary Server that had the Sybase database.

  • On Linux/Appliance: Run the script available in: /opt/microfocus/zenworks/install/downloads/tools/cleanupSybase.sh.

Viewing the Renamed Services and File Locations on a Windows Server

After a successful upgrade, you can now go ahead and view the changes introduced in this release:

New File Path for ZENworks Server Data

Example:

  • Log Files: The log files will now be available in the new Micro Focus path. Example: C:\Program Files (x86)\Micro Focus\ZENworks\logs.

    The log files in the old Novell path will be retained. Example: C:\Program Files (x86)\Novell\ZENworks\logs. These files will not be deleted after you run the cleanup utility.

    NOTE:All new server related logs files that are generated after the upgrade, will be available only in the new Micro Focus file path and not in the old Novell file path.

  • Libraries: The libraries for only the ZENworks Server will now be available in the new Micro Focus path. Example: C:\Program Files (x86)\Micro Focus\ZENworks\lib.

    The libraries for both the server and the agent will also be retained in the old Novell path. Example: C:\Program Files (x86)\Novell\ZENworks\lib. When you run the cleanup utility, the libraries related to the ZENworks Server will be deleted from the old path.

Renamed Services

ZENworks Server services have been renamed from Novell to Micro Focus. Example: Novell ZENworks Join Proxy is renamed to Microfocus ZENworks Join Proxy. Similarly, the service Novell ZENworks Loader is renamed to Microfocus ZENworks Loader, Novell ZENworks Services Monitor is renamed to Microfocus ZENworks Services Monitor and Novell ZENworks Server server is renamed to Microfocus ZENworks Server.

However, the services that use the old Novell naming convention will still be displayed but will be disabled. You need to run the cleanup utility to remove these services.

NOTE:Services such as the Novell ZENworks Agent Service will remain enabled and will retain the Novell naming convention after running the cleanup utility.

The service related to the embedded database for PostgreSQL will also retain the Novell naming convention, that is, the Novell ZENworks Embedded Datastore-PostgreSQL will remain enabled and will not be removed during cleanup.

Introduction of a New Environment Variable

A new environment variable %ZENSERVER_HOME% has been introduced in this release that points to the new Micro Focus file path C:\Program Files (x86)\Micro Focus\ZENworks. The existing environment variable %ZENWORKS_HOME% is still applicable to access the ZENworks agent data, which is retained in the Novell file path.

Renamed Configure Actions

Configure actions have been renamed from Novell to Micro Focus. For example, the configure action novell-zenworks-configure -c CalibrateMemoryConfigureAction is now renamed to microfocus-zenworks-configure -c CalibrateMemoryConfigureAction. Configure actions that follow the Novell naming convention have been deprecated in this release and will be available along with the Configure actions that follow the Micro Focus naming convention.

Running the Cleanup Utility on Windows Server

The cleanup utility enables you to remove the old ZENworks Server data that is retained on the Novell file path and the old versions of the ZENworks Server services that are disabled. Run the cleanup utility only after verifying whether the upgraded ZENworks Server is working as expected. The following are retained after running the cleanup utility:

  • ZENworks agent related data such as configuration files and libraries will be retained in the Novell file path. Example: C:\Program Files (x86)\Novell\ZENworks.

  • The log files will be retained in the Novell file path. Example: C:\Program Files (x86)\Novell\ZENworks\logs.

  • The ZENworks System Updater Service (ZeUS) folder will be retained in the Novell file path. Example: C:\Program Files (x86)\Novell\ZENworks\ZeUS.

  • Services related to the ZENworks agent will retain the Novell naming convention, that is, the Novell ZENworks Agent Service will remain enabled. They will not be removed during cleanup.

  • The service related to the embedded database for PostgreSQL will also retain the Novell naming convention, that is, the Novell ZENworks Embedded Datastore-PostgreSQL will be in a enabled state. It will not be removed during cleanup.

To cleanup the retained data, run the cleanup utility as an administrator. The utility is available at the following location:

%ZENSERVER_HOME%\bin\ZENLegacyCleanup.exe

The logs for this cleanup utility can be found at the %ZENSERVER_HOME%\logs\LegacyUninstall\ZENLegacyCleanup_<timestamp>.log location.

After running the command, you can verify whether the ZENworks Server data in the old Novell file path and the ZENworks Server services that follow the Novell naming convention, are removed from the server or not.

NOTE:When you run the cleanup utility, Sybase related files will be retained, which can be removed manually after verifying whether the upgraded ZENworks Server is working as expected.

If you have migrated the Sybase database to any other database using the database migration tool, the database files, services, and Sybase packages might be retained in the Primary Server. To clean-up the data, run the following scripts on the Primary Server that had the Sybase database.

  • On Windows: Open the PowerShell console and run the script available in the ZENWORKS_HOME/install/downloads/tools/cleanupSybase.ps1 location.

    Ensure that you DO NOT USE COMMAND PROMPT.

2.2.6 Post-Upgrade Configurations

After successfully upgrading the Primary Servers, perform the following post-upgrade configurations:

  1. Configure the system update entitlement by activating ZENworks licenses. For more information on licensing, see TID 7024521.

    NOTE:

    • After licensing ZENworks, ensure that you check for updates in ZENworks System Update page.

  2. Using the appliance key from Software Licenses and Downloads, register and then configure Online Updates. For more information, see:

  3. Ensure that you verify the version of ZENworks in ZENworks Control Center (Configuration > Server Hierarchy).

  4. Ensure that the status of System Update is successful.

  5. Ensure that you run the latest ZDC to verify the schema. For more information, see ZENworks Diagnostic Center.

  6. (Conditional) Ensure that you apply the latest Tuxera NTFS driver or imaging updates. For more information, see Adding Tuxera Driver for ZENworks Imaging.

  7. Ensure that you configure reporting to get the newly available domains. For more information, see ZENworks Reporting Configuration.

  8. (Conditional) If ZENworks is connected to ZENworks Reporting Server, then ensure that you upgrade the Reporting database domain to the upgraded ZCM Database. For more information, see Reconfiguring ZENworks Reporting Appliance in ZENworks Reporting Appliance Deployment and Administration Reference.

  9. Ensure that the ZooKeeper service is up and running at all times to enable proper functioning of various ZENworks components such as the ZENworks Loader services and the Vertica database. To verify the status of the ZooKeeper service, see the Diagnostics page in ZCC. For more information on the ZooKeeper component, see ZooKeeper in the Vertica Reference Guide.

    NOTE:

    • The TID is applicable only for Window servers. Refer to the TID and perform the specified steps.

    • In case of multiple Primary servers in the zone, by default, the Zookeeper service is and active on the first upgraded Primary Server node.

    If the Primary Servers in your zone are unable to communicate with the ZooKeeper service due to firewall restrictions, you can run the following configure action to open the ZooKeeper ports:You also need to ensure that the firewall allows client connections from other Primary Servers to the ZooKeeper services on port 6789. If the Primary Servers in your zone are unable to access the ZooKeeper service, then to open the ports, you can run the following Configure action on the server in which ZooKeeper is enabled.

    microfocus-zenworks-configure -c ClusterFirewallConfigureAction -Doperation=add -Dservice=zookeeper

    However, if the Primary Server that is within the DMZ is unable to access the ZooKeeper service within the corporate network, then you need to manually open the port 6789 in the corporate firewall.

    For more information on the ZooKeeper ports, see ZENworks 2020 TCP and UDP Ports.

  10. After upgrade, the ZENworks server configuration will be copied from the old Novell file path to the new Micro Focus file path. However, the ZENworks server binaries and old configuration in the old file path is retained during the upgrade process. After verifying whether the upgraded version of the ZENworks Server is working as expected, you can run the cleanup utility provided with the build after a couple of weeks, to remove the retained server data.

    For more information, see Running Cleanup Utility on a Linux or Appliance Server or Running the Cleanup Utility on Windows Server.

  11. (Optional) When you run the cleanup utility, Sybase related files will be retained, which can be removed manually after verifying whether the upgraded ZENworks Server is working as expected.

    If you have migrated from the Sybase database to any other database using the database migration tool, the database files, services, and Sybase packages might be retained in the Primary Server. To cleanup the data, run the following scripts on the Primary Server that had the Sybase database.

    • On Linux/Appliance: Run the script available in: /opt/microfocus/zenworks/install/downloads/tools/cleanupSybase.sh

    • On Windows: Open the PowerShell console and run the script available in the ZENWORKS_HOME/install/downloads/tools/cleanupSybase.ps1 location.

      On Windows, ensure that you DO NOT USE COMMAND PROMPT.