I B M O P E R A T I N G S Y S T E M / 2 L A N S E R V E R V E R S I O N 1 . 3 D O M A I N C O N T R O L D A T A B A S E M I G R A T I O N H A N D B O O K SPECIAL NOTICES References in this publication to IBM products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights or other legally protectible rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Purchase, NY 10577. The following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBM corporation in the United States and/or other countries: IBM Operating System/2 OS/2 The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law. INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS INFORMATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. ii This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time. Requests for copies of this information and for technical information about IBM products should be made to your IBM Authorized Dealer or your IBM Marketing Representative. (C) Copyright International Business Machines Corporation 1990. All rights reserved. Note to US Government Users: Documentation and programs related to restricted rights. Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. iii CONTENTS ABOUT THIS BOOK ................................... vii BEFORE YOU BEGIN .............................. vii WHO SHOULD USE THIS BOOK ...................... viii HOW THIS BOOK IS STRUCTURED ................... viii ORGANIZATION .............................. viii CONVENTIONS ............................... ix RELATED PUBLICATIONS ...................... x CHAPTER 1. INTRODUCTION TO THE MIGRATION PROCESS... 1-1 MIGRATION CONTENTS ............................ 1-4 CONSIDERATIONS ................................ 1-5 THE MIGRATION PROCESS ......................... 1-7 ERROR HANDLING ................................ 1-8 CHAPTER 2. MIGRATING AN ENTIRE PCLP 1.3 DOMAIN AT ONE TIME .............................. 2-1 PREPARING THE NETWORK AND USER COMMUNITY ...... 2-3 PLANNING FOR THE EXPORT PHASE ................. 2-3 EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY DCDB FILE ...................... 2-4 PLANNING FOR THE IMPORT PHASE ................. 2-6 IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN ....................... 2-8 COMPLETING THE MIGRATION ...................... 2-10 CHAPTER 3. MIGRATING A PCLP 1.3 DOMAIN IN STAGES .. 3-1 PREPARING THE NETWORK AND USER COMMUNITY ...... 3-3 PLANNING FOR THE EXPORT PHASE ................. 3-3 EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY DCDB FILE ...................... 3-5 PLANNING FOR THE IMPORT PHASE ................. 3-7 IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN ....................... 3-8 SETTING UP THE INTERMEDIATE ENVIRONMENT ....... 3-10 COMPLETING THE MIGRATION ...................... 3-13 iv CHAPTER 4. MIGRATING AN ENTIRE LAN SERVER 1.0 DOMAIN AT ONE TIME ....................... 4-1 PREPARING THE NETWORK AND USER COMMUNITY ...... 4-3 PLANNING FOR THE EXPORT PHASE ................. 4-3 EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY DCDB FILE ...................... 4-5 PLANNING FOR THE IMPORT PHASE ................. 4-7 IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN ....................... 4-9 COMPLETING THE MIGRATION ...................... 4-11 CHAPTER 5. MIGRATING A LAN SERVER 1.0 DOMAIN IN STAGES ................................ 5-1 PREPARING THE NETWORK AND USER COMMUNITY ...... 5-3 PLANNING FOR THE EXPORT PHASE ................. 5-3 EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY DCDB FILE ...................... 5-6 PLANNING FOR THE IMPORT PHASE ................. 5-8 IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN ....................... 5-9 SETTING UP THE INTERMEDIATE ENVIRONMENT ....... 5-11 COMPLETING THE MIGRATION ...................... 5-15 APPENDIX. ERROR MESSAGES AND ERROR RECOVERY ...... A-1 PCLP 1.3 EXPORT ERRORS ........................ A-1 LAN SERVER 1.0 EXPORT ERRORS .................. A-1 IMPORT ERRORS ................................. A-2 USER ERRORS .............................. A-2 PROGRAM CODE ERRORS .......................A-7 WARNING MESSAGES ......................... A-10 v FIGURES 2-1. AN ENTIRE PCLP 1.3 DOMAIN MIGRATED TO LAN SERVER 1.3 ALL AT ONE TIME.........2-2 3-1. A PCLP DOMAIN MIGRATED TO LAN SERVER 1.3 OVER TIME IN STAGES............3-2 4-1. LAN SERVER 1.0 DOMAIN MIGRATED TO LAN SERVER 1.3 DOMAIN ALL AT ONE TIME.....4-2 5-1. LAN SERVER 1.0 DOMAIN MIGRATED TO LAN SERVER 1.3 OVER TIME IN STAGES........5-2 vi ABOUT THIS BOOK This handbook describes the tasks required to migrate from current IBM* Local Area Network Server environments (PC LAN Program 1.3 and IBM Operating System/2* LAN Server 1.0) to an IBM Operating System/2 LAN Server 1.3 environment. NOTE: If you are upgrading from OS/2* LAN Server 1.2, refer to OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED to proceed with normal installation. You do not reinitialize the domain control database (DCDB). There is no need to use the Migration Utility when upgrading from OS/2 LAN Server 1.2. A Migration Utility is used to move the domain definitions from the current environment to the DCDB in the new environment while preserving the integrity and consistency of the data. Migration tasks for each type of domain (DOS and OS/2) are listed in scenarios for migrating the entire domain at one time or migrating the domain in stages over a period of time. BEFORE YOU BEGIN You should be familiar with the Operating System/2 program to use this handbook. During the migration, you will need to refer to IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED and the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE in order to accomplish the required tasks. You will also need to be familiar with a text editor or word processor in order to edit and work with various files. If you are not familiar with the OS/2 program, see "RELATED PUBLICATIONS" on page x in this handbook for a list of books from which you can get the information you need. vii WHO SHOULD USE THIS BOOK This handbook assists the network administrator or person responsible for release-to-release migration of LAN environments in the following tasks: - Planning and preparing the network for migration - Migrating to the OS/2 LAN Server 1.3 environment - Restoring and creating the LAN resources not affected by the migration. HOW THIS BOOK IS STRUCTURED This handbook is designed to acquaint you with the migration process and to describe the tasks and procedures required to complete the migration of your environment to a LAN Server 1.3 environment. ORGANIZATION This handbook is organized as follows: - CHAPTER 1, "INTRODUCTION TO THE MIGRATION PROCESS," introduces and briefly describes the migration software. - CHAPTER 2, "MIGRATING AN ENTIRE PCLP 1.3 DOMAIN AT ONE TIME," describes the tasks required to migrate from a PCLP 1.3 domain to a LAN Server 1.3 domain all at one time. - CHAPTER 3, "MIGRATING A PCLP 1.3 DOMAIN IN STAGES," describes the tasks required to migrate from a PCLP 1.3 domain to a LAN Server 1.3 domain in stages (migrating the servers first, followed by the requesters) over an unspecified period of time. - CHAPTER 4, "MIGRATING AN ENTIRE LAN SERVER 1.0 DOMAIN AT ONE TIME," describes the tasks required to migrate from a LAN Server 1.0 domain to a LAN Server 1.3 domain all at one time. viii - CHAPTER 5, "MIGRATING A LAN SERVER 1.0 DOMAIN IN STAGES," describes the tasks required to migrate from a LAN Server 1.0 domain to a LAN Server 1.3 domain in stages (migrating the servers first, followed by the requesters) over an unspecified period of time. - APPENDIX, "ERROR MESSAGES AND ERROR RECOVERY," lists error messages that can be received during the Export and Import phases of the migration and the appropriate actions for recovery. CONVENTIONS This handbook uses the following terminology conventions unless otherwise noted: - PCLP 1.3 refers to PC LAN Program Version 1.3. - LAN Server 1.0 refers to IBM Operating System/2 Local Area Network Server Version 1.0. - LAN Server 1.3 refers to IBM Operating System/2 Local Area Network Server Version 1.3. - LAN Requester refers to the LAN Requester component of IBM Operating System/2 Extended Edition Version 1.3. - OS/2 EE 1.3 and the OS/2 program refer to IBM Operating System/2 Extended Edition Version 1.3. - DOS refers to IBM DOS 3.3 or 4.01. - DOS LAN Requester refers to the component of the OS/2 LAN Server 1.3 program that enables users at DOS workstations to be members of an OS/2 local area network. ix RELATED PUBLICATIONS The following is a list of related publications. For information about ordering these publications, contact your IBM authorized dealer or IBM marketing representative. - IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED - IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE - IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 USER'S GUIDE - IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 DOS LAN REQUESTER USER'S GUIDE - IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 COMMANDS REFERENCE - IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 GETTING STARTED - IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 USER'S GUIDE, VOLUME 1: BASE OPERATING SYSTEM - IBM PC LOCAL AREA NETWORK PROGRAM VERSION 1.3 REFERENCE - IBM OPERATING SYSTEM/2 SERVER INSTALLATION AND CONFIGURATION GUIDELINES - IBM OPERATING SYSTEM/2 INFORMATION AND PLANNING GUIDE. x CHAPTER 1. INTRODUCTION TO THE MIGRATION PROCESS The migration process moves the domain definitions from a LAN Server 1.0 or PCLP 1.3 domain to a LAN Server 1.3 domain while preserving the integrity and consistency of the data. NOTE: If you are upgrading from OS/2 LAN Server 1.2, refer to OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED to proceed with normal installation. You do not need to reinitialize the domain control database (DCDB). There is no need to use the Migration Utility when upgrading from OS/2 LAN Server 1.2. The domain definitions are stored in a DCDB in the LAN Server 1.0 and 1.3 environments and in directories in the PCLP 1.3 environment. Throughout these instructions, the domain definitions in all cases are referred to as the DCDB. The DCDB contains information such as user IDs and passwords, logon assignments, application selector information, group information, and resources to be shared as defined by the network administrator. Each resource that is subject to access control must be defined by an access control profile for that resource. The LAN Server 1.3 access control profile for a resource resides on the same server as the physical resource (unlike LAN Server 1.0, where the profiles resided on the domain controller only). A domain can be migrated at one time or in stages over a period of time. The resources in the destination domain can be the same or different from those in the source domain. The DCDB migration can occur on the same or different physical networks. The migration process uses the Domain Control Database Migration Utility to process the data related to the user, group, and resource definitions. The Migration Utility uses DCDB Export and DCDB Import functions to move and process the domain definitions from the current domain to the new one. The Export function is contained on the Migration Utility diskette. The network administrator runs the Export function on the source (PCLP 1.3 or LAN Server 1.0) domain controller. The 1-1 import function is contained within the OS/2 LAN Server program itself. The network administrator runs the Import function on the destination (LAN Server 1.3) domain controller. The Export function uses a mapping component to map the attributes of the LAN objects (for example, users, groups, and access profiles) from the source DCDB format to the destination DCDB format. The exported attributes are written to a temporary DCDB file. After OS/2 EE 1.3 and LAN Server 1.3 are installed, the Import function is used to import the information from the temporary file into the LAN Server 1.3 DCDB and the OS/2 EE 1.3 User Profile Management (UPM) database. Only the definitions of the LAN objects and access control profiles are migrated. The resources themselves are not migrated. The network administrator and network users must manually move physical resources, such as software applications and user files, from the source domain to the destination domain. If a critical error occurs during migration, the process stops. The network administrator can check the history file generated by the utility to find out which operations have been completed and where the error occurred. After correcting the error (by editing the temporary file or changing the LAN Server 1.3 DCDB), the network administrator can decide whether to continue the migration from the point at which the error occurred or to start the process from the beginning. A noncritical error, such as a duplicate resource not being migrated or a resource not being shared, that occurs during the migration is also logged in the history file. The network administrator can review and correct noncritical errors at any time. See "ERROR HANDLING" on page 1-8 for more information. NOTES: 1. The migration scenarios describe migration to a LAN Server 1.3 domain containing only the default LAN definitions. If this is not the case, then prior to importing, check for duplicate information between the temporary DCDB file and the existing LAN Server 1.3 DCDB. If duplicates are found, make the 1-2 appropriate changes either to the temporary DCDB file or to the LAN Server 1.3 DCDB. When the Import function is executed, existing entries in the LAN Server 1.3 DCDB are preserved if conflicts (such as duplicate entries) arise with imported entries. For example, if the temporary DCDB file contains a resource ID that is identical to an ID already residing on the destination domain, the ID on the destination domain is retained. The exception to this happens when the temporary DCDB file contains a duplicate server and resource combination, such as a printer that uses the same server and same port as the printer that is already assigned to the destination domain. In this case, the migration stops and the network administrator must decide which resource to keep. 2. The network administrator must verify that the country information is the same in the source and destination domains (the code page, country code, and keyboard parameters in the CONFIG.SYS file). 3. If the DCDB is too large to fit on one diskette, the Export and Import functions support multiple diskettes. During the Export phase, the network administrator is prompted for additional formatted diskettes and a new temporary file name for each additional diskette. The temporary file names should be unique and in sequential order (for example, DCDB1.TMP, DCDB2.TMP, and DCDB3.TMP). The Import function does not prompt for additional diskettes. The network administrator must use the Import function to process each diskette in the same sequential order in which it was created. The Import phase is complete when all diskettes have been processed. 4. Certain text editors may insert tab characters in the files that you edit. Verify that the TAB option is set to OFF for the editor you are using. The OS/2 System Editor does not add tab characters. 1-3 MIGRATION CONTENTS The following domain definitions are migrated: - Machine definitions (excluding requesters) - Files alias definitions (including directory structures) - Printer alias definitions (including queues) - Serial device alias definitions (including queues and external resources) - Public application definitions (excluding working directories) -- Application files assignments -- Application printer assignments -- Application serial device assignments. - User definitions -- Logon file assignments -- Logon printer assignments -- Logon serial device assignments -- Application selector list. - Groups definitions - Access control profiles. These definitions (their attributes and values) are exported into a temporary DCDB file in the order shown. This temporary DCDB file can be edited to change or add values as necessary before importing the domain definitions to the new LAN Server 1.3 DCDB. However, the order of the definitions in the temporary DCDB should not be changed. See the appendix that lists values for domain definitions in IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED. The requester definitions and image files for remote IPL are not migrated by this utility. Remote IPL support can be installed using the LAN Server 1.3 install program. New DOS LAN Requester IPL images can be built using the LAN Server 1.3 full-screen interface. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 1-4 GETTING STARTED and the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for more information. The global access list used in LAN Server 1.0 is not used in LAN Server 1.3. Therefore, the global access list is not migrated. Only the definition of the user's home directory is migrated. The files in the home directory should be backed up before starting the migration. After the migration is completed, the backed-up files can be restored. DOS and OS/2 users are all migrated to the IBM LAN Server 1.3 domain, which does not distinguish between DOS and OS/2 users. CONSIDERATIONS Names used in LAN Server 1.3 must contain from 1 to 8 characters. The first character cannot be numeric. The last character cannot be the dollar sign ($) character. An error occurs if the name does not follow naming conventions. Because original user passwords cannot be decrypted, the Migration Utility randomly sets a new password for each migrated user in the destination domain. The new passwords are contained in the \IBMLAN\NETPROG\DCDBPSWD.DAT file located on the destination domain controller. The network administrator must notify users of their new passwords so they can log on to the destination domain. If the number of servers in the destination domain does not match the number of servers in the source domain, the network administrator should make the appropriate adjustments. PCLP 1.3 and LAN Server 1.0 directories and files without access control profiles were given maximum access permissions. This changed in LAN Server 1.2 and higher to denying access to directories and files without an access control profile. 1-5 What this means is that PCLP 1.3 or LAN Server 1.0 applications could have had access to a resource without an access control profile. The same applications running under LAN Server 1.2 and higher will be denied access to resources without an access control profile. Thus, an application that accesses resources with no access control profile specified may not run properly after migration. To prevent this, the Import phase will create a profile with all permissions except the "P" permission for the root. This allows access to all files and directories on the drive that do not have an access control profile. To take advantage of the expanded access control provisions in LAN Server 1.2 and higher, the network administrator should create the appropriate access control profiles throughout the directory structures and then update or delete the access control profile at the root. In addition, the network administrator should assure that access control profiles exist for resources that are shared using NET SHARE commands. Releases prior to LAN Server 1.2 required that the domain name and the server (machine) name be the same for the domain controller. LAN Server 1.2 and higher require that the domain name and server (machine) names be unique. For this reason, you will have to change either the domain name or the server (machine) name on the domain controller when you install LAN Server 1.2 or higher. 1. If the domain name is selected to be changed, it will be changed during installation of LAN Server and LAN Requester 1.2 or higher. Changing the domain name requires changes to any batch (.BAT) or command (.CMD) files containing instruction using the domain name. 1-6 2. If the server (machine) name is selected to be changed, it will be changed during the installation of LAN Server and LAN Requester 1.2 or higher. Changing the server name also requires making global changes in the migration export temporary file to reflect the new server name(s). Other areas that may require server name changes could be batch (.BAT) or command (.CMD) files containing instructions using the server (machine) name. If servers or shared resources are added for the new domain, the network administrator can define additional resources after the migration has been completed. If there are servers or resources that will be eliminated from the destination domain, the network administrator should change the definitions of aliases or possible user logon assignments before running the Export function. It is also possible to change the resource assignments by editing the temporary DCDB file (created during the Export process) prior to starting the Import phase. Before starting the migration, the network administrator should manually back up the source DCDB using a series of XCOPY commands or (for LAN Server 1.0 only) the DCDBBACK Utility. The Migration Utility does not perform this function. It is important to have a copy of the original DCDB if there are errors or system failure during the migration. The steps for backing up the DCDB are described in the migration chapter for each environment. To verify the domain definitions, the network administrator should print the definitions before and after the migration process and compare both sets. The Migration Utility does not perform this function. THE MIGRATION PROCESS The migration tasks are described in the following phases: - Preparing the network and user community, which involves such tasks as upgrading hardware if necessary and informing network users about the migration schedule. 1-7 - Planning for the Export phase, which involves such tasks as printing the existing domain definitions for later comparisions and creating a backup copy of the existing domain definitions on diskette, as well as reviewing and documenting the current access permissions for each network resource. - Exporting the source domain definitions to a temporary file. - Planning for the Import phase, which involves preparing the new domain controller (installing the appropriate software) and modifying the temporary DCDB file for the new environment as required. - Importing the domain definitions from the temporary file to the destination DCDB. - In staged migration only, creating an intermediate environment to continue providing resources to the network. - Completing the migration, which involves such tasks as restoring resources that have not been migrated and upgrading the requesters in the domain. All servers in the source domain must be started in order to export the DCDB. All servers in the destination domain must be started in order to import the DCDB. NOTE: During the actual migration, no other users or administrators should be logged on to the domain, since this could interfere with the process. It is especially important that other network administrators do not modify any domain definitions in the databases while the migration is taking place. ERROR HANDLING If the migration process encounters an error, an error message is displayed at the workstation and logged in a history file (\PCLP13XS\NET1_30\PCLP13MU.HST for exporting from PCLP 1.3 or \IBMLAN\NETPROG\LS10MU.HST for exporting from LAN Server 1.0). The history file 1-8 \IBMLAN\NETPROG\LS12MU.HST is created each time the Import function is used on the LAN Server 1.3 domain. The history file contains chronological data about the migration in the form of activity and error entries. Each activity that is performed by a component during the migration process is contained in a record. Each error entry is also contained in a record. Both the activity and error entries are logged in the history file. If an error occurs during the Export phase, the network administrator should check the history file, find and correct the error, and start the migration from the beginning. If an error occurs during the Import phase and the error can be traced to an entry in the history file, the network administrator can correct the error in the temporary file and start the migration from the point at which the error occurred. 1-9 CHAPTER 2. MIGRATING AN ENTIRE PCLP 1.3 DOMAIN AT ONE TIME This chapter describes the tasks required to migrate from a PCLP 1.3 domain (servers and requesters) to a LAN Server 1.3 environment all at one time. The following figure shows the typical migration scenario for this environment. 2-1 Original PC LAN Final LAN Server 1.3 Program 1.3 Domain Domain (Domain IBMDC) (Domain IBM13DOM) ÉÍÍÍÍ» ÉÍÍÍÍ» º º by download service º º ÚÈÍÍÍͼ¿º --------------------------------->ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ PC13_W º DOS_LR º º º º ÉÍÍÍÍ» º ÉÍÍÍÍ» º ºRIPLº by RIPL image º ºRIPLº ºÚÈÍÍÍͼ¿ --------------------------------->ºÚÈÍÍÍͼ¿ ÌÀÄÄÄÄÄÄÙ create feature ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» º PC13_W ÉÍÍÍÍ» º DOS_LR º º º º º º ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ by diskette ÀÄÄÄÄÄÄÙ¹ PC13_W º --------------------------------> DOS_LR º º installation º º º º º º ÉÍÍÍÍ» º ÉÍÍÍÍ» º º º by diskette º º º ºÚÈÍÍÍͼ¿ --------------------------------> ºÚÈÍÍÍͼ¿ ÌÀÄÄÄÄÄÄÙ installation ÌÀÄÄÄÄÄÄÙ º PC13_W º EE13_LR ÉÍÍÍÍ» º ÉÍÍÍÍ» º º º º º º º ÚÄÈÍÍÍͼĿº by diskette ÚÄÈÍÍÍͼĿº ³ADSERV01³º-------------------------------->³ADSERV01³º ÀÄÄÄÄÄÄÄÄÙ¹ installation ÀÄÄÄÄÄÄÄÄÙ¹ PC13_AS º LS13_AS º º ÉÍÍÍÍ» º ÉÍÍÍÍ» º º º º º º ºÚÄÈÍÍÍͼĿ ºÚÄÈÍÍÍͼĿ º³ IBMDC ³ by diskette º³ IBMDC ³ ÌÀÄÄÄÄÄÄÄÄÙ ------------------------------->ÌÀÄÄÄÄÄÄÄÄÙ PC13_DC installation LS13_DC ==> ==> ==> ==> ==> ==> ==> ==> ==> Migration Path Legend: PC13_W = PC LAN Program 1.3 Workstation PC13_AS = PC LAN Program 1.3 Additional Server PC13_DC = PC LAN Program 1.3 Domain Controller DOS_LR = DOS LAN Requester EE13_LR = OS/2 Extended Edition 1.3 LAN Requester LS13_DC = OS/2 LAN Server 1.3 Domain Controller LS13_AS = OS/2 LAN Server 1.3 Additional Server RIPL = Remote IPL workstation FIGURE 2-1. AN ENTIRE PCLP 1.3 DOMAIN MIGRATED TO LAN SERVER 1.3 ALL AT ONE TIME 2-2 PREPARING THE NETWORK AND USER COMMUNITY The migration from a PCLP 1.3 environment to a LAN Server 1.3 environment can require a hardware upgrade for the servers. For information about system, memory, and fixed-disk space requirements, see the IBM OPERATING SYSTEM/2 INFORMATION AND PLANNING GUIDE and the OS/2 LAN Server Version 1.3 slipcase cover. It is recommended that you notify system users about the upgrade to the new product release. Include the following information in this notification: - Tell users about the schedule (when their workstation will be migrated). - Tell users to back up their home filesets before the migration and to restore the filesets after the migration has been completed (unless the network administrator is going to do this). - Tell users that private applications (that exist on the user's workstation only) will not be migrated. Explain that these applications must be added to their application selectors after the migration has been completed. - Tell users to get their new password from the network administrator after the migration has been completed. PLANNING FOR THE EXPORT PHASE Before you export the domain definitions to the temporary file, complete the following steps: 1. Print the current LAN domain definitions by doing the following: a. Log on as an administrator to the source domain controller. b. Verify that no other users or administrators are logged on and accessing the DCDB. c. Select "PCLP" from the APPLICATION SELECTOR menu. d. Select "PRINTDDF" from the PCLP FUNCTIONS menu. 2-3 2. Create a backup copy of the current LAN domain definitions by using the following sequence of DOS XCOPY commands: XCOPY C:\PCLPUSER A:\PCLPUSER /S /E XCOPY C:\APPS A:\APPS /S /E XCOPY C:\PCLP13XS\USER.MDL A:\PCLP13XS\USER.MDL /S /E XCOPY C:\PCLP13XS\FILESETS A:\PCLP13XS\FILESETS /S /E XCOPY C:\PCLP13XS\PRINTERS A:\PCLP13XS\PRINTERS /S /E XCOPY C:\PCLP13XS\LISTS A:\PCLP13XS\LISTS /S /E XCOPY C:\PCLP13XS\BATCH A:\PCLP13XS\BATCH /S /E NOTE: This process may require more than one formatted diskette. If an XCOPY command requires more than one diskette, you should use the BACKUP command. See your DOS documentation for information about this command. EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY DCDB FILE To export the domain definitions to a temporary DCDB file, complete the following steps at the source domain controller: 1. Insert the Migration Utility diskette into the A: drive. 2. Copy the following files to the C:\PCLP13XS\NET1_30 directory (this syntax assumes you are installing from the A:\> prompt at the command line): A:\>copy A:\PCLP13MU.FMT C:\PCLP13XS\NET1_30 A:\>copy A:\PCLP13MU.MSG C:\PCLP13XS\NET1_30 A:\>copy A:\PCLPEXPO.EXE C:\PCLP13XS\NET1_30 The PCLP13MU.FMT format file is used to generate the temporary DCDB file. The PCLP13MU.MSG message file logs the activities (or messages) in the history file and displays prompts to the user at the workstation. The PCLPEXPO.EXE file contains the executable Export program for PCLP 1.3. 3. Remove the Migration Utility diskette from the A: drive. 2-4 4. Start all PCLP 1.3 servers (the domain controller and additional servers) in the domain. 5. Log on as an administrator to the domain controller. NOTE: You may have to change the NET START parameter to make additional memory available to enable you to log on to the domain controller. 6. Select "DOS". 7. Make C:\PCLP13XS\NET1_30 the current directory. 8. Enter the following to invoke the Export function: PCLPEXPO path where the path parameter specifies the full path and file name of the temporary DCDB file you want to create during the Export phase. The path can include the drive letter. For example, to create the temporary DCDB export file DCDB.TMP on the A: drive, enter the following: PCLPEXPO A:DCDB.TMP In the command, PCLPEXPO calls the executable Export program (PCLPEXPO.EXE), which starts the Export function. The Export function reads each attribute for the LAN objects defined in the PCLP 1.3 source domain and maps each attribute to the corresponding attribute in the LAN Server 1.3 DCDB format. The Export function then writes the attribute to a temporary DCDB file that can be edited by the network administrator as necessary. The following message is displayed when the Export function completes: Program completed successfully. 9. If you have remote IPL machine definitions, do the following: a. Enter the following to copy the RPL.MAP file to a new diskette: COPY C:\PCLP13XS\IMAGES\RPL.MAP A: 2-5 b. If the remote IPL server name has changed, edit the DCDB.TMP files and the RPL.MAP file to reflect the new server name. Ensure that no extra characters or blank lines are added to the files. NOTES: 1. If the DCDB being exported is larger than one diskette, the function prompts for another formatted diskette and a new file name. The file names on the multiple diskettes should be in sequential order. 2. If an error occurs, see APPENDIX, "ERROR MESSAGES AND ERROR RECOVERY," for information about how to continue. 3. The C:\PCLP13XS\NET1_30\PCLP13MU.HST history file is created each time the Export function is invoked. PLANNING FOR THE IMPORT PHASE Before you import the domain definitions to the new DCDB, complete the following steps: 1. Install the OS/2 EE 1.3 and LAN Server 1.3 programs on the workstation that has been designated as the new (destination) domain controller and the workstations designated as the additional servers. 2. Verify that the source server (machine) name for the domain controller in the temporary DCDB file is the same as the server (machine) name for the domain controller in the destination domain. If the names are not the same, edit the temporary file globally replacing the PCLP 1.3 domain controller server (machine) name with the LAN Server 1.3 domain controller server (machine) name. Also, verify that all names of additional servers in the temporary file match the names of their counterpart servers in the destination domain. If they are not the same, edit the temporary file and globally replace the PCLP server names with the new LAN Server 1.3 server (machine) names. 3. Edit the temporary DCDB file to change all devices (such as LPT1) to queues (such as LPT1Q) in the PRINTER ALIASES section. 2-6 NOTE: If you print the temporary DCDB file after the Export phase completes, the DCDB prints in columnar form; however, the DCDB that is displayed on your workstation (if you are using the OS/2 System Editor) is not. To display the DCDB on your workstation exactly as it is printed out, you must change the font setting on the System Editor. Do the following: 1. Select "Option" from the System Editor pull-down. 2. Select "Set fonts" from the Option pull-down. 3. Select "HELV font" from the Fonts panel. 4. Define and start all LAN Server 1.3 servers. 5. Log on as an administrator to the domain controller. 6. Create a Print Manager spooler queue for each printer to be migrated. See the IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 USER'S GUIDE, VOLUME 1: BASE OPERATING SYSTEM for information about creating spooler queues. NOTES: 1. A redirected drive cannot be used to import access control profiles. For example, if the source domain has resources on Server 1 on the D: drive and the destination domain Server 1 does not have a physical D: drive, the temporary file must be edited to change the drive designation for all resources on Server 1 from the D: drive to the C: drive. 2. The X: drive is reserved to perform the Import function. 2-7 IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN To import the domain definitions to the new DCDB on the destination domain, complete the following steps at the destination domain controller: 1. Invoke the Import function of the Migration Utility using the following command: LS12IMPO path where the path parameter specifies the full path and file name of the temporary DCDB file (created during the Export phase). The path can include the drive letter. For example, to invoke the Import function with the temporary DCDB export file DCDB.TMP located on the A: drive, enter the following: LS12IMPO A:DCDB.TMP In the command, LS12IMPO calls the Import function (which is part of the LAN Server 1.3 product and does not require installation). The Import function reads the attributes of each LAN object from the temporary DCDB file in order, and writes these attributes to the new DCDB in the destination domain. A message is displayed on the workstation for each object definition that is successfully written to the new DCDB. If the Import function encounters a duplicate server and path or server and spooler queue combination, or cannot process an attribute, a message that indicates the error is displayed and the function stops. The error message is also logged in the \IBMLAN\NETPROG\LS12MU.HST file (which also contains entries for all migration activities performed). After you correct the error, edit the temporary DCDB file to correct the attribute in this file as well, and then start the Import function again using the LS12IMPO command described previously. NOTES: a. Duplicate user, group, or resource information is ignored by the Import function (the process does not stop). However, warning messages that indicate the duplicate information are displayed on the workstation and logged in the history file. 2-8 b. If you are at the C: prompt and want to print the LS12MU.HST file to locate the error, enter the following command: TYPE LS12MU.HST > PRN Before the Import function completes, it also generates the \IBMLAN\NETPROG\DCDBPSWD.DAT password file. This file contains new passwords for users that are migrated to the new LAN Server 1.3 domain. When the Import function completes, the following message is displayed: Program completed successfully. NOTE: If multiple diskettes were used to export the domain definitions, you must run the Import function on each diskette. (You will not be prompted to insert multiple diskettes.) Be sure to process the diskettes in the sequential order in which they were created. The Import function is actually complete after the last diskette has been processed. If the Import function does not complete successfully, look through the LS12MU.HST history file to find the error. If you correct an error, you must rename the history file to preserve its entries before starting the Import function again. 2. Secure the \IBMLAN\NETPROG\DCDBPSWD.DAT password file that was generated by the Import function. 3. Migrate the resources from the PCLP domain controller to the LAN Server 1.3 domain controller. This includes printers, serial devices, files, and applications. 4. Migrate the contents of the users' home directories on the PCLP domain controller to the LAN Server 1.3 domain controller. 5. If you have remote IPL machine definitions, copy the RPL.MAP file to the appropriate subdirectory: COPY A:RPL.MAP C:\IBMLAN\DCDB\IMAGES 2-9 COMPLETING THE MIGRATION Complete the migration with the following steps: 1. Print the imported LAN domain definitions and verify the migrated definitions by doing the following: a. Log on as an administrator to the domain controller. b. Select "Definitions" from the main menu. c. Select "Print the domain definition" from the Definitions pull-down. d. Select the default printer (or the printer that applies to you) from the Device Name column on the Print Domain Definition panel. 2. Issue new passwords for the user IDs that require a password from the \IBMLAN\NETPROG\DCDBPSWD.DAT file that was generated during the Import function. 3. If you have remote IPL images that were migrated, do the following: - If standard image names were migrated, use the LAN Server 1.3 full-screen interface to select and make each standard image used in the RPL.MAP file. - If nonstandard images were migrated, the network administrator must create and make each nonstandard image. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for more information. 4. For the requesters in the domain: a. Create DOS LAN Requester IPL images and machine definitions to replace the PCLP 1.3 Requester IPL images and definitions if remote IPL machines will continue to be supported. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for information about how to create these images. 2-10 b. Install the appropriate operating system on the workstations. If the workstation will be an OS/2 requester, verify that the workstation is appropriately configured (memory and fixed-disk space) and install the OS/2 EE 1.3 program. See IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 GETTING STARTED for installation information. If the workstation will be a DOS requester, install DOS 3.3 or 4.01, the PC LAN Support Program, and the IBM DOS LAN Requester program. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED for installation information. 2-11 CHAPTER 3. MIGRATING A PCLP 1.3 DOMAIN IN STAGES This chapter describes the tasks required to migrate from a PCLP 1.3 domain to a LAN Server 1.3 environment over time, in stages. During this staged migration, the network administrator must install and configure an additional system as the new LAN Server 1.3 domain controller. While the network administrator is migrating the domain definitions and existing resources from the PCLP domain to this additional system (which will serve as the LAN Server 1.3 domain controller) and setting up the new environment, the existing PCLP 1.3 domain controller is still providing logon service to users. It is important to note that once a server is migrated, users whose home filesets are on that server cannot log on to the domain until the migration has been completed. To provide the required access to the LAN Server 1.3 resources from the PCLP 1.3 requesters, the network administrator should define appropriate access control privileges to the GUEST user ID in the LAN Server 1.3 domain. After all PCLP 1.3 requesters have been upgraded to OS/2 EE 1.3 requesters or DOS LAN Requesters, the access privileges assigned to the GUEST user ID should be reviewed and modified as required. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for information about how to assign the access control privileges to the GUEST user ID. NOTE: Using the GUEST user ID in this situation not only allows users at PCLP 1.3 requesters to access LAN Server 1.3 resources; it also allows any user ID not defined in the LAN Server 1.3 domain to also access the LAN Server 1.3 resources. The following figure shows the typical migration scenario for this environment. 3-1 Original PC LAN Final LAN Server 1.3 Program 1.3 Domain Intermediate Stage Domain (Domain IBMDC) (Domains IBMDC (Domain IBM13DOM) and IBM13DOM) ÉÍÍÍÍ» ÉÍÍÍÍ» ÉÍÍÍÍ» ºRIPLº ºRIPLº ºRIPLº ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ PC13_W º ÉÍÍÍÍ» DOS_LR º ÉÍÍÍÍ» DOS_LR º ÉÍÍÍÍ» º º º º º º º º º ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ º º º PC13_W º º º PC13_W º º º DOS_LR ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ PC13_W º ÉÍÍÍÍ» DOS_LR º ÉÍÍÍÍ» DOS_LR º ÉÍÍÍÍ» º º º º º º º º º ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ º º º PC13_W º º º PC13_W º º º EE13_LR ÚÄÈÍÍÍͼĿº ÚÄÈÍÍÍͼĿº ÚÄÈÍÍÍͼĿº ³ADSERV01³º ³ADSERV01³º ³ADSERV01³º ÀÄÄÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÄÄÙ¹ PC13_AS º ÉÍÍÍÍ» LS13_AS º ÉÍÍÍÍ» LS13_AS º º º º º º º º ºÚÄÈÍÍÍͼĿ ºÚÄÈÍÍÍͼĿ º º³ IBMDC ³ º³ IBMDC ³ º ÌÀÄÄÄÄÄÄÄÄÙ ÌÀÄÄÄÄÄÄÄÄÙ Ì º PC13_DC º PC13_DC º º º(PCLP Logon º º ÉÍÍÍÍ» º Services ) ÉÍÍÍÍ» º º º º º º º º º ÚÄÈÍÍÍͼĿº ÚÄÈÍÍÍͼĿº º ³ LS13DC ³¹ ³ LS13DC ³¹ º ÀÄÄÄÄÄÄÄÄÙº ÀÄÄÄÄÄÄÄÄÙº LS13_DC LS13_DC (External Resources) (Complete Control) ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> Migration Path Legend: PC13_W = PC LAN Program 1.3 Workstation PC13_AS = PC LAN Program 1.3 Additional Server PC13_DC = PC LAN Program 1.3 Domain Controller DOS_LR = DOS LAN Requester EE13_LR = OS/2 Extended Edition 1.3 LAN Requester LS13_DC = OS/2 LAN Server 1.3 Domain Controller LS13_AS = OS/2 LAN Server 1.3 Additional Server RIPL = Remote IPL workstation. FIGURE 3-1. A PCLP 1.3 DOMAIN MIGRATED TO LAN SERVER 1.3 OVER TIME IN STAGES 3-2 PREPARING THE NETWORK AND USER COMMUNITY The migration from a PCLP 1.3 environment to a LAN Server 1.3 environment can require a hardware upgrade for the servers. For information about system, memory, and fixed-disk space requirements, see the IBM OPERATING SYSTEM/2 INFORMATION AND PLANNING GUIDE and the OS/2 LAN Server Version 1.3 slipcase cover. It is recommended that you notify system users about the upgrade to the new product release. Include the following information in this notification: - Tell users about the schedule (when their workstation will be migrated). - Tell users to back up their home filesets before the migration and to restore the filesets after the migration has been completed (unless the network administrator is going to do this). - Tell users that private applications (that exist on the user's workstation only) will not be migrated. Explain that these applications must be added to their application selectors when the migration has been completed. - Tell users to get their new password from the network administrator after the migration has been completed. PLANNING FOR THE EXPORT PHASE Before you export the domain definitions to the temporary file, complete the following steps: 1. Connect an additional system that will serve as the new LAN Server 1.3 domain controller to the current network. See the documentation that came with your network adapter for connection information. 2. Install and configure the new system as the LAN Server 1.3 domain controller. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED for information about installing this system. 3-3 NOTE: In these instructions, the LAN Server 1.3 domain name is referred to in examples as IBM13DOM and the server name for the domain controller is referred to as LS13DC. 3. On the existing (source) domain controller, print the current LAN domain definitions by doing the following: a. Log on as an administrator to the domain controller. b. Verify that no other users or administrators are logged on and accessing the DCDB. c. Select "PCLP" from the APPLICATION SELECTOR menu. d. Select "PRINTDDF" from the PCLP FUNCTIONS menu. 4. Also on the existing domain controller, create a backup copy of the current LAN domain definitions by using the following sequence of DOS XCOPY commands: XCOPY C:\PCLPUSER A:\PCLPUSER /S /E XCOPY C:\APPS A:\APPS /S /E XCOPY C:\PCLP13XS\USER.MDL A:\PCLP13XS\USER.MDL /S /E XCOPY C:\PCLP13XS\FILESETS A:\PCLP13XS\FILESETS /S /E XCOPY C:\PCLP13XS\PRINTERS A:\PCLP13XS\PRINTERS /S /E XCOPY C:\PCLP13XS\LISTS A:\PCLP13XS\LISTS /S /E XCOPY C:\PCLP13XS\BATCH A:\PCLP13XS\BATCH /S /E NOTE: This process may require more than one formatted diskette. If an XCOPY command requires more than one diskette, you should use the BACKUP command. See your DOS documentation for information about this command. 3-4 EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY DCDB FILE To export the domain definitions to a temporary DCDB file, complete the following steps at the source domain controller: 1. Insert the Migration Utility diskette into the A: drive. 2. Copy the following files to the C:\PCLP13XS\NET1_30 directory (this syntax assumes you are installing from the A:\> prompt at the command line): A:\>copy A:\PCLP13MU.FMT C:\PCLP13XS\NET1_30 A:\>copy A:\PCLP13MU.MSG C:\PCLP13XS\NET1_30 A:\>copy A:\PCLPEXPO.EXE C:\PCLP13XS\NET1_30 The PCLP13MU.FMT format file is used to generate the temporary DCDB file. The PCLP13MU.MSG message file logs the activities (or messages) in the history file and displays prompts to the user at the workstation. The PCLPEXPO.EXE file contains the executable Export program for PCLP 1.3. 3. Remove the Migration Utility diskette from the A: drive. 4. Start all PCLP 1.3 servers (the domain controller and additional servers) in the domain. 5. Log on as an administrator to the domain controller. 6. Make C:\PCLP13XS\NET1_30 the current directory. 7. Enter the following to invoke the Export function: PCLPEXPO path where the path parameter specifies the full path and file name of the temporary DCDB file you want to create during the Export phase. The path can include the drive letter. For example, to create the temporary DCDB export file DCDB.TMP on the A: drive, enter the following: PCLPEXPO A:DCDB.TMP 3-5 In the command, PCLPEXPO calls the executable Export program (PCLPEXPO.EXE), which starts the Export function. The Export function reads each attribute for the LAN objects defined in the PCLP 1.3 source domain and maps the attribute to the corresponding attribute in the LAN Server 1.3 DCDB format. The Export function then writes the attribute to a temporary DCDB file that can be edited by the network administrator as necessary. The following message is displayed when the Export function completes: Program completed successfully. 8. If you have remote IPL machine definitions, do the following: a. Enter the following to copy the RPL.MAP file to a new diskette: COPY C:\PCLP13XS\IMAGES\RPL.MAP A: b. If the remote IPL server name has changed, edit the DCDB.TMP files and the RPL.MAP file to reflect the new server name. Ensure that no extra characters or blank lines are added to the files. NOTES: 1. If the DCDB being exported is larger than one diskette, the function prompts for another formatted diskette and a new file name. The file names on the multiple diskettes should be in sequential order. 2. If an error occurs, see APPENDIX, "ERROR MESSAGES AND ERROR RECOVERY," for information about how to continue. 3. The C:\PCLP13XS\NET1_30\PCLP13MU.HST history file is created each time the Export function is invoked. 3-6 PLANNING FOR THE IMPORT PHASE Before you import the domain definitions to the new DCDB, complete the following steps: 1. Install the OS/2 EE 1.3 and LAN Server 1.3 programs on the workstation that has been designated as the new (destination) domain controller and the workstations designated as the additional servers. 2. Edit the temporary DCDB file to change the following: a. All occurrences of the server name IBMDC to LS13DC. b. All devices (such as LPT1) to queues (such as LPT1Q) in the PRINTER ALIASES section. NOTES: a. Verify that the server (machine) names in the temporary file are the same names that are in the destination domain. If they are not the same, edit the temporary file and globally replace the PCLP server (machine) names with the new LAN Server 1.3 server (machine) names. b. If you print the temporary DCDB file after the Export phase completes, the DCDB prints in columnar form; however, the DCDB that is displayed on your workstation (if you are using the OS/2 System Editor) is not. To display the DCDB on your workstation exactly as it is printed out, you must change the font setting on the System Editor. Do the following: 1. Select "Option" from the System Editor pull-down. 2. Select "Set fonts" from the Option pull-down. 3. Select "HELV font" from the Fonts panel. 3. Define and start all LAN Server 1.3 servers. 4. Log on as an administrator to the domain controller. 5. Create a Print Manager spooler queue for each printer to be migrated. See IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 USER'S GUIDE, VOLUME 1: BASE OPERATING SYSTEM for information about creating spooler queues. 3-7 NOTES: 1. A redirected drive cannot be used to import access control profiles. For example, if the source domain has resources on Server 1 on the D: drive and the destination domain Server 1 does not have a physical D: drive, the temporary file must be edited to change the drive designation for all resources on Server 1 from the D: drive to the C: drive. 2. The X: drive is reserved to perform the Import function. IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN To import the domain definitions to the DCDB on the destination domain, complete the following steps at the destination domain controller: 1. Invoke the Import function of the Migration Utility using the following command: LS12IMPO path where the path parameter specifies the full path and file name of the temporary DCDB file (created during the Export phase). The path can include the drive letter. For example, to invoke the Import function with the temporary DCDB export file DCDB.TMP located on the A: drive, enter the following: LS12IMPO A:DCDB.TMP In the command, LS12IMPO calls the Import function (which is part of the LAN Server 1.3 product and does not require installation). The Import function reads the attributes of each LAN object from the temporary DCDB file in order and writes these attributes to the new DCDB in the destination domain. A message is displayed on the workstation for each object definition that is successfully written to the new DCDB. If the Import function encounters a duplicate server and path or server and spooler queue combination, or cannot process an attribute, a message that indicates the error is displayed and the function stops. The error message is also logged in the \IBMLAN\NETPROG\LS12MU.HST file (which also contains entries for all migration activities performed). After you correct the error, edit the temporary DCDB 3-8 file to correct the attribute in this file as well, and then start the Import function again using the LS12IMPO command described previously. NOTES: a. Duplicate user, group, or resource information is ignored by the Import function (the process does not stop). However, warning messages that indicate the duplicate information are displayed on the workstation and logged in the history file. b. If you are at the C: prompt and want to print the LS12MU.HST file to locate the error, enter the following command: TYPE LS12MU.HST > PRN Before the Import function completes, it also generates the \IBMLAN\NETPROG\DCDBPSWD.DAT password file. This file contains new passwords for users that are migrated to the new LAN Server 1.3 domain. When the Import function completes, the following message is displayed: Program completed successfully. NOTE: If multiple diskettes were used to export the domain definitions, you must run the Import function on each diskette. (You will not be prompted to insert multiple diskettes.) Be sure to process the diskettes in the same sequential order in which they were created. The Import function is actually complete after the last diskette has been processed. If the Import function does not complete successfully, look through the LS12MU.HST history file to find the error. If you correct an error, you must rename the history file to preserve its entries before starting the Import function again. 2. Secure the \IBMLAN\NETPROG\DCDBPSWD.DAT password file that was generated by the Import function. 3. Migrate the resources from the PCLP domain controller to the LAN Server 1.3 domain controller. This includes printers, serial devices, files, and applications. 3-9 4. Migrate the contents of the users' home directories on the PCLP domain controller to the LAN Server 1.3 domain controller. 5. If you have remote IPL machine definitions, copy the RPL.MAP file to the appropriate subdirectory: COPY A:RPL.MAP C:\IBMLAN\DCDB\IMAGES SETTING UP THE INTERMEDIATE ENVIRONMENT Set up the intermediate environment (see Figure 3-1) with the following steps: 1. Print the imported LAN domain definitions and verify the migrated definitions by doing the following: a. Log on as an administrator to the domain controller. b. Select "Definitions" from the main menu. c. Select "Print the domain definition" from the Definitions pull-down. d. Select the default printer (or the printer that applies to you) from the Device Name column on the Print Domain Definition panel. 2. Create new external resource definitions to access the current resources after they are migrated to the LAN Server 1.3 domain. For example, on an existing PCLP 1.3 domain controller called IBMDC, the directory C:\PAYROLL\PAY89 is shared with the network name PAY (with the definition NET SHARE PAY=C:\PAYROLL\PAY89), and has the following NET USE definition: NET USE E: \\IBMDC\PAY To access the PAY resource after it is migrated to the new LAN Server 1.3 domain controller (LS13DC), change the NET USE definition to the following: NET USE E: \\LS13DC\PAY 3-10 If the names of additional servers are maintained when installing LAN Server 1.3, no changes to NET USE resource definitions are required for the files resources on the additional server. For example, the network name PAY has the following NET USE definition on an additional server called ADSERV01: NET USE E: \\ADSERV01\PAY If the additional server name was maintained (ADSERV01), the NET USE definition is still valid. Since PCLP shares printer ports (such as LPT1 and LPT2), the network administrator must create printer queues for the printer resources to be shared in the LAN Server 1.3 environment. For example, a printer is defined on the existing PCLP 1.3 domain controller to be shared with the following NET SHARE and NET USE definitions: NET SHARE PRINT1 = LPT2 NET USE LPT3 \\IBMDC\PRINT1 In the LAN Server 1.3 environment, the NET SHARE and NET USE definitions are as follows: NET SHARE LPT2Q /PRINT NET USE LPT3 \\LS13DC\LPT2Q LPT2Q is the queue name created with the Print Manager for the migrated printer that is attached to the LPT1 port on server LS13DC. 3. Give the GUEST user ID access permission to those network resources required by users at PCLP workstations. 4. Verify that all user logon assignments (NET USE definitions) have been updated as required. 5. Issue the new passwords for the user IDs that require a password from the \IBMLAN\NETPROG\DCDBPSWD.DAT file that was generated during the Import phase. 6. If you have remote IPL images that were migrated, do the following: - If standard image names were migrated, use the LAN Server full-screen interface to select and make each standard image used in the RPL.MAP file. 3-11 - If nonstandard images were migrated, the network administrator must create and make each nonstandard image. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for more information. 7. For the requesters in the domain: a. Create DOS LAN Requester IPL images to replace the PCLP 1.3 Requester IPL images if remote IPL machines will continue to be supported. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for information about how to create these images. b. Install the appropriate operating system on the requesters. If the workstation will be an OS/2 requester, verify that the workstation is appropriately configured (memory and fixed-disk space), and install the OS/2 EE 1.3 program. See IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 GETTING STARTED for installation information. If the workstation will be a DOS LAN Requester, install DOS 3.3 or 4.01, the PC LAN Support Program, and the IBM DOS LAN Requester program. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED for installation information. In summary, the intermediate environment has now been created. Users at PCLP 1.3 workstations continue to log on at the PCLP domain controller. Users at DOS LAN Requesters or EE 1.3 Requesters log on to the new LAN Server 1.3 domain. The PCLP users have access to the network resources on the LAN Server 1.3 domain controller to which the GUEST user ID has been given access permission. 3-12 COMPLETING THE MIGRATION Complete the migration with the following steps: 1. Upgrade the PCLP workstations to OS/2 EE 1.3 requesters or DOS LAN Requesters. 2. Review the GUEST user ID account. Revise as necessary to restrict the access permissions. The PCLP 1.3 domain controller is no longer needed to provide logon service. This workstation can now be reconfigured as an additional server or requester as required by your network. See the IBM OPERATING SYSTEM/2 INFORMATION AND PLANNING GUIDE and the LAN Server 1.3 slipcase cover for server memory, fixed-disk, and minimum system requirements. 3-13 CHAPTER 4. MIGRATING AN ENTIRE LAN SERVER 1.0 DOMAIN AT ONE TIME This chapter describes the tasks required to migrate from a LAN Server 1.0 environment to a LAN Server 1.3 environment all at one time. The following figure shows the typical migration scenario for this environment. 4-1 Original LAN Server 1.0 Domain Final LAN Server 1.3 Domain (Domain IBMDC) (Domain IBM13DOM) ÉÍÍÍÍ» ÉÍÍÍÍ» º º by download service º º ÚÈÍÍÍͼ¿º --------------------------------->ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ PC13_W º DOS_LR º º º º ÉÍÍÍÍ» º ÉÍÍÍÍ» º ºRIPLº by RIPL image º ºRIPLº ºÚÈÍÍÍͼ¿ --------------------------------->ºÚÈÍÍÍͼ¿ ÌÀÄÄÄÄÄÄÙ create feature ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» º PC13_W ÉÍÍÍÍ» º DOS_LR º º º º º º ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ by diskette ÀÄÄÄÄÄÄÙ¹ PC13_W º --------------------------------> DOS_LR º º installation º º º º º º ÉÍÍÍÍ» º ÉÍÍÍÍ» º º º by diskette º º º ºÚÈÍÍÍͼ¿ --------------------------------> ºÚÈÍÍÍͼ¿ ÌÀÄÄÄÄÄÄÙ installation ÌÀÄÄÄÄÄÄÙ º EE11_LR º EE13_LR ÉÍÍÍÍ» º ÉÍÍÍÍ» º º º º º º º ÚÄÈÍÍÍͼĿº by diskette ÚÄÈÍÍÍͼĿº ³ADSERV01³º-------------------------------->³ADSERV01³º ÀÄÄÄÄÄÄÄÄÙ¹ installation ÀÄÄÄÄÄÄÄÄÙ¹ LS10_AS º LS13_AS º º ÉÍÍÍÍ» º ÉÍÍÍÍ» º º º º º º ºÚÄÈÍÍÍͼĿ ºÚÄÈÍÍÍͼĿ º³ IBMDC ³ by diskette º³ IBMDC ³ ÌÀÄÄÄÄÄÄÄÄÙ ------------------------------->ÌÀÄÄÄÄÄÄÄÄÙ LS10_DC installation LS13_DC ==> ==> ==> ==> ==> ==> ==> ==> ==> Migration Path Legend: PC13_W = PC LAN Program 1.3 Workstation EE11_LR = OS/2 Extended Edition 1.1 LAN Requester LS10_AS = OS/2 LAN Server 1.0 Additional Server LS10_DC = OS/2 LAN Server 1.0 Domain Controller DOS_LR = DOS LAN Requester EE13_LR = OS/2 Extended Edition 1.3 LAN Requester LS13_DC = OS/2 LAN Server 1.3 Domain Controller LS13_AS = OS/2 LAN Server 1.3 Additional Server RIPL = Remote IPL workstation. FIGURE 4-2. LAN SERVER 1.0 DOMAIN MIGRATED TO LAN SERVER 1.3 DOMAIN ALL AT ONE TIME 4-2 PREPARING THE NETWORK AND USER COMMUNITY The migration from a LAN Server 1.0 environment to a LAN Server 1.3 environment can require a hardware upgrade of the servers. For information about system, memory, and fixed-disk space requirements, see the IBM OPERATING SYSTEM/2 INFORMATION AND PLANNING GUIDE and the OS/2 LAN Server Version 1.3 slipcase cover. It is recommended that you notify system users about the upgrade to the new product release. Include the following information in this notification: - Tell users about the schedule (when their workstation will be migrated). - Tell users to back up their home directories before the migration and to restore the directories after the migration has been completed (unless the network administrator is going to do this). - Tell users that private applications (that exist on the user's workstation only) will not be migrated. Explain that these applications must be backed up to diskette and copied back onto their workstations when the migration has been completed if the partition has been formatted. - Tell users to get their new password from the network administrator after the migration has been completed. PLANNING FOR THE EXPORT PHASE Before you export the domain definitions to the temporary file, complete the following steps: 1. Print the current LAN domain definitions by doing the following: a. Log on as an administrator to the domain controller. b. Verify that no other users or administrators are logged on and accessing the DCDB. 4-3 c. Select "Definitions" from the main menu. d. Select "Print the domain definition" from the Definitions pull-down. e. Select the default printer (or the printer that applies to you) from the Printer Selection panel, and select Enter. 2. Create a backup copy of the current DCDB using one of the following methods: - For an environment with a domain controller and an additional server, you can use the DCDBBACK function. From the command line, enter the following: DCDBBACK servername /W:n /S:n /D:n The parameters in this command are as follows: servername Identifies the name of the backup (additional) server. /W:n Specifies the drive to be used as the temporarily redirected drive on the same machine. The drive specified cannot be a drive that has been redirected already. The E: drive is the default drive. /S:n Specifies the drive in which the LAN programs on the source machine are stored. The C: drive is the default drive. /D:n Specifies the drive in which the LAN programs on the destination machine are stored. The C: drive is the default drive. 4-4 - Issue the following sequence of XCOPY/COPY commands: XCOPY d:\IBMLAN\DCDB\USERS A:\IBMLAN\DCDB\USERS /S /E XCOPY d:\IBMLAN\DCDB\DEVICES A:\IBMLAN\DCDB\DEVICES /S /E XCOPY d:\IBMLAN\DCDB\PRINTERS A:\IBMLAN\DCDB\PRINTERS /S /E XCOPY d:\IBMLAN\DCDB\APPS A:\IBMLAN\DCDB\APPS /S /E XCOPY d:\IBMLAN\DCDB\FILES A:\IBMLAN\DCDB\FILES /S /E XCOPY d:\IBMLAN\DCDB\DATA A:\IBMLAN\DCDB\DATA /S /E COPY d:\IBMLAN\NETPROG\*.TXT A:\IBMLAN\NETPROG\*.TXT COPY d:\IBMLAN\NETPROG\R???PANH.LIB A:\IBMLAN\NETPROG\ COPY d:\IBMLAN\NETPROG\ROI1PANA.LIB A:\IBMLAN\NETPROG\ XCOPY d:\PCLPUSER A:\PCLPUSER /S /E XCOPY d:\IBMLAN\USERS A:\IBMLAN\USERS /S /E NOTES: a. d: specifies the drive on which LAN Server 1.0 is installed. b. This process may require more than one formatted diskette. 3. Delete any access control profiles that are out of date or are no longer required. 4. Create any profiles that will be needed by LAN Server 1.3. See "CONSIDERATIONS" on page 1-5 for more information. 5. Document all access permissions for each network resource. 6. If a global access list (the file \IBMLAN\IBMLAN.GLB) was used on the source domain controller, print the list or copy it to a diskette for future reference. EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY FILE To export the domain definitions to a temporary DCDB file, complete the following steps at the source domain controller: 1. Insert the Migration Utility diskette into the A: drive. 2. Copy the following files to the \IBMLAN\NETPROG directory: COPY A:\LS10MU.FMT d:\IBMLAN\NETPROG COPY A:\LS10MU.MSG d:\IBMLAN\NETPROG COPY A:\LS10EXPO.EXE d:\IBMLAN\NETPROG 4-5 NOTE: d: is the drive on which LAN Server 1.0 is installed. The LS10MU.FMT format file is used to generate the temporary DCDB file. The LS10MU.MSG message file logs the activities (or messages) in the history file and displays prompts to the user at the workstation. The LS10EXPO.EXE file contains the executable Export program for LAN Server 1.0. 3. Remove the Migration Utility diskette from the A: drive. 4. Start all LAN Server 1.0 servers (the domain controller and additional servers) in the domain. 5. Log on as an administrator to the domain controller. 6. Make \IBMLAN\NETPROG the current directory. 7. Enter the following to invoke the Export function: LS10EXPO path where the path parameter specifies the full path and file name of the temporary DCDB file that you want to create during the Export phase). The path can include the drive letter. For example, to create the temporary DCDB export file DCDB.TMP on the A: drive, enter the following: LS10EXPO A:DCDB.TMP In the command, LS10EXPO calls the executable Export program (LS10EXPO.EXE), which starts the Export function. The Export function reads each attribute for the LAN objects defined in the LAN Server 1.0 source domain and maps the attribute to the corresponding attribute in the LAN Server 1.3 DCDB format. The Export function then writes the attribute to a temporary DCDB file that can be edited by the network administrator as necessary. The following message is displayed when the Export function completes: Program completed successfully. 4-6 8. If you have remote IPL machine definitions, do the following: a. Enter the following to copy the RPL.MAP file to a new diskette: COPY C:\IBMLAN\DCDB\IMAGES\RPL.MAP A: b. If the remote IPL server name has changed, edit the DCDB.TMP files and the RPL.MAP file to reflect the new server name. Ensure that no extra characters or blank lines are added to the files. NOTES: 1. If the DCDB being exported is larger than one diskette, the function prompts for another formatted diskette and a new file name. The file names on the multiple diskettes should be in sequential order. 2. If an error occurs, see APPENDIX, "ERROR MESSAGES AND ERROR RECOVERY," for information about how to continue. 3. The C:\IBMLAN\NETPROG\LS10MU.HST history file is created each time the Export function is invoked. PLANNING FOR THE IMPORT PHASE Before you import the domain definitions to the new DCDB, complete the following steps: 1. Install the OS/2 EE 1.3 and LAN Server 1.3 programs on the workstation that has been designated as the new (destination) domain controller and the workstations designated as the additional servers. 2. Verify that the source server (machine) name for the domain controller in the temporary DCDB file is the same as the server (machine) name for the domain controller in the destination domain. If the names are not the same, edit the temporary file globally replacing the LAN Server 1.0 domain controller server (machine) name with the LAN Server 1.3 domain controller server (machine) name. Also, verify that all names of additional servers in the temporary file match the names of their counterpart servers in the destination domain. If they are not the same, edit the temporary file and globally replace the LAN Server 1.0 server (machine) names with the new LAN Server 1.3 server (machine) names. 4-7 NOTE: If you print the temporary DCDB file after the Export phase completes, the DCDB prints in columnar form; however, the DCDB that is displayed on your workstation (if you are using the OS/2 System Editor) is not. To display the DCDB on your workstation exactly as it is printed out, you must change the font setting on the System Editor. Do the following: 1. Select "Option" from the System Editor pull-down. 2. Select "Set fonts" from the Option pull-down. 3. Select "HELV font" from the Fonts panel. 3. Define and start all LAN Server 1.3 servers. 4. Log on as an administrator to the domain controller. 5. Create a Print Manager spooler queue for each printer to be migrated. See the IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 USER'S GUIDE, VOLUME 1: BASE OPERATING SYSTEM for information about creating spooler queues. NOTES: 1. A redirected drive cannot be used to import access control profiles. For example, if the source domain has resources on Server 1 on the D: drive and the destination domain Server 1 does not have a physical D: drive, the temporary file must be edited to change the drive designation for all resources on Server 1 from the D: drive to the C: drive. 2. The X: drive is reserved to perform the Import function. 4-8 IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN To import the domain definitions to the DCDB on the destination domain, complete the following steps at the destination domain controller: 1. Invoke the Import function of the Migration Utility using the following command: LS12IMPO path where the path parameter specifies the full path and file name of the temporary DCDB file (created during the Export phase). The path can include the the drive letter. For example, to invoke the Import function with the temporary DCDB export file DCDB.TMP located on the A: drive, enter the following: LS12IMPO A:DCDB.TMP In the command, LS12IMPO calls the Import function (which is part of the LAN Server 1.3 product and does not require installation). The Import function reads the attributes of each LAN object from the temporary DCDB file in order and writes these attributes to the new DCDB in the destination domain. A message is displayed on the workstation for each object definition that is successfully written to the new DCDB. If the Import function encounters a duplicate server and path or server and spooler queue combination, or cannot process an attribute, a message that indicates the error is displayed and the function stops. The error message is also logged in the \IBMLAN\NETPROG\LS12MU.HST file (which also contains entries for all migration activities performed). After you correct the error, edit the temporary DCDB file to correct the attribute in this file as well, and then start the Import function again using the LS12IMPO command described previously. 4-9 NOTES: a. Duplicate user, group, or resource information is ignored by the Import function (the process does not stop). However, warning messages that indicate the duplicate information are displayed on the workstation and logged in the history file. b. If you are at the C: prompt and want to print the LS12MU.HST file to locate the error, enter the following command: TYPE LS12MU.HST > PRN Before the Import function completes, it also generates the \IBMLAN\NETPROG\DCDBPSWD.DAT password file. This file contains new passwords for users that are migrated to the new LAN Server 1.3 domain. When the Import function completes, the following message is displayed: Program completed successfully. NOTE: If multiple diskettes were used to export the domain definitions, you must run the Import function on each diskette. (You will not be prompted to insert multiple diskettes.) Be sure to process the diskettes in the same sequential order in which they were created. The Import function is actually complete after the last diskette has been processed. If the Import function does not complete successfully, look through the LS12MU.HST history file to find the error. If you correct an error, you must rename the history file to preserve its entries before starting the Import function again. 2. Secure the \IBMLAN\NETPROG\DCDBPSWD.DAT password file that was generated by the Import function. 3. If access control profiles that were defined by the users have been imported, check the destination DCDB to make sure the profiles have been imported correctly. 4-10 NOTE: If a printer or serial device does not have an access control profile, the Migration Utility (during the Import phase) adds a default access control profile that grants access to the printer or serial device for all users. 4. Migrate the resources from the LAN Server 1.0 domain controller to the LAN Server 1.3 domain controller. This includes printers, serial devices, files, and applications. 5. Migrate the contents of the users' home directories on the LAN Server 1.0 domain controller to the LAN Server 1.3 domain controller. 6. If a global access list was used on the source domain, check to see if you need to create or modify the access control profiles for the resources on that list. NOTE: LAN Server 1.3 does not use global access lists. In addition, LAN Server 1.3 grants access to resources only as specified in the access control profiles. Access is denied to any resource that does not have an access control profile. 7. If you have remote IPL machine definitions, copy the RPL.MAP file to the appropriate subdirectory: COPY A:RPL.MAP C:\IBMLAN\DCDB\IMAGES COMPLETING THE MIGRATION Complete the migration with the following steps: 1. Print the imported LAN domain definitions and verify the migrated definitions by doing the following: a. Log on as an administrator to the domain controller. b. Select "Definitions" from the main menu. c. Select "Print the domain definition" from the Definitions pull-down. 4-11 d. Select the default printer (or the printer that applies to you) from the Device Name column on the Print Domain Definition panel. 2. Issue new passwords for the user IDs that require a password from the \IBMLAN\NETPROG\DCDBPSWD.DAT file that was created during the Import function. 3. If you have remote IPL images that were migrated, do the following: - If standard image names were migrated, use the LAN Server 1.3 full-screen interface to select and make each standard image used in the RPL.MAP file. - If nonstandard images were migrated, the network administrator must create and make each nonstandard image. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for more information. 4. For the requesters in the domain: a. Create DOS LAN Requester IPL images to replace the PCLP 1.3 Requester IPL images if remote IPL machines will continue to be supported. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for information about how to create these images. b. Install the appropriate operating system on the requesters. If the workstation will be an OS/2 requester, verify that the workstation is appropriately configured (memory and fixed-disk space), and install the OS/2 EE 1.3 program. See IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 GETTING STARTED for installation information. If the workstation will be a DOS requester, install DOS 3.3 or 4.01, the PC LAN Support Program, and the IBM DOS LAN Requester program. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED for installation information. 4-12 CHAPTER 5. MIGRATING A LAN SERVER 1.0 DOMAIN IN STAGES This chapter describes the tasks required to migrate from a LAN Server 1.0 domain to a LAN Server 1.3 environment over time, in stages. During this staged migration, the network administrator must install and configure an additional system as the new LAN Server 1.3 domain controller. While the network administrator is migrating the domain definitions and existing resources from the LAN Server 1.0 domain to this additional system (which will serve as the LAN Server 1.3 domain controller) and setting up the new environment, the existing LAN Server 1.0 domain controller is still providing logon service to users. It is important to note that once a server is migrated, users whose home filesets are on that server cannot log on to the domain until the migration has been completed. If there are PCLP 1.3 requesters in the LAN Server 1.0 domain, the network administrator should define appropriate access control privileges to the GUEST user ID in order to provide the required access to the LAN Server 1.3 resources from the requesters. After all PCLP 1.3 requesters have been upgraded to OS/2 EE 1.3 requesters or DOS LAN Requesters, the access privileges assigned to the GUEST user ID should be reviewed and modified as required. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for information about how to assign the access control privileges to the GUEST user ID. NOTE: Using the GUEST user ID in this situation not only allows users at PCLP 1.3 requesters to access LAN Server 1.3 resources; it also allows any user ID not defined in the LAN Server 1.3 domain to also access the LAN Server 1.3 resources. The following figure shows the typical migration scenario for this environment. 5-1 Original LAN Server 1.0 Final LAN Server 1.3 Domain Intermediate Stage Domain (Domain IBMDC) (Domains IBMDC (Domain IBM13DOM) and IBM13DOM) ÉÍÍÍÍ» ÉÍÍÍÍ» ÉÍÍÍÍ» ºRIPLº ºRIPLº ºRIPLº ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ PC13_W º ÉÍÍÍÍ» DOS_LR º ÉÍÍÍÍ» DOS_LR º ÉÍÍÍÍ» º º º º º º º º º ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ º º º PC13_W º º º PC13_W º º º DOS_LR ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÚÈÍÍÍͼ¿º ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÙ¹ EE11_LR º ÉÍÍÍÍ» EE13_LR º ÉÍÍÍÍ» EE13_LR º ÉÍÍÍÍ» º º º º º º º º º ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ºÚÈÍÍÍͼ¿ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ ÉÍÍÍÍ» ÌÀÄÄÄÄÄÄÙ º º º EE11_LR º º º EE11_LR º º º EE13_LR ÚÄÈÍÍÍͼĿº ÚÄÈÍÍÍͼĿº ÚÄÈÍÍÍͼĿº ³ADSERV01³º ³ADSERV01³º ³ADSERV01³º ÀÄÄÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÄÄÙ¹ ÀÄÄÄÄÄÄÄÄÙ¹ LS10_AS º ÉÍÍÍÍ» LS13_AS º ÉÍÍÍÍ» LS13_AS º º º º º º º º ºÚÄÈÍÍÍͼĿ ºÚÄÈÍÍÍͼĿ º º³ IBMDC ³ º³ IBMDC ³ º ÌÀÄÄÄÄÄÄÄÄÙ ÌÀÄÄÄÄÄÄÄÄÙ Ì º LS10_DC º LS10_DC º º º(EE 1.1 and º º ÉÍÍÍÍ» º PCLP Logon ÉÍÍÍÍ» º º º º º Services ) º º º º ÚÄÈÍÍÍͼĿº ÚÄÈÍÍÍͼĿº º ³ LS13DC ³¹ ³ LS13DC ³¹ º ÀÄÄÄÄÄÄÄÄÙº ÀÄÄÄÄÄÄÄÄÙº LS13_DC LS13_DC (External Resources) (Complete Control) ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> ==> Migration Path Legend: PC13_W = PC LAN Program 1.3 Workstation EE11_LR = OS/2 Extended Edition 1.1 LAN Requester LS10_AS = OS/2 LAN Server 1.0 Additional Server LS10_DC = OS/2 LAN Server 1.0 Domain Controller DOS_LR = DOS LAN Requester EE13_LR = OS/2 Extended Edition 1.3 LAN Requester LS13_DC = OS/2 LAN Server 1.3 Domain Controller LS13_AS = OS/2 LAN Server 1.3 Additional Server RIPL = Remote IPL workstation. FIGURE 5-1. LAN SERVER 1.0 DOMAIN MIGRATED TO LAN SERVER 1.3 OVER TIME IN STAGES 5-2 PREPARING THE NETWORK AND USER COMMUNITY The migration to a LAN Server 1.3 environment from a LAN Server 1.0 environment can require a hardware upgrade of the servers. For information about system, memory, and fixed-disk space requirements, see the IBM OPERATING SYSTEM/2 INFORMATION AND PLANNING GUIDE and the IBM OS/2 LAN Server Version 1.3 slipcase cover. It is recommended that you notify system users about the upgrade to the new product release. Include the following information in this notification: - Tell users about the schedule (when their workstation will be migrated). - Tell users to back up their home directories before the migration and to restore the directories after the the migration has been completed (unless the network administrator is going to do this). - Tell users that private applications (that exist on the user's workstation only) will not be migrated. Explain that these applications must be backed up to diskette and copied back onto their workstations when the migration has been completed if the partition has been formatted. - Tell users to get their new password from the network administrator after the migration has been completed. PLANNING FOR THE EXPORT PHASE Before you export the domain definitions to the temporary file, complete the following steps: 1. Connect an additional system that will serve as the new LAN Server 1.3 domain controller to the current network. See the documentation that came with your network adapter for connection information. 5-3 2. Install and configure the new system as the LAN Server 1.3 domain controller. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED for information about installing this system. NOTE: In these instructions, the LAN Server 1.3 domain name is referred to in examples as IBM13DOM and the server name for the domain controller is referred to as LS13DC. 3. On the existing (source) domain controller, print the current LAN domain definitions by doing the following: a. Log on as an administrator to the source domain controller. b. Verify that no other users or administrators are logged on and accessing the DCDB. c. Select "Definitions" from the main menu. d. Select "Print the domain definition" from the Definitions pull-down. e. Select the default printer (or the printer that applies to you) from the Printer Selection panel, and select Enter. 4. Create a backup copy of the current LAN DCDB using one of the following methods: - For an environment with a domain controller and an additional server, you can use the DCDBBACK function. From the command line, enter the following: DCDBBACK servername /W:n /S:n /D:n The parameters in this command are as follows: servername Identifies the name of the backup (additional) server. 5-4 /W:n Specifies the drive to be used as the temporarily redirected drive on the same machine. The drive specified cannot be a drive that has been redirected already. The E: drive is the default drive. /S:n Specifies the drive in which the LAN programs on the source machine are stored. The C: drive is the default drive. /D:n Specifies the drive in which the LAN programs on the destination machine are stored. The C: drive is the default drive. - Issue the following sequence of XCOPY/COPY commands: XCOPY d:\IBMLAN\DCDB\USERS A:\IBMLAN\DCDB\USERS /S /E XCOPY d:\IBMLAN\DCDB\DEVICES A:\IBMLAN\DCDB\DEVICES /S /E XCOPY d:\IBMLAN\DCDB\PRINTERS A:\IBMLAN\DCDB\PRINTERS /S /E XCOPY d:\IBMLAN\DCDB\APPS A:\IBMLAN\DCDB\APPS /S /E XCOPY d:\IBMLAN\DCDB\FILES A:\IBMLAN\DCDB\FILES /S /E XCOPY d:\IBMLAN\DCDB\DATA A:\IBMLAN\DCDB\DATA /S /E COPY d:\IBMLAN\NETPROG\*.TXT A:\IBMLAN\NETPROG\*.TXT COPY d:\IBMLAN\NETPROG\R???PANH.LIB A:\IBMLAN\NETPROG\ COPY d:\IBMLAN\NETPROG\ROI1PANA.LIB A:\IBMLAN\NETPROG\ XCOPY d:\PCLPUSER A:\PCLPUSER /S /E XCOPY d:\IBMLAN\USERS A:\IBMLAN\USERS /S /E NOTES: a. d: specifies the drive on which LAN Server 1.0 is installed. b. This process may require more than one formatted diskette. 5. Delete any access control profiles that are out of date or are no longer required. 6. If necessary, create profiles for migrated resources that do not have access control profiles. 7. Document all access permissions for each network resource. 8. If a global access list (the file \IBMLAN\IBMLAN.GLB) was used on the source domain controller, print the list or copy it to a diskette for future reference. 5-5 EXPORTING THE DOMAIN DEFINITIONS TO A TEMPORARY FILE To export the domain definitions to a temporary DCDB file, do the following at the source domain controller: 1. Insert the Migration Utility diskette into the A: drive. 2. Copy the following files to the \IBMLAN\NETPROG directory: copy A:\LS10MU.FMT d:\IBMLAN\NETPROG copy A:\LS10MU.MSG d:\IBMLAN\NETPROG copy A:\LS10EXPO.EXE d:\IBMLAN\NETPROG NOTE: d: is the drive on which LAN Server 1.0 is installed. The LS10MU.FMT format file is used to generate the temporary DCDB file. The LS10MU.MSG message file logs the activities (or messages) in the history file and displays prompts to the user at the workstation. The LS10EXPO.EXE file contains the executable Export program for LAN Server 1.0. 3. Remove the Migration Utility diskette from the A: drive. 4. Start all LAN Server 1.0 servers (the domain controller and additional servers) in the domain. 5. Log on as an administrator to the domain controller. 6. Make \IBMLAN\NETPROG the current directory. 7. Enter the following to invoke the Export function: LS10EXPO path where the path parameter specifies the full path and file name of the temporary DCDB file you want to create during the Export phase. The path can include the drive letter. For example, to create the temporary DCDB export file DCDB.TMP on the A: drive, enter the following: LS10EXPO A:DCDB.TMP 5-6 In the command, LS10EXPO calls the executable Export program (LS10EXPO.EXE), which starts the Export function. The Export function reads each attribute for the LAN objects defined in the LAN Server 1.0 source domain and maps the attribute to the corresponding attribute in the LAN Server 1.3 DCDB format. The Export function then writes the attribute to a temporary DCDB file that can be edited by the network administrator as necessary. The following message is displayed when the Export function completes: Program completed successfully. 8. If you have remote IPL machine definitions, do the following: a. Enter the following to copy the RPL.MAP file to a new diskette. COPY C:\IBMLAN\DCDB\IMAGES\RPL.MAP A: b. If the remote IPL server name has changed, edit the DCDB.TMP files and the RPL.MAP file to reflect the new server name. Ensure that no extra characters or blank lines are added to the files. NOTES: 1. If the DCDB being exported is larger than one diskette, the function prompts for another formatted diskette and a new file name. The file names on the multiple diskettes should be in sequential order. 2. If an error occurs, see APPENDIX, "ERROR MESSAGES AND ERROR RECOVERY," for information about how to continue. 3. The C:\IBMLAN\NETPROG\LS10MU.HST history file is created each time the Export function is invoked. 5-7 PLANNING FOR THE IMPORT PHASE Before you import the domain definitions to the new DCDB, complete the following steps: 1. Edit the temporary DCDB file to change all occurrences of the server name IBMDC to LS13DC. NOTES: a. Verify that the server (machine) names in the temporary file are the same names that are in the destination domain. If they are not the same, edit the temporary file and replace the LAN Server 1.0 server (machine) names with the new LAN Server 1.3 server (machine) names. b. If you print the temporary DCDB file after the Export phase completes, the DCDB prints in columnar form; however, the DCDB that is displayed on your workstation (if you are using the OS/2 System Editor) is not. To display the DCDB on your workstation exactly as it is printed out, you must change the font setting on the System Editor. Do the following: 1. Select "Option" from the System Editor pull-down. 2. Select "Set fonts" from the Option pull-down. 3. Select "HELV font" from the Fonts panel. 2. Install the OS/2 EE 1.3 and LAN Server 1.3 programs on the workstation that has been designated as the new (destination) domain controller and the workstations designated as the additional servers. 3. Define and start all LAN Server 1.3 servers. 4. Log on as an administrator to the domain controller. 5. Create a Print Manager spooler queue for each printer to be migrated. See the IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 USER'S GUIDE, VOLUME 1: BASE OPERATING SYSTEM for information about creating spooler queues. NOTES: 1. A redirected drive cannot be used to import access control profiles. For example, if the source domain has resources on Server 1 on the D: drive and 5-8 the destination domain Server 1 does not have a physical D: drive, the temporary file must be edited to change the drive designation for all resources on Server 1 from the D: drive to the C: drive. 2. The X: drive is reserved to perform the Import function. IMPORTING THE DOMAIN DEFINITIONS TO THE DESTINATION DOMAIN To import the domain definitions to the new DCDB on the destination domain, complete the following steps at the destination domain controller: 1. Invoke the Import function of the Migration Utility using the following command: LS12IMPO path where the path parameter specifies the full path and file name of the temporary DCDB file (created during the Export phase). The path can include the the drive letter. For example, to invoke the Import function with the temporary DCDB export file DCDB.TMP located on the A: drive, enter the following: LS12IMPO A:DCDB.TMP In the command, LS12IMPO calls the Import function (which is part of the LAN Server 1.3 product and does not require installation). The Import function reads the attributes of each LAN object from the temporary DCDB file in order and writes these attributes to the new DCDB in the destination domain. A message is displayed on the workstation for each object definition that is successfully written to the new DCDB. If the Import function encounters a duplicate server and path or server and spooler queue combination, or cannot process an attribute, a message that indicates the error is displayed and the function stops. The error message is also logged in the \IBMLAN\NETPROG\LS12MU.HST file (which also contains entries for all migration activities performed). After you correct the error, edit the temporary DCDB file to correct the attribute in this file as well, and then start the Import function again using the LS12IMPO command described previously. 5-9 NOTES: a. Duplicate user, group, or resource information is ignored by the Import function (the process does not stop). However, warning messages that indicate the duplicate information are displayed on the workstation and logged in the history file. b. If you are at the C: prompt and want to print the LS12MU.HST file to locate the error, enter the following command: TYPE LS12MU.HST > PRN Before the Import function completes, it also generates the \IBMLAN\NETPROG\DCDBPSWD.DAT password file. This file contains new passwords for users that are migrated to the new LAN Server 1.3 domain. When the Import function completes, the following message is displayed: Program completed successfully. NOTE: If multiple diskettes were used to export the domain definitions, you must run the Import function on each diskette. (You will not be prompted to insert multiple diskettes.) Be sure to process the diskettes in the same sequential order in which they were created. The Import function is actually complete after the last diskette has been processed. If the Import function does not complete successfully, look through the LS12MU.HST history file to find the error. If you correct an error, you must rename the history file to preserve its entries before starting the Import function again. 2. Secure the \IBMLAN\NETPROG\DCDBPSWD.DAT password file that was generated by the Import function. 3. If access control profiles that were defined by the users have been imported, check the destination DCDB to make sure the profiles have been imported correctly. NOTE: If a printer or serial device does not have an access control profile, the Migration Utility (during the Import phase) adds a default access control profile that grants access to the printer or serial device for all users. 5-10 4. Migrate the resources from the LAN Server 1.0 domain controller to the LAN Server 1.3 domain controller. This includes printers, serial devices, files, and applications. 5. Migrate the contents of the users' home directories on the LAN Server 1.0 domain controller to the LAN Server 1.3 domain controller. 6. If a global access list was used on the source domain, check to see if you need to create or modify the access control profiles for the resources on that list. NOTE: LAN Server 1.3 does not use global access lists. In addition, LAN Server 1.3 grants access to resources only as specified in the access control profiles. Access is denied to any resource that does not have an access control profile. 7. If you have remote IPL machine definitions, copy the RPL.MAP file to the appropriate subdirectory: COPY A:RPL.MAP C:\IBMLAN\DCDB\IMAGES SETTING UP THE INTERMEDIATE ENVIRONMENT Set up the intermediate environment (see Figure 5-1) with the following steps: 1. Print the imported LAN domain definitions and verify the migrated definitions by doing the following: a. Log on as an administrator to the domain controller. b. Select "Definitions" from the main menu. c. Select "Print the domain definition" from the Definitions pull-down. d. Select the default printer (or the printer that applies to you) from the Device Name column on the Print Domain Definition panel. 5-11 2. Create new external resource definitions to access the current resources after they are migrated to the new LAN Server 1.3 domain. See the printout of the imported DCDB definitions that you made earlier for the netname and server location aliases. For example, on the LAN Server 1.3 domain controller (LS13DC), the directory C:\PAYROLL\PAY89 is defined with a files alias name PAY. The PAY files alias must be redefined on the LAN Server 1.0 domain as an external files alias as follows: a. Log on as an administrator. b. Select "Definitions" from the Main Panel. c. Select the "Aliases" option. d. Select the "Files" option. e. Select the "PAY" alias. f. Select "Actions" from the action bar. g. Select the "Delete" option to delete the internal PAY files alias. h. Select "Definitions" from the Main Panel. i. Select the "Aliases" option. j. Select the "External Resources" option. k. Select "--New--" from the Manage Aliases panel. l. Select "Actions" from the action bar. m. Select the "Create" option from the Actions pull-down. The Create Alias panel is displayed. n. Complete the panel with the appropriate information, and select Enter. 5-12 o. Create the external alias batch file for OS/2 (EE 1.3 requesters) or DOS (PCLP 1.3 requesters) users with one of the following: - Select "Edit OS/2.CMD file" to create the external alias batch file for OS/2 users. - Select "Edit DOS.BAT file" to create the external alias batch file for DOS users. If both OS/2 and DOS users are to access the external resource, create a batch file for each type of user. p. Add a NET USE command to connect to the external resource by entering the command after the appropriate comment in the batch file as shown in the following: # # This is where you put in your external resource # connection commands. # NET USE %1 \\LS13DC\PAY Use the following as the corresponding disconnect command: NET USE %1 /D Repeat this process for all internal aliases (printers, serial devices, and files). Use the temporary file or printout of the LAN Server 1.3 domain definitions as the source document to convert LAN Server 1.0 alias definitions from internal to external. 3. Verify that all user logon assignments (NET USE definitions) have been updated as required. 4. Issue new passwords for the user IDs that require a password from the \IBMLAN\NETPROG\DCDBPSWD.DAT file that was generated during the Import function. The new passwords should be the same in both the LAN Server 1.0 and 1.3 domains. 5-13 5. If you have remote IPL images that were migrated, do the following: a. If standard image names were migrated, use the LAN Server 1.3 full-screen interface to select and make each standard image used in the RPL.MAP file. b. If nonstandard image names were migrated, the network administrator must create and make each nonstandard image. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for more information. 6. For the requesters in the domain: a. Create DOS LAN Requester IPL images to replace the PCLP 1.3 Requester IPL images if remote IPL machines will continue to be supported. See the IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 NETWORK ADMINISTRATOR'S GUIDE for information about how to create these images. b. Install the appropriate operating system on the requesters. If the workstation will be an OS/2 requester, verify that the workstation is appropriately configured (memory and fixed-disk space), and install the OS/2 EE 1.3 program. See IBM OPERATING SYSTEM/2 EXTENDED EDITION VERSION 1.3 GETTING STARTED for installation information. If the workstation will be a DOS LAN Requester, install DOS 3.3 or 4.01, the PC LAN Support Program, and the IBM DOS LAN Requester program. See IBM OPERATING SYSTEM/2 LOCAL AREA NETWORK SERVER VERSION 1.3 GETTING STARTED for installation information. In summary, the intermediate environment has now been created. Users at LAN Server 1.0 workstations continue to log on at the LAN Server 1.0 domain controller. Users at DOS LAN Requesters or EE 1.3 Requesters log on to the new LAN Server 1.3 domain. The LAN Server 1.0 users have access to the network resources on the LAN Server 1.3 domain controller to which the GUEST user ID has been given access permission. 5-14 COMPLETING THE MIGRATION Complete the migration with the following steps: 1. Upgrade the LAN Server 1.0 workstations to DOS LAN Requesters or OS/2 EE 1.3 requesters. If there are PCLP workstations in the LAN Server 1.0 domain, upgrade these workstations as well. 2. If you had PCLP workstations in the LAN Server 1.0 environment and assigned the GUEST user ID to the users at these workstations, review the GUEST user ID account. Revise the account as necessary to restrict the access permissions. The LAN Server 1.0 domain controller is no longer needed to provide logon service. This workstation can now be reconfigured as an additional server or requester as required by your network. See the IBM OS/2 VERSION 1.3 INFORMATION AND PLANNING GUIDE and the LAN Server 1.3 slipcase cover for server memory, fixed-disk, and minimum system requirements. 5-15 APPENDIX. ERROR MESSAGES AND ERROR RECOVERY The error descriptions in this appendix list the error message and the recovery action to be taken by the network administrator during migration to LAN Server 1.3. PCLP 1.3 EXPORT ERRORS During the PCLP 1.3 Export phase of the migration, the network administrator can receive the following user errors. The recovery action for each error is also listed. MESSAGE: Error opening output file. ACTION: The error may be caused by an invalid file name. Type the valid file name and try again. MESSAGE: Error opening format file. ACTION: The error may be caused by an invalid file name. Type the valid file name and try again. MESSAGE: Error getting free disk space on target drive. ACTION: Erase any unnecessary files on the target drive and try again. LAN SERVER 1.0 EXPORT ERRORS During the LAN Server 1.0 Export phase of the migration, the network administrator can receive the following user errors. The recovery action for each error is also listed. MESSAGE: No user is logged on this machine. ACTION: Log on to the domain controller and try again. MESSAGE: You do not have Administrator privilege. ACTION: Log off and then log on as an administrator. Message: You are not running on a domain controller. ACTION: Log off and then log on to the domain controller. MESSAGE: The definition format file does not exist. ACTION: Reinstall the export program in the \IBMLAN\NETPROG directory and try again. A-1 MESSAGE: The definition format file has internal errors. ACTION: Reinstall the export program and try again. If the problem persists, contact your service coordinator. MESSAGE: Cannot create the output file. ACTION: The error may be caused by an invalid file name. Type the valid file name and try again. MESSAGE: Cannot write to the output file. ACTION: The error may be caused by an invalid file name. Type the valid file name and try again. MESSAGE: Internal errors. The Logon assignments file cannot be accessed. ACTION: Print the domain definition. Correct any reported errors and try again. If the problem persists, use your most recent network database backup, or contact your service coordinator. MESSAGE: Program stack overflow or malloc failed. ACTION: The error may be caused by a format error in the export file. Check the export file to make sure each definition has the correct EOE (end of entry) and EOR (end of record) markers. MESSAGE: Internal errors. System files cannot be found. Files in DCDB are missing. ACTION: Print the domain definition. Correct any reported errors and try again. If the problem persists, use your most recent network database backup, or contact your service coordinator. IMPORT ERRORS During the Import phase of the migration, the network administrator can receive user and nonuser (program code) errors. USER ERRORS MESSAGE: No user is logged on this machine. ACTION: Log on to the domain controller and try again. MESSAGE: You do not have Administrator class privilege. ACTION: Log off and then log on as an administrator. A-2 MESSAGE: You are not running on a domain controller. ACTION: Log off and then log on to the domain controller. MESSAGE: Cannot open file. ACTION: Verify that the import file has the correct name and run the Migration Utility again. MESSAGE: Unrecognized command or attributes. CAUSE: The error may be caused when the user edits the import file. Check the import file to make sure each record in the file has the correct format. MESSAGE: Function is not supported. ACTION: The error may be caused when a function other than add is used. Check the import file to make sure only the add function is used. MESSAGE: Incorrect resource type specified in input file. ACTION: Check the import file to make sure the resource types are listed correctly. MESSAGE: Incorrect profile type specified in input file. ACTION: Check the import file to make sure the profile types are listed correctly. MESSAGE: Unrecognized field type in input file. ACTION: Check the import file to make sure the field types are listed correctly. MESSAGE: Insufficient memory to run program. ACTION: Erase any unnecessary files to make more memory available. MESSAGE: Insufficient privilege to access resource. ACTION: Log off and then log on as an administrator. MESSAGE: Administrative privilege required. ACTION: Log off and then log on as an administrator. MESSAGE: Incorrect parameter specified. ACTION: Check the import file to make sure the parameters are correct for the database definition. Correct the import file and try again. A-3 MESSAGE: Network name cannot be found. ACTION: The error may be caused by an invalid network name. Check the import file to make sure the network names are valid. MESSAGE: The Server service is not started. ACTION: Start the Server and try again. MESSAGE: User name not found. ACTION: Check the destination domain to make sure the user name is defined and try again. MESSAGE: Incorrect username or groupname parameter. ACTION: Check the import file to make sure the parameters are correct for the user or group definition. Correct the import file and try again. MESSAGE: Operation not allowed on special group. ACTION: Delete the special group from the import file and try again. MESSAGE: Server cannot be located. ACTION: The error may be caused by an invalid server name. Check the import file to make sure all the server names are valid. MESSAGE: The name has already been shared. ACTION: Delete the conflicting share and try the action again. MESSAGE: The operation is not allowed on a redirected resource. ACTION: Specify devices that are not redirected, or delete the assignments to the redirected devices. MESSAGE: The printer queue does not exist. ACTION: Check the printer section of the import file to identify the spooler queue names. Use the LAN Server 1.3 Print Manager to create necessary spooler queues. Try again. A-4 MESSAGE: Too many permission records. ACTION: If migrating from a PCLP 1.3 domain: 1. Determine sets of users with matching access permissions to the resource. 2. Delete these permissions and rerun the Export and Import phases. 3. Create a new group definition on the LAN Server 1.3 domain and add those users whose permissions were removed to the new group. 4. Give the group access permissions to the resources that match those of the removed users. ACTION: If migrating from a LAN Server 1.0 domain: 1. Define new groups of users to the LAN Server 1.0 domain. 2. Delete users with similar access permissions from the profile that exceeded the limit and add them to the newly defined group. 3. Give the groups access permissions to the resources that match those of the removed users. MESSAGE: Device cannot be shared as both a spooled and a non-spooled resource. ACTION: Delete the existing shares for the device or select another device for this share. MESSAGE: The drive letter is in use locally. ACTION: Try another drive letter that is not in use. MESSAGE: No more file handles. ACTION: Close a file and try again. MESSAGE: Disk full. ACTION: Delete a file or files to create more disk space and try again. MESSAGE: Error reading or writing file. ACTION: The I/O error may be caused by a bad device or media. Try again. If the problem persists, run the Export program again to create a new import file that uses a different media or device. A-5 MESSAGE: Cannot create home fileset directory. ACTION: A drive is bad or a redirected drive is already in use. Check the import history file to identify the home directory drive. Examine this drive to locate the problem. Correct the problem and try again. MESSAGE: Server and Path/Spooler Queue combination is already defined by another alias. ACTION: Determine why the other alias also uses the same UNC name. Delete the existing alias, or delete the redundant alias from the import file and try again. MESSAGE: Network path not found; possible bad UNC name. ACTION: The error may be caused by an invalid server name, netname, or path name. Check the import file to make sure these names are valid. MESSAGE: Program stack overflow or malloc failed. ACTION: The error may be caused by a format error in the import file. Check the import file to make sure each definition has the correct EOE (end of entry) and EOR (end of record) markers. MESSAGE: Cannot create path. ACTION: The error may be caused by an invalid path. Verify that the path format is valid for the operating system being used. MESSAGE: Unrecognized command or attributes. ACTION: Check the import file to verify that each record has the correct format and the file has been saved with the editor's tab option set to off. If tab characters are found or are suspected in the import file, run the Export program again. MESSAGE: Accounts database is full. ACTION: If possible, delete several network accounts and try again. If the problem persists, contact your service coordinator. MESSAGE: Cannot access accounts database. ACTION: Print the domain definition and correct network database errors. If the problem persists, use your most recent database backup, or contact your service coordinator. A-6 PROGRAM CODE ERRORS Following are nonuser (program code) errors. MESSAGE: Cannot get workstation WKS record. CAUSE: The workstation (WKS) record at the domain controller cannot be accessed. ACTION: Stop all applications currently running and stop and restart the server. Reformat and reinstall your target machine. Redo your export process. Ensure that either you or the network administrator has ADMIN privilege when logging on. If the problem persists, contact your service coordinator. MESSAGE: Incorrect parameter specified. CAUSE: An incorrect parameter was passed to a LAN API call. ACTION: Stop all applications currently running, reinstall the server code, and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: Unexpected error from DosFind Call. CAUSE: An unexpected error was received from DosFind Call. ACTION: Check the history file to identify which record caused the problem. Check the contents of the input file and make sure the file is correct. If there is a problem with the format of the input file, use the correct input file and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: Unexpected error from DosQFileMode. CAUSE: An unexpected error was received from DosQFileMode. ACTION: Check the history file to identify which record caused the problem. Check the contents of the input file and make sure the input file is correct. If there is a problem with the format of the input file, use the correct input file and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. A-7 MESSAGE: Incorrect level specified. CAUSE: The wrong data structure level was used when invoking the LAN API. ACTION: Stop all applications currently running, reinstall the server code, and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: Additional data is available. CAUSE: The buffer size for information passed to the LAN API is too small. ACTION: Ensure that the input data is correct and ended properly. Retry the operation. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: The API return buffer is too small. CAUSE: The API return buffer is too small for fixed-length data. ACTION: Stop all applications currently running, reinstall the server code, and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: Remote API error occurred. CAUSE: A remote API error has occurred. ACTION: Check the history file to identify which record caused the problem. Identify the server name in the record and ensure that the server has been started. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: An Internal error occurred when the workstation driver was called. CAUSE: An internal error occurred when the workstation driver was called. ACTION: Stop all applications currently running, reinstall the requester and server code, and restart the Migration Utility. If the problem persists, contact your service coordinator. A-8 MESSAGE: RSDE database consistency check failure. CAUSE: The checksum of information stored in the DCDB files is incorrect. Write errors, reboots during writes, or a power failure occurred. ACTION: Restore the DCDB from a backup and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: RSDE rsd_enum select function abort. CAUSE: An internal error occurred. Possible causes are: the disk is full or out of memory. ACTION: Restore the DCDB from a backup and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: DCDB file is locked. CAUSE: An error occurred. ACTION: Restore the DCDB from a backup and restart the Migration Utility. If the problem persists, have your service coordinator send both your history and input file to IBM. MESSAGE: Protection violation. CAUSE: A protection violation has occurred. ACTION: Reinstall the server code. If the problem persists, see your service coordinator and have your system dump sent to IBM. A-9 WARNING MESSAGES During the Import phase of the migration, the network administrator can receive the following warning messages: ** Warning ** An alias cannot be defined for a removable drive. ** Warning ** File path will not be created. Profile not migrated. ** Warning ** Profile path. ** Warning ** Resource name already exists. Entity not migrated. ** Warning ** Resource could not be shared at this time. ** Warning ** Profile already exists. ** Warning ** Username or group name already exists. ** Warning ** Resource name not found. Access Control not migrated. ** Warning ** Requested Device not valid. A-10