To create and edit the Security report, follow these steps:

1. From the Generate Upgrade Reports screen, select the Create button next to Security report.
2. Select the Edit button next to the Security report, as shown in the following figure.

   Figure 5-31 Generate Security Report Screen

   ---

   
   The system displays the Select a Text Editor screen as shown in Figure 5-25. The editor you chose previously is the default editor.
3. Select the OK button. The Security report is displayed with a list of the PATHWORKS LAN Manager share paths for each share that needs its security upgraded to PATHWORKS Advanced Server as shown in the following figure.

Figure 5-32 Security Report Screen

The Security report lists the root directory of each share contained in the share report. The security upgrade checks all shares from each directory in the Security report, converting PATHWORKS LAN Manager security to PATHWORKS Advanced Server security. If there are directories in the report that you do not want to upgrade, then add a backslash (\) in front of the directory name, or delete the name from the report.

5.6.7.4.1 Security Upgrade Restrictions

Note the following security upgrade restrictions:

• If a file is open during the security upgrade, the security access information on the file will be upgraded. You have the option of editing the Security report and upgrading these files later, after the files are closed. Or, you can enable the dynamic security upgrade when running the PATHWORKS Advanced Server. For information about how to enable dynamic security, refer to Section 5.3, How the Upgrade Utility Works, in this guide.
• If you have a group deny security ACE, it will not upgrade.

After you finish editing the report, exit the editor. The system returns you to the Generate Upgrade Reports screen. Refer to Appendix B, Resolving Log File Error Messages, in this guide, for information about how to edit the Security report.

5.6.7.4.2 Upgrading Miscellaneous Components (Security Policy Parameters)

Security policy parameters are system-wide settings, such as password length or password expiration. These settings are upgraded when you start the upgrade if you selected the Miscellaneous option in the Select V5 Objects to Upgrade screen. If you did not select the Miscellaneous option, follow these steps:

1. From the Generate Upgrade Reports screen, select Back to return to the Select Objects to Upgrade screen.
2. From the Select Objects to Upgrade screen, select the Miscellaneous option. There is no upgrade report for the Miscellaneous option.
3. When all of the Upgrade reports are accurate, and you are ready to start the Upgrade, make sure the Miscellaneous option is selected on the Start and Track the Upgrade screen.

The security parameters will be upgraded automatically when you start the upgrade.

5.6.8 Step 6: Start and Track the Upgrade

When the upgrade reports are accurate, you can start and track the upgrade from the Start and Track the Upgrade screen as shown in the following figure.

Figure 5-33 Start and Track the Upgrade Screen

All the objects you selected in the Select V5 Objects to Upgrade screen for the upgrade should be listed 'Selected' on the Start and Track the Upgrade screen.

Follow these steps to upgrade any objects not marked 'Selected' in the Start and Track the Upgrade screen:

1. Select the Back button to return to the Select Objects to Upgrade screen.
2. From the Select Objects to Upgrade screen, select the missing object.
3. Create and edit the upgrade report if necessary.

The Upgrade utility displays a warning as shown in the following figure.

Figure 5-34 Security Warning Screen

When you have accurate reports that accurately reflect your desired V6 environment, you can start the upgrade as follows:

1. On the Start and Track the Upgrade screen, select the Start button to activate the upgrade. The Start Options dialog box displays, as shown in the following figure.

Figure 5-35 Start Options Dialog Box

The Start Options Dialog Box allows you to choose the start options shown in the following table:

Table 5-6 Start Options

To...	Select the...
Display a running status of the upgrade	Display detailed running status option.
Start the upgrade	Start button.
Cancel the upgrade and return to the previous screen, where you can edit the upgrade report	Cancel button or enter Ctrl/Z.

5.6.8.1 When the Upgrade Completes

Table 5-7 Upgrade Status Messages

Upgrade Status	Meaning
Passed	Upgrade completed without warnings
Warnings	Upgrade encountered warnings or errors

If there are no warnings and the upgrade was successful, you can exit the Upgrade utility. Warnings may be informational, but you should review them before you exit the Upgrade utility.

If the upgrade partially or completely fails, see Section 5.7, Troubleshooting, in this guide.

5.7 Troubleshooting

This section describes how to troubleshoot:

• Problems that may occur during the upgrade.
• Problems that may occur after the upgrade.

If the upgrade partially or completely fails, the system returns you to the Start and Track the Upgrade screen and prompts you to display the log file. Select the Logfile button to display messages logged during the upgrade. You can also display the log file at the DCL prompt as described in Appendix B, Resolving Log File Error Messages, in this guide.

Figure 5-36 Log File Screen

See Appendix B, Resolving Log File Error Messages, in this guide, for more information on troubleshooting.

5.7.2 Resolving Problems After the Upgrade

After the upgrade, you may need to repeat the upgrade process if any of the following problems occur:

• The PATHWORKS Advanced Server will not start.
• A component failed to upgrade or failed to upgrade properly.

If you need to repeat the upgrade, delete the PATHWORKS Advanced Server database files created by the Upgrade utility, described in Appendix A, Files Created by the Upgrade Utility.

