Order Number: AA-R6G3A-TE

This guide describes how to upgrade the DIGITAL PATHWORKS V5 for OpenVMS (LAN Manager) software to DIGITAL PATHWORKS V6 for OpenVMS (Advanced Server) software. It contains the preliminary information you need to plan an effective migration.

Revision/Update Information: This guide supersedes the PATHWORKS for OpenVMS Server Migration Guide, part number AA-Q2FYC-TE .

Operating System and Version: DIGITAL OpenVMS Version 7.1

Software Version: DIGITAL PATHWORKS V6 for OpenVMS (Advanced Server)

Digital Equipment Corporation
Maynard, Massachusetts

First Printing, March 1994
Revised, August 1997

Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor.

© Digital Equipment Corporation 1997. All rights reserved.

The following are trademarks of Digital Equipment Corporation:

Alpha, Compaq, DECdirect, DECnet-Plus, DECprint, DIGITAL, OpenVMS, PATHWORKS, VAX, VAX DOCUMENT, VAXcluster, VMS, and the Compaq logo.

The following are third-party trademarks:

AT&T is a registered trademark of American Telephone and Telegraph Company.
Apple, AppleShare, LaserWriter, Macintosh, and TRUETYPE are registered trademarks of Apple Computer, Inc.
DEC Rdb is a trademark of Oracle Corporation.
Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.
IBM and OS/2 are registered trademarks of International Business Machines Corporation.
Microsoft, MS-DOS, and Windows are registered trademarks, and Windows 95, Windows 98, and Windows NT are trademarks of Microsoft Corporation.
MultiNet and TCPWARE are registered trademarks of Process Software Corporation.
Novell and NetWare are registered trademarks of Novell, Inc.
PostScript is a registered trademark of Adobe Systems Incorporated.

All other trademarks and registered trademarks are the property of their respective holders.

The DIGITAL PATHWORKS for OpenVMS documentation set is available on CD-ROM.

Contents

Index

About this Guide

Welcome to the DIGITAL PATHWORKS for OpenVMS (Advanced Server) Server Migration Guide. PATHWORKS and its associated OpenVMS system platform provide a powerful, reliable, and versatile operating environment that meets the demands of client-server computing. For the purpose of this guide, the PATHWORKS for OpenVMS (Advanced Server) is referred to as the PATHWORKS Advanced Server.

This guide describes how to migrate a server from PATHWORKS LAN Manager to PATHWORKS Advanced Server. It addresses the issues in upgrading existing PATHWORKS LAN Manager configurations and identifies areas that may require additional system management tasks.

You can reduce interruption in services to your users by carefully planning your migration and by implementing your migration in phases. In this way, you can introduce a new functionality without impacting existing functionality.

Audience

This guide is for OpenVMS network administrators who plan to migrate from PATHWORKS LAN Manager to PATHWORKS Advance Server. It assumes you have:

• A basic understanding of a PC LAN and WAN network
• A basic understanding of OpenVMS system management
• Access to PATHWORKS V6 for OpenVMS (Advanced Server) documentation

Organization of this Guide

This guide contains the following sections:

Section	Description
Chapter 1, Planning for Advanced Server Migration	Describes the PATHWORKS Advanced Server software and summarizes the differences between PATHWORKS LAN Manager and PATHWORKS Advanced Server.
Chapter 2, Overview of the Migration Process	Describes the steps in the server migration process.
Chapter 3, Changing Server Roles and Domain Names	Describes when and how to change the role of servers
Chapter 4, Installing the Upgrade Utility	Explains how to install the Upgrade utility.
Chapter 5, Upgrading Your Server Information	Explains how to generate upgrade reports and upgrade the server.
Chapter 6, Completing the Migration	Describes the tasks you perform after you upgrade the server information.
Chapter 7, Verifying the Migration	Explains how to verify the migration by checking interfaces, services and event logs.
Appendix A, Files Created by the Upgrade Utility	Describes the files created by the Upgrade utility.
Appendix B, Resolving Log File Error Messages	Describes Upgrade utility error messages and warnings.
Appendix C, Editing Upgrade Reports	Describes how to resolve errors in Upgrade reports.
Appendix D, Migration Worksheet	Contains a worksheet you can use to collect information for the upgrade. The worksheet is only available in the printed copy of this guide.

Related Documents

The following documents are part of the PATHWORKS Advanced Server documentation set. Reference these documents for complete descriptions and procedural information about DIGITAL PATHWORKS Advanced Server utilities and software interfaces.

Document	Description
PATHWORKS for OpenVMS Server Installation and Configuration Guide	Explains how to install and configure PATHWORKS for OpenVMS (Advanced Server) software.
Advanced Server for OpenVMS Concepts and Planning Guide	Provides an overview of and introduction to the PATHWORKS for OpenVMS (Advanced Server) software and associated networking concepts for system administrators and operators.
PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide	Explains how to manage and customize the PATHWORKS for OpenVMS (Advanced Server) software.
Advanced Server for OpenVMS Commands Reference Manual	Provides command syntax descriptions for all ADMINISTER commands and NET command equivalents.
Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses	Describes the license server software and how to manage PATHWORKS for OpenVMS (Advanced Server) licenses.

