29.5 Upgrading ZENworks for Desktops 3.2 SP3 Servers

You upgrade your ZENworks for Desktops 3.2 SP3 servers by using the ZENworks 7 Desktop Management Server installation program.

The upgrade process for the Application Management, Workstation Management, Workstation Imaging, Remote Management, and Workstation Inventory components is fairly simple and includes few issues you need to plan for as you upgrade.

An upgrade installation is identical to a new installation. The following steps provide only the information you need to launch the installation program and make choices specific to upgrading. For more detailed installation information, see Section 9.0, Installing the ZENworks Desktop Management Server.

  1. From the installing workstation, authenticate to eDirectory as a user with administrative rights to the eDirectory tree whose schema you extended for ZENworks 7 (see Section 9.1.1, Extending the Schema Before the Installation).

  2. Insert the Novell ZENworks 7 Desktop Management CD (or the Novell ZENworks 7 Desktop Management with Support Pack 1 CD) into the CD drive of the workstation to autorun the ZENworks 7 installation program.

    If the installation program does not autorun, launch winsetup.exe from the root of the CD.

    ZENworks 7 installation program

  3. Select Desktop Management, then select English to display the ZENworks 7 Desktop Management page.

    ZENworks 7 installation program > Desktop Management page

  4. Select Desktop Management Services to launch the ZENworks Desktop Management Server installation program.

  5. Follow the prompts until you've added the servers you want to upgrade and the Server Selection page is still displayed, as shown below.

    ZENworks Desktop Management Server installation program > Server Selection page

  6. Deselect any components you don't want installed to the server.

    For example, because you are not upgrading Workstation Inventory, deselect Inventory Database, Inventory Server, and Inventory Proxy Server. Select a component to display a description in the Component Description box.

  7. (Optional) If you don't want the installation program to check the target servers to ensure that they meet the ZENworks 7 prerequisites, deselect the Prerequisite Check option.

    With the Prerequisite Check option selected, if a target server does not meet the prerequisites, installation does not occur on that server until you upgrade the server or rerun the installation program with the option deselected.

  8. Click Next, then follow the remaining prompts to install the software.

  9. Review the information in the following sections to complete the upgrade process:

29.5.1 Completing the Application Management Upgrade

The following sections provide information to help you complete your upgrade of the Application Management component of ZENworks Desktop Management:

Updating the Application Launcher Startup Method

When you upgrade the ZENworks 3.2 Server to the ZENworks 7 Desktop Management Server, nalexpld.exe and nal.exe are updated to launch naldesk or nalwin32 from the local directory where the ZENworks 7 Desktop Management Agent will be installed. This change affects ZENworks for Desktops 3.2 SP3 workstations using the Novell Client that have not been updated with the ZENworks 7 Desktop Management Agent.

Until you can update the ZENworks for Desktops 3.2 SP3 workstations, you need to make sure that users are able to access the old Application Launcher. There are solutions for two scenarios:

If Users Access the Application Launcher When Connected to the Network

If your users primarily access the Novell Application Launcher™ while connected to the network, you might want to continue using the client login script to start the Application Launcher. One way of checking the workstation for updated ZENworks 7 Desktop Management files is to use the exist.exe tool to check c:\program_files\novell\zenworks for the existence of nalwin32.exe or naldesk.exe.

NOTE:The exist.exe tool can be downloaded from the Novell ZENworks Cool Solutions page. Run this tool from a login or application startup script to check for the presence of any file you specify. If the specified file is detected, the .exe returns ERROR_LEVEL of zero (0).

When you have downloaded exist.exe, edit your login scripts to put in a check to run ZENworks for Desktops 3.2 Novell Application Launcher locally, from the server, or to let the ZENworks 7 version run. These lines must be after the sys:\public directory is added to the search path or the exist.exe must have the full path specified. You need to modify the following (or an equivalent) line:

@z:\nalwin32.exe

This is how you need to modify the line:

; First check to see if the ZENworks 7 agent is present. If so, then
; you don’t need	t                                                                                                              do anything; it will be launched automatically on
; the desktop.
#exist %<windir>\..\Program Files\Novell\Zenworks\naldesk.exe
; If the ZENworks 7 agent is NOT present, then keep checking
if ;"%ERRORLEVEL"!="0" then
; Check now to see if the ZfD 3.x App Launcher has been placed on the ;workstation
#exist %<windir>\system32\nalwin32.exe
; If the ZfD 3.x App Launcher has NOT been placed on the workstation
; then go and launch the App Launcher from the server.
if "%ERRORLEVEL"!="0" then
; Check our Windows 95 friends
#exist %<windir>\..\novell\client32\nalwin32.exe
if "%ERRORLEVEL"!="0" then
@z:\ZfD32NAL\nalwin32.exe
else
@%<windir>\..\novell\client32\nalwin32.exe
end
else
@%<windir>\system32\nalwin32.exe
end
end

This script change launches Application Launcher in one of three ways:

  • From the workstation copy of the ZENworks 7 Desktop Management Agent (it will automatically start, so it does not need to be launched from the login script)

  • From a local copy of the ZENworks for Desktops 3.2 Application Launcher code, if it is present

  • From the server if the ZENworks 7 Desktop Management Agent and the local ZENworks for Desktops 3.2 Application Launcher code are not on the workstation.

