You can upgrade by using a graphical user interface (GUI) program or a command line (Linux only).
IMPORTANT:
Do not use the ZENworks System Update to upgrade the Primary Servers to ZENworks 2017.
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.
To migrate a ZENworks 11 SP4 Appliance to ZENworks 2017, see Section 3.0, Appliance Migration.
Perform the following procedure on the Primary Server that you want to upgrade to ZENworks 2017 if all the prerequisites explained in Section 1.4, Prerequisites are met:
To start the ZENworks 2017 upgrade program:
Linux: Open a Linux terminal, browse to the root of the ZENworks 2017 installation media, then enter the sh setup.sh command.
Windows: Do one of the following:
Browse to the root of the ZENworks 2017 installation media, then double-click setup.exe.
Open a DOS window, browse to the root of the ZENworks 2017 installation media, then enter the setup.exe command.
During upgrade, see Table 1-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.
Do one of the following on the Windows device:
If you selected to reboot automatically (you selected the Yes, restart the system option during the upgrade; see Restarting the Server (applicable only for Windows)), continue with Step 5 after the booting process has completed and the services have started.
If you selected to reboot manually (you selected the No, I will restart the system myself option during the upgrade; see Restarting the Server (applicable only for Windows)), wait for the upgrade to complete and the services to start in order to verify it in Step 4.
After the upgrade is complete and the ZENworks services are restarted, do any of the following to verify that ZENworks 2017 is running:
Check the Windows services by using the GUI:
On the server, click Start, select Administrative Tools > Services, then review the status of the Novell ZENworks Loader and Novell ZENworks Server services.
If the services are not running, start them. Right-click the Novell ZENworks Server service, select Start, right-click the Novell ZENworks Loader service, then select Start.
Alternatively, you can use the Restart option for Novell ZENworks Server to stop all of the related services, which stops and then starts each of them in their correct order, including Novell ZENworks Loader.
Launch ZENworks Control Center:
Use the following URL to open ZENworks Control Center in a web browser on any device in your network:
https://DNS_name_or_IP_address_of_Primary_Server:port_number/zenworks
Check the Linux services by using the specific service command:
On the server, run the following commands:
/etc/init.d/novell-zenserver status
/etc/init.d/novell-zenloader status
For SLES 12, or later servers run the following commands:
systemctl status novell-zenserver
systemctl status novell-zenloader
If the services are not running, run the following commands to start the ZENworks services:
/etc/init.d/novell-zenserver start
/etc/init.d/novell-zenloader start
For SLES 12, or later servers run the following commands:
systemctl start novell-zenserver
systemctl start novell-zenloader
Check the Linux services by using the configuration command:
On the server, run the following command:
/opt/novell/zenworks/bin/novell-zenworks-configure ‑c SystemStatus
ZENworks services and their statuses are displayed.
To start the services, run the following command:
/opt/novell/zenworks/bin/novell-zenworks-configure ‑c Start
To upgrade another Primary Server, repeat from Step 1.
IMPORTANT:Repeat these steps until all Primary Servers in the Management Zone are upgraded.
The Table 1-1 provides the upgrade information for upgrading from ZENworks 11 SP4 to ZENworks 2017.
Table 1-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 ZENworks 2017 Update2 System Requirements. 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 1-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.
|
|
ZENworks Diagnostic Center |
Verify the database using ZENworks Diagnostic Center. For more information, see Running ZENworks Diagnostic Center to Verify the Database Schema. NOTE:Verify the database before you upgrade the first Primary Server to ZENworks 2017. You will not be prompted to verify the database for the subsequent server upgrades. After you verify the database, select Yes, I have verified the database schema using ZDC. This option confirms that you have verified the ZENworks database schema is correct. |
|
ZENworks Services Optimization |
If ZENworks services are not configured for high performance, this page is displayed. You can select Yes to reconfigure the ZENworks Services setting during installation or select No to ignore. If you select Yes, then the ZENworks upgrade installer increases the RAM configuration settings for ZENServer and ZENloader. |
|
ZENworks Licensing |
In the ZENworks Licensing page, enter the ZENworks 2017 license information. |
|
Pre-upgrade summary |
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. Upgrade Database: Indicates the upgrade status of the ZENworks database and automatically checks whether it needs to be upgraded or not. 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. During the upgrade, you can click Cancel to stop, which leaves changes in the files that were upgraded up to that point. For more information on what to do after canceling, contact Micro Focus Support. |
|
Upgrading errors |
If there are errors during the upgrade, this page is displayed. For detailed information, see the log files in the following locations: On Windows
On Linux
Resolve the errors and restart the upgrade. |
|
Post-upgrade actions |
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. |
|
Restarting the Server (applicable only for Windows) |
Upon a successful upgrade on a Windows Primary Server, you can select between rebooting immediately or later:
|
|
Upgrade completion |
The actions you selected previously are performed, including:
|
Table 1-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. Upgrade Database: Indicates whether the ZENworks database will be upgraded. Its status is automatically checked by the program to see whether it needs to be upgraded. |
|
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. For detailed information, see the log files in the following locations: On Windows
On Linux
You must resolve the errors and restart the upgrade. |
|
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:
|
|
Upgrade completion |
The actions you selected previously are performed, including:
|
Perform the following on the Primary Server that you want to upgrade from ZENworks 11 SP4 (11.4.x) to ZENworks 2017:
Ensure that the upgrade prerequisites are met, as explained in Section 1.4, Prerequisites.
Start the ZENworks 2017 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
Select the language. English is the default language. Select the number corresponding to your language, then press Enter to continue.
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.
To accept the end-user license agreement (EULA), type 1, then press Enter.
To accept the license agreement, type 1, then press Enter.
If you disagree, the upgrade wizard quits.
The Prerequisite check page is displayed. If there are any warning or error messages, resolve the errors, then press Enter to continue.
Type 1 if this is the first Primary Server to be upgraded; otherwise, type 2,then press Enter.
(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.
(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.
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.
Specify a password for the administrator, then press Enter.
If the device connects to the database server, continue with Step 13. If not, you will be prompted for the database details. Specify the database details, then press Enter.
Run ZENworks Diagnostic Center to verify the database. For more information, see Running ZENworks Diagnostic Center to Verify the Database Schema.
NOTE:Verify the database before you upgrade the first Primary Server to ZENworks 2017. You do not need to verify the database for the subsequent server upgrades.
Confirm that you have verified the ZENworks database schema by using the ZENworks Diagnostic Center. Press Y to continue.
You need to confirm to proceed with the upgrade.
In the ZENworks licensing page, enter the ZENworks 2017 license, and then click Next.
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 Primary Servers in the Management Zone.
Except for the database service, no ZENworks service should be running during the upgrade process.
If ZENworks services are not configured for high performance, select 1 to reconfigure the ZENworks services setting during installation or select 2 to ignore.
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.
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.
Do any of the following to verify that ZENworks 2017 is running:
Check the Linux services by using the specific service commands
On the server, run the following commands:
/etc/init.d/novell-zenserver status
/etc/init.d/novell-zenloader status
For SLES 12, or later servers run the following commands:
systemctl status novell-zenserver
systemctl status novell-zenloader
If the services are not running, run the following commands to start the ZENworks services:
/etc/init.d/novell-zenserver start
/etc/init.d/novell-zenloader start
For SLES 12, or later servers run the following commands:
systemctl start novell-zenserver
systemctl start novell-zenloader
Check the Linux services by using the configuration command
On the server, run the following commands:
/opt/novell/zenworks/bin/novell-zenworks-configure ‑c SystemStatus
ZENworks services and their status are listed.
To start the services, run the following command:
/opt/novell/zenworks/bin/novell-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
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 Guide.
The first time you upgrade any Primary Server to ZENworks 2017, you must verify the database schema. Do not perform this procedure for the subsequent server upgrades.
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: %ZENWORKS_HOME%\logs\zdcreports\%SESSION%
On a Linux Primary Server the reports are stored in the following location:
/var/opt/novell/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: %ZENWORKS_HOME%\logs\zdcreports\zdc_zen11_verify_%SESSION%.log
On Linux: /var/opt/novell/log/zenworks/zdcreports
Perform the following steps to verify an external database schema such as external Sybase, Microsoft SQL, or Oracle database schema:
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.
Specify the type of database. Type the relevant number based on the database type:
(1) Sybase
(2) MS-SQL
(3) Oracle
Specify the database details, based on the selected database (Microsoft SQL, Sybase, 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>
(Conditional) If the database is Remote Sybase, 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: %ZENWORKS_HOME%\logs\zdcreports\%SESSION%
On a Linux Primary Server the reports are stored in the following location:
/var/opt/novell/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: %ZENWORKS_HOME%\logs\zdcreports\zdc_zen11_verify_%SESSION%.log
On Linux: /var/opt/novell/log/zenworks/zdcreports