After you upgrade the PATHWORKS Advanced Server information, you can complete the migration. This section includes the following topics:

• Scheduling an Interruption of Services --- explains why you must schedule downtime prior to installing the PATHWORKS Advanced Server software.
• Before You Install the PATHWORKS Advanced Server Software --- describes how to enable a Roll Back procedure in the event a server is not upgraded properly.
• Installing and Starting the PATHWORKS Advanced Server Software --- describes how to install the PATHWORKS Advanced Server software.
• Setting Up Licensing --- describes how to set up licensing for the PATHWORKS Advanced Server.

When you install the PATHWORKS Advanced Server, it will shut down the PATHWORKS LAN Manager server and replace PATHWORKS V5 LAN Manager images with PATHWORKS Advanced Server images. Therefore, you must schedule downtime on the server prior to installation to avoid an unexpected interruption of services.

6.3 Before You Install the PATHWORKS Advanced Server Software

PATHWORKS Advanced Server provides a Roll Back procedure that allows you to restore the PATHWORKS LAN Manager server database if the server is not upgraded properly. To enable the Roll Back procedure, you must answer Yes to the following prompt during the VMSINSTAL procedure:

Do you want to preserve the V5 (LAN Manager) environment [Yes]? Yes

The system will prompt you for a location to store the saveset the procedure will create. The Roll Back procedure needs this saveset to restore the LAN Manager environment.

Refer to the PATHWORKS for OpenVMS Server Installation and Configuration Guide for more information on the VMSINSTAL procedure.

6.4 Installing and Starting the PATHWORKS Advanced Server Software

After you have upgraded server information, you can install and configure the PATHWORKS Advanced Server software.

Start the PATHWORKS Advanced Server using the
SYS$STARTUP:PWRK$STARTUP.COM procedure, also described in the PATHWORKS for OpenVMS Server Installation and Configuration Guide.

6.4.1 Starting PDCs

After completing the installation and configuration, make sure you start the PATHWORKS Advanced Server on the PDC first.

6.4.2 Starting BDCs

After completing the installation and configuration, follow these steps:

1. On the domain PDC, remove this PDC's listenname (computer name). Or, if the node is a member of a VMScluster, remove the PATHWORKS cluster alias name from the SERVERS group, if present.
   If you do not remove the BDC's listenname from the SERVERS group on the PDC, the PDC will log the following warning message:

   NetLogon has detected two machine accounts for server <servername>. The server can be either a Windows NT Server that is a member of the domain or the server can be a LAN Manager server with an account in the SERVERS global group. It cannot be both."

   
   If the BDC was previously a PATHWORKS LAN Manager BDC or member server in this domain, a special user account (often referred to as the machine account) is created and made a member of the SERVERS group. This account is used for account replication purposes. Now that the server is running PATHWORKS Advanced Server, a different method of domain membership is utilized. To allow the PATHWORKS Advanced Server BDC to operate properly in the domain, you must remove this BDC's machine account from the SERVERS group on the PDC.
   For example, if the BDC computername is DOROTHY, and the PDC is running PATHWORKS Advanced Server, remove this name from the SERVERS group as follows:

   \\domain\server> MODIFY GROUP SERVERS/REMOVE=DOROTHY

2. Start PATHWORKS Advanced Server on the BDC.

To set up licensing for the PATHWORKS Advanced Server, follow these steps:

1. Register and load client-access (PWLMXXXCA06.00) license PAKs, as described in the OpenVMS License Management Utility Manual.
2. Configure automatic license upgrade. (Optional)
3. Use the License Manager to allocate licenses to clients or to server-based licensing, as described in the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.

By default, the PATHWORKS license server does not perform license upgrades. To configure a PATHWORKS License Server to upgrade PATHWORKS LAN Manager licenses to PATHWORKS Advanced Server licenses, edit the PATHWORKS license server start-up command file SYS$STARTUP:PWRK$LICENSE_S_START.COM to include the following logical name definition:

$ DEFINE PWRK$LS_V6_ACCESS_UPGRADE 1

Define this logical before the following command:

$ RUN SYS$SYSTEM:PWRK$LICENSE_SERVER

If the PWRK$LS_V6_ACCESS_UPGRADE logical is undefined or defined to be zero (0), the PATHWORKS license server will not upgrade licenses. If the PWRK$LS_V6_ACCESS_UPGRADE logical is defined to be any numeric value other than zero, clients requesting assignment or verification of PATHWORKS LAN Manager licenses will have their licenses upgraded to PATHWORKS Advanced Server licenses, provided sufficient PATHWORKS Advanced Server licenses exist.

When an upgrade operation occurs, the PATHWORKS license server logs both the assignment of the PATHWORKS Advanced Server license and the name of the license returned to the client to the following PATHWORKS license server log file:

PWRK$Logs:PWRK$License_Server_node-name.LOG