The only difference in launching the ZENworks for Desktops 3.2 files locally rather than from the server is that if you start the Application Launcher locally, updated ZENworks for Desktops 3.2 Application Launcher files on the server are not pushed to the workstation. During a migration period, this is usually not necessary, but if it does become necessary, you can use an Application Launcher /i command line switch in a Policy package to update the local ZENworks for Desktops 3.2 Application Launcher files. For more information, see the ZENworks for Desktops 3.2 Administration Guide in ZENworks for Desktops 3.2 archived documentation.

NOTE:If your network environment contains shared workstations, you should edit all of the login scripts at the same time, regardless of when the container, partition, or site is upgraded to ZENworks 7. This prevents shared workstations from having old Application Launcher files distributed to them.

If Users Access the Application Launcher When Disconnected from the Network

If your users are often disconnected from the network, you can start the Application Launcher by specifying in the ZENworks 7 Desktop Management Agent installation that the Application Launcher or the Application Explorer should be launched from the Startup Folder. Although this is the simplest method, command line parameters cannot be added to the shortcut and users sometimes remove items from the Startup folder.

If you want to specify command line parameters, you can start the Application Launcher by editing the Windows registry and adding NALWIN32 or NALDESK to the HKLM\Software\Microsoft\Windows\CurrentVersion\Run key.

Updating Applications

You should prepare your applications to move to ZENworks 7 Desktop Management. With ZENworks 7 Desktop management you need to decide if you are going to continue to have the Novell Client installed on your workstations or if you are moving to Desktop Management feature delivery through the ZENworks Middle Tier Server.

If you are going to continue to use the Novell Client, application objects require no changes in order to function in the new Desktop Management environment. You will, however, be required to install the Desktop Management Agent in order to update the ZENworks functionality of the Novell Client.

If you plan to deploy the Desktop Management Agent without the Novell Client on the workstation, see Section 12.0, Installing and Configuring the Desktop Management Agent.

Any MSI applications to be delivered outside the corporate firewall must be marked Forced Cache. The Microsoft MSI installer is not aware of the ZENworks Middle Tier Server and cannot properly request applications through the browser; consequently, all of the files must be cached on the local workstation prior to installation.

Transitioning from System Requirements to Distribution Rules

The System Requirements configuration option used to help define ZENworks for Desktops 3.2 SP3 application distribution has been renamed to Distribution Rules to better reflect the enhanced functionality and to differentiate it from the old system requirements. ZENworks 7 Distribution Rules support more flexible distribution conditions through the use of AND/OR Boolean operators and groupings of requirements. In ZENworks for Desktops 3.2 SP3, the AND operator was used for all system requirements and there was no ability to group requirements.

Only ZENworks 6.5 (or later) versions of Novell Application Launcher have the ability to process the new operator logic and groupings used with the distribution rules. Therefore, to maintain backwards compatibility with the ZENworks for Desktops 3.2 SP3Application Launcher, existing system requirements are retained as legacy system requirements during upgrading of your eDirectory tree's schema. Both the ZENworks for Desktops 3.2 SP3 Application Launcher and the ZENworks 7 Application Launcher can process the legacy system requirements, which means that applications with legacy system requirements continue to be available to users regardless of which Application Launcher version they are using.

