This article describes a project in which we are migrating and consolidating OES NetWare to OES Linux and introducing thin clients, terminal servers, identity management, Linux desktop, virtualization and email with GroupWise.
Contents:
This document is about a virtual project for a company with five locations. The main location is called City, the other (smaller) locations are called: North, East, South and West. At every location we have one OES NetWare server for file and print services, so in total there are five OES NetWare servers.
All five OES NetWare servers will be migrated to one OES Linux server at City. NDPS printing will be migrated to iPrint on OES Linux.
As preparation, you have to be sure that everything is ready, beginning at the bottom of the OSI -layer. Make sure all of the cabling is functioning, and your network equipment is working and is documented. Think about load balancing both network interfaces on your server, and your Remote Access card, if you have them.
Make sure all services like: DNS, DHCP, SLP, NTP are working. This is critical for all installations.
Spend enough time on your design document. This is one of the most important documents.
Two new machines will be installed with OES Linux and will be inserted into the running eDirectory. One machine is for file and print services (FPS) and the other machine is for Novell GroupWise (GWM).
3.1 Installation
All servers are equipped with a RAID1 disk set for OS and a RAID5 disk set for data. The installation of OES Linux is quite simple if you have taken care of the preparation in the Preparation section.
OES Linux is installed on partition /sda. Leave the RAID5 partition called /sdb alone. This partition will be used for NSS and all NSS preparation will be done through iManager.
At the eDirectory part of the installation you will be asked if you want to install this server into an existing eDirectory. If DNS and SLP are working well, you will have no problems. If you do have problems installing eDirectory on this server, think about using DNS entries in the /etc/hosts file and add a DNS entry for the Treename. There is also the command line installation of eDirectory (ndsconfig), and don't use dollars($) in the eDirectory admin account.
You will also be asked to configure Linux User Management (LUM). You have to enable LUM for all users when using NSS. You need this when you are migrating files from OES NetWare NSS volumes to OES Linux NSS volumes to prevent file ownership, but you also need this if you want to let your eDirectory users logon to Linux. The last option is for the Linux Desktop (SLED10) running NoMachine's NX Server.
After a successful installation, run a NDS Health check as described in Novell TID 10060600.
3.2 Configuring Services
When you want to migrate services from NetWare to OES Linux, there are some services which can be easily implemented and some services you have to build from scratch.
NTP and SLP can be configured on OES Linux using the existing configuration, but for DNS and DHCP there are no migration paths, although you can export DNS (on NetWare) and import it (on Linux), but you have to do some configuration manually.
3.3 Linux User Management
LUM is the Novell way to let eDirectory users authenticate on Linux. LUM has a couple of objects in eDirectory. LUM uses PAM modules. How to setup LUM on a SLED10 is described in Novell TID 3994289.
Linux users: LUM enabled users
Linux groups: LUM enabled groups
Linux Workstation object: LUM enabled groups use this workstation for LUM
Linux Config object: Posix information like, homedirectory, uid and gid
3.4 Novell Storage Services
There are two ways to configure NSS: iManager and the command line tool nssmu.
First you have to configure NSS with Yast. You will be asked to enter your LUM configuration objects and LDAP configuration to login to eDirectory and set the proper information for LUM and SMS.
Novell has an excellent tool for migrating data and printers from NetWare to OES Linux. It is called the Novell Server and Consolidation Utility (SCU). You can migrate data and printers from NetWare to Linux through a Windows machine. The Windows machine must have the latest Novell Client and iPrint client.
4.1 Preparation
If you are migrating from NetWare (traditional or NSS) to OES Linux you must have NFS name space loaded on the NetWare volumes:
load nfs.nam
ADD NAME SPACE nfs TO VOLUME datatrad
ADD NAME SPACE nfs TO VOLUME datanss
Load the latest SMS (smdr.nlm) and TSA (tsa500.nlm or tsa600.nlm or tsafs.nlm) version on the NetWare server.
Check if these modules are running on the OES linux server:
/etc/init.d/novell-smdrd start
/opt/novell/sms/bin/smsconfig -l tsafs
During the verification stage, SCU is checking if on the NetWare and Linux server the minimum versions of SMS are running, and if not they will be installed. You only have to unpack and start them.
NetWare
'SMDR.NLM' running on server 'fsnw51' is not the correct version, it is '6.54.1'. This utility requires version '6.54.3' or newer to proceed. This utility should have already copied the correct version to the server. You need to manually unload and reload this NLM on the server before proceeding.
'TSAFS.NLM' running on server 'fsnw51' is not the correct version, it is '6.50.11'. This utility requires version '6.51.1' or newer to proceed. This utility should have already copied the correct version to the server. You need to manually unload and reload this NLM on the server before proceeding.
OES Linux
The installed SMS RPM must be version 1.1.4-6 or newer. For your convenience, the required SMS RPM has already been copied to this server.
You can update the installed SMS RPM with the command:
rpm -Uvh /usr/novell/sys/scu/novell-sms-i586.rpm
You will then need to restart SMS with the command:
rcnovell-smdrd restart
4.2 Server Consolidation and Migration Toolkit
When you start SCU, you will be asked for your source platform, NetWare OES or Windows NT.
After selecting NetWare OES, you select Consolidate and Copy Data and Printing Between Servers.
Create a new project and give it a name. It will be saved as a .mdb file.
In this example I have two Trees. A LOP-TREE with on NetWare 5.1 server (fsnw51) in it and a OES-TREE with one OES Linux (oeslinux) server in it. I'm going to migrate data from the NetWare server to the Linux server.
First I must have a connection to both trees.
You'll get a warning if you don't have a iPrint client installed, but migrating NDPS printers to iPrint printers on OES Linux is as easy as migrating data.
Drag and drop volumes, directories and files from traditional and NSS volumes to any destination volume on your OES Linux server.
Start the migration with:
Project, Verify and copy data.
Then you get a lot of questions like:
After the data migration you will get an error and success log. This toolkit is well documented on the Novell documentation site.
4.3 Scheduled Tasks
You can copy and synchronize data an a regular base (scheduled tasks). Create a scheduled task with these parameters:
"C:\Program Files\Novell Server Consolidation and Migration Toolkit\MigWin32\FC.exe"
"C:\Documents and Settings\Administrator\My Documents\This is a new SCU project.mdb" y <password> <password>
Unfortunately you have to put both passwords of the Source and Destination tree in the parameters in clear text, but you can run it every weekend.
4.4 Login Scripts
Don't forget to change your server names in your login scripts when you have migrated to your OES Linux server. All login scripts will work on OES Linux.
Support
Documentation
Learning Services
Partner Programs