The following table lists related OpenVMS documents.

OpenVMS Document	Description
OpenVMS Alpha V7.1 Upgrade and Installation Manual	Describes how to install the OpenVMS Alpha V7.1 system software.
OpenVMS Alpha V7.2 Upgrade and Installation Manual	Describes how to install the OpenVMS Alpha V7.2 system software.
OpenVMS VAX V7.1 Upgrade and Installation Manual	Describes how to install the OpenVMS VAX V7.1 system software.
OpenVMS VAX V7.2 Upgrade and Installation Manual	Describes how to install the OpenVMS VAX V7.2 system software.
OpenVMS System Manager's Manual	A task-oriented guide to managing an OpenVMS system.
OpenVMS System Management Utilities Reference Manual	A reference guide to the utilities and tools used in managing an OpenVMS system.
OpenVMS License Management Utility Manual	Explains how to load and manage license Product Authorization Keys (PAKs)

Conventions

The following conventions are used in the Advanced Server documentation set:

Convention	Meaning
[Ctrl/] x	While you hold down the Ctrl key, press another key or a pointing device button.
Italic	Indicates a place holder for information or parameters that you must provide. For example, if the procedure asks you to type file-name, you must type the actual name of a file. Italics also indicate path names, new terms, and the titles of other documents.
monospace	Indicates the actual commands, words, or characters that you type in a dialog box or at a command prompt or system output.
Note:	Provides information of special importance.
Caution:	Provides information to avoid damaging the software or hardware.
Warning:	Provides information that is essential to people's safety.
/	A forward slash in command descriptions indicates that a command qualifier follows.
...	A horizontal ellipsis following an entry in a command line indicates that the entry or a similar entry can be repeated any number of times. An ellipsis following a file name indicates that additional parameters, values, or information can be entered.
. . .	A vertical ellipsis in an example indicates that not all the data is shown.

Before you begin the migration process, you need to understand the differences between PATHWORKS LAN Manager and PATHWORKS Advanced Server so you can plan for the changes PATHWORKS Advanced Server presents to your network environment. This section describes these differences and includes the following topics:

• About the PATHWORKS Advanced Server --- describes the PATHWORKS Advanced Server interoperability with PATHWORKS LAN Manager servers.
• Server Administration Differences --- describes the differences between the PATHWORKS LAN Manager and the PATHWORKS Advanced Server.
• LAN Manager Features That Are Not Supported --- describes those features of the PATHWORKS LAN Manager that are not supported under the PATHWORKS Advanced Server.
• Client Impact --- describes the impact of server migration to the PATHWORKS Advanced Server in the client environment.
• LAN Manager Impact --- describes the impact of server migration to the PATHWORKS Advanced Server in the PATHWORKS LAN Manager environment.
• Server License Requirements --- describes the licensing requirements for PATHWORKS Advanced Server.

A PATHWORKS LAN Manager server can be upgraded to a PATHWORKS Advanced Server or can continue running PATHWORKS LAN Manager and act as a backup domain controller (BDC), member server, or standalone server in a domain in which the primary domain controller (PDC) is a PATHWORKS Advanced Server or a Windows NT Server computer.

PATHWORKS Advanced Server maintains compatibility with LAN Manager client and server software. You can gradually integrate a PATHWORKS Advanced Server into an existing network and migrate to the new technology at your own pace.

1.2.1 Domain Composition

Both the PATHWORKS Advanced Server and the LAN Manager server organize clients and servers into domains. Every domain has one database that contains user accounts, group accounts, and security policy settings. Every server in the domain that is running the PATHWORKS Advanced Server maintains a copy of this database.

The minimum requirement for a domain is one server running either PATHWORKS Advanced Server (OpenVMS or DIGITAL UNIX) or Windows NT Server software. This computer serves as the PDC and stores the master copy of the domain's user and group database. A domain can contain only one PDC. A domain can include other servers running PATHWORKS Advanced Server (OpenVMS or DIGITAL UNIX), Windows NT Server software, or LAN Manager 2.x servers, acting as BDCs or member servers. Clients include Windows NT workstation computers, and other clients such as those running Windows for Workgroups and MS-DOS clients running PATHWORKS.

For more information about PATHWORKS Advanced Server domains, see the Advanced Server for OpenVMS Concepts and Planning Guide.

1.2.2 LAN Manager Servers

In a domain containing LAN Manager and PATHWORKS Advanced Servers, LAN Manager backup, member, and standalone servers function in the same way as they do in a LAN Manager-only domain. However, LAN Manager BDCs cannot validate Windows NT domain logons nor can they be promoted to PDCs in domains that include PATHWORKS Advanced Server servers.

1.2.3 NetWare Servers