As you transition from using legacy system requirements to using distribution rules, you need to be aware of the following:

  • Distribution rules are defined on the Application object's Distribution Rules page (Application object > Availability tab > Distribution Rules page).

  • Legacy system requirements are available from the Distribution Rules page by clicking the Legacy button, then clicking Edit Legacy Settings. You can use this option to edit existing legacy system requirements or add new system legacy requirements (for example, if you create a new Application object that you want available on workstations running the ZENworks for Desktops 3.2 SP3 Application Launcher.

  • When you access the Distribution Rules page for an application that has legacy system requirements but no distribution rules, you are prompted to import the requirements into the distribution rules. If you choose not to import them, you can import them later by using the Import Legacy Settings option on the Distribution Rules page.

  • After you import legacy system requirements into distribution rules or manually define distribution rules, the ZENworks 7 Application Launcher processes only the distribution rules. It ignores the legacy system requirements. The ZENworks for Desktops 3.2 SP3 Application Launcher, however, continues to process the legacy system requirements because it does not know about the new distribution rules. Therefore, if you want to use distribution rules but still have workstations running the ZENworks for Desktops 3.2 SP3 Application Launcher, you need to maintain both a distribution rules list and a legacy system requirements list.

  • Changes you make to distribution rules are not added to the legacy system requirements. Likewise, changes you make to legacy system requirements are not added to the distribution rules.

  • If you define distribution rules and then import legacy system rules, your existing distribution rules are overwritten by the legacy system rules.

  • The requirement for an operating system to be defined before an application is available has been removed. In ZENworks for Desktops 3.2 SP3, an OS platform had to be defined in System Requirements before an application would be available for distribution and launching. This requirement has been removed. The new behavior uses the following logic: If an application runs only on a specific operating system, define an operating system distribution rule. If an application does not require a specific operating system, there is no need to define a distribution rule. By default, applications without a defined operating system distribution rule are available on all supported platforms (Windows 98, Windows 2000, and Windows XP).

Keeping the above listed details in mind, we recommend the following process to ensure a smooth transition from system requirements to distribution rules:

  1. For each Application object, import the legacy system rules into distribution rules. Modify the rules as desired.

  2. Retain the legacy system requirements to support workstations using ZENworks for Desktops 3.2 SP3 Application Launcher.

  3. If an application's distribution conditions change, modify both the distribution rules and the legacy system requirements to ensure that both the ZENworks 7 and ZENworks for Desktops 3.2 SP3 Application Launcher enforce the distribution condition.

  4. After all workstations are upgraded to the ZENworks 7 Application Launcher (see Section 30.8, Upgrading Workstations), remove the legacy system requirements.

    or

    If you are supporting Windows NT 4.0 workstations in your environment by continuing to run the ZENworks for Desktops 3.2 SP3 Desktop Management Agent on the workstations, do not remove the legacy system requirements. You need to keep both the legacy system requirements and distribution rules.

For more information about distribution rules and legacy system requirements, see Distribution Rules Page in Application Management in the Novell ZENworks 7 Desktop Management Administration Guide.

29.5.2 Completing the Workstation Management Upgrade

When you first install ZENworks 7 Desktop Management into your eDirectory tree, additional ZENworks 7 Desktop Management policy schemas are placed there. Existing ZENworks for Desktops 3.2 SP3 policies are automatically migrated into your tree when new ZENworks 7 Desktop Management policies are created.

The following sections provide information to help you complete your upgrade of the Workstation Management component of ZENworks Desktop Management:

Updating Search Policies

Examine eDirectory to see if there are any Search policies in the tree. Search policies, part of the Container Package, are very important because they keep ZENworks agents from walking to the root to find policies and configuration information.

If the tree does not have a Search policy, you need to create a new ZENworks 7 Desktop Management Search policy to ensure optimal performance of the ZENworks agents. There are some policy behaviors that you need to consider:

  • If you plan to authenticate using only the Novell Client in your network environment, the search policy functions the same way as a ZENworks for Desktops 3.2 SP3 Search policy.

  • If you plan to use the ZENworks Middle Tier Server and run the Desktop Management Agent on workstations without the Novell Client, the behavior of the search policies might change when you upgrade the network.

Unlike ZENworks for Desktops 3.2 agents, ZENworks 7 agents do not recognize the partition boundary of a container. Consequently, if you have any existing Search policies that are based on the partition boundary, the ZENworks 7 agents search to the container where the Container Package is associated, regardless of whether the agents cross any partition boundaries in search of policies.

For example, assume that you have the following tree:

Figure 29-1 An eDirectory Tree with a ZENworks for Desktops 3.2 Search Policy Set to Search to the Partition Boundary.

Illustration showing an eDirectory tree structure with a Search policy based on the partition boundary.

With ZENworks for Desktops 3.2 SP3, the agents for the users or workstations first walk to their parent container and find the associated Search policy that states that the agents should look only to the partition boundary for their policies. When the agents look for policies, they walk the tree only to the Chicago container (partition boundary).

With ZENworks 7 Desktop Management, the Partition option is not available in the Search Policy. It has been replaced with the Associated Container option. This means that any earlier Search Policies that were upgraded to ZENworks 7 with the Partition option are now replaced with the Associated Container option. If you do not plan for this change, a different policy retrieval could result.

If you want to continue receive the same search results as when you used the Partition option as the search boundary, you need to associate the container package (that is, the policy package where the configured Search policy resides) to the eDirectory container that represents the partition boundary where you want user and workstation objects to end their search for policies.

Figure 29-2 An eDirectory Tree with a ZENworks for Desktops 3.2 Search Policy Upgraded to ZENworks 7. The Policy is Set to Search to the Associated Container.

Illustration showing an eDirectory tree structure with the Container Policy Package and the Search policy associated to the containers that are partition boundaries.

When the ZENworks 7 agents search the tree now, they find the Container Package with the Search Policy at Chicago, and then search for policies up to Chicago, because it is the associated container.

NOTE:The container that is associated with the package determines where the agents will stop walking the tree. It is not based on where the package is actually stored in the directory. The search level in the Search policy will now apply to the associated container rather than the partition boundary.

Additional Information about Upgrading Policies

  • If a workstation with ZENworks for Desktops 3.2 SP3 and the Novell Client installed is upgraded to the new ZENworks 7 agent, and the client remains, the workstation continues to use the policies that were created in the directory prior to the ZENworks 7 upgrade.

  • If a workstation with ZENworks for Desktops 3.2 SP3 and the Novell Client is upgraded to the new ZENworks 7 agent and the client is removed, the workstation uses only those policies that are valid in ZENworks 7 (for example, the RAS configuration policy would not be enforced).

  • If a new workstation has only the ZENworks 7 agent installed (no client or ZENworks for Desktops 3.2 SP3), the workstation uses only those policies that are valid in ZENworks 7.

  • If you install ZENworks 7 without upgrading an existing ZENworks for Desktops 3.2 SP3 installation, only the valid ZENworks 7 policies are present. The original ZENworks for Desktops 3.2 SP3 policies are present only if an upgrade is performed.

For a comparison of ZENworks for Desktops 3.2 policies and ZENworks 7 Desktop Management policies, see Section A.0, Differences in ZENworks for Desktops 3.2 and ZENworks 7 Policy Packages.

29.5.3 Completing the Workstation Imaging Upgrade

When you install ZENworks 7 Desktop Management, you should upgrade your ZENworks for Desktops 3.2 SP3 Workstation Imaging to benefit from the new ZENworks 7 Desktop Management image compression features.

Upgrading the Imaging Server

To upgrade to the ZENworks 7 Workstation Imaging server, insert the Novell ZENworks 7 Desktop Management CD (or the Novell ZENworks 7 Desktop Management with Support Pack 1 CD), then run the ZENworks 7 Desktop Management installation program to install Workstation Imaging. This upgrades the ZENworks for Desktops 3.2 SP3 Imaging engine.

Upgrading Imaging When the Linux Partition Resides on Workstations

Because ZENworks 7 uses a new Linux distribution for Workstation Imaging, when you upgrade from ZENworks for Desktops 3.2 to ZENworks 7 Desktop Management, you need to either remove the old Linux partition and then install the ZENworks 7 Linux partition, or discontinue the use of a local partition in favor of using ZENworks 7 Preboot Services.

Upgrading to ZENworks 7 Preboot Services

If you decide to move to ZENworks 7 Preboot Services (PXE) to eliminate the Linux partitions on your workstations, use the following steps:

  1. Install ZENworks 7 Preboot Services on a network server.

    For installation and setup instructions, see Section 9.1, Desktop Management Server Installation Procedure in this guide and Using ZENworks Desktop Management Preboot Services in the Novell ZENworks 7 Desktop Management Administration Guide.

    You might need to make some configuration changes to the DHCP server.

  2. Verify that ZENworks 7 Preboot Services is working either through the PXE supplied on your network cards, or through a PXE bootable floppy you generate with pxebuilder.exe.

  3. In ConsoleOne, right-click the ZENworks Imaging Policy in the Server Policy Package > click Properties > General > Imaging Partition.

  4. Disable the ZENworks imaging partition.

This procedure makes the Linux partition non-bootable on the workstation hard drive. It does not eliminate the Linux partition.

If you want to eliminate the Linux partition, you need to restore a base image on the workstation and select the option to delete the existing Linux partition in the Image object, which you can reference in the Server Policy package or the Workstation Policy package.

29.5.4 Completing the Remote Management Upgrade

The ZENworks 7 Desktop Management console can remotely control both the ZENworks for Desktops 3.2 agent workstations and the ZENworks 7 agent workstations. However, ZENworks 7 Desktop Management does not provide migration for any 3.2 features that were discontinued in later releases, and the ZENworks for Desktops 3.2 agents do not support any enhancements provided in ZENworks 7 Desktop Management.

NOTE:It is no longer necessary to use Remote Management Application objects to control the Remote Management Agents on workstations. The Remote Management Agents are now installed on the workstation as part of the Desktop Management Agent installation.

29.5.5 Completing the Workstation Inventory Upgrade

To upgrade Workstation Inventory from ZENworks for Desktops 3.2 SP3 to ZENworks 7, perform the following tasks in the order listed:

  1. Review the information in Pre-Upgrade Considerations.

  2. Preform the tasks explained in Tasks To Be Performed Before Upgrading and Database Migration.

  3. Perform the tasks explained in Upgrading the ZENworks for Desktops 3.2 SP3 Inventory Database.

  4. Perform the tasks explained in Upgrading the ZENworks for Desktops 3.2 SP3 Inventory Server.

  5. Perform the tasks explained in Manually Migrating ZENworks for Desktops 3.2 SP3 Inventory Policies.

  6. Perform the tasks explained in Tasks to Perform after Database Migration.

Pre-Upgrade Considerations

Before you upgrade ZENworks for Desktops 3.2 SP3 Inventory components, review the following sections:

Inventory Server

  • ZENworks for Desktops 3 or ZENworks for Desktops 3.2 SP1 is not backward compatible with ZENworks 7 Desktop Management. You must upgrade all ZENworks for Desktops 3, ZENworks for Desktops 3 SP1, ZENworks for Desktops 3.2, ZENworks for Desktops 3.2 SP1, or ZENworks for Desktops 3.2 SP2 Inventory servers in your Inventory tree to ZENworks for Desktops 3.2 SP3 before upgrading to ZENworks 7 Desktop Management.

    In order for your network to support both ZENworks for Desktops 3.2 and ZENworks 7 Desktop Management, you must first install ZENworks for Desktops 3.2 SP3 into your network. Installing ZENworks 7 Desktop Management without first installing ZENworks for Desktops 3.2 SP3 does not provide the Novell eDirectory schema or ConsoleOne plug-in support for ZENworks for Desktops 3.2 policies. On the other hand, installing ZENworks for Desktops 3.2 SP3 first places the ZENworks for Desktops 3.2 schema and the plug-ins into ConsoleOne. When you install ZENworks 7 Desktop Management after ZENworks for Desktops 3.2 SP3, the ZENworks for Desktops 3.2 schema and plug-ins remain.

    If the Inventory server is running ZENworks for Desktops 3, you must install ZENworks for Desktops 3.2 and ZENworks for Desktops 3.2 SP3, and start the Inventory service and the database at least once prior to upgrading the server to ZENworks 7 Desktop Management. For more information on how to install ZENworks for Desktops 3.2, see the Novell Support Web site.

  • After you install ZENworks 7 Desktop Management, ZENworks 7 Desktop Management Workstation Inventory and ZENworks for Desktops 3.2 SP3 agents and policies coexist in the following ways:

    • Inventory data from ZENworks 7 Desktop Management agents cannot be sent to a ZENworks for Desktops 3.2 SP3 Inventory server and placed in a ZENworks for Desktops 3.2 SP3 database. A ZENworks for Desktops 3.2 SP3 Inventory Agent cannot send its inventory data to a new ZENworks 7 Desktop Management Inventory server. It can send its inventory data only to a ZENworks for Desktops 3.2 SP3 Inventory server or to a ZENworks 7 Desktop Management Inventory server that has been upgraded from ZENworks for Desktops 3.2 SP3.

    • ZENworks for Desktops 3.2 SP3 Inventory servers can roll up their inventory data to a ZENworks 7 Desktop Management Inventory server, but a ZENworks 7 Desktop Management Inventory server cannot roll up its inventory data to a ZENworks for Desktops 3.2 SP3 server.

    • ZENworks for Desktops 3.2 SP3 Inventory servers can roll up their databases to a ZENworks 7 Desktop Management Inventory server, but a ZENworks 7 Desktop Management Inventory server cannot roll up its database to a ZENworks for Desktops 3.2 SP3 server.

    • Any ZENworks for Desktops 3.2 SP3 Inventory servers that roll up their data to a ZENworks 7 Desktop Management Inventory server must be patched in order to function properly.

    • A ZENworks for Desktops 3.2 SP3 inventory server cannot roll up its data to a ZENworks for Desktops 3.2 SP3 or ZENworks 7 Desktop Management Inventory server in another eDirectory tree.

  • ZENworks for Desktops 3.2 SP3 Inventory servers must be upgraded to ZENworks 7 Desktop Management in a top-down order. If you perform roll-up of your inventory data, the root server must be upgraded first, then the intermediate servers, and lastly the leaf servers.

  • A ZENworks 7 Desktop Management Inventory server cannot send its inventory data to a ZENworks for Desktops 3.2 SP3 Inventory server.

  • Do not attach a ZENworks 7 Desktop Management Inventory database directly to a ZENworks for Desktops 3.2 SP3 Inventory server.

  • A ZENworks 7 Desktop Management Inventory server can process the .str files of the ZENworks for Desktops 3.2 SP3 inventoried workstations.

  • A ZENworks for Desktops 3.2 SP3 Inventory server can roll up its database information to ZENworks for Desktops 3.2 SP3 or ZENworks 7 Desktop Management Inventory server.

  • A ZENworks 7 Desktop Management Inventory server can process the .zip files of the ZENworks for Desktops 3.2 SP3 Inventory servers.

  • Do not delete the ZENworks for Desktops 3.2 SP3 .str and .zip files in SCANDIR and its subdirectories of a ZENworks for Desktops 3.2 SP3 Inventory server that has been migrated to ZENworks 7 Desktop Management.

  • Do not have a ZENworks for Desktops 3.2 SP3 Inventory server and a ZENworks 7 Desktop Management Inventory server store the inventory data directly to the same Inventory database.

  • Do not specify an Inventory server residing in another eDirectory tree as the next-level server in the Roll-Up policy of a ZENworks for Desktops 3.2 SP3 Inventory server.

  • Do not associate a ZENworks for Desktops 3.2 SP3 Roll-up policy to a ZENworks 7 Desktop Management Inventory server.

  • The ZENworks for Desktops 3.2 SP3 Inventory server and a ZENworks 7 Desktop Management Inventory server can use a ZENworks for Desktops 3.2 SP3 Roll-Up policy that has been migrated to ZENworks 7 Desktop Management.

  • Upgrading a ZENworks for Desktops 3.2 SP3 Inventory server to ZENworks 7 Desktop Management does not change the role of the Inventory server.

  • If the ZENworks for Desktops 3.2 SP3 Inventory server rolls up the scan data to another ZENworks for Desktops 3.2 SP 3 Inventory server or to a ZENworks 7 Desktop Management Inventory server, it must have the required authentication patch installed. For more information on the authentication patch, see Step 2 in Upgrading the ZENworks for Desktops 3.2 SP3 Inventory Server.

Inventory Agent

  • A ZENworks for Desktops 3.2 SP3 Inventory Agent cannot send its inventory data to a new ZENworks 7 Desktop Management Inventory server. It can send its inventory data only to a ZENworks for Desktops 3.2 SP3 Inventory server or to a ZENworks 7 Desktop Management Inventory server that has been upgraded from ZENworks for Desktops 3.2 SP3.

  • A ZENworks for Desktops 3.2 SP3 or ZENworks 7 Desktop Management Inventory Agent can use a ZENworks for Desktops 3.2 SP3 Inventory policy that has been migrated to ZENworks 7 Desktop Management, or it can use a newly created ZENworks 7 Desktop Management Inventory policy.

  • A ZENworks 7 Desktop Management Inventory Agent cannot send its inventory data to a ZENworks for Desktops 3.2 SP3 Inventory server.

  • If you want to install or upgrade the ZENworks for Desktops 3.x agents through Workstation Imaging, ensure that the image is taken on a ZENworks 7 Desktop Management workstation that is unregistered.

Management Console

  • Do not use both ZENworks for Desktops 3.2 SP3 and ZENworks 7 management consoles to configure the same ZENworks for Desktops 3.2 SP3 Inventory objects.

  • You cannot use a ZENworks for Desktops 3.2 SP3 management console to administer ZENworks 7 Desktop Management inventory data and inventory objects.

  • You can use ZENworks 7 Desktop Management ConsoleOne snap-ins to administer both ZENworks for Desktops 3.2 SP3 and ZENworks 7 Desktop Management inventory data and inventory objects (such as Inventory Service object, database objects, Workstation Inventory policy, Roll-Up policy, Dictionary Updated policy, and Database Location policy).

Tasks To Be Performed Before Upgrading and Database Migration

After reviewing the facts mentioned in Pre-Upgrade Considerations, you must perform the following tasks before you upgrade from ZENworks for Desktops 3.2 SP3 to ZENworks 7 Desktop Management:

  1. Stop the Inventory service.

    • On a NetWare Inventory server: At the server console prompt, enter stopser *.

      If you do not want the Sybase database to be stopped automatically when you stop the Inventory services, comment the Unload dbsrv8.nlmline in the sys:\system\invstop.ncf file.

    • On a Windows 2000 Inventory server: In the Control Panel, double-click Administrative Tools > Services, select ZENworks Inventory Service, then click Stop.

  2. Stop the Sybase Inventory database:

    • On NetWare: At the Sybase console prompt, press the Q key.

    • On Windows 2000: In the Control Panel, double-click Administrative Tools > Services, then select Adaptive Server Anywhere - Zenworks for Desktops 3, then click Stop.

  3. If Java has not been unloaded on the target NetWare servers, unload java.nlm (at the server console, enter java -exit).

    IMPORTANT:This command stops all Java processes running on the server. Verify that all Java processes can be stopped while you are installing Desktop Management.

  4. On the target Windows servers, close the Services window.

  5. Make sure that you have made and archived a reliable backup of the ZENworks for Desktops 3.2 SP3 database.

  6. Make sure that the ZENworks for Desktops 3.2 SP3 database is not accessed from ConsoleOne.

  7. Make sure that the recommended ZENworks 7 Workstation Inventory requirements are met. For more information, see Section II, Preparation.

  8. If you have a ZENworks for Desktops 3.2 SP3 database running Oracle, you must perform the following tasks before the migration:

    1. In inventory_database_installation_path\init.ora_path\init.ora, set the value of db_block_buffers to obtain a net value of approximately 128 MB for the database buffer cache.

      If the db_block_size is 4096 then the minimum value must be 32768. This allocates 128 MB of database cache for the Inventory database. If the existing value of db_block_buffers is greater than 128 MB, do not change the value.

      We recommend that you set the Oracle's Shared Global (SGA) memory to 30-40 % or above during the database migration.

    2. Ensure that the Inventory database is up and running.

    3. You must have a bigger rollback segment because the database migration and the storage of further data cannot succeed because of ORA-01555 and other rollback segment issues.

      To increase the value of the rollback segment, execute the following sql script to add an additional data file to the rollback segment (rbs) and to add a Redo log group. 

      connect internal;

      alter tablespace rbs add datafile ’Inventory_database_installation_path\rbs2.ora’ size 40M autoextend on next 50K maxsize 60M;

      alter rollback segment rb0 storage (maxextents unlimited);

      alter rollback segment rb1 storage (maxextents unlimited);

      ALTER DATABASE ADD LOGFILE GROUP 3 (’Inventory_database_installation_path\log3.ora’) SIZE 50M;

Upgrading the ZENworks for Desktops 3.2 SP3 Inventory Database

During the ZENworks 7 Desktop Management Server installation, if you choose to install Sybase and you do not choose to overwrite the database files, the server installation program automatically upgrades only the existing ZENworks for Desktops 3.2 SP3 database engine. During the Sybase database upgrade, a message indicating that the existing database can be migrated is displayed. If you choose Yes, then the existing database is overwritten by the new ZENworks 7 Desktop Management database files. If you choose No, the database is migrated when the Inventory service starts for the first time.

IMPORTANT:You can upgrade multiple Inventory servers and database servers at the same time by running the ZENworks 7 Desktop Management Server installation program.

However, you must manually migrate the existing ZENworks for Desktops 3.2 Workstation Inventory policy, Database Location policy, and Roll-up policy. If you have manually created the database object, you must also migrate the database object. For more information on how to manually migrate the policies, see Manually Migrating the Database Objects.

You must perform the following tasks to upgrade the Inventory database:

Changing the Database Cache Size

If you have a ZENworks for Desktops 3.2 SP3 database running Sybase, ensure that the value of Sybase cache (“-c” parameter) is set to 25% or above of the server's memory.

To change the database cache size on a NetWare database server:

  1. Close all connections to the Inventory database.

  2. Quit the Sybase server.

  3. Open the mgmtdbs.ncf file in the sys:\system directory.

  4. Modify the -c parameter. For example, -c 128M sets the cache size to 128 MB.

  5. Save the file.

  6. On the server console, load the inventory database. Enter MGMTDBS.

To change the database cache size on a Windows database server:

  1. Stop the Sybase service.

    On Windows NT, in the Control Panel, double-click Services, select Novell Database - Sybase, then click Stop.

    On Windows 2000, in the Control Panel, double-click Administrative Tools > double-click Services, select Novell Database - Sybase, then click Stop.

  2. On the database server, run the ntdbconfig.exe file from the \dbengine directory.

    Ntdbconfig.exe is a ZENworks database configuration utility for the ZENworks database using Sybase on Windows NT/2000 servers. This utility enables you to reconfigure the Sybase service.

  3. Modify the -c parameter.

  4. Click OK.

  5. Restart the Sybase service. On Windows NT, in the Control Panel, double-click Services, select Novell Database - Sybase, then click Start. On Windows 2000, in the Control Panel, double-click Administrative Tools > double-click Services, select Novell Database - Sybase, then click Start.

Manually Migrating the Database Objects

If you have a ZENworks for Desktops 3.2 SP3 Oracle database object, or if you have manually created Sybase database objects, you must manually migrate the database object using the Inventory Migration tool. For more information, see Manually Migrating the Database Objects.

  1. In ConsoleOne with ZENworks 7 Desktop Management Workstation Inventory snap-ins installed, click Tools, click ZENworks Inventory, then click Inventory Migration.

  2. Click Browse to browse for and select the database object to be migrated or the container that has the database object.

  3. If you selected a container in Step 2, do the following:

    1. If you want to search for the database object in all the subcontainers within the selected container, select the Search SubContainers check box.

      The Search SubContainers check box is available only if you select a container in Search Context.

    2. Select the Search for Database Objects check box to search for the database objects within the selected container to be migrated.

      This option is available only if you select a container in Search Context. By default, this option is selected.

    3. Click Find.

      All the ZENworks for Desktops 3.2 database objects that are found within the specified context are displayed in the Report panel.

  4. Click Migrate.

  5. Click Close.

  6. In ConsoleOne, right-click the database object, click Properties, then click the ZENworks Database tab.

  7. Ensure that the following database object options have the specified values mentioned depending on the Inventory database:

    Database Object Options

    Value for the Sybase Inventory Database Object

    Value for the Oracle8i Inventory Database Object

    Database (Read-Write) User Name

    MW_DBA

    MW_DBA

    Database (Read-Write) Password

    novell

    novell

    Database (Read Only) User Name

    MW_READER

    MWO_READER

    Database (Read Only) Password

    novell

    novell

    Database (Write Only) User Name

    MW_UPDATER

    MWO_UPDATER

    Database (Write Only) Password

    novell

    novell

  8. Click Apply, then click Close.

Upgrading the ZENworks for Desktops 3.2 SP3 Inventory Server

Before you upgrade a ZENworks for Desktops 3.2 SP3 Inventory server, make sure that you have upgraded the associated database server.

You can upgrade the ZENworks for Desktops 3.2 SP3 Inventory server by installing ZENworks 7 Desktop Management Inventory server if the server where you want to install the ZENworks 7 Desktop Management Inventory server meets the installation requirements. For more information on how to install the ZENworks 7 Desktop Management Inventory server, see Section 9.1, Desktop Management Server Installation Procedure. The ZENworks 7 Desktop Management Inventory server supports the same set of roles as ZENworks for Desktops 3.2 SP 3. Therefore, when you upgrade from ZENworks for Desktops 3.2 SP3 to ZENworks 7 Desktop Management, the role of the Inventory server is retained.

IMPORTANT:If you have a ZENworks for Desktops 3.2 SP3 Inventory server attached to a ZENworks for Desktops 3.2 SP3 database and if you upgrade either the Inventory server or the database to ZENworks 7 Desktop Management, you must upgrade the associated component to ZENworks 7 Desktop Management (the ZENworks for Desktops 3.2 SP3 Inventory services should not interact with ZENworks 7 Desktop Management-compliant database and vice versa).

If you have multiple ZENworks for Desktops 3.2 SP3 Inventory servers connected to a ZENworks for Desktops 3.2 SP3 database server and if you upgrade the database server to ZENworks 7 Desktop Management, you must also upgrade all the associated ZENworks for Desktops 3.2 SP3 Inventory servers.

The ZENworks 7 Desktop Management installation program automatically migrates only the ZENworks for Desktops 3.2 SP3 Inventory Service object to ZENworks 7 Desktop Management. Before starting the Inventory service, you must manually migrate the existing ZENworks for Desktops 3.2 SP 3 policies to ZENworks 7 Desktop Management policies using the ZENworks for Desktops Inventory Migration tool. For more information, see Manually Migrating ZENworks for Desktops 3.2 SP3 Inventory Policies.

After migrating the policies, do the following:

  1. If a ZENworks for Desktops 3.2 SP3 Inventory server is rolling up its information to a ZENworks 7 Desktop Management Inventory server, you must apply the following authentication patches that are bundled with the ZENworks 7 Desktop Management Companion 2 CD (or in the Novell ZENworks 7 with Support Pack 1 Companion 2 CD):

    Server

    Source file

    Target destination on Inventory server

    NetWare

    all files in the \invzfd3xpatch\zfd32\common\public\zenworks\wminv\lib directory

    Inventory_server_installation_path\zenworks\inv\server\wminv\lib

     

    \invzfd3xpatch\zfd32\nw\java\bin\zenws.nlm

    sys:\java\bin

     

    all files in the \invzfd3xpatch\zfd32\nw\java\lib directory

    sys:\java\lib

    Windows NT/2000

    all files in the \invzfd3xpatch\zfd32\common\public\zenworks\wminv\lib directory

    Inventory_server_installation_path\zenworks\inv\server\wminv\lib

     

    \invzfd3xpatch\zfd32\nt\zenworks\jre\1.2\bin\ zenws.dll

    sys_share\zenworks\jre\1.2\bin

     

    all files in the \invzfd3xpatch\zfd32\nt\zenworks\jre\1.2\lib directory

    sys_share\zenworks\jre\1.2\lib

  2. In the Workstation Inventory policy, select the Enable Scan of Machine option to reactivate the inventory scanning for all the inventoried workstations that send the inventory data directly to this Inventory server.

  3. If the inventory data is rolled up, start the Sender service running on all lower-level Inventory servers that roll up the inventory data to this Inventory server.

Manually Migrating ZENworks for Desktops 3.2 SP3 Inventory Policies

  1. In ConsoleOne with ZENworks 7 Desktop Management Workstation Inventory snap-ins installed, click Tools > ZENworks Inventory > Inventory Migration.

  2. Click Browse to browse for and select the Inventory Service object or the container that has the Inventory Service object.

  3. If you selected a container in Step 2, do the following:

    1. If you want to search for the Inventory Service object in all the subcontainers within the selected container, select the Search SubContainers check box.

      The Search SubContainers check box is available only if you select a container in Search Context.

    2. Select the Search for Policies check box to search for the Inventory policies associated with the Inventory Service object within the selected container.

      This option is available only if you select a container in Search Context. By default, this option is selected.

    3. Click Find.

      All the ZENworks for Desktops 3.2 SP3 Inventory policies that are associated with the Inventory Service object and are found within the specified context are displayed in the Report panel.

  4. Click Migrate.

  5. Click Close.

After migrating the policies, perform the following tasks:

  1. Start the ZENworks 7 Desktop Management Inventory services.

    When you start the Inventory service, the Upgrade Service automatically migrates the ZENworks for Desktops 3.2 database schema and the inventory data to a ZENworks 7 Desktop Management database. The data migration process might take a significant amount of time. On the Inventory server screen, messages indicating that the database has been successfully migrated and initialized are displayed.

    After the database is migrated, the Inventory ConsoleOne utilities (Query, Summary, Inventory Report, and Database Export) and the Storer can access the database

  2. Create and configure the Dictionary Update policy to get the latest version of the dictionary for ZENworks 7 Inventory Agent. For more information on how to create the Dictionary Update policy, see Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

Tasks to Perform after Database Migration

You must perform the following tasks after upgrading the Inventory server and migrating the Inventory database:

  1. Stop the Inventory service.

  2. If your Inventory database is running Oracle, do the following to improve the database performance:

    1. In the inventory_database_installation_path\_start.sql file, delete the existing entries and add the following entries:

      SET ECHO ON

      CONNECT INTERNAL

      SET ECHO OFF

      STARTUP PFILE=
inventory_database_installation_path\path_to_init.ora\init.ora

      SET NUMWIDTH 20

      SET CHARWIDTH 40

      SET ECHO ON

      connect mw_dba;

      SET ECHO OFF

      alter table cim.t$product cache;

      SET ECHO ON

      connect internal

      SET ECHO OFF

      @<path to oracle home directory>/rdbms/admin/dbmspool

      call sys.dbms_shared_pool.keep(’zenworks.zenpin’,’P’);

      EXIT

    2. Extract atlasperf_alterfreelist.sql from ZENworks_installation_directory\zenworks\inv\server\wminv\properties\sql.zip and execute at the SQLPLUS prompt.

    3. Execute the oracle\common\oracle_perf.sql and oracle\common\oracle_perf2.sql files from the Inventory_server_installation_path\zenworks\inv\server\wminv\properties\sql.zip to add performance enhancing indexes to the database.

    4. Execute oracle_dbexport_perf.sql from the Novell ZENworks 7 Companion 2 CD (or in the Novell ZENworks 7 Companion 2 CD) \database\oracle8i\common directory.

  3. (Optional) If the Inventory database is running MS SQL, execute the following scripts from Inventory_server_installation_path\zenworks\inv\server\wminv\properties\sql.zip with appropriate user logins as explained below from the MS SQL Query Analyzer:

    1. Log in as CIM, and execute mssql_perf_cim.sql.

    2. Log in as mw_dba and execute mssql_perf_mw_dba.sql.

    3. Log in as zenworks and execute mssql_perf_zenworks.sql.

      This enhances the performance of the Inventory database.

      For more information on how to improve the performance of the Inventory database, see Performance Tips in Workstation Inventory in the Novell ZENworks 7 Desktop Management Administration Guide.

  4. Start the Inventory services.