Before you introduce a Novell Small Business Suite 6.6 server into an existing network, you must run the Novell Deployment Manager to update the network.
IMPORTANT: The browser-based version of Deployment Manager can be run only in an Internet Explorer 5 or 6 browser.
On a Windows NT*/2000 or Windows XP Professional Edition workstation that has the latest Novell client 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 Novell Deployment Manager, you can specify the IP address of the server by clicking Details.
Insert the Novell Small Business Suite 6.6 NetWare 6.5 CD 1 Operating System with SP3 CD and go to the root of the CD.
If you want to run the browser-based version of Deployment Manager and you have 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.
Under the Network Preparation heading on the left side of the browser window, click the Overview link to see the tasks that you need to perform.
(Optional but Recommended) Under the Network Preparation heading on the left side of the browser, click the Back Up Data link and follow the instructions that display to back up any server data and Novell eDirectory data.
Backing up your data is an optional step, but one that we recommend you complete.
Under the Network Preparation heading on the left side of the browser, click the Search Tree for eDirectory/NDS Versions link to update eDirectory in your tree to a level that is compatible with the version of NDS® or eDirectory installed by Novell Small Business Suite 6.6.
IMPORTANT: If the tree is using NDS or eDirectory, a compatible version of NDS or eDirectory must be running on all servers in the tree.
This task checks the NetWare and NDS versions of all servers and updates NetWare 4/NDS 6 and NetWare 5/NDS 7 servers to be compatible with eDirectory. It does not update NetWare servers already running eDirectory.
Under the Network Preparation heading on the left side of the browser, click the Prepare for New eDirectory link and follow the displayed instructions to extend the network schema.
This ensures that the new Novell Small Business Suite 6.6 server can communicate with an existing NDS/eDirectory tree.
This step requires that you have already updated NetWare 4/NDS 6 and NetWare 5/NDS 7 servers to be compatible with eDirectory as described in Step 6. It also requires access to a server with a Read/Write replica of the Root partition.
(Conditional) If you have NetWare 4.11 or 4.2/NDS 6 servers in your tree, under the Network Preparation heading on the left side of the browser, click the Generate GUIDs on NetWare 4 Servers link and follow the instructions to generate the necessary GUIDs.
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 Novell Small Business Suite 6.6 server.
This step requires you to update NetWare 4.11 or 4.2/NDS 6 servers to be compatible with eDirectory and to extend the core schema of your tree, as described in Step 6 and Step 7. Step 6 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 new 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 Novell Small Business Suite 6.6. If a problem does occur, see TID# 10078892 - Trustee Assignments Appear to No Longer Work After NetWare 4x to NetWare 6x Upgrade for more information.
(Conditional) Under the Network Preparation heading on the left side of the browser, click the Prepare a Server for Upgrade link and follow the displayed instructions to run a health check on the server that you are upgrading to OES NetWare.
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.
(Conditional) 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. under the Network Preparation heading on the left side of the browser, click the Prepare Cluster for Upgrade link to follow the instructions to run the Prepare a Novell Cluster for Upgrade program.
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.
Under the Network Preparation heading on the left side of the browser, click the Update Certificate Authority Objects link and follow the instructions displayed to create or update a Security container object and a Certificate Authority (CA) object.
Novell Certificate ServerTM 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 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.
(Optional) Under the Network Preparation heading on the left side of the browser, click the Prepare for Universal Password link, read the explanation of the Universal Password feature of NetWare 6.5, click the Universal Password Deployment Guide link, then follow the step-by-step instructions in the deployment guide for setting up the Universal Password feature.
(Conditional) Under the Network Preparation heading on the left side of the browser, click the Prepare for CIFS/AFP link and follow the instructions displayed to prepare your new NetWare 6.5 server so CIFS (Microsoft Windows native networking workstations) and AFP (Apple* Macintosh native networking workstations) users can log in to it.
(Conditional) Under the Network Preparation heading on the left side of the browser, click the Verify NICI Keys link and follow the displayed instructions to check your eDirectory tree for SDI key consistency.
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.
If any invalid keys exist, they should be fixed by running SDIDIAG at the server console.
(Optional) Under the Network Preparation heading on the left side of the browser, click the Schema Update link to extend the eDirectory schema for the products you plan to install on your OES NetWare servers.
This optional task extends the eDirectory schema for all of the products and services that are bundled with OES NetWare. Doing so eliminates the need for future server installers to have administrative rights to the root of the tree.
After you have completed the Network Preparation section of Novell Deployment Manager, click the Overview link located under the Install/Upgrade Options heading to help you choose the install option that best meets your needs.
(Optional) If you have a new computer that you want to install Novell Small Business Suite 6.6 on, or if you are adding a Novell Small Business Suite 6.6 server to your existing network, click the Install NetWare 6.5 link under the Install/Upgrade Options heading for instructions.
(Optional) To automate the Novell Small Business Suite 6.6 installation using a response file and to access the Response File Generator utility which assists you in creating response files, click the Automate an Installation link under the Install/Upgrade Options heading for instructions.
After completing the Novell Small Business Suite 6.6 installation, run the Deployment Manager again and click the links under the Post-Install Tasks heading for information on the following:
After deciding on an installation or upgrade option, exit the Novell Deployment Manager and prepare the computer to be a Novell Small Business Suite 6.6 server (see Preparing the Computer).
To install a NetWare 6.5 server into a pure NetWare 4 tree, run the Novell Deployment Manager utility and follow the directions to copy updated NetWare 4 NDS files to the network, generate GUIDs, and update the schema.
After running the Deployment Manager, but before attempting to install the NetWare 6.5 server, do the following.
NOTE: These steps are necessary only in a pure NetWare 4 tree. If any NetWare 5.1 or NetWare 6.0 servers already exist in the tree, this procedure is not necessary.
Run DSRepair on a server that holds a writable copy of the Root partition.
Select Advanced Options Menu > Global Schema Operations.
Log in as the Admin, if necessary, then run the Post NetWare 5 Schema Update.
Return to the main menu and select Advanced Options Menu > Repair Local DS Database.
Set the Rebuild Operational Schema option to Yes.
Run the local database repair.