With OES, Novell provides a number of tools to facilitate system preparation, deployment, and migration.
Deployment Manager is Novell’s server installation, upgrade, and system preparation utility. It provides easy access to a number of tasks you might need to perform as you prepare your network for OES server installations or upgrades. It also presents a consolidated interface to various server install/upgrade options and post-install tasks, along with links to relevant documentation and hints to ensure the success of your OES deployment.
Before you introduce an OES server into an existing network, whether through a new installation or by upgrading an older server, you should run Deployment Manager to ensure that your network—and eDirectory™ in particular—is properly prepared.
While Deployment Manager is primarily a NetWare® server deployment tool, it can also be used to prepare eDirectory when you are installing an OES Linux server into a tree containing no NetWare 6.5 or OES NetWare servers.
If you already have a NetWare 6.5 or OES NetWare server in your eDirectory tree, you do not need to run Deployment Manager.
Table 2-1 summarizes the options available in Deployment Manager and indicates when they should be run. The options are listed in the order they are presented in Deployment Manager.
Table 2-1 Deployment Manager Options
|
Deployment Manager Option |
What It Does |
When You Should Run It |
|---|---|---|
|
Network Preparation |
||
|
Overview |
Provides a summary of each of the options in the Network Preparation category (information only). |
To get a quick idea of what each of the Network Preparation options does. |
|
Back Up Data |
Provides instructions for backing up data on NetWare 5.1 servers with SBACKUP and NetWare 6 servers with SBCON (information only). |
To find out how to run SBACKUP or SBCON to back up data on your NetWare servers before upgrading them. |
|
Search Tree for eDirectory/ NDS Versions |
Launches the View and Update NDS utility to check the NetWare and NDS® versions of servers in a tree and update NDS on servers that require it. |
You have NetWare 4/NDS 6 servers or NetWare 5/NDS 7 or NDS 8 servers in your eDirectory tree. You must complete the Prepare for New eDirectory task after running this utility. |
|
Prepare for New eDirectory |
Launches the Extend the Core Schema utility to extend the core schema of the NDS tree in preparation for installing the version of eDirectory that comes with OES NetWare. |
You have NetWare 4/NDS 6 servers or NetWare 5/NDS 7 or NDS 8 servers in your tree. You must complete the Search Tree for eDirectory/NDS Versions task before running this utility. |
|
Generate GUIDs on NetWare 4 servers |
Launches the View NetWare 4 Servers and Restart NDS utility to check for NetWare 4.11 and 4.2 servers in your tree that have the updated NDS files that support GUID generation and (optionally) restart ds.nlm to trigger the GUID generation. |
Your tree contains NetWare 4 servers that you will upgrade to OES NetWare. |
|
Prepare a Server for Upgrade |
Launches the Server Health Utility to perform a general health check on a NetWare server and to ensure, among other things, that there is enough memory, a sys: volume is in place, and that the server meets the minimum requirements for an OES NetWare upgrade. |
You have a NetWare 5 or 6 server that you plan to upgrade to OES NetWare. |
|
Prepare Cluster for Upgrade |
Launches the Prepare a Cluster utility to prepare an existing Novell Cluster Services cluster so that the NetWare 5.1 servers in the cluster can be upgraded to OES NetWare without trustees and rights being lost. |
You have a NetWare 5.1 cluster that you plan to upgrade to OES NetWare. After you complete the server upgrades, you must complete the Install/Upgrade Cluster task in the Post-Install Tasks category. |
|
Update Certificate Authority Objects |
Provides instructions for updating the Certificate Authority (CA) server from a NetWare 5 Public Key Infrastructure (PKI) installation, and for configuring your network for Novell Certificate Server v2.x (information only). |
You installed the base-level PKI as part of a NetWare 5 installation and designated a NetWare 5 server as the Organizational Certificate Authority. |
|
Prepare for Universal Password |
Provides information about preparing your network for the Universal Password feature in OES NetWare (information only). |
You plan to enable the Universal Password feature (it is disabled by default in OES NetWare). |
|
Prepare for CIFS/AFP |
Provides information on preparing your OES NetWare server to support Windows* native networking workstations through CIFS and Macintosh native networking workstations through AFP (information only). |
You have Windows or Macintosh workstations on your network that you want to be able to access data on your new OES NetWare server without having the Novell Client™ software installed. |
|
Verify NICI Keys |
Provides information about running the SDIDiag utility to check your eDirectory tree for SDI (Security Domain Infrastructure) key consistency (information only). |
You have invalid SDI keys in eDirectory from a previous installation of NICI. |
|
Schema Update |
Launches the Schema Update utility to extend the schema of an existing NDS/eDirectory tree for the products and services that are bundled with OES on both the NetWare and Linux platforms. |
To extend the schema for products and services that might be installed as part of future server installations or upgrades. Doing this eliminates the need for future installers to have Admin rights to the root of the tree. You must complete the Search Tree for eDirectory/NDS Versions and Prepare for New eDirectory tasks before running this utility. |
|
Install/Upgrade Options |
||
|
Overview |
Provides a summary of each of the options in the Install/Upgrade category (information only). |
To get a quick idea of what each of the Install/Upgrade options does. |
|
Install NetWare 6.5 |
Provides information about the OES NetWare installation procedure, with links to the online documentation (information only). |
To see what is involved in installing a new OES NetWare server. |
|
Automate an Installation |
Provides general information about using a response file to automate a NetWare server installation, and launches the Response File Generator to assist you in creating a customized response file. |
To create a response file to do a “silent” or “unattended” server installation. |
|
Upgrade to NetWare 6.5 |
Provides links to the online documentation for in-place server upgrades, and launches the Upgrade a Server Remotely utility to perform a remote upgrade. |
To perform a remote server upgrade from your Deployment Manager workstation. |
|
Consolidate or Migrate Servers |
Launches Install/Run the Server Consolidation and Migration Toolkit to either install the version of the toolkit on NetWare 6.5 CD 1 or run the toolkit if it is already installed on your workstation. |
To install or run the Server Consolidation and Migration Toolkit. The toolkit combines NetWare Migration Wizard 8.1 and Server Consolidation Utility 4.11 under a single launch interface. Migration Wizard migates data from an older NetWare server to a new OES NetWare server. The new server replaces the old server and assumes its server name and IP address. The Server Consolidation Utility copies data from NetWare or Windows NT* servers to OES servers (both NetWare and Linux). Source servers can continue to exist and retain their server names and IP addresses. |
|
Post-Install Tasks |
||
|
Creating Additional Volumes |
Provides links to the online documentation for creating additional volumes during the NetWare server installation (information only). |
To know how to create volumes other than sys: on your server during the NetWare installation procedure. |
|
Install NetWare 6.5 Products |
Launches the Remote Product Install utility to do a post-installation of OES NetWare products remotely. |
To remotely install additional OES NetWare products on a server from your Deployment Manager workstation. |
|
Use DSREPAIR |
Provides instructions for running the DSRepair utility to check the NDS/eDirectory and schema status after installing or upgrading to a new version of NetWare (information only). |
To verify that changes made to NDS/eDirectory and the schema have properly synchronized on your new NetWare server and that the new server's time is synchronized with other servers on the network. |
|
Install/Upgrade Cluster |
Launches the Install or Upgrade a Cluster utility to complete the upgrade of a NetWare 5.1 cluster server. |
To complete the upgrade of a NetWare 5.1 cluster server. |
|
Remove Deployment Manager |
Launches the Remove Deployment Manager function to remove the files that Deployment Manager copied to your workstation the first time you ran it. |
To remove the approximately 80 MB of Deployment Manager files to save disk space, or to clear the current version so you can run an older version of Deployment Manager from an earlier NetWare 6.5 Support Pack release. |
For more information and instructions on how to use Deployment
Manager, see Prepare
the Network with Deployment Manager
in the OES
NetWare Installation Guide.
You can complete the following Deployment Manager tasks from the Install and Upgrade option in Novell iManager 2.6:
Novell eDirectory relies on a sophisticated Public Key Infrastructure (PKI) to provide the strong encryption and certificate issuing mechanisms that are necessary for maintaining secure connections. If the security infrastructure is not functioning correctly, the installation and configuration of some OES components will fail.
PKIDiag is a diagnostic tool for analyzing the security infrastructure and resolving errors and configuration problems. It runs as a NetWare Loadable Module™ (NLM™) at the NetWare server console.
The Novell Deployment Manager runs PKIDiag as part of its Server Health Utility. However, it runs PKIDiag in diagnostic mode, which identifies errors but does not fix them. If the Server Health Utility detects PKI problems, you must run PKIDiag and resolve any problems before you can successfully upgrade an existing NetWare server in the tree to OES NetWare.
For more information about eDirectory and PKI issues in OES, see Section 2.2.5, Security and Certificate Management.
To download the PKIDiag utility, see TID 2967938 - “PKI Diag Utility 2”.
For more information on the PKIDiag utility, see the following:
If you have an NDS/eDirectory tree that was created during the installation of a previous version of NetWare, it is possible that a different version of Novell International Cryptography Infrastructure (NICI) was used to create the SDI (Security Domain Infrastructure) keys.
NOTE:SDI keys are referred to as NICI keys in the Novell Deployment Manager utility.
Each server within an eDirectory tree should hold matching copies of the SDI keys in order for products such as Novell Certificate Server and Novell Modular Authentication Services (NMAS™) to function correctly. If you have servers running versions of NICI earlier than 2.4.2, or if your tree is running a version of NDS or eDirectory earlier than 8.7.1, you should run the SDIDiag utility to ensure that your Security Domain Infrastructure is properly configured.
The SDIDiag utility is an SDI diagnostic and repair utility that lets you view the various keys within a tree and ensure that all servers are synchronized with consistent keys. It can be run either as an NLM program at the NetWare server console or as a Windows .exe program on a network workstation.
For more information about eDirectory certificate management issues in OES, see Section 2.2.5, Security and Certificate Management.
To download the SDIDiag utility, see TID 2966746 - “SDIDiag 2.1”.
For more information on the SDIDiag utility, see the following:
OES comes with a number of tools to help you install, upgrade, and migrate your network servers.
Novell has integrated the OES for Linux installation with the SUSE® YaST program. YaST is a graphical Linux-based utility that greatly simplifies the installation and configuration of components on SUSE Linux Enterprise Server 9 (SLES 9) servers. When you install and configure OES Linux, you also install and configure SLES 9.
For more information and instructions on installing OES for Linux, see the OES Linux Installation Guide.
In OES SP2, YaST installs SLES 9 SP3 and OES components at the same time. The default selection for Novell Open Enterprise Server is to install all OES components except the following:
If you require these services, Novell recommends that you install them after the initial OES installation is complete.
If you want to install a specialized OES Linux server, you can select from the following predefined server types in YaST:
OES SP2 provides the ability to install and configure multiple
servers at the same time using a control file in AutoYaST. This
is similar in concept to using a response file in OES NetWare installations.
The servers should share similar hardware and perform similar tasks.
For more information, see Installing
and Configuring Multiple Servers Using AutoYaST
in
the OES Linux Installation Guide.
You can also use YaST to upgrade an existing SLES 9, SLES
9 SP1, or SLES 9 SP2 server to OES Linux. (These are the only supported
upgrades for this release. Upgrading to OES from SUSE Linux Enterprise
Server 8 is not supported.) For more information, see Upgrading
to OES Linux
in the OES Linux Installation
Guide.
To apply the latest support pack to an existing OES Linux
server, see Patching
an OES Linux Server
in the OES Linux
Installation Guide.
OES SP2 for NetWare and NetWare 6.5 Support Pack 6 are the same product and they use the same CD set and installation program. The option to choose between Open Enterprise Server and a NetWare 6.5 Support Pack installation was removed from the Install program in OES SP1.
When you install OES SP2 for NetWare, you can optionally install the following updated products:
This is the cross-platform version of iManager which lets you manage both OES NetWare and OES Linux servers. This version also includes enhanced performance and a new administration interface.
In OES FCS and SP1, the administration interface for Virtual Office was removed from iManager and incorporated into Virtual Office.
Virtual Office is not included in NetWare 6.5 SP5. Existing Virtual Office installations will continue to run on servers updated to OES SP2. If you are creating a new server and want to install Virtual Office, install it using the OES SP1 CDs, then update or patch the server to OES SP2. The OES SP1 CD images are available on the Novell Support Web site.
OES includes QuickFinder Server 4, a powerful search engine that indexes a wide variety of Web and file system data and makes it easy for users to find the information they are looking for. QuickFinder Server is an updated version of the NetWare Web Search Server that has been enhanced to run on both NetWare and Linux.
NOTE:In OES SP2, the NetWare Install program refers to the latest version of QuickFinder as version 4.2.0. In YaST, the software is simply referred to as Novell QuickFinder. Make sure you are using the OES SP2 CDs to install or upgrade to the latest version of QuickFinder.
To avoid the possibility of installing incompatible products on the same server, the NetWare Install program does not allow iManager 2.6 and Virtual Office 1.0 to be installed on the same server.
Likewise, NetWare Web Search Server and QuickFinder Server cannot coexist on the same NetWare server. Because QuickFinder runs on both NetWare and Linux, it is the logical choice for the OES environment.
You can also use the NetWare 6.5 installation program to perform in-place upgrades to OES NetWare. Remote or across-the-wire upgrades can be launched from either Deployment Manager or iManager.
For more information and instructions on installing OES NetWare, see the OES NetWare Installation Guide.
In OES SP1 and later releases, the NetWare Migration Wizard and the Novell Server Consolidation Utility are 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.
In version 4.11 of the Server Consolidation Utility, you can copy data from NetWare or Windows source servers to OES Linux and OES NetWare servers. When copying data from NetWare to OES Linux, the destination volume must be an NSS volume. For data coming from NetWare servers, the Server Consolidation Utility preserves as much of the existing metadata as possible, including NetWare trustee rights, file/directory attributes, and ownership information. For data coming from Windows servers, the NTFS file permissions are mapped to Novell rights to give you similar security functionality.
Due to inherent differences in the way the Linux operating
system handles file systems, there are a number of migration issues
you need to be aware of when copying data to OES Linux servers.
For more information, see Consolidating
Data to OES Linux
in the Novell Server Consolidation
and Migration Toolkit 1.1 Administration Guide.
Another new feature is the ability to migrate iPrint printers
and Print Managers from NetWare 6.5 to an OES Linux environment.
For more information, see Migrating
iPrint Printers and Print Managers from NetWare to Linux
in
the Novell Server Consolidation and Migration Toolkit
1.1 Administration Guide.
Use NetWare Migration Wizard to migrate to OES NetWare. Migrations from Windows source servers or from NetWare sources to OES Linux destinations are not supported in the Migration Wizard.
For more information on using the utilities included in the Server Consolidation and Migration Toolkit, see the Novell Server Consolidation and Migration Toolkit Administration Guide.