Deployment Manager is a set of utilities to help you prepare for a new installation of, or upgrade to, Novell Open Enterprise Server. It also contains documentation and hints to ensure the success of your installation or upgrade.
Before you introduce an OES NetWare server into an existing network, whether through a new installation or by upgrading an older server, you should run the Novell Deployment Manager to ensure that your network is properly prepared.
Deployment Manager provides easy access to a number of tasks you might need to perform as you prepare your network for server installations or upgrades. It also provides a consolidated interface to various install/upgrade and post-install tasks. Accordingly, the Deployment Manager tasks are divided into three sections: Network Preparation, Install/Upgrade Options, and Post-Install Tasks.
Network Preparation tasks:
Install/Upgrade Options tasks:
The tasks you need to perform in Deployment Manager depend on a number of factors, such as the version of NDS/eDirectory you have in your tree, whether you are installing or upgrading a server, the version of NetWare on your server, and whether the server is part of a cluster.
If you already have a NetWare 6.5 or OES NetWare server in your tree, you do not need to run Deployment Manager.
Optionally, you can complete the Schema Update task to make the required extensions to the eDirectory schema and the extensions for products and services that are bundled with OES NetWare. This eliminates the need for future server installers to have Admin rights to the root of the tree.
If you are upgrading NetWare 4, 5, or 6.0 servers to OES NetWare, review all of the tasks and complete those that apply to your version of NetWare.
If you are installing an OES Linux server into an existing eDirectory tree that contains no NetWare 6.5 or OES NetWare servers, you must first complete the Prepare for New eDirectory task if the tree is any version of NDS or eDirectory earlier than eDirectory 8.6.
Optionally, you can complete the Schema Update task to make the required extensions to the eDirectory schema and the extensions for products and services that are bundled with OES Linux. This eliminates the need for future server installers to have Admin rights to the root of the tree.
No other Deployment Manager tasks apply to OES Linux servers. See the OES Linux Installation Guide for information about preparing a Linux server for OES.
Deployment Manager is run from a Windows* workstation on the network and requires the Novell Client™ for Windows software. It also requires access to a server with a Read/Write replica of the eDirectory tree’s Root partition.
On a Windows 2000 or Windows XP Professional Edition workstation that has the latest Novell Client software installed on it, log in to your existing network as a user with the Supervisor right.
If you are prompted to log in again while running the Deployment Manager, you can specify the IP address of the server by clicking Details.
Insert NetWare 6.5 SP6 CD 1 (Operating System) and go to the root of the CD.
If you want to run the browser-based version of Deployment Manager and you have an Internet Explorer 5 or 6 browser installed, run nwdeploy.exe located at the root of the CD.
If you prefer to run a standalone version of Deployment Manager that does not require a browser, or you do not want to use the ActiveX Control included with the browser-based version, run nwdeploynobrowser.exe located at the root of the CD.
Complete the applicable tasks to properly prepare your network before installing or upgrading to NetWare 6.5 or OES NetWare, or before installing an OES Linux server into an existing NDS 6, 7, or 8 tree.
If you are upgrading an existing NetWare server to NetWare 6.5 or OES NetWare, you should back up the server data and the eDirectory data.
Backing up your data is an optional task, but one that Novell recommends you complete.
Choose this task and follow the displayed instructions to back up any server data and Novell eDirectory data.
The NetWare 6.5/OES NetWare server installation installs a new version of eDirectory. Before you upgrade or install your first NetWare 6.5 or OES NetWare server, a compatible version of NDS or eDirectory must be running on all servers in your tree.
This task checks the NetWare and NDS versions of all servers in your tree and updates NetWare 4/NDS 6 and NetWare 5/NDS 7 and 8 servers to be compatible with eDirectory. It does not update NetWare servers already running eDirectory.
Choose this task to search the tree for NDS versions that need to be updated.
This task extends the core schema to ensure that new NetWare 6.5 or OES NetWare servers can communicate with an existing NDS/eDirectory tree.
This task requires that you have already completed the Search Tree for eDirectory/NDS Versions task and updated NetWare 4/NDS 6 and NetWare 5/NDS 7 servers to be compatible with eDirectory as described in Search Tree for eDirectory/NDS Versions. It also requires access to a server with a Read/Write replica of the Root partition.
Choose this task and follow the displayed instructions to extend the schema.
If you have NetWare 4.11 or 4.2/NDS 6 servers in your tree, you should generate GUIDs before upgrading to NetWare 6.5 or OES NetWare.
IMPORTANT:The GUID generator in Deployment Manager does not work with NetWare 4.10 servers, only with 4.11 or 4.2 servers. If there is a NetWare 4.10 server in your tree, it must be removed or you cannot install a new NetWare 6.5 server.
Choose this task and follow the displayed instructions to generate the necessary GUIDs.
This task requires that you update NetWare 4.11 or 4.2/NDS 6 servers to be compatible with eDirectory as described in Search Tree for eDirectory/NDS Versions and extend the core schema of your tree as described in Prepare for New eDirectory . These tasks copied a new ds.nlm and a new sguid.nlm that support GUID generation to each selected NetWare 4 server. With these updated files in place, and with the core schema extended and synchronized, when ds.nlm is restarted on a NetWare 4.11 or 4.2/NDS 6 server, it automatically generates GUIDs for objects in master replicas on that server.
Even though the GUID generator for NetWare 4 helps to avoid GUID compatibility issues, problems can still occur. Always back up all file system trustees before any upgrade or migration to NetWare 6.5. If a problem does occur, see TID# 10078892 - Trustee Assignments Appear to No Longer Work After NetWare 4.x to NetWare 6.x Upgrade or the AppNote titled NetWare 6 Trustee Rights: How They Work and What to Do When It All Goes Wrong for more information.
This task runs a health check utility on an existing NetWare server to ensure that there is enough memory, a sys: volume is in place, and the server meets the minimum requirements for the upgrade. The utility reports if problems are detected that could cause the upgrade to fail.
If you are upgrading Novell Cluster Services™ from NetWare 5.1 and your cluster has shared storage, you must prepare your NetWare 5.1 cluster servers before upgrading them to OES NetWare and before upgrading Novell Cluster Services. This preparation is necessary to ensure existing shared-volume trustee assignments can be used after the upgrade.
This task is necessary only if you are upgrading from a NetWare 5.1 cluster to OES NetWare, not if you are upgrading from a NetWare 6.0 cluster.
Novell Certificate Server™ is an integrated Public Key Infrastructure (PKI) built in to eDirectory. The NetWare installation process uses Novell Certificate Server to create an Organizational Certificate Authority (CA) and to issue certificates for applications that consume Secure Socket Layer (SSL) services.
Novell delivered a base-level PKI with NetWare 5.0. Because your network might be configured with the NetWare 5.0 PKI, you should follow the steps outlined here to properly upgrade from the NetWare 5.0 PKI and to correctly configure your network for Novell Certificate Server.
Choose this task and follow the displayed instructions to create or update a Security container object and a Certificate Authority (CA) object.
OES NetWare offers a Universal Password feature to simplify the integration and management of different password and authentication systems into a coherent network.
Universal Password specifically addresses two problems:
This is accomplished by moving all services to utilize a common password, or Universal Password, in the system. Backwards compatibility is maintained to support legacy systems in the network.
Universal Password is not turned on by default. This is to avoid problems with users logging in who might have international characters in their passwords or who had used case-sensitive passwords.
If you plan to enable Universal Password, choose this task. It is an informational step only, containing a link to information about Universal Password deployment which provides step-by-step instructions for setting up the Universal Password feature.
If you have CIFS (Microsoft* Windows native networking workstations) and AFP (Apple* Macintosh* native networking workstations) users on your network and you want them to log in to your new OES NetWare server, you must implement one of the following two options:
This task is an informational step only, providing instructions to prepare your new OES NetWare server so CIFS and AFP users can log in to it and containing links for more detailed information.
If you have updated eDirectory, Novell recommends that you check your tree for SDI key consistency. If the tree contains invalid SDI keys, then CIFS, AFP, Nsure Identity Manager, and Universal Password might not work after installing OES NetWare.
Choose this task and follow the displayed instructions to check your eDirectory tree for SDI key consistency. If any invalid keys exist, they should be fixed by running SDIDIAG at the server console.
This optional task extends the eDirectory schema for all of the products and services that are bundled with OES on both the NetWare and Linux platforms. Doing so eliminates the need for future server installers to have administrative rights to the root of the tree.
Before performing the schema update for OES NetWare, you must have already updated NetWare 4/NDS 6 and NetWare 5/NDS 7 servers to be compatible with eDirectory as described in the Prepare for New eDirectory task. You also need access to a NetWare server with a Read/Write replica of the Root partition by an admin user with rights to [Root].
If you want to do this, choose this task before upgrading or installing new servers to allow the schema updates to synchronize to all partitions in your tree.
After you have completed the Network Preparation section of Deployment Manager, click the Overview link located under the Install/Upgrade Options heading to help you choose the installation or upgrade task that best meets your needs.
If you have a new computer that you want to install OES NetWare on, or if you are adding an OES NetWare server to your existing network, choose this task for links to instructions and prerequisites.
Choose this task for instructions on automating the OES NetWare installation using a response file and to access the Response File Generator utility which assists you in creating response files.
For more information about response files and running the Response File Generator utility, see the OES for NetWare Response File Installation Guide.
If the NetWare server that you are upgrading meets the minimum hardware requirements for OES NetWare, choose this task for upgrade instructions.
You can also access the remote upgrade utility from this task.
In OES SP1, the Novell Server Consolidation Utility 4.1 and the NetWare Migration Wizard 8.1 were combined under a single launch interface called the Novell Server Consolidation and Migration Toolkit. The launch interface asks you what type of consolidation or migration project you want to perform and then launches the appropriate utility automatically.
With Server Consolidation Utility 4.1, you can copy data from any number of NetWare servers to OES servers on either NetWare or Linux.
You can also copy data from servers in Windows NT* 4.0 or Windows 2000/2003 domains to OES servers in a Novell eDirectory tree. Shared folders are migrated to a NetWare or Linux file system and Windows permissions are converted to NetWare or Linux equivalents. During the consolidation, the domain users and local/global groups are converted to eDirectory objects and placed in the destination tree.
You can also use the Server Consolidation Utility to reassign NDPS® Printer Agents to an NDPS Printer Manager in the same eDirectory tree, or to migrate an iPrint printing configuration from an OES NetWare (6.5 FCS through SP6) environment to the OES Linux environment.
With NetWare Migration Wizard 8.1, you can migrate file system and NDS/eDirectory data from an existing NetWare 4, 5, or 6 server to a new OES NetWare server on your network. After the migration, the new server replaces and assumes the identity of the old one.
You can install the toolkit from this task in Deployment Manager. Click the Install/Run the Server Consolidation and Migration Toolkit link. If you have already installed the toolkit, clicking this link starts the toolkit.
After you have run the NetWare Install program, you can return to Deployment Manager and perform any necessary post-install tasks.
By default, the NetWare Install program creates a sys: volume on the server. (When NetWare 6.5 and OES NetWare are installed, a special _Admin volume is also created.)
NetWare 6.5 and OES NetWare give you the option to create additional volumes during the installation process. This allows you to install products on a new data volume rather than filling up the server's sys: volume.
If you want to create additional data volumes after the installation is completed, choose this task for information and links to relevant documentation.
Installating additional products after an OES NetWare server installation is a simple procedure. Products can be installed at the server GUI console, or remotely by clicking the link.
After installing or upgrading to a new version of NetWare, you should run DSRepair. The DSRepair utility is provided with NetWare to repair problems with eDirectory on a single-server basis. It does not correct problems on other servers; it must be run on each server individually.
Choose this task for additional information on running DSRepair.
This task is to be performed after you have completed the task to prepare your NetWare 5.1 cluster servers. It is not necessary if you are upgrading a NetWare 6.0 or 6.5 cluster.
You should have already completed the following:
Choose this task to run the Novell Cluster Services install/upgrade utility.
The first time you run Deployment Manager, it installs files totaling approximately 80 MB onto your Windows workstation. The utility should load faster after the first time it is run because these files have already been installed.
If you want to remove the Deployment Manager files to save disk space or to run an older version of Deployment Manager from a previous NetWare 6.5 Support Pack release, choose this task.
After you have completed the tasks in the Network Preparation section and decided on an installation or upgrade option, exit Deployment Manager by closing the browser window.