To upgrade from ZfS 3/SP1 to ZfS 3.0.2, review the following sections:
The Upgrade Wizard upgrades ZfS 3/SP1 Tiered Electronic Distribution (TED) objects and servers to ZfS 3.0.2. This wizard does not upgrade other ZfS components.
We recommend that you upgrade Policy and Distribution Services from the ZENworks for Servers Program CD or the ZENworks 6 Server Management Program CD. However, if you need to copy the CD structure to a hard drive, the path between the root of the hard drive and the first CD directory can contain only directory names that conform to the 8.3-character DOS file naming convention. If any long directory names exist in the path, the upgrade program will not work.
Review the following to understand what the Upgrade Wizard does, and to understand the issues involved in upgrading Policy and Distribution Services from ZfS 3/SP1 to ZfS 3.0.2:
In summary, the Upgrade Wizard upgrades the ZfS 3/SP1 objects to ZfS 3.0.2 objects for the associated servers. It also installs ZfS 3.0.2 software on ZfS 3/SP1 servers.
We recommend that you upgrade your Distributors first; otherwise, your Distributors might not be able to send Distributions to the upgraded Subscribers. You can then gradually upgrade your Subscribers. For more information, see Issues Concerning Upgrading Incrementally and Installing ZfS Software to New Servers When You Are Also Upgrading Incrementally.
In summary, the Upgrade Wizard does not install ZfS 3.0.2 where ZfS 3/SP1 was not installed. ZfS objects are necessary for identifying target servers.
You use the Upgrade Wizard to upgrade Distributor and Subscriber objects in a given tree.
If you have multiple trees with ZfS objects, you will need to run the Upgrade Wizard twice per tree, because the wizard discovers your target servers by their corresponding Distributor or Subscriber objects contained in the tree. You would run the wizard once for Distributors, and again for Subscribers.
For a variety of reasons, you might need to upgrade your ZfS 3/SP1 Subscriber objects incrementally per tree. For example, because the upgrade process is done for one object and its server at a time, your network could have so many Subscriber servers that you might not want to perform the upgrade in one long session.
Review the following sections to determine whether to upgrade incrementally:
We recommend (per tree) that you upgrade all of your Distributors first, then upgrade your Subscribers. Consider the following in determining whether to upgrade your Subscribers incrementally:
1. Upgrade the ZfS 3 Distributor to version 3.0.2 that was sending Desktop Application Distributions.
2. Rebuild the Desktop Application Distributions as version 3.0.2 Distributions, but do not allow them to be sent yet.
3. Upgrade the version 3 Subscribers that need the upgraded Desktop Application Distributions.
4. Send the upgraded Desktop Application Distributions.
If you have ZfS 3/SP1 in your network, and also have servers where ZfS has not been installed and you want to install ZfS to those servers, then you must do the following to prevent incompatibility problems:
This will ensure that all Distributors and Subscribers work together correctly.
You can upgrade Policy and Distribution Services on the following NetWare and Windows server platforms:
WARNING: If you intend to upgrade incrementally, be aware that some system requirements for ZfS 3.0.2 should not be applied to servers where you will continue to use ZfS 3/SP1. Meet the server requirements only for the servers you will be upgrading to ZfS 3.0.2.
The NetWare servers where you upgrade Policy and Distribution Services must meet the following minimum system requirements:
Requirement | NetWare 5.1 | NetWare 6 |
---|---|---|
Support Pack Version |
5 For instructions, see Installing NetWare 5.1 Support Pack 3 or 4. |
2 (or 3 if using JVM 1.4.1) |
Novell eDirectory |
8.x |
8.x |
Cache for ZENworks Database |
32 MB |
32 MB |
Server RAM |
384 MB; 512 MB is recommended for larger deployments of Policy and Distribution Services. |
512 MB |
Server CPU Type |
Pentium* II or faster To enhance ZfS efficiency, it is more important to increase the amount of RAM than to increase the processor speed. |
Pentium III or faster To enhance ZfS efficiency, it is more important to increase the amount of RAM than to increase the processor speed. |
Disk Space for Policy and Distribution Services Files |
35 MB |
35 MB |
Disk Space for ConsoleOne Files |
70 MB |
70 MB |
Database File Location |
Any volume other than SYS: |
Any volume other than SYS: |
The Windows servers where you upgrade Policy and Distribution Services must meet the following minimum system requirements:
Requirement | Windows NT Server | Windows 2000 Server |
---|---|---|
Service Pack Version |
6a For instructions, see Installing Windows NT 4 Service Pack 6a. |
2 For instructions, see Installing Windows 2000 Service Pack 3. |
Novell eDirectory |
8.x |
8.x |
Server RAM |
384 MB |
512 MB |
Server CPU Type |
Pentium II or faster |
Pentium III or faster |
Disk Space for Policy and Distribution Services Files |
35 MB |
35 MB |
Disk Space for ConsoleOne Files |
50 MB |
50 MB |
IMPORTANT: All target servers should have fully qualified DNS names. For more information, see Ensuring Successful DNS Name Resolution.
You need to know the following information to upgrade ZfS 3/SP1 objects and servers to ZfS 3.0.2:
Determine the trees where ZfS 3/SP1 objects have been installed. You need to extend the schema on these trees before upgrading. Extending the ZfS 3.0.2 schema does not remove the ZfS 3/SP1 schema extensions.
If you have ZfS 3/SP1 installed across multiple trees, you should first upgrade the Distributors per tree, then incrementally upgrade the Subscribers in those trees.
ZfS 3/SP1 and ZfS 3.0.2 can coexist in your network. You can upgrade ZfS 3/SP1 objects incrementally, or all at once (per tree). Determine per tree whether you want to upgrade the ZfS 3/SP1 objects incrementally. For more information, see Issues Concerning Upgrading Incrementally.
The upgrade wizard displays all ZfS 3/SP1 Distributor objects in the tree.
If you are upgrading incrementally in a given tree, make lists of the installed ZfS 3/SP1 Distributor objects that you want to upgrade together. If you need to temporarily keep a ZfS 3 Distributor for distributing NAL/TED Distributions, note this Distributor separately for upgrading later.
If you will be upgrading all Distributor objects in one pass for a given tree, you do not need to make a list.
The upgrade wizard displays all ZfS 3/SP1 Subscriber objects in the tree.
If you are upgrading incrementally in a given tree, make lists of the ZfS 3/SP1 Subscriber objects that you want to upgrade together, so you can use that list to select which Subscribers to upgrade.
If you will be upgrading all Subscriber objects in one pass for a given tree, you do not need to make a list.
For servers that were both a ZfS 3/SP1 Distributor and Subscriber, the Subscriber software is also upgraded when you upgrade the Distributor software (which is usually done first). Therefore, you do not need to list these Subscriber servers for upgrading again if you have already upgraded them as Distributors.
IMPORTANT: Make sure that you do not upgrade a server to be a ZfS 3.0.2 Subscriber when it is still a ZfS 3 Distributor. If you select to upgrade a ZfS 3/SP1 Distributor to be only a ZfS 3.0.2 Subscriber, all Distributor functionality will be lost. Keep this in mind for any NAL/TED Distributors you can upgrade later.
If you have ZfS objects installed to multiple trees, repeat the following upgrade instructions for each tree. Also, if you are upgrading incrementally, repeat the following upgrade instructions for each incremental group.
To upgrade ZfS 3/SP1 to ZfS 3.0.2, perform the following tasks in order:
To prepare for upgrading ZfS 3/SP1 to 3.0.2:
Review the Readme for any last-minute information concerning upgrading.
README.TXT is located at the root of the ZENworks for Servers Program CD or in the ZENWORKSFORSERVERS directory on the ZENworks 6 Server Management Program CD. READMEZFS302.HTML is located in the DOCUMENT directory on the Program CD, and the most up-to-date HTML version is located on the Novell Documentation Web site.
Make sure you have met the workstation requirements listed in Getting Started.
IMPORTANT: Make sure you have updated each of your ConsoleOne installations, because you will be updating the ZfS 3.0.2 snap-ins before completing the upgrade process (see Installing the New Snap-Ins to ConsoleOne).
Select the workstation you will use to upgrade from.
Make sure you have met all of the server requirements listed in Meeting Policy and Distribution Services Requirements for NetWare and Windows Servers.
If Java has not been unloaded on the target NetWare servers, unload JAVA.NLM.
For example, at each NetWare server's console prompt, type:
java -exit
This will also cause all ZfS software to stop running on the server.
If you have not already done so, log in to the eDirectory tree where you will be updating the ZfS objects.
If you are not logged into this tree, you will not be able to select it during the upgrade process.
You can upgrade Distributors and Subscribers one tree at a time. You can run the Upgrade Wizard as many times as needed.
You will be extending the schema for ZfS 3.0.2 on this tree.
If necessary, update your server with the required support pack to ensure that you have the correct JVM (see Meeting Policy and Distribution Services Requirements for NetWare and Windows Servers).
Continue with Using the Upgrade Wizard.
To upgrade ZfS 3/SP1 to ZfS 3.0.2:
On the upgrade workstation, insert the Program CD.
The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, run WINSETUP.EXE at the root of the CD.
IMPORTANT: If you copied the Program CD structure to the upgrade workstation's hard drive, the path between the root of the hard drive and the first CD directory can contain only directory names that conform to the 8.3-character DOS file naming convention. If any long directory names exist in the path, the upgrade program will not work.
Click Schema Extensions > follow the prompts.
To upgrade ZfS 3/SP1 to 3.0.2, you must extend the schema on the trees where you will be updating ZfS objects.
Click the Policy-Enabled Server Management option.
Click the Upgrade from ZfS 3 option to start the Upgrade Wizard.
If you agree with the Software License Agreement, click Accept > Next.
On the upgrade options page, click the Pause File Copying check box if you want to unload Java where it is running during the upgrade process.
Java cannot be running on a target NetWare server during the upgrade.
Click one of the following radio buttons > click Next:
You can upgrade only one type of object at a time.
IMPORTANT: You must upgrade Distributors first, because ZfS 3.0.2 Subscribers cannot receive Distributions from ZfS 3/SP1 Distributors; however, ZfS 3 Subscribers can receive Distributions from ZfS 3.0.2 Distributors, except as explained concerning NAL/TED Distributions (see Determining Whether to Upgrade Incrementally).
Browse for a target tree > click Next.
The Objects to Upgrade page is displayed, where you can select which Distributor or Subscriber objects to upgrade.
The objects displayed in the Available Objects box are all ZfS 3/SP1 objects in the current tree of the type your are upgrading (Distributor or Subscriber).
Select one or more objects in the Available Objects box > click Add.
The Add button moves the selected objects to the Selected Objects box.
Repeat Step 9 until you have selected all the objects you want to upgrade at this time > click Next.
On the File Installation Paths and Options page, select one or more objects in the Selected Servers list.
Select objects individually or in groups, depending on whether their servers share the same installation paths and ZfS software launching methods.
To have servers for the selected objects automatically start ZfS 3.0.2 on server startup, click the Launch Policy and Distribution Services On Startup check box.
To change the default installation path, browse for or enter the new installation directory for the selected objects.
ZENWORKS is the default installation directory for the ZfS 3.0.2 software. For example, SYS:\ZENWORKS or C:\ZENWORKS.
IMPORTANT: Do not use double-byte or extended characters in any part of an installation path, including a NetWare volume name.
If you select multiple server objects, the Browse button is dimmed. You must enter a directory that will be used by all of the selected servers.
Repeat Step 11 through Step 13 for each group of selected objects > click Next.
On the Upgrade Summary page, click Finish to begin the upgrade process.
IMPORTANT: You should not reboot the server at this time, because this would start ZfS before you have completed the upgrade process.
If you upgraded Distributors and now need to upgrade Subscribers, repeat Step 3 through Step 15.
Continue with Completing the Upgrade.
To complete the upgrade process, do the following in order:
Make sure you have already upgraded to the newest version of ConsoleOne from the ZENworks for Servers Companion CD or ZENworks 6 Companion 1 CD (see Installing ConsoleOne 1.3.5 from the Companion CD). This is required before installing the ZfS 3.0.2 snap-ins to any instance of ConsoleOne on a workstation or server.
To install the ZfS 3.0.2 snap-ins for ConsoleOne for each upgraded instance of ConsoleOne:
On the installation workstation, insert the Program CD.
The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, run WINSETUP.EXE at the root of the CD.
Click Policy-Enabled Server Management.
Click Install/Upgrade to start the installation program.
If you agree with the Software License Agreement, click Accept > Next.
Click Next to perform a new installation.
Click Next to install Policy and Distribution Services.
On the Installation Options page, click the Create eDirectory Objects and the Pause File Copying check boxes to disable those options > click Next.
Click Add > browse for all server objects where you installed ConsoleOne to the server.
For these servers where you installed ConsoleOne, click the ConsoleOne Snap-ins check box.
If you installed ConsoleOne on your current workstation, click the ConsoleOne Snap-ins check box for Local Machine.
When you have finished configuring the selected servers, click Next.
On the Installation Summary page, click Finish to install the ZfS 3.0.2 snap-ins to each copy of ConsoleOne you identified in Step 9 through Step 10.
After the installation program has finished, review the installation log file to determine whether any components failed to install.
The log file is located at:
C:\TEMP\_RESNumber.TXT
where Number is increased incrementally each time a new installation log is created.
If necessary, rerun the installation program.
Select only the components that failed to install.
Repeat Step 1 through Step 14 for each workstation where you need to update ConsoleOne with the new ZfS 3.0.2 snap-ins.
Continue with Starting ZENworks for Servers.
You must start ZfS 3.0.2 on servers where you have upgraded from ZfS 3/SP1 in order to complete the upgrade process for servers that are managed using policies.
On a server where you upgraded from ZfS 3/SP1 to 3.0.2, do the appropriate procedure for your platform:
Repeat Step 1 for each server that you upgraded.
Continue with Verifying That the Policy and Distributions Services Agents Are Loaded on NetWare Servers.
On the target server's console, press Ctrl+Esc to view the loaded software programs.
If the ZfS item (Policy/Package Agent) is not displayed, review the ZFSINIT.TXT file (under ZENWORKS\PDS\SMANAGER), which contains information about why the agent did not start.
Use this information to reinstall ZfS to the server.
This file is used to log startup problems only.
If the TED item (TED Agent) is not displayed, review the DEFAULTLOG.TXT file (under PDS\TED), which contains information about why the agent did not start.
Use this information to reinstall ZfS to the server.
This file is used to log startup problems only.
Rerun the installation program as necessary (see Installing Policy and Distribution Services).
On the target server, open the Control Panel > double-click Services (on Windows 2000, double-click Admin Tools > click Services) > determine if the following services are running:
Repeat Step 1 for each Windows server.
Rerun the installation program as necessary (see Installing Policy and Distribution Services).