34.2 Testing the Upgrade CPKs

For the CPKs that you want to use to upgrade your servers, you should test the CPKs first in order to determine whether the variables required by the CPKs are working correctly, how long it takes for each CPK’s Distribution to complete, and to confirm that the Desktop Management software is being upgraded correctly.

Plan to configure test servers for the platforms in your network where you will be upgrading ZENworks Desktop Management. To test all of the .cpk files, you need to test servers that are properly configured for NetWare, Windows, and OES Linux. All information in this section pertaining to the NetWare platform applies also to OES NetWare.

34.2.1 Testing Prerequisites Checklist

  • Test Machines: Select test machines that are similar to your production servers so that the timing notes you take in Step 9 are accurate.

  • eDirectory: For Windows test servers, eDirectory™ 8.7 must be installed to the C: drive as specified in Section 3.2.1, Software Requirements for Installing All Components.

    ZENworks 7 did not support eDirectory 8.8, so the ZENworks 7 software that you will install on a Windows test server will not work with eDirectory 8.8, and it can compromise your CPK upgrade testing.

  • Desktop Management Server software: Install the version you want to test. The software must be in a configured and working state.

  • Middle Tier software: Install the version you want to test. The software must be in a configured and working state.

  • Subscriber and Policy/Package Agent software: ZENworks 6.5 (or later) Server Management must be running on your test servers in order to execute the CPKs.

    A Distributor server is not needed because you are only testing the CPKs by running them individually; you are not distributing them.

  • ConsoleOne: This must be the minimum version required for the version of ZENworks Desktop Management installed on your test server. ConsoleOne must not be in use when testing the CPK upgrade for the ConsoleOne snap-ins.

  • Schema Extensions: Make sure the tree where these test servers are located has its schema extended to ZENworks 7 Desktop Management with SP1.

    For information on extending the schema, see Section 29.3, Extending the eDirectory Schema.

34.2.2 Testing the CPKs

  1. To have the CPKs available on your test server for local upgrade testing, copy the .cpk files that you want to test to your applicable test servers. Use the following list to determine which files to copy (be sure to note the full path to where you copied the files).

    For upgrading NetWare and OES NetWare test servers  

    Located on the Novell ZENworks 7 with Support Pack 1 Companion 4 CD

    stopinv.cpk

    zdn7bksp1.cpk

    stopwol.cpk

    zdn7midsp1.cpk

    startinv.cpk

    c1-zen7-snap.cpk

    startwol.cpk

    language-agent.cpk

    For upgrading clustered NetWare and OES NetWare test servers  

    Located on the Novell ZENworks 7 with Support Pack 1 Companion 4 CD

    stopinv.cpk

    zdnc7bksp1.cpk

    stopwol.cpk

    c1-zen7-snap.cpk

    startinv.cpk

    language-agent.cpk

    startwol.cpk

     

    For upgrading Windows test servers  

    Located on the Novell ZENworks 7 with Support Pack 1 Companion 4 CD

    zdw7bksp1.cpk

    c1-zen7-snap.cpk

    zdw7midsp1.cpk

    language-agent.cpk

    For upgrading OES Linux test servers  

    Located on the Novell ZENworks 7 with Support Pack 1 Companion 3 CD

    zdl7mbcksp1.cpk

    language-agent.cpk

    c1-zen7-snap.cpk

     

    For your convenience, the language-agent.cpk and c1-zen7-snap.cpk files have been duplicated on the two Companion CDs because they are used by both the OES Linux and NetWare/Windows upgrades. These CPKs only copy the MSI files so that they are accessible when needed.

  2. To have the CPKs available in ConsoleOne for viewing their descriptions:

    1. On a workstation running ConsoleOne, right-click the Server Software Packages namespace, then select Insert Software Package.

    2. Browse for and select a .cpk file from where you copied them in Step 1, then click Open.

      In the Files of Type field, you might need to select All Files to see the .cpk files.

  3. Repeat Step 2 until all of the .cpk files you want to test have been inserted under the Server Software Packages namespace.

  4. To view the description of a CPK, click the CPK name and view the information in the right pane.

    You can also click the plus symbol to expand the CPK to view its components, then click the individual components to view the descriptions for each of them.

  5. In the test Subscriber server’s ConsoleOne properties, select the Variables tab and define the variables that are applicable to the Distributions you are testing.

    See Defining Subscriber Variables for a listing.

  6. (Windows only) To make sure that eDirectory is not in a state where it cannot be brought down and back up by the CPKs when the Desktop Management Server component is upgraded, enter the following commands on one of the servers:

    net stop "nds server0"

    net start "nds server0"

  7. (Windows only) Because the IIS Admin Service must be fully functional and in a healthy state when the Middle Tier component is upgraded, check this service’s state before upgrading by manually stopping and starting it, or by restarting the server.

    The IIS Admin Service must be running before applying the CPK so that the CPK can stop the service; otherwise, the CPK will fail to complete.

  8. To test a NetWare or Windows CPK where the Subscriber software is installed (as required in Section 34.2.1, Testing Prerequisites Checklist):

    • NetWare: On the NetWare test server’s console, enter

      package process volume_name:\path_to_file\filename.cpk

      where filename is one of the .cpk filenames.

      This command can be used because on your test server.

    • Windows: Do the following:

      1. Open the c:\zenworks\pds\bin\zfsservice.cfg file in a text editor.

      2. Change the DosBox=Off line to be DosBox=On.

      3. Save and exit the file.

      4. On the DOS command line, enter

        package process drive_letter:\path_to_file\filename.cpk

        where filename is one of the .cpk filenames.

    See Step 11 for Linux CPK testing instructions.

    For each platform you are testing, run the CPKs in the following order:

    NetWare Server  

    1. stopinv.cpk

    2. stopwol.cpk

    3. zdn7bksp1.cpk

    4. startinv.cpk

    5. startwol.cpk

    6. zdn7midsp1.cpk

    7. c1-zen7-snap.cpk

    8. language-agent.cpk

    NetWare Server Cluster  

    1. stopinv.cpk

    2. stopwol.cpk

    3. zdnc7bksp1.cpk

    4. startinv.cpk

    5. startwol.cpk

    6. c1-zen7-snap.cpk

    7. language-agent.cpk

    IMPORTANT:This must be performed on the clustered resource. Then each node must be made the resource, and the process repeated until all nodes have been upgraded.

    Windows Server  

    1. zdw7bksp1.cpk

    2. zdw7midsp1.cpk

    3. c1-zen7-snap.cpk

    4. language-agent.cpk

  9. As a NetWare CPK is running, note how long it takes for each CPK to complete.

    You will need this information to properly configure the schedules when creating and sending the Distributions.

    When sending multiple Distributions to one server, especially if the Distributions include the helper CPKs for your NetWare servers, the distribution processes for each CPK should occur sequentially.

  10. Repeat Step 8 and Step 9 for each NetWare or Windows CPK you want to test.

  11. To test the OES Linux CPKs, follow the instructions in Section 34.4.1, Upgrading with a Distribution, but send the Distributions to only one server, preferably a test server.

    Timing and variable issues do not apply to the OES Linux CPK (zdl7mbcksp1.cpk), so to test it you only need to send the Distributions to one server.

  12. To verify that the CPKs upgraded properly, follow the instructions in Section 34.5.2, Verifying That the Servers Have Been Upgraded, then return to Step 13.

  13. Continue with Section 34.3, Upgrade Prerequisites Checklist for your production servers.