HP OpenVMS Systems Documentation
DIGITAL PATHWORKS for OpenVMS (Advanced Server)
Server Migration Guide
Order Number: AA-R6G3A-TE
August 1997 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
First Printing, March 1994
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
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.
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.
This guide is for OpenVMS network administrators who plan to migrate from PATHWORKS LAN Manager to PATHWORKS Advance Server. It assumes you have:
Organization of this Guide
This guide contains the following sections:
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.
The following table lists related OpenVMS documents.
The following conventions are used in the Advanced Server documentation set:
Digital Equipment Corporation recommends that you install a standalone license server before upgrading LAN Manager and NetWare servers, for continuous licensing services.
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:
|PATHWORKS LAN Manager||PATHWORKS Advanced Server|
Servers can be defined as any of the following:
Servers can be defined as one of the following:
Migration Impact: You need to change roles for servers
currently defined as member servers and standalone servers to PDC or
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
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 from:
Server administration from:
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
For more information about logon requests, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
You can set the security model to any one of the following:
You can define the security model as one of the following:
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.
You can manage access to shares with share-specific passwords. The
share access modes supported are:
The share access modes supported are:
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 18.104.22.168, Share Security in this guide, or the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.
|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.