NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: NetWare Migration Utility
DOCUMENT ID: TID000191
DOCUMENT REVISION: B
DATE: 20SEP93
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: MIGRAT.EXE
NOVELL PRODUCT and VERSION:
NetWare 2.2
NetWare 3.11
NetWare 4.0
ABSTRACT:
The MIGRAT.EXE file contains tools to simplify the upgrade from NetWare
v2.x to NetWare 3.11 as well as NetWare 4.0 upgrade.
_________________________________________________________________
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.
NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.
HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.
_________________________________________________________________
Self-Extracting File Name: MIGRAT.EXE Revision: B
Files Included Size Date Time
\
ATW909.TXT (This File)
MIGRATE.EXP 822 07-15-93 3:06p
LMINFO.MSG 4974 08-20-93 9:15a
MIGRATE.EXE 713401 08-20-93 11:57a
BRINFO.MSG 8135 07-30-93 4:37p
BWINFO.MSG 11227 08-02-93 8:33a
MIGRATE.MSG 15410 08-20-93 10:01a
PCLPINFO.MSG 2562 07-30-93 4:53p
MNCOPY.MSG 5085 07-30-93 4:39p
MIGRATE.HEP 32894 08-20-93 10:02a
LSINFO.MSG 5212 08-20-93 9:24a
TEXTUTIL.MSG 29466 01-27-93 6:56p
TEXTUTIL.HEP 11735 10-26-92 4:06p
TEXTUTIL.IDX 9170 12-10-90 1:37p
_RUN.OVL 2815 01-19-93 10:33a
IBM_RUN.OVL 2815 01-19-93 10:33a
CMPQ_RUN.OVL 2815 01-19-93 10:33a
CPYRIGHT.DAT 287 06-29-90 10:54a
IBMMIG.DOC 159674 10-26-90 8:59a
LS10EXPO.EXE 68232 12-10-90 3:12p
LS10MU.MSG 2196 12-07-90 11:17a
LS10MU.FMT 5962 03-06-90 3:56p
PCLP13MU.MSG 2490 03-01-90 5:41p
PCLP13MU.FMT 4004 03-08-90 2:31p
PCLPEXPO.EXE 41176 03-08-90 2:31p
Upgrade Using Migration
-----------------------
Overview
The NetWare Migration Utility allows you to upgrade your servers from
NetWare 2.1x, 3.x, or another network operating system (LAN Server, PCLP or
LAN Manager) to 3.x or 4.x using two methods:
o Across-the-wire, where you move your network information from a NetWare
2.1x or 3.x server to a 3.x or 4.x server that is on the same network.
o Same-server, where you change your NetWare 2.x or 3.x server to a 3.x or
4.x server.
The source and destination platforms supported by the migration utility are
listed below.
Source LANs Destination LANs
--------------------------------------------------
NetWare 2.x NetWare 3.x
NetWare 3.x NetWare 4.x
IBM PCLP 1.3 Extended Services
IBM LAN Server 1.0
IBM LAN Server 1.1
IBM LAN Server 1.2
IBM LAN Server 1.3
Microsoft LAN Manager 2.0
What a Migration Does
In across-the-wire migration, files are migrated from a source server
across the network to the destination server.
Selected bindery information is migrated to a working directory on the
local hard drive, translated to NetWare v4.x format, and then migrated to
the destination server, through bindery emulation. Bindery emulation
occurs when NetWare Directory Services (NDS) - emulates a flat structure
for the objects within an Organization or Organizational Unit container
object.
When you use the migration utility, it is important to have only bindery
connections, because the utility depends on bindery emulation to work. To
ensure only bindery connections, log in to the server using the /b option.
For example, you would type
LOGIN SRV1\SUPERVISOR /B
Or use the migration utility to log in to the destination server.
A bindery is the database in NetWare versions 2.x and 3.x that contains
definitions for entities such as users, groups, workgroups, NetWare
servers, and print servers. For more information, see -Bindery and -Bindery
emulation in Concepts.
The across-the-wire method allows you to preserve your user environment
(users, groups, and their trustee assignments) as well as the default
account restrictions, accounting methods, and print queues and print
servers by copying the bindery to the NetWare 4.x Directory Database.
In NetWare v4.x, the Directory database replaces the bindery, which served
as the system database for previous releases of NetWare. While the bindery
supports the operation of a single NetWare server, NetWare Directory
Services supports an entire network of servers. NetWare Directory Services
is a single, logical database: all users, applications, and servers go to
one database for information. For more information on NDS, see
-Understanding NetWare Directory Services in Getting Started with NetWare
v4.0.
NOTE: If a power failure occurs, or if the migration utility stops while
you are running it, restart the utility.
When you restart the utility after a power failure, the entire migration
process is repeated. Anything that was successfully migrated previously
will exist on the destination server.
How Data Is Migrated Across the Wire
------------------------------------
o The migration utility leaves the source server intact and only copies
information to the destination 3.x or 4.x server.
o The system login script is not migrated, but user login scripts are.
Examine each user login script after migration and make
corrections if the server name or path names have changed.
Migrating Files
---------------
o NetWare 2.x or v3.x system files are not migrated.
o Any file on a source server that has the same name as one that exists on
the destination server is not copied to the destination server.
An error message appears on the screen during the migration, and is also
written to the migration report, to let you know that a file by that name
already exists on the destination server.
If needed, either rename the file and copy it to the destination server or
manually copy it over the old file after migration.
Migrating Directories
---------------------
o If a directory is being migrated that has the same name and path as a
directory that already exists on the NetWare 3.x or 4.x server, the files
from both directories are merged under the destination directory name.
o The directory structure and files are migrated and become a part of the
3.x or 4.x file system. If necessary, modify the organization on the
destination server after all source servers are migrated.
Migrating Users
---------------
Users on the source server are created as new users on the destination
server.
Account restrictions and user designations for existing users are copied.
Users with the same username are merged; that is, their user designations
are added together, with the exception of user restrictions which are left
untouched.
The table below shows the information you can migrate using the NetWare
Migration utility.
Information that can be migrated using the NetWare Migration utility
----------------------------------------------------------------
Category to be migrated Description
----------------------------------------------------------------
All Information Migrates all information listed
in this table.
Data Files Migrates all data files and
their DOS and NetWare attributes
for files and directories to the
corresponding 3.x or 4.x
attributes.
For details on what the
corresponding attributes are,
see "Migrating File Attributes."
Data files are not migrated for
same-server migration.
Trustee Assignments Migrates rights assigned to
users and groups for directories
and files to corresponding 3.x
or 4.x rights.
If you select this category, you
should also select "Users,"
"Goups," and "Data Files" if the
users and data files do not
already exist on the destination
server.
If you migrate "Trustee
Assignments" and the
corresponding users and groups
do not exist on the destination
server, or the directories do
not exist, a series of error
messages appears.
For details on what the
corresponding rights are, see
"Migrating Directory
Attributes."
Users Migrates the following, unless
they already exist on the
destination server:
o Users
o User login scripts for both
DOS and OS/2 (LOGIN.BAK is
not migrated)
User Restrictions Migrates account restrictions,
station restrictions (not
migrated from LAN Server or LAN
Manager), and time restrictions.
If a user exists on the
destination server, his or her
restrictions are not
overwritten.
If you select this category, you
must also select "Users."
If a user with a corresponding
set of restrictions doesn't
exist on the destination server,
then the restrictions set on the
source server are migrated to
the destination server and are
not overwritten or merged by any
subsequently migrated source
servers.
Volume and disk restrictions for
users do not get migrated
because of differences in
NetWare 2.x and 3.x or 4.x. In
2.x, the restrictions were
server-wide, whereas in 3.x or
4.x the restrictions are
volume-specific.
Groups Migrates the Group's members and
assigned group trustee rights
for directories and files.
If multiple source servers are
migrated, then groups from the
servers are merged on the
destination server.
Default Account Restrictions Migrates default account
restrictions. Default account
restrictions on the destination
server are overwritten by any
source server that also has
default account restrictions.
The set of default restrictions
includes
Account balance and low limit
Account expiration date
Concurrent connections limit
Grace logins
Home directory for users
Intruder detection
Password minimum length
Periodic password interval
Time restrictions
Accounting Information Migrates the accounting charge
method chosen to charge for
services (blocks read, blocks
written, connect time, disk
storage, service requests).
Migrates account servers.
Print Queues and Print Servers LAN Server and LAN Manager only
migrate print queues. NetWare
migrates the following:
Print queues
Print queue operators and users
Print queue servers
Print queue status
Print servers
Print server operators and users
Print server control files
The table below describes LAN Server and LAN Manager components that do not
get migrated.
LAN Server and LAN Manager components that are not migrated
-----------------------------------------------------------
LS/LM component Explanation NetWare equivalent
ALERTER Notifies the None, but NetWare
administrator keeps track
of defined events. of many of these
events.
AT Gives Execute None
command at a set
time.
AUTO LOG OFF Shuts the system None
down after extended
inactivity.
External resources These don't apply None
to NetWare.
MACHINE ID Unique workstation name. Use network
board ID.
NETRUN Allows you to run programs None
at the server.
REPLICATOR Periodically duplicates None
selected files.
RIPL Remote Initial Remote Reset
Program Load. or Remote Boot
Station Defines which machine ID Must be set up
restrictions can be used by a username using NetWare
to log in to the LAN and LAN card
Server domain. ID.
How Rights and Attributes are Migrated
--------------------------------------
In NetWare 2.x, rights are assigned only at the directory level. In NetWare
3.x or 4.x, rights are assigned at the file and directory levels.
When you use the across-the-wire migration, all NetWare 2.x rights and
attributes are translated into the 3.x or 4.x format. The Maximum Rights
Mask is replaced with an Inherited Rights Mask, which allows rights to flow
down the directory structure.
The tables under -Migrating Rights and Attributes list the corresponding
NetWare3.x or 4.x rights and attributes. There is no change in directory
and file rights in any v3.x version.
Migrating Directory and File Rights
-----------------------------------
In NetWare 3.x or 4.x, rights are granted for a specific directory or file
by trustee assignments. A user with a trustee assignment to a directory or
file is a trustee of that directory or file.
If you are migrating from LAN Server or LAN Manager, permissions (rights)
do not flow down, but are limited to the directory where they are set.
After the migration to NetWare 3.x or 4.x, rights do flow down the
directory structure.
Also, LAN Server universal rights are not migrated. These rights are
similar to NetWare rights given to group EVERYONE.
Password Migration
------------------
Passwords are not migrated. The migration utility allows you to either
o Assign passwords that are generated randomly for all migrated users.
o Allow users to log in to the new system without a password.
Passwords generated randomly are stored in a file called NEW.PWD in
SYS:SYSTEM on the NetWare 3.x or 4.x destination server and can only be
accessed by the user SUPERVISOR.
Strategies for Merging Source Servers
-------------------------------------
Choose one of several strategies to help you minimize the amount of time
you spend customizing your 3.x or 4.x server after you migrate several
servers to it.
The table titled, -Information that can be migrated using the NetWare
Migration utility, shows the types and descriptions of information you can
choose to migrate from a source server.
Read through these categories and their descriptions; then see - Setting Up
Your Destination Server.
Setting Up Your Destination Server
----------------------------------
To Then
---------------------------------------------------------------
Set up default account Set up the Default Account
restrictions on the Balance/Restrictions on the first
destination server. source server and include that
category in the information to be
migrated.
On subsequent source servers that
you migrate to the same
destination server, do not migrate
that category.
Set up uniform user On the first source server, set up
restrictions on the Default Account Balances/
destination server. Restrictions with the values you
want on the destination server.
Choose "Users" and "Default
Account Balances/Restrictions" as
categories to migrate, but do not
choose "User Restrictions."
On subsequent source servers, do
not choose "User Restrictions" or
"Default Account
Balances/Restrictions."
Preserve each user's Choose "User Restrictions" for
individual user restrictions. each source server.
Merge users and groups Choose "Groups" and "Users" on all
from several source servers. source servers.
The corresponding users on the
destination server are added to
the appropriate groups.
Set up print queues Choose "Print Queues" and "Print
and print servers. and Servers" on source servers.
In NetWare 3.x or 4.x, multiple
printers can be serviced by each
queue and multiple queues can
service the same printer.
Necessary Resources
-------------------
o A working copy of the NetWare diskettes.
o (If migrating from CD ROM) a CD ROM reader.
o The NetWare Migration Utility files located on the Migration diskette.
o A DOS workstation with at least 640 KB of memory and 5 MB of free disk
space on either a hard drive or another network drive. Be sure the
following line is in the CONFIG.SYS file: files=20. Be sure the following
line is in the NET.CFG file: ipx retry count=60.
o NetWare 3.x or 4.x installed on a server with a 386 or higher
processor.
o A network with a DOS workstation (using NETx.COM 3.02 or later), a
NetWare 2.x or 3.x source server (or LAN Server, PCLP or LAN Manager), and
a 3.x or 4.x destination server attached.
o A backup device for data storage Prerequisites
o For across-the-wire migration, set up the NetWare 3.x or 4.x destination
server.
Create the volumes you want to migrate data to. You cannot create volumes
from the migration utility.
You may want to create a directory to migrate the NetWare 2.x or 3.x SYS:
volume to so that you can remove unnecessary 2.x or 3.x files more easily.
NOTE: Since two servers on the same network cannot share the same name, the
destination server must have a unique name.
LAN SERVER NOTE: If you are migrating from LAN Server, add -/API /NMS:2
/NVS:2 to the DOSLAN.INI file. For the order of parameters, see your LAN
Server documentation.
o Make sure that all users (this includes print servers), except
SUPERVISOR, are logged out of the source and destination servers and that
all files (except bindery files) are closed during migration.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, you must
either be the domain administrator or have administrative privileges in the
domain.
o Remove unnecessary files.
Decide if you want to migrate .BAK or .LST files, or any other temporary
files. You may want to consolidate some files and directories.
Value Added Processes (VAPs) that are in a directory that you migrate are
copied to the destination NetWare 3.x or 4.x server, but VAPs are not
compatible with 3.x or 4.x, so you may want to delete them before you start
the migration.
IMPORTANT: The following NetWare 2.1x files are not compatible with NetWare
3.x or 4.x and should be deleted.
LARCHIVE.EXE
LRESTORE.EXE
MACBACK.EXE
NARCHIVE.EXE
NRESTORE.EXE
If these files are only in SYS:PUBLIC or SYS:SYSTEM, the migration utility
blocks them from being transferred. If copies of these files are in other
directories, they are transferred.
IMPORTANT: The following NetWare 2.0a files are not compatible with NetWare
3.x or 4.x. Delete these files also:
ENDSPOOL.EXE
Q.EXE
QUEUE.EXE
SPOOL.EXE
o Prepare Macintosh file support.
To store Macintosh files and folders on the new NetWare 3.x or 4.x server,
add name space support to any volume that needs to store files with long
names. For more information, see -Add Name Space in Utilities Reference.
Install NetWare for Macintosh (a separate Novell product) to provide
native-mode support for Macintosh workstations that connect to the 3.x or
4.x server.
o Rename DOS files and directories that have long names.
NetWare 2.2 and earlier lets you give directories 14character names.
NetWare 3.x or 4.x allows only DOS naming conventions for DOS directories.
DOS limits directory names to 8 characters with a 3-character extension.
(Macintosh and OS/2 files can still follow their respective naming
conventions.)
IMPORTANT: Only directories and files that conform to DOS naming
conventions (8.3) are migrated.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, OS/2
extended attributes and long names are not migrated. Files that use
extended attributes or long names will be truncated. All files must conform
to DOS 8.3 naming conventions.
o User login scripts are migrated from SYS:MAIL to the user's new mail
directory on the destination server.
Other files left in the mail directories are not copied to the destination
mail directory.
o Prepare the workstation.
Make sure the CONFIG.SYS file includes the following line: files=20. If you
add the line to the CONFIG.SYS file, save the file and then reboot the
workstation. Make sure the NET.CFG file includes the following: ipx retry
count=60. Load LAN drivers on the DOS workstation and run NETX.COM.
In some cases, the setting may already be established or set to a higher
value.
In such cases, leave the setting at its present value.
o If you are running DR DOS' memory manager (EMM386.SYS), use the NetWare
shell (NETX, XMSNETX, etc.) instead of the DOS Requester. Running
EMM386.SYS and the DOS Requester may result in memory conflicts.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, use
Novell's ODINSUP or LANSUP protocol stack. These products allow for loading
dual requesters on DOS clients to allow access to both LAN Server or LAN
Manager and NetWare server resources.
For more information on ODINSUP, see NetWare Application Notes articles
entitled -ODINSUP Interoperability Configurations for DOS Workstations,
(February 1993) or -NetWare and Windows for Workgroups Integration, (March
1993).
Administrative privileges are required from the LAN Server or LAN Manager
side.
o Modify the subdirectory depth to 25.
NetWare 3.x or 4.x sets the default for subdirectory depth to 25 levels,
and the migration utility does not copy subdirectories deeper than 25.
If the source server has subdirectories deeper than 25, modify the
subdirectory structure so that the subdirectories aren't so deep. Do this
before you start the migration.
o Plan for space on the destination server.
If you merge two or more NetWare 2.x or 3.x servers onto the same NetWare
3.x or 4.x server, plan for extra disk space for volume SYS:. SYS: requires
at least 6 MB of disk space to accommodate additional users and their login
scripts.
o Obtain NLMs to replace third-party VAPs that are running on the 2.x
server.
VAPs do not run on NetWare 3.x or 4.x. To find out about NLMs that are
available to replace your third-party VAPs, contact your vendor or call
Novell product information at 1-800-NETWARE.
o Run BINDFIX on the source server.
BINDFIX can delete mail subdirectories and trustee rights of all users who
no longer exist on the source server.
For more information on -BINDFIX, see Utilities Reference.
o When setting up interoperability between NetWare and LAN Server or LAN
Manager, use NETX.COM.
Procedure
---------
1. Create a directory called MIGRATE on your hard drive.
If you are migrating using a CD ROM, follow Steps 1 through 6
under-Installing from CD-ROM on page19 of your Installation and Upgrade
manual.
If you are migrating using a network directory, follow Steps 1 through 4
under -Installing from Network Directory on page20 of your Installation and
Upgrade manual.
NOTE: If you are using a network drive instead of a hard drive, you must
have Create, Read, Write, and File Scan rights in this directory.
WARNING: Do not try to run from a network drive that has been mapped as a
fake root.
2. Insert the Migration diskette into drive A: and type
copy a:*.* c:\migrate <Enter>
The following files are copied:
Filename Contents
----------------------------------------------------------------
BRINFO.MSG Message information while the
utility is reading the bindery
import data.
BWINFO.MSG Message information while the
utility is writing the bindery
export data.
IBM_RUN.OVL Replaces the IBM$RUN.OVL file
used in 2.2 and 3.11.
LSINFO.MSG Message information while the
utility is reading LAN Server
import data.
LMINFO.MSG Message information while the
utility is reading LAN Manager
import data.
MIGRATE.EXE Executable code for the
migration utility.
MIGRATE.EXP List of elements from the source
network operating system that may not
translate/transfer to the destination
server.
MIGRATE.HEP Help screens for the migration
utility.
MIGRATE.MSG Message information for the menus in
the utility.
MNCOPY.MSG Message information during the
copying of files.
PCLPINFO.MSG Message information while the utility
is reading PCLP import data.
_RUN.OVL Replaces the $RUN.OVL file in 2.2 and
3.11.
CPQ_RUN.OVL Replaces the CPQ$RUN.OVL file in 2.2
and 3.11.
TEXTTUTIL.HEP Replaces SYS$HELP.DAT.
TEXTUTIL.IDX Replaces SYS$ERR.DAT.
TEXTUTIL.MSG Replaces SYS$MSG.DAT.
PCLP13MU.FMT Used to migrate from PCLP.
PCLP13MU.MSG Used to migrate from PCLP.
PCLPEXPO.EXE Used to migrate from PCLP.
LS10MU.FMT Used to migrate from LAN Server v1.0.
LS10MU.MSG Used to migrate from LAN Server v1.0.
LS10EXPO.EXE Used to migrate from LAN Server v1.0.
IBMMIG.DOC IBM-specific utility file
CPYRIGHT.DAT IBM-specific utility file
3. Complete the migration by following the procedures under-Using the
Migration Utility.
Using the Migration Utility
---------------------------
The NetWare Migration utility allows you select specific types of
information to migrate.
For example, if you don't want to overwrite default account restrictions,
you do not have to migrate the account restrictions from any source
servers. For more information on how to customize the destination server,
see -Setting Up Your Destination Server on page 215.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, you must
be logged in to the domain server you want to migrate from.
Starting the Across-the-Wire Migration
--------------------------------------
Procedure
You should have the necessary resources and have completed the prerequisite
tasks.
1. Start the migration utility by changing to the directory that
contains the migration utility files and typing
MIGRATE <Enter>
The -Select the Type of Migration menu appears.
2. From the -Select the Type of Migration menu, choose -
Across-the-Wire Migration.
3. From the -Select the source LAN type menu, choose a source LAN type
(2.x, 3.x, LAN Server, PCLP or LAN Manager).
4. From the -Select the destination LAN type menu, choose a
destination LAN type (3.x or 4.x).
When selecting a source and destination, the migration utility does version
checking according to the source type and destination type you selected.
5. Under Step 1 on the configuration form, press the Down-arrow key to
accept the default working directory or press <Enter> to specify another
working directory.
The working directory is where the bindery information and migration
reports are stored. Data files are not stored here. You need 5 MB of free
disk space in this directory.
Usually, the working directory is located on the hard disk drive of the
workstation, but you can also put it on a network drive.
NOTE: If you are using a network drive instead of a hard drive, you must
have Create, Read, Write, and File Scan rights in this directory.
If this directory doesn't exist, the migration utility creates it for you
on your hard disk.
Follow the Quick Help to specify a different working directory.
6. Under Step 1 on the configuration form, press <Enter> to select an
error/warning action.
Error/Warning Action Description
----------------------------------------------------------------
Pause after warnings and Choose this option if you want
errors. the utility to stop after each
warning and error and prompt you
to continue with the migration.
Each time an error is reported
and you are prompted, you can
choose to discontinue the
prompting.
Do not pause after warnings Choose this option if you do not
and errors. want to be prompted after each
warning and error.
IMPORTANT: All errors are listed in the report file regardless of the
option you select.
7. Under Step 2 on the configuration form, press <Enter> to display a
list of source servers.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, the screen
shows the domain obtained from the DOSLAN.INI file. Edit this field if the
domain you are logged into is not the same as the one listed in the
DOSLAN.INI file.
8. Choose the source server you want to migrate from.
This selection must match the source type you specified in Step 3.
If the NetWare source server you want to select is not shown, press <Ins>
to see a list of available servers you can log in to.
NOTE: When migrating multiple source servers, only one source server can be
migrated at a time.
9. Under Step 2 on the configuration form, press <Enter> to display
categories of information you want to migrate.
S/LM NOTE: If you are migrating from LAN Server, PCLP or LAN Manager, you
are limited to the following categories to migrate:
Access Control profiles
All information
Data files
Groups
Print queues
Users
10. Using <F5>, mark the information you want to migrate.
Mark as many of the categories as necessary.
Follow the Quick Help for details on how to select information.
IMPORTANT: If you select -All Information, all categories are migrated.
11. Under Step 2 on the configuration form, press <Enter> again to
display a list of source volumes on the source server you want to migrate
data from.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, source
drives are listed.
12. Mark the volumes using <F5>, and then press <Enter>.
Mark source volumes to migrate only if you are migrating data files, or
trustee assignments on those volumes.
If you are only migrating one or more of the following categories, you do
not need to select a source volume:
Accounting Information
Default Account Balance/Restrictions
Groups
Print Queues
User Restrictions
Users
You must select a source volume (or a source drive in LAN Server or LAN
Manager) to migrate if you select any of the following categories to
migrate:
All Information
Data Files
Trustee Assignments (or Access Control permissions in LAN Server
or LAN Manager)
13. Under Step 3 on the configuration form, press <Enter> to display a
list of NetWare servers.
14. Choose the NetWare 3.x or 4.x destination server you want to
migrate the source server to.
This selection must match the destination type you specified in Step 4.
If the destination server you want to select is not shown, press <Ins> to
see a list of available servers that you can log in to.
15. Under Step 3 on the configuration form, select a volume (or source
drive in LAN Server or LAN Manager) and press <Enter> to specify the
destination volume and directory on the NetWare 3.x or 4.x server.
Destination volumes that match the source volumes are displayed as the
default.
16. Press <Ins> to see a list of available volumes and directories on
the NetWare 3.x or 4.x server.
If you specify a directory that does not exist on the 3.x or 4.x server,
you are prompted to create it. Volumes must already be created on the
destination server before you can migrate data to them.
The volume organization, as well as the directory structure, is migrated.
You can modify the organization on the destination server after all source
servers have been migrated.
17. Press <Enter> when you complete the destination path of the source
volume.
18. Continue to specify destination paths if you have multiple source
volumes.
19. Press <F10> when you finish filling out the -Volumes destination
field, and continue with Step 20 to assign user passwords.
LAN MANAGER NOTE: If you are migrating from LAN Manager, password lengths
are global. For example, if a user has a -password not required flag set on
the LAN Manager side, he will have no password on the destination server.
If a password is required and the length of the password is zero (0), the
migration utility assigns the destination default password length.
20. Under Step 3 on the configuration form, press <Enter> to choose a
password option.
21. To proceed with the migration, press <F10> to display the -Select a
Migration Action menu.
22. Choose a -Migration Action option and then press <Enter>.
If you select -Start the Migration, all information about the migration is
displayed on the screen and entered into a report file, which you can
review later.
23. (Conditional) If errors occur during migration and you chose to be
prompted after errors and warnings, you receive the following error message
and must answer the question.
A migration error has occurred and is displayed in the migration log above.
Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):
24. When the migration is complete, the following message appears:
Migration from the source server to the destination
server is complete.
Press <Enter> to continue.
25. Press <Enter> to view the -Select a Migration Action menu.
26. (Optional) From the -Select a Migration Action menu, select -View
Migration Reports and view the migration report.
26a. Select the report for the migration you completed and press
<Enter>.
The reports reside in the working directory that you specified earlier.
Use the report to help you complete and customize definitions, attributes,
and access privileges on the 3.x or 4.x server.
If you find errors on your destination server after the migration, locate
them in the migration report file and determine what actions to take on the
destination server to correct the errors.
The report file is an ASCII text file that consists of the following:
o Summary information of the bindery import phase (migrating bindery data
from the source server to the working directory).
o Summary information of the bindery export phase (migrating bindery data
from the working directory to the destination server).
o Listing of each item in each category that was read from the source
server.
o Listing of each item in each category that was written to or created on
the destination server.
o The number of errors that occurred during the migration.
26b. To exit the report, press <Esc> once.
26c. To return to the -Select a Migration Action menu, press <Esc>
again.
27. From the -Select a Migration Action menu, choose -Exit (return to
DOS).
28. Read -What to Do After the Migration.
What to Do After the Migration
------------------------------
After the migration is complete, check the NetWare 3.x or 4.x server and do
the following:
o Update references to the server in user login scripts. Although user
login scripts are migrated, they are not modified, and server names and
directory paths are not changed to match your new environment.
o Run third-party applications. You may have to reinstall them to work
properly under NetWare 3.x or 4.x. You may also need to enter new paths in
the setup files for third-party applications.
o Check applications to see if they run properly. The following conditions
require you to reinstall an application:
o The application has an .EXE file that will not migrate.
o The application is path-specific and you changed the path structure
during migration.
Some DOS applications don't work when installed on volumes that have more
than 32 MB of disk space. Some of these applications can be made to work by
doing the following:
o Restrict the application's disk space on the destination server with
DSPACE in the application's directory.
o Make the directory a fake root with MAP (see -Fake Root in Concepts).
o Examine the files in merged directories and reorganize them if
necessary. Any directories that were merged may contain unrelated files.
o Update migrated print queues and print servers.
o Check user restrictions and accounting charge rates to make sure your
system is configured the way you want it.
o If you chose to assign random passwords, you may want to print the
NEW.PWD file and distribute the password information to your users. The
users should change their passwords immediately.
The report, an ASCII text file, shows passwords sorted by date. If users
were migrated from more than one server, the current password is the last
one listed on the report.
o Check print servers and print queues to make sure they are configured
correctly. Also make sure that the physical printer connection is secure.
Use the NetWare print utilities to accomplish these tasks.
LS/LM NOTE: Also, if you are migrating from LAN Server or LAN Manager, set
up print servers and print queues.
Same-Server Migration
---------------------
Use the same-server migration to update a server that will be installed on
the same hardware as the old server, allowing you to change your NetWare
2.x server to a NetWare 3.x or 4.x server
Necessary Resources
o The NetWare Migration Utility files located on the Migration diskette.
o A DOS workstation with at least 640 KB of memory and 5 MB of free disk
space on either a hard drive or another network drive.
Be sure the following line is in the CONFIG.SYS file: files=20. Be sure the
following line is in the NET.CFG file: ipx retry count=60.
o A NetWare 2.1x or 3.x server with a 386 or higher processor.
o A network with a DOS workstation (using NETx.COM 3.02 or later) and a
NetWare 2.x source server (or LAN Server, PCLP or LAN Manager).
o A backup device for data storage.
Prerequisites
o Back up the data from your source server.
Use your regular backup utility to back up your current NetWare server at
least twice to ensure a good copy.
The NetWare same-server migration procedure destroys all data on your hard
disk. Back up trustees and bindery information. The migration utility
converts the trustees and bindery information to NetWare 3.x or 4.x format.
o Make sure that all users, except SUPERVISOR, are logged out of the
source and destination servers (this includes print servers) and that all
files (except bindery files) are closed during migration.
If you are migrating from LAN Server or LAN Manager, you must either be the
domain administrator or have administrative privileges in the domain.
o Remove unnecessary files.
Decide if you want to migrate .BAK or .LST files, or any other temporary
files. You may want to consolidate some files and directories.
Value Added Processes (VAPs) that are in a directory that you migrate are
copied to the destination 3.x or 4.x server, but VAPs are not compatible
with NetWare 3.x or 4.x, so you may want to delete them before you start
the migration.
The following NetWare 2.1x files are not compatible with NetWare 3.x or
4.x. Delete the following files:
LARCHIVE.EXE
LRESTORE.EXE
MACBACK.EXE
NARCHIVE.EXE
NRESTORE.EXE
If these files are only in SYS:PUBLIC or SYS:SYSTEM, the migration utility
blocks them from being transferred. If copies of these files are in other
directories, they are transferred.
The following NetWare 2.0a files are not compatible with NetWare 3.x or
4.x. Delete these files also:
ENDSPOOL.EXE
Q.EXE
QUEUE.EXE
SPOOL.EXE
o Rename DOS files and directories that have long names.
Although NetWare 2.2 and earlier lets you give directories 14character
names, NetWare 3.x or 4.x allows only DOS naming conventions for DOS
directories and files.
DOS limits directory names to 8 characters with a 3-character extension.
(Macintosh files can still follow Macintosh naming conventions.) Only
files that conform to DOS naming conventions (8.3) are migrated.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, OS/2
extended attributes and long names are not migrated. Files that use
extended attributes or long names can be truncated. All files must conform
to DOS 8.3 naming conventions.
o User login scripts are migrated from SYS:MAIL to the user's new mail
directory on the destination server.
Other files left in the mail directories are not copied to the destination
mail directory.
o Prepare the workstation.
Make sure the CONFIG.SYS file includes the following line: files=20. If you
had to add the line to the CONFIG.SYS file, save the file and then reboot
the workstation. Make sure the NET.CFG file includes the following line:
ipx retry count=60. Load your LAN drivers on the DOS workstation and run
NETX.COM. In some cases, the setting may already be established or set to
a higher value, in such cases, leave the setting at its present value.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, use
Novell's ODINSUP or LANSUP protocol stack. These products allow for loading
dual requesters on DOS clients to allow access to both LAN Server or LAN
Manager and NetWare server resources.
Administrative privileges are required from the LAN Server or LAN Manager
side.
o Obtain NLMs to replace third-party VAPs running on the 2.x server.
VAPs do not run on a NetWare 3.x or 4.x system. To find out about NLMs that
are available to replace your third-party VAPs, contact your vendor or call
Novell product information at 1-800-NETWARE.
o Run BINDFIX on the source server.
BINDFIX can delete mail subdirectories and trustee rights of all users who
no longer exist on the source server.
For more information on BINDFIX, see Utilities Reference.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, you must
be logged in to the domain server you want to migrate from.
Using the Same-Server Migration Method
--------------------------------------
Procedure
1. Create a directory called MIGRATE on your hard drive.
NOTE: If you are using a network drive instead of a hard drive, you must
have Create, Read, and Write rights in this directory.
WARNING: Do not try to run from a network drive that has been mapped as a
fake root.
2. Insert the Migration diskette into drive A: and type
copy a:*.* c:\migrate <Enter>
The following files are copied:
Filename Contents
----------------------------------------------------------------
BRINFO.MSG Message information while the utility is
reading the bindery import data.
BWINFO.MSG Message information while the utility is
writing the bindery export data.
IBM_RUN.OVL Replaces a file of the same name used in
2.2 and 3.11.
LSINFO.MSG Message information while the utility is
reading LAN Server import data.
LMINFO.MSG Message information while the utility is
reading LAN Manager import data.
MIGRATE.EXE Executable code for the migration utility.
MIGRATE.EXP List of elements from the source network
operating system that may not
translate/transfer to the destination
server.
MIGRATE.HEP Help screens for the migration utility.
EMIGRATE.MSG Message information for the menus in the
utility.
MNCOPY.MSG Message information during the copying of
files.
PCLPINFO.MSG Message information while the utility is
reading PCLP import data.
_RUN.OVL Replaces a file of the same name used in
2.2 and 3.11.
CPQ_RUN.OVL Replaces a file of the same name used in
2.2 and 3.11.
TEXTTUTIL.HEP Replaces SYS$HELP.DAT.
TEXTUTIL.IDX Replaces SYS$ERR.DAT.
TEXTUTIL.MSG Replaces SYS$MSG.DAT.
PCLP13MU.FMT Used to migrate from PCLP.
PCLP13MU.MSG Used to migrate from PCLP.
PCLPEXPO.EXE Used to migrate from PCLP.
LS10MU.FMT Used to migrate from LAN Server v1.0.
LS10MU.MSG Used to migrate from LAN Server v1.0.
LS10EXPO.EXE Used to migrate from LAN Server v1.0.
IBMMIG.DOC IBM-specific utility file.
CPYRIGHT.DAT IBM-specific utility file.
Start the Same-Server Migration
-------------------------------
Procedure
1. Have the necessary resources and complete the prerequisite tasks.
2. Start the migration utility by moving to the directory that
contains the migration utility files and typing
MIGRATE <Enter>
The -Select the Type of Migration menu appears.
3. From the -Select the Type of Migration menu, choose - Same-Server
migration.
The same-server option allows you to stop the utility after you migrate the
bindery information to the working directory so that you can install
NetWare 3.x or 4.x.
4. From the -Select the source LAN type menu, choose a source LAN type
(2.x, 3.x, LAN Server, PCLP or LAN Manager).
5. From the -Select the destination LAN type menu, choose a
destination LAN type (3.x or 4.x).
Once you have selected a source and destination, the migration utility
verifies that you selected compatible versions for the migration.
6. Under Step 1 on the configuration form, press the Down-arrow key to
accept the default working directory or press <Enter> to specify another
working directory.
The working directory is where the bindery information and migration
reports are stored.
Usually, the working directory is located on the hard disk drive of the
workstation, but you can also put it on a network drive. You need 5 MB free
disk space in this directory.
NOTE: If you use a network drive instead of a hard drive, you must have
Create, Read, and Write rights in this directory.
WARNING: Do not try to run from a network drive that has been mapped as a
fake root.
If this directory doesn't exist, the migration utility creates it for you
on your hard disk.
Follow the Quick Help to specify a different working directory.
7. Under Step 1 on the configuration form, press <Enter> to select an
error/warning action.
Error/Warning Action Description
----------------------------------------------------------------
Pause after warnings and errors Choose this option if you
want the utility to stop
after each warning and
error and prompt you to
continue with the
migration.
Each time an error is
reported and you are
prompted, you can choose to
discontinue the prompting.
Do not pause after warnings Choose this option if you
and errors. do not want to be prompted
after each warning and
error.
NOTE: All errors are listed in the report file regardless of the option you
select.
8. Under Step 2 on the configuration form, press <Enter> to display a
list of source servers.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, the screen
shows the domain obtained from the DOSLAN.INI file. Edit this field if the
domain you are logged into is not the same as the one listed in the
DOSLAN.INI file.
9. Choose the source server you want to migrate from.
This selection must match the type you specified in Step 4.
If the source server you want to select is not shown, press <Ins> to see a
list of available servers that you can log in to.
10. Under Step 2 on the configuration form, press <Enter> to display
categories of information you want to migrate.
LS/LM NOTE: If you are migrating from LAN Server, PCLP or LAN Manager, you
are limited to the following categories to migrate:
Access Control profiles
All information
Groups
Print queues
Users
11. Using <F5>, mark the information you want to migrate.
Mark as many of the categories as necessary.
Follow the Quick Help for details on how to select information.
12. Under Step 2 on the configuration form, press <Enter> to display a
list of source volumes on the source server that you want to migrate
trustee assignments from.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, source
drives are listed.
13. Mark the volumes using <F5>, then press <Enter>.
Mark source volumes to migrate only if you are migrating information that
is contained on those volumes.
For example, you do not need to mark a source volume if you are only
migrating any of the following categories:
Accounting Information
Default Account Balance/Restrictions
Groups
Print Queues
User Restrictions
Users
You must select a source volume to migrate if you select either All
Information or Trustee Assignments.
14. Review the fields on the configuration form and make necessary
changes. You cannot complete the information for the destination server,
since it does not yet exist.
After you migrate the source information and install NetWare 3.x or 4.x,
you return to the migration utility and complete the destination server
information.
15. To proceed with the migration, press <F10> to display the -Select a
Migration Action menu
16. Select -Migrate to the Working Directory, then press <Enter>.
All information about the migration is displayed on the screen and is
entered into a report file which you can review later.
17. (Conditional) If errors occur during migration and you chose to be
prompted after errors and warnings, you receive the following error message
and must answer the question.
A migration error has occurred and is displayed in the migration log above.
Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):
18. When the migration to the working directory is complete, the
following message appears.
Migration from the working directory is complete. Press <Enter> to
continue.
19. Press <Enter> to view the -Select a Migration Action menu.
20. (Optional) From the -Select a Migration Action menu, select -View
Migration Reports and view the migration report.
20a. Select the report for the migration you completed and press
<Enter>.
The reports reside in the working directory that you specified earlier.
Use the report to help you complete and customize definitions, attributes,
and access privileges on the NetWare 3.x or 4.x server.
If you find errors on your destination server after the migration, locate
them in the report and determine what actions to take on the destination
server.
The report file is an ASCII text file that consists of
o Summary information of the bindery import phase (migrating bindery data
to the working directory).
o A listing of each item in each category that was read from the source
server.
o The number of errors that occurred during the migration.
20b. To exit the report, press <Esc> once.
20c. To return to the -Select a Migration Action menu, press <Esc>
again.
21. To exit the utility, choose -Exit (Return to DOS).
22. Install NetWare 3.x or 4.x on the server.
Follow the instructions under -Complete the Upgrade to NetWare v4.0 Using
INSTALL.NLM, to install your NetWare 3.x or 4.x server.
23. Prepare Macintosh file support.
To store Macintosh files and folders on the new NetWare 3.x or 4.x server,
add name space support to any volume that needs to store files with long
names. For more information, see -Add Name Space in Utilities Reference.
NOTE: Install NetWare for Macintosh (a separate Novell product) to provide
native-mode support for Macintosh workstations that connect to the 3.x or
4.x server.
24. Restore the data files from your backup device to a network
directory on the NetWare 3.x or 4.x server.
Make a note of where you restore the data files so that you can direct the
bindery information to the correct location.
25. Restart the migration utility by changing to the directory where
the migration utility files are and typing
MIGRATE <Enter>
The -Select the Type of Migration menu appears.
NOTE: Make sure that the working directory is the same one you used when
you migrated from the source server to the working directory.
26. From the -Select the Type of Migration menu, choose - Same- Server
migration.
27. From the -Select Source LAN Type menu, choose a source LAN type
(NetWare 2.x or LAN Server, PCLP or LAN Manager).
This should be the same source LAN type you selected in Step 4.
28. From the -Select the Destination LAN Type menu, choose a
destination LAN type (3.x or 4.x).
This should be the same destination LAN type you selected in Step 5.
29. (Optional) Change the -Error/Warning prompt if you want.
30. Move the cursor to Step 3 on the configuration form and press
<Enter> to display a list of NetWare servers.
IMPORTANT: Do not change the source server information on the configuration
form.
31. Choose the NetWare 3.x or 4.x destination server that you want to
migrate the source server information to.
Choose the NetWare 3.x or 4.x server you just installed.
32. Press <Enter> to display a list of selected source volumes and
their default destination volumes.
Destination volumes that match the source volumes are displayed as the
default.
33. Select a volume and press <Enter> to specify the destination volume
and directory on the NetWare 3.x or 4.x server. Press <Ins> to see a list
of available volumes and directories on the 3.x or 4.x server.
If you specify a directory that does not exist on the 3.x or 4.x server,
you are prompted to create it. Volumes must already be created before you
can migrate them.
34. Press <Enter> when you have completed the destination path of the
source volume.
35. Continue to specify destination paths if you have multiple source
volumes.
36. Press <F10> when you finish filling out the -Volumes destination
field.
37. Under Step 3 on the configuration form, press <Enter> and choose a
password option.
LAN MANAGER NOTE: If you are migrating from LAN Manager, passwords lengths
are global. For example, if a user has a -password not required flag set on
the LAN Manager side, he will have no password on the destination server.
If a password is required and the length of the password is zero (0), the
migration utility assigns the destination default password length.
38. Review the fields on the configuration form and make necessary
changes.
IMPORTANT: Do not change the information in the source server area.
39. To proceed with the migration, press <F10> to display the -Select a
Migration Action menu.
40. Select -Migrate from Working Directory.
All information about the migration displays on the screen and goes into a
report file, which you can review later.
When the migration from the working directory is complete, the migration
utility notifies you.
41. (Conditional) If errors occur during migration and you chose to be
prompted after errors and warnings, you receive the following error message
and must answer the question. A migration error has occurred and is
displayed in the migration log above. Do you want to continue with the
migration? (Y=Yes/N=No/I=Ignore Error):
42. Press <Enter> to view the -Select a Migration Action menu.
43. (Optional) From the -Select a Migration Action menu, select -View
Migration Reports and view the migration report.
43a. Select the report for the migration you completed.
The reports reside in the working directory that you specified earlier.
Use the report to help you complete and customize definitions, attributes,
and access privileges on the 3.x or 4.x server.
If you find errors on your destination server after the migration, review
the migration report to see if you can find where they occurred.
The report file is an ASCII text file that consists of the following:
o Summary information of the bindery export phase (migrating bindery data
from the working directory to the destination server).
o Listing of each item in each category that was read from the source
server.
o Listing of each item in each category that was written to or created on
the destination server.
o The number of errors that occurred during the migration.
43b. To exit the report, press <Esc> once.
43c. To return to the -Select a Migration Action menu, press <Esc>
again.
44. To exit the migration utility, select -Exit (Return to DOS).
45. Read -What to Do After the Migration.
What to Do After the Migration
------------------------------
After the migration is complete, check the 3.x or 4.x server and do the
following if they apply:
o Update references to the server in user login scripts if you changed the
server name.
Although user login scripts are migrated, they are not modified, and server
names and directory paths are not changed to match your new environment.
o Run third-party applications. You may have to reinstall them to work
properly under NetWare 3.x or 4.x. You may also need to enter new paths in
the setup files for any third-party applications.
o Check applications to see if they run properly. The following conditions
require you to reinstall an application:
o The application has an .EXE file that did not migrate.
o The application is path-specific and you changed the path structure
during migration.
Some DOS applications don't work when installed on volumes that have more
than 32 MB of disk space. Some of these applications can be made to work by
doing the following:
o Restrict the application's disk space on the destination server using
DSPACE in the application's directory.
o Make the directory a fake root with MAP.
o Check user restrictions and accounting charge rates to make sure your
system is configured the way you want it.
o If you chose to assign random passwords, you may want to print the
NEW.PWD file and distribute the password information to your users. The
users should change their passwords immediately.
The report, an ASCII text file, shows passwords sorted by date. If users
were migrated from more than one server, the current password is the last
one listed on the report.
o Check print servers and print queues to make sure they are configured
correctly. Also make sure that the physical printer connection is secure.
Use the NetWare print utilities to accomplish these tasks.
o If you migrated Macintosh directories, look in the report file to see
where the directory information went. Because of the DOS naming convention
(8.3) it is possible that directories at the same directory level, with
identical names, have been merged.
o Use PRINTCON to create PRINTCON.DAT files for the users on your
destination server. See Print Services for detailed PRINTCON instructions.
LS/LM NOTE: If you are migrating from LAN Server or LAN Manager, set up
print servers and print queues.
NOTE: For information on migrating rights and attributes, see Appendix A,
"Migrating Rights and Attributes," in Installation and Upgrade.
ΓΏ