At one time, networks pretty much ran only one network operating system (NOS). In today’s world, that’s the exception rather than the rule. Novell realized this change and has provided network administrators with a way to manage NetWare, NT, and Solaris (and soon Linux) from a central console. This product originally started life as NDS for NT, but the need grew beyond merely synchronizing user accounts and passwords. For the purposes of this Daily Drill Down, we’ll be working with a NetWare 5.0 server and an NT domain.
Getting ready for installation
As with any product, there are a few housekeeping details that must be taken care of to get a satisfactory installation. We’ll start with what you’ll need to check on the NetWare server(s) that will be working with NDS Corporate Edition.
You’ll need a NetWare 5.0 server running at least Support Pack 2. Depending on what other Novell or third-party products you have on your server, you should think about using at least Support Pack 5. You’ll need to log in either as Admin or a username that has rights to [Root] to modify the NDS schema.
New to this version is the ability to handle the user administration tasks through ConsoleOne. Although it’s not specifically listed as a requirement, I strongly suggest downloading the latest version of ConsoleOne v1.2c2 from Novell.
If you haven’t previously installed ConsoleOne, you’ll be pleasantly surprised. The NDS Corporate Edition Quick Start manual says you should have at least a 200-MHz processor and a minimum of 64 MB of RAM. Although Novell has sometimes been accused of overstating their product requirements, in this case you should consider exceeding the minimums shown here for ConsoleOne. This is especially true in workstation memory. While you can run ConsoleOne with 64 MB of RAM, I think you’ll see much better performance when you have at least 96 MB.
You’ll also need to use the latest client software. You can download this from www.novell.com/download. At the time this article was written, the latest version of the Novell client for Windows 95/98 was v3.21 and for Windows NT/2000 was v4.71.
One other requirement that you should strictly adhere to is installing the latest version of Novell’s Cryptography Support module (NICI) for the servers and/or client workstations if you’ll be using ephemeral key support for SSL connections. Because of recent changes on Novell’s Web site, some of the files shown as available for download can’t be downloaded. Until this situation is corrected, you can download the files from www.novell.com/products/cryptography. Click Download Support Modules to get to the files you need.
Your NT servers should be running NT 4 with Service Pack 3 or later. I recommend at least Service Pack 5 to avoid potential problems with SNMP memory leaks that were known to be an issue with NT Service Pack 4.
You should be running a Pentium 200-speed processor with 64 MB of RAM and a palette greater than 16 colors. Depending on what your NT servers are used for, you probably have more than this amount of memory in the server. Your server should also have a static IP address.
You’ll need to be able to log in to the NT server with Administrative rights so that you can make the necessary file and registry changes when NDS Corporate Edition is installed. You should also have at least version 4.5 or later of the Novell Client for Windows NT installed. I suggest copying the directory containing the Novell NT client onto each of the NT servers on which you’ll be installing NDS Corporate Edition so that you won’t have to hunt down the NetWare Client CD or have to map a drive to the NetWare server that holds the copy of the client software. This will be especially handy when you must make changes to previously installed features on the client.
If you’re running Microsoft’s Exchange mail server, you’ll need to be running either Exchange 5.0 with Service Pack 1 or Exchange 5.5 to use the Mailbox Manager for Exchange. If you inherited an Exchange server and didn’t install it, I suggest running at least Service Pack 2 with Exchange 5.5. A little pruning of unneeded users and mailboxes is also appropriate before starting the NDS Corporate Edition installation on your NT servers. This could save considerable cleanup time later after the two NOSs are talking.
If the bulk of your experience has been with NetWare, there are a couple of extra steps you should take with your NT servers in preparation for installing NDS Corporate Edition. Make sure that you have at least one, preferably two, good backups of the servers you’ll be working with just in case something happens during the installation, causing you to have to restore from tape.
Become familiar with NT’s Rdisk utility. This creates the Emergency Repair Disk (ERD) that can prove to be a lifesaver when trouble strikes. I recommend creating one ERD before starting the NDS Corporate Edition install and marking this disk pre-NDS Corporate Edition. After you’ve finished installing the software, make another ERD and label it post-NDS Corporate Edition. The first ERD will be most useful if you have problems during the installation process and need to do an NT Repair process to get back to a known good install point. The post-install ERD will be useful in fixing problems that show up after the NT server is talking to the NDS tree.
Although the documentation doesn’t mention this and you won’t see a warning until you are well into the installation of NDS Corporate Edition, make sure you know which of your servers is the PDC (Primary Domain Controller) and which are the BDCs (Backup Domain Controllers). If you aren’t sure which are which, go to Server Manager on your NT server to find out.
You should install Corporate Edition first on the PDC and then on the BDCs. This is an all-or-nothing situation—if you install Corporate Edition on the PDC, you’ll also have to install it on all of the BDCs in the domain that you’re integrating into NDS. If you don’t, your users will experience difficulty logging in at times.
Installing NDS Corporate Edition on NetWare
Before starting the installation process, carefully review the Readme file. Take a few minutes to check the version of NDS currently installed on the server on which you’re going to install Corporate Edition to see which updated version of DSREPAIR.NLM you should copy to the SYS:SYSTEM directory. After putting the new DSREPAIR in place, you should perform a Post-NetWare 5 Schema Update per the instructions in the Readme file. If you aren’t very comfortable with DSREPAIR, choose Advanced Options | Global Schema Operations | NetWare 5 Schema Update.
Load NWCONFIG.NLM from your server console, highlight Install A Product Not Listed, and press [Enter]. When the Path box appears, press [F3], type SYS:NDS_CORP (substituting the volume and path where you copied the files from the NDS Corporate Edition CD), and press [Enter].
A status box will appear, indicating the progress of the files are being copied, the NDS schema being extended, etc. Depending on the revision level of the various NLMs on your server, you may not have to copy much from the NDS Corporate Edition CD. If you receive a message that NDS v8.0.6 is already installed, you can proceed to installing NDS Corporate Edition on your NT server(s).
Installing NDS Corporate Edition on NT
To begin this stage of the installation, insert the NDS Corporate Edition CD into the CD-ROM drive of the NT server on which you want to install NDS. Log in to the NT server either as Administrator or with a login ID with administrative privileges. Run SETUP.EXE from the NT directory on the NDS Corporate Edition CD. When the login screen appears, four options will be available: Install Novell Directory Services, Integrate Windows NT Domains With NDS, Integrate Microsoft Exchange Accounts With NDS, and Install Management Utilities.
Don’t be concerned if the Integrate Microsoft Exchange option is grayed out when you first see the install screen. It will become a selectable option when you check the Integrate Windows NT Domains option. For the purposes of this Daily Drill Down, we will be doing a full implementation of NDS Corporate Edition. Select all of the options and click Install.
One of the first things the installation program will do is check for the presence of the Novell client. If it finds either no client or an old version, it will prompt you to install the client. Click Yes. When the Novell Client Installation screen appears, you have the choice of either a Typical or Custom Installation. I recommend the Custom Installation, as this will let you choose exactly the options you want. Choose Custom Installation and click Install. By default, the only option that will be selected on the Novell Client Installation screen will be Novell Client For Windows NT (Required). I also suggest that you select the ZENworks Application Launcher NT Service because this will allow you to run the NAL application from this server as well. Click Next to continue.
The next screen allows you to choose which protocol(s) you want to use from this server. Since the network I’m using is a pure IP network, I checked the IP Only box and clicked Next. Select the protocol combination for your network.
The next screen will ask you to select the method of authentication to use for this network. Select the NDS option and click Next. Click Finish on the next screen to start the client installation process. Review the license agreement and click Yes.
A gas gauge will appear, indicating what files are being copied and how far along the process is. When the process is complete, click OK to reboot the server. Once the server has rebooted, you should see a Novell Client For Windows NT login screen.
After logging in, the next step is the installation of the NDS Management Utilities. On the Welcome screen, click Next. Review the license agreement and click Yes. You’ll be prompted to indicate where to install the NDS utilities—on the local drive of the NT server you’re working with or on a NetWare server. I recommend the local install because it places a copy of the program on the server that you can work with without having to go across the network. Click Yes to install the utilities locally. A Destination Local screen will appear, showing a default installation path of C:\NOVELL\PUBLIC\WIN32. Unless you need to install the utilities in a different place because of drive space requirements, accept the default path and click Next.
You’ll be asked to pick the installation folder for the icons and links to the utilities being installed. Accept the default values and click Next. A review screen will appear, confirming the installation choices you’ve made. After checking to see that everything is okay, click Next.
A gas gauge will appear, showing the files being copied and how far along the process is. Once the files have been copied, an information screen will appear, indicating that the C:\NOVELL directory has been set up as a shared directory named SYS. Click OK, and a Setup Complete screen should appear. Click Finish.
Next, you must install ConsoleOne v1.2. Click the Next buttons at the bottom of the Install screens to accept the default values, and then click Finish.
Now you’ll move on to the installation of NDS for NT. When the Novell NDS 8 For NT Product Installation screen appears, click Next. Review the license agreement and click Accept. The default installation path will be C:\NOVELL\NDS. Unless you need to install the files elsewhere, click Next to accept this path and continue.
You’ll be prompted to create the path since it doesn’t exist. Click Yes. The next screen will prompt you to insert the license disk into the server on which you’re installing NDS Corporate Edition. Although the default path will appear as A:\LICENSE, you may need to click the Browse button to the right of the Path field if you get an error about the license file not being found.
Browse the directory structure until you find a file with an .ntk extension. After you click OK, your path should look something like file:///A:\LICENSE\. Click Next. You will now see an NDS install screen with two options: Install Directory Services Into An Existing NDS Tree and Create A New NDS Tree.
Choose Install Directory Services Into An Existing NDS Tree and click Next. Use the Discovery button to find and select the proper tree name (to make sure the name gets entered exactly the way the installation program is expecting it).
Next, click the Discovery button beside the input field for the fully qualified NDS name of the user with rights to the root of the tree. Once you have everything entered correctly, your screen should look like Figure A.
|Enter all of the information about your NDS tree before proceeding.|
Click Next and the information you just entered will be validated. I encountered a little problem getting the server name exactly the way the installation program wanted it. I found that although the browsing process didn’t highlight the server name correctly, if the server name was the last thing I selected before clicking OK on the browsing screen, the server name would properly appear with full NDS naming context when I returned to the previous installation screen.
Click Next. A summary screen will appear listing all the components that will be installed and the approximate amount of disk space they will use. Click Finish.
After the information has been checked one more time, another gas gauge will indicate how far along the file-copying process is. Once the files have been copied, Directory Services will be installed. Depending on the size of your tree, this may take several minutes. A good sign that everything has gone well will be an indication on your NetWare server console screen that it has made contact with your NT server. The NT server should then begin installing NICI, LDAP, and the remaining modules.
The last component you’ll install from Corporate Edition will be the one that integrates Microsoft Exchange with NDS. If your Exchange server isn’t running on either your BDC or PDC, a few additional files will be copied from the Exchange server to the server where you installed the Exchange integration piece. When the Integration wizard runs, you’ll proceed through a series of screens that will allow you to place the NDS object representing the Exchange information and then map the Exchange/NT accounts to their NetWare counterparts if the two already exist on the different systems.
In this Daily Drill Down, I’ve walked you through the basics of installing NDS Corporate Edition on your network and administering two different operating systems from a common console. While not the only solution, NDS Corporate Edition presents an option for managing both Novell and NT on the same console. If you’re stronger on the Novell side than you are on the NT side, NDS Corporate Edition can help reduce dual administration when dealing with users, groups, etc.
The authors and editors have taken care in preparation of the content contained herein but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.