Be aware that when an equivalent PATHWORKS Advanced Server license is returned to the client, the name of the license assigned (PWLMXXXCA06.00) will not match the name of the license returned to the client. For example, if a client requests assignment of a PWLMXXXFP05.00 license (a PATHWORKS LAN Manager license) from the PATHWORKS license server, the PATHWORKS license server will upgrade the request to a PATHWORKS Advanced Server license and assign a PWLMXXXCA06.00 license (assuming one is available). However, the name of the license returned to the client will be PWLMXXXFP06.00.

The reason for this difference is that the client will only accept licenses of the type requested (such as PWLMXXXFPmm.nn) with the requested or higher version number (that is, 05.00 or higher). To get the client to accept an equivalent PATHWORKS Advanced Server license, the PATHWORKS license server returns a different name than that assigned.

From the client's perspective, the license assigned is PWLMXXXFP06.00 and the client will accept that. From the PATHWORKS license server's perspective (as displayed by the PATHWORKS License Manager), the client was assigned a PWLMXXXCA06.00 license. For more information on the names of the licenses returned to clients due to upgrade operations, see the Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.

After the migration, you should verify that the server is working properly. This section describes how to verify the migration, and includes the following topics:

• Displaying Domain Servers and Users --- describes how to use the ADMINISTER command to display the domain and the users.
• Displaying Services --- describes how to use the ADMINISTER command to check services.
• Verifying Client Access --- describes how to verify client access to shares.
• Verifying Printer Access --- describes how to verify client access to printers.
• Displaying Event Logs --- describes how to use the ADMINISTER command to check event logs.
• How to Roll Back to PATHWORKS LAN Manager --- describes the PATHWORKS Advanced Server Roll Back procedure to use for restoring the PATHWORKS LAN Manager environment if the server was not upgraded properly.

For more information about how to perform these administrative tasks, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.

7.2 Displaying Domain Servers and Users

To ensure the server is set up in the domain properly, start the server, then use the ADMINISTER commands to display the domain and the users as follows:

1. At the DCL prompt, enter the ADMINISTER command:

   $ ADMINISTER LANDOFOZ\\TINMAN>

   
   The prompt indicates the current domain name and local server.

2. To check all upgraded servers and domain member computers, enter the SHOW COMPUTERS command:

   LANDOFOZ\\TINMAN> SHOW COMPUTERS Computers in domain "LANDOFOZ": Computer Type Description ---------------- -------------------- ------------------ [PD] TINMAN OpenVMS 3.51 Primary PATHWORKS V6.0 for OpenVMS (Advanced Server) Total of 1 computer

3. To display the user account information for the domain, enter the SHOW USERS command:

   LANDOFOZ\\TINMAN> SHOW USERS User Name Full Name Type Description ---------------- -------------- ------ ---------------- Administrator Global Built-in account for administering the domain Guest Global Built-in account for guest access to the domain LION Global Total of 3 user accounts

4. To display the list of groups defined for a domain, enter the SHOW GROUPS command:

   LANDOFOZ\\TINMAN> SHOW GROUPS Groups in domain "LANDOFOZ" Group Name Type Description ------------------- ------ ----------------------------- Account Operators Local Members can administer domain user and group accounts Administrators Local Members can fully administer the domain Backup Operators Local Members can bypass file security to back up files Domain Admins Global Designated administrators of the domain Domain Guests Global All domain guests Domain Users Global All domain users Guests Local Users granted guest access to the domain Print Operators Local Members can administer domain printers Replicator Local Supports file replication in a domain Server Operators Local Members can administer domain servers Users Local Ordinary users Lion Local Ordinary users Total of 11 groups

5. To display the members of a group, enter the SHOW GROUPS command:

   LANDOFOZ\\TINMAN> SHOW GROUPS/MEMBERS Groups in domain "LANDOFOZ": Group Name Type Description -------------------- ------ ----------------------------- Account Operators Local Members can administer domain user and group accounts Members: (No members) Administrators Local Members can fully administer the domain Members: [US] Administrator, [GR] Domain Admins Backup Operators Local Members can bypass file security to back up files Members: (No members) Domain Admins Global Designated administrators of the domain Members: [US] Administrator Domain Guests Global All domain guests Members: [US] Guest Domain Users Global All domain users Members: [US] Administrator Guests Local Users granted guest access to the domain Members: [GR] Domain Guests Print Operators Local Members can administer domain printers Members: (No members) Replicator Local Supports file replication in a domain Members: (No members) Server Operators Local Members can administer domain servers Members: (No members) Users Local Ordinary users Members: [GR] Domain Users Total of 11 groups

6. To display shared resource availability, enter the SHOW SHARES command:

   LANDOFOZ\\TINMAN> SHOW SHARES Shared resources on server "LANDOFOZ": Name Type Description -------------------- ------------- ----------------------- NETLOGN Directory Logon Scripts Directory PWUTIL Directory PATHWORKS Client-based Utilities USERS Directory Users Directory Total of 3 shares

   
   

To add a share or for detailed information on procedures using the ADMINISTER command, refer to the PATHWORKS for OpenVMS (Advanced Server) Server Administrator's Guide.

If you encounter error messages using these commands, refer to the Advanced Server for OpenVMS Commands Reference Manual for information on command syntax.