If you are running the PATHWORKS for OpenVMS NetWare server on the same system, you must upgrade the NetWare server as well as the PATHWORKS Advanced Server. The NetWare server is upgraded automatically when you install the PATHWORKS Advanced Server. No separate upgrade procedure is required.

1.2.4 PATHWORKS License Servers

A PATHWORKS standalone license server runs the PATHWORKS license server but not the PATHWORKS LAN Manager or NetWare server. A standalone license server requires no special upgrade procedures to migrate from PATHWORKS LAN Manager to PATHWORKS Advanced Server. Follow the procedures described in the PATHWORKS for OpenVMS Server Installation and Configuration Guide for installing and configuring the standalone license server.

The following table describes the basic differences between PATHWORKS LAN Manager and PATHWORKS Advanced Server, and the impact these differences have on server administration as it pertains to:

• Server roles
• Domain trust relationships
• Users and groups
• Server administration
• OpenVMS clusters
• Security
• Share access
• Privileges

The sections following the table describe these differences in more detail.

Table 1-1 Server Administration Differences

PATHWORKS LAN Manager	PATHWORKS Advanced Server
Server Roles
Servers can be defined as any of the following: PDC BDC Member Standalone	Servers can be defined as one of the following: PDC BDC
Migration Impact: You need to change roles for servers currently defined as member servers and standalone servers to PDC or BDC. For more information, see Chapter 3, Changing Server Roles and Domain Names, in this guide.
Domain Trust Relationships
Servers provide access to file and print services for users of the local domain only. Does not support trust relationships.	Servers provide access to file and print services for users of the local domain and can be defined with trust relationships to provide access to specified users in other domains.
Migration Impact: You have more flexibility in domain management and can continue to provide services during migration. Trust relationships can be established after the server is running PATHWORKS Advanced Server. For more information, see the Advanced Server for OpenVMS Concepts and Planning Guide.
Users and Groups
You can organize users into global groups, providing access to domain services.	You can organize users into global groups for access to local domain services. Users from other domains may optionally be included in local groups to access services or resources in the local domain.
Migration Impact: You have more flexibility in domain management. You can establish local groups after the migration process is complete. For more information, see the Advanced Server for OpenVMS Concepts and Planning Guide.
Server Administration
Server administration from: ADMIN/PATH character cell interface LAN Manager Net commands command line interface Clients running ManageWORKS software Clients running LAN Manager Clients running Windows NT server administration tools Clients running Windows NT Server software LAN Manager servers	Server administration from: ADMINISTER commands DCL interface Clients running LAN Manager (limited functionality) Clients and servers running Windows NT server administration tools Clients and servers running Windows NT Server software Servers running Advanced Server for DIGITAL UNIX software
Migration Impact: You must become familiar with the PATHWORKS Advanced Server command line interface. For more information see the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide and the Advanced Server for OpenVMS Commands Reference Manual.
Domain Logon Server
A specific logon server may be specified in each user's account. The user's domain logon request is processed by this server each the user connects.	Client account information does not include a logon server. The server with the lightest load processes the user's domain logon request.
Migration Impact: Administrators can no longer explicitly specify which domain server validates the client domain logon request. For more information about logon requests, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
Security
You can set the security model to any one of the following: LAN Manager only LAN Manager and OpenVMS LAN Manager and Creator	You can define the security model as one of the following: Advanced Server only model Advanced Server and OpenVMS model
Migration Impact: You must determine whether the server will perform only Advanced Server security or both OpenVMS and Advanced Server security. PATHWORKS Advanced Server is the default security mode. If you choose both OpenVMS and Advanced Server security mode, the OpenVMS security in effect is determined by the OpenVMS account to which the PATHWORKS Advanced Server account maps. For more information, refer to the Advanced Server for OpenVMS Concepts and Planning Guide.
Share Access
You can manage access to shares with share-specific passwords. The share access modes supported are: User-level security Share-level security	The share access modes supported are: User-level security You can provide user access to shares through group membership. You can also set individual permissions for share access; however, it is much easier to administer group permissions.
Migration Impact: For V5 servers running with share-level security, after you upgrade, you must define groups for access to shares. You can also grant permissions for individual users to the shares (now running user-level security). The PATHWORKS Advanced Server software does not request share passwords. For more information, refer to Section 1.3.5.2, Share Security in this guide, or the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
Account Privileges
Privileges are set individually. Each user account may have privileges attached.	Privileges are set by group membership. Predefined user groups have associated levels of access to management resources.
Administrator and operator privileges are designated by assigning Admin or Operator privilege in the user account.	Default Administrator and Operator groups are created when Advanced Server is installed. You grant administrator or operator privilege to a user by adding the user to the appropriate group.
Migration Impact: Users with current assigned privileges are upgraded to the respective privileged group. Refer to the Advanced Server for OpenVMS Concepts and Planning Guide for more information about differences between PATHWORKS LAN Manager and PATHWORKS Advanced Server.

Refer to the Advanced Server for OpenVMS Concepts and Planning Guide for complete information about Advanced Server differences.