You upgrade your ZfD 3.2 SP3 Servers by using the ZENworks 6.5 Desktop Management Server installation program.
The upgrade process for the Application Management, Workstation Management, Remote Management, and Workstation Imaging 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 Installing the ZENworks Desktop Management Server.
From the installing workstation, authenticate to eDirectory as a user with administrative rights to the eDirectory tree whose schema you extended for ZENworks 6.5 (see Extending the eDirectory Schema).
Insert the Novell ZENworks 6.5 Desktop Management CD into the CD drive of the workstation to autorun the ZENworks 6.5 installation program.
If the installation program does not autorun, launch winsetup.exe from the root of the CD.
Select Desktop Management, the select English to display the ZENworks 6.5 Desktop Management page.
Select Desktop Management Services to launch the ZENworks Desktop Management Server installation program.
Follow the prompts until you've added the servers you want to upgrade and the Server Selection page is still displayed, as shown below.
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.
(Optional) If you don't want the installation program to check the target servers to ensure that they meet the ZENworks 6.5 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.
Click Next, then follow the remaining prompts to install the software.
Review the information in the following sections to complete the upgrade process:
The following sections provide information to help you complete your upgrade of the Application Management component of ZENworks Desktop Management:
When you upgrade the ZENworks 3.2 Server to the ZENworks 6.5 Desktop Management Server, nalexpld.exe and nal.exe are updated to launch naldesk or nalwin32 from the local directory where the Desktop Management Agent was installed. This change affects ZENworks for Desktops 3.2 SP3 workstations using the Novell Client that have not been updated with the ZENworks 6.5 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 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 6.5 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 6.5 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 6.5 agent is present. If so, then you don't need
; to do anything; it will be launched automatically on the desktop.
#exist %<windir>\..\Program Files\Novell\Zenworks\naldesk.exe
; If the ZENworks 6.5 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 will launch Application Launcher in one of three ways:
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 6.5. This will prevent shared workstations from having old Application Launcher files distributed to them.
If your users are often disconnected from the network, you can start the Application Launcher by specifying in the ZENworks 6.5 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.
You should prepare your applications to move to ZENworks 6.5 Desktop Management. With ZENworks 6.5 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 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.
The System Requirements feature used to help define ZfD 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 6.5 Distribution Rules support more flexible distribution conditions through the use of AND/OR Boolean operators and groupings of requirements. In ZfD 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 LauncherTM have the ability to process the new operator logic and groupings used with the distribution rules. Therefore, to maintain backwards compatibility with the ZfD 3.2 SP3 Application Launcher, existing system requirements are retained as legacy system requirements during upgrading of your eDirectory tree's schema. Both the ZfD 3.2 SP3 Application Launcher and the ZENworks 6.5 Application Launcher can process the legacy stem 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:
Keeping the above listed details in mind, we recommend the following process to ensure a smooth transition from system requirements to distribution rules:
For each Application object, import the legacy system rules into distribution rules. Modify the rules as desired.
Retain the legacy system requirements to support workstations using ZfD 3.2 SP3 Application Launcher.
If an application's distribution conditions change, modify both the distribution rules and the legacy system requirements to ensure that both the ZENworks 6.5 and ZfD 3.2 SP3 Application Launcher enforce the distribution condition.
After all workstations are upgraded to the ZENworks 6.5 Application Launcher (see 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 ZfD 3.2 SP3 Desktop Management Agent on the workstations, do not remove the legacy system requirements. You will 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 6.5 Desktop Management Administration Guide.
When you first install ZENworks 6.5 Desktop Management into your eDirectory tree, additional ZENworks 6.5 Desktop Management policy schemas are placed there. Existing ZENworks for Desktops 3.2 SP3 policies are automatically migrated into your tree when new ZENworks 6.5 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:
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 6.5 Desktop Management Search policy to ensure optimal performance of the ZENworks agents. There are some policy behaviors that you need to consider:
Unlike ZENworks for Desktops 3.2 agents, ZENworks 6.5 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 6.5 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:
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 6.5 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 6.5 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.
When the ZENworks 6.5 agents search the tree now, they will find the Container Package with the Search Policy at Chicago, and then will 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.
The list below includes some things you need to know when you upgrade ZENworks for Desktops 3.2 SP3 policies:
For a comparison of ZENworks for Desktops 3.2 policies and ZENworks 6.5 Desktop Management policies, see Differences in ZENworks for Desktops 3.2 and ZENworks 6.5 Policy Packages.
When you install ZENworks 6.5 Desktop Management, you should upgrade your ZENworks for Desktops 3.2 SP3 Workstation Imaging to benefit from the new ZENworks 6.5 Desktop Management image compression features.
To upgrade to the ZENworks 6.5 Workstation Imaging server, insert the Novell ZENworks 6.5 Desktop Management CD, then run the ZENworks 6.5 Desktop Management installation program to install Workstation Imaging. This upgrades the ZENworks for Desktops 3.2 SP3 Imaging engine.
If you continue to use the Linux partition on your ZENworks for Desktops 3.2 SP3 workstations, the imaging engine is updated when the workstations next contact the imaging server. If necessary, all other Linux OS files are copied to the Linux partition and installed after you upgrade to ZENworks 6.5 Workstation Imaging.
Following the automatic updates, all of the workstations with Linux partitions will be running the ZENworks 6.5 Desktop Management system.
If you decide to move to ZENworks 6.5 Preboot Services (PXE) to eliminate the Linux partitions on your workstations, use the following steps:
Install ZENworks 6.5 Preboot Services on a network server.
For installation and setup instructions, see Desktop Management Server Installation Procedurein this guide and "Using ZENworks Desktop Management Preboot Services" in the Novell ZENworks 6.5 Desktop Management Administration Guide.
You might need to make some configuration changes to the DHCP server.
Verify that ZENworks 6.5 Preboot Services is working either through the PXE supplied on your network cards, or through a PXE bootable floppy you generate with pxebuilder.exe.
In ConsoleOne, right-click the ZENworks Imaging Policy in Server Policy Package > click Properties > General > Imaging Partition.
Disable the ZENworks imaging partition.
This procedure will make the Linux partition non-bootable on the workstation hard drive. It will 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.
ZENworks 6.5 Desktop Management console can remotely control both the ZENworks for Desktops 3.2 agent workstations and the ZENworks 6.5 agent workstations. Be aware, however, that the ZENworks 6.5 Desktop Management do not provide any features that have been discontinued, and the ZENworks for Desktops 3.2 agents do not support any enhancements provided in ZENworks 6.5 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.
To upgrade Workstation Inventory from ZENworks for Desktops 3.2 SP3 to ZENworks 6.5, perform the following tasks in the order listed:
Before you upgrade ZENworks for Desktops 3.2 SP3 Inventory components, review the following facts:
In order for your network to support both ZENworks for Desktops 3.2 and ZENworks 6.5 Desktop Management, you must first install ZENworks for Desktops 3.2 SP3 into your network. Installing ZENworks 6.5 Desktop Management without first installing ZENworks for Desktops 3.2 SP3 will not have 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 6.5 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 6.5 Desktop Management. For more information on how to install ZENworks for Desktops 3.2, see the Novell Support Web site.
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 6.5 Desktop Management:
NOTE: If you do not want the Sybase database to be stopped automatically when you stop the Inventory services, comment the Unload dbsrv8.nlm line in the sys:\system\invstop.ncf file.
To stop the Sybase Inventory database:
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.
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.
Ensure that the Inventory database is up and running.
You must have a bigger rollback segment because the database migration and the storage of further data will not succeed due to ORA-01555 and other rollback segment related issues.
To increase the value of rollback segment, execute the following sql script to add an additional data file to 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;
During the ZENworks 6.5 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 the existing ZENworks for Desktops 3.2 SP3 database engine only. 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 will be overwritten by the new ZENworks 6.5 Desktop Management database files. If you choose No, the database will be migrated when the Inventory service starts for the first time.
You must perform the following tasks to upgrade the Inventory database:
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.
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.
IMPORTANT: You can upgrade multiple Inventory servers and database servers at the same time by running the ZENworks 6.5 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.
In ConsoleOne with ZENworks 6.5 Desktop Management Workstation Inventory snap-ins installed, click Tools, click ZENworks Inventory, then click Inventory Migration.
Click Browse to browse for and select the database object to be migrated or the container that has the database object.
If you selected a container in Step 2, do the following:
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.
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.
Click Find.
All the ZENworks for Desktops 3.2 database objects that are found within the specified context are displayed in the Report panel.
Click Migrate.
Click Close.
In ConsoleOne, right-click the database object, then click Properties, then click the ZENworks Database tab.
Ensure that the following database object options have the specified values mentioned depending on the Inventory database:
Click Apply, then click Close.
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 6.5 Desktop Management Inventory server if the server where you want to install the ZENworks 6.5 Desktop Management Inventory server meets the installation requirements. For more information on how to install the ZENworks 6.5 Desktop Management Inventory server, see Desktop Management Server Installation Procedure. The ZENworks 6.5 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 6.5 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 6.5 Desktop Management, you must upgrade the associated component to ZENworks 6.5 Desktop Management (the ZENworks for Desktops 3.2 SP3 Inventory services should not interact with ZENworks 6.5 Desktop Management compliant database and vice versa).
If you have multiple ZENworks for Desktops 3.2 SP 3 Inventory servers connected to a ZENworks for Desktops 3.2 SP3 database server and if you upgrade the database server to ZENworks 6.5 Desktop Management, you must also upgrade all the associated ZENworks for Desktops 3.2 SP3 Inventory servers.
The ZENworks 6.5 Desktop Management installation program automatically migrates only the ZENworks for Desktops 3.2 SP3 Inventory Service object to ZENworks 6.5 Desktop Management. Before starting the Inventory service, you must manually migrate the existing ZENworks for Desktops 3.2 SP 3 policies to ZENworks 6.5 Desktop Management policies using the ZENworks for Desktops Inventory Migration tool. For more information, see Manually Migrating ZENworks for Desktops 3.2 SP 3 Inventory Policies.
After migrating the policies, do the following:
If a ZENworks for Desktops 3.2 SP3 Inventory server is rolling up its information to a ZENworks 6.5 Desktop Management Inventory server, you must apply the following authentication patches that are bundled with the ZENworks 6.5 Desktop Management Companion 2 CD:
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.
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.
In ConsoleOne with ZENworks 6.5 Desktop Management Workstation Inventory snap-ins installed, click Tools > ZENworks Inventory > Inventory Migration.
Click Browse to browse for and select the Inventory Service object or the container that has the Inventory Service object.
If you selected a container in Step 2, do the following:
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.
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.
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.
Click Migrate.
Click Close.
After migrating the policies, perform the following tasks:
Start the ZENworks 6.5 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 6.5 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
Create and configure the Dictionary Update policy to get the latest version of the dictionary for ZENworks 6.5 Inventory Agent. For more information on how to create the Dictionary Update policy, see "Workstation Inventory" in the Novell ZENworks 6.5 Desktop Management Administration Guide.
You must perform the following tasks after upgrading the Inventory server and migrating the Inventory database:
Stop the Inventory service.
If your Inventory database is running Oracle, do the following to improve the database performance:
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
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.
Execute oracle_dbexport_perf.sql from the Novell ZENworks 6.5 Companion 2 CD\database\oracle8i\common directory.
For more information on how to improve the performance of the Inventory database, see "Performance Tips" in "Workstation Inventory" in the Novell ZENworks 6.5 Desktop Management Administration Guide.
Start the Inventory services.