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 NetWare 6.5 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.
NOTE:If you already have an NetWare 6.5 or NetWare 6.5 server in your tree, you do not need to run Deployment Manager.
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 four sections: Required Tasks, Network Preparation, Install/Upgrade Options, and Post-Install Tasks.
Required Tasks
Network Preparation tasks:
Install/Upgrade Options tasks:
Post-Install tasks:
You run Deployment Manager run from a Windows* workstation on the network. It 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 .
Insert the NetWare 6.5 SP8 CD 1 (Operating System) or NetWare 6.5 SP8 DVD and go to the root of the CD/DVD.
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/DVD.
or
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/DVD.
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 an NetWare 6.5 or NetWare 6.5 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 NetWare 6.5. This eliminates the need for future server installers to have Admin rights to the root of the tree.
If you are installing an OES Linux server into an existing eDirectory tree that contains no NetWare 6.5 or NetWare 6.5 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 2 SP2: Installation Guide for information about preparing a Linux server for OES.
Complete the applicable tasks to properly prepare your network before installing or upgrading to NetWare 6.5 or NetWare 6.5, or before installing an OES Linux server into an existing NDS 6, 7, or 8 tree.
This task extends the core schema to ensure that new NetWare 6.5 or NetWare 6.5 servers can communicate with an existing NDS/eDirectory tree. This task requires access to a server with a Read/Write replica of the Root partition.
Start Deployment Manager, choose this task, and follow the displayed instructions to extend the schema.
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 in this task to properly upgrade from the NetWare 5.0 PKI and to correctly configure your network for Novell Certificate Server.
Start Deployment Manager, choose this task, and follow the displayed instructions to create or update a Security container object and a Certificate Authority (CA) object.
NetWare 6.5 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:
Management of multiple types of password authentication methods from disparate systems
Authentication from different systems using passwords with extended characters
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 used case-sensitive passwords.
If you plan to enable Universal Password, Start Deployment Manager and choose this task. It is an informational step only, containing a link to information about Universal Password deployment that provides step-by-step instructions for setting up the Universal Password feature.
If you have CIFS (Microsoft* Windows native networking workstations) and AFP (Apple* Filing Protocol native networking workstations) users on your network and you want them to log in to your new NetWare 6.5 server, you must implement one of the following options:
Novell Modular Authentication Service (NMAS) must be running on a server in the same partition that the new NetWare 6.5 server is to reside in. Additionally, the server running NMAS must contain a read/write replica of the partition where the CIFS and AFP users exist.
The new NetWare 6.5 server that you want your CIFS and AFP users to log in to must contain a read/write replica of the partition.
Start Deployment Manager and choose this task.This task is an informational step only, providing instructions to prepare your new NetWare 6.5 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 NetWare 6.5.
Start Deployment Manager, choose this task, and follow the displayed instructions to check your eDirectory tree for SDI key consistency. If any invalid keys exist, fix them 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 NetWare 6.5, you must have already updated 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, start Deployment Manager and 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 link located under the heading to help you choose the installation or migration task that best meets your needs.
If you have a new computer that you want to install NetWare 6.5 on, or if you are adding an NetWare 6.5 server to your existing network, start Deployment Manager and choose this task for links to instructions and prerequisites.
Start Deployment Manager and choose this task for instructions on automating the NetWare 6.5 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 Section A.0, NetWare Response File Reference.
OES 2 includes a new set of migration tools for migrating from NetWare to OES Linux. The core file system migration tools are installed by default on every OES 2 Linux server. For instructions on using these tools, see the OES 2 SP2: Migration Tool Administration Guide.
The Server Consolidation and Migration Toolkit is also included in OES 2 for NetWare to NetWare migrations. You can install the toolkit from this task in Deployment Manager. Start Deployment Manager and click the link. If you have already installed the toolkit, clicking this link starts the toolkit. For instruction on using the toolkit, see the Novell Server Consolidation and Migration Toolkit Administration Guide.
After you 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 NetWare 6.5 are installed, a special _Admin volume is also created.)
NetWare 6.5 and NetWare 6.5 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, start Deployment Manager and choose this task for information and links to relevant documentation.
Installing additional products after an NetWare 6.5 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.
Start Deployment Manager and choose this task for additional information on running DSRepair.
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 runs 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, start Deployment Manager and 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.