To allow clients that are configured for WINS support to use an Advanced Server alias name to connect to a clustered Advanced Server across a WAN, you must add to the WINS database a static multihomed entry for the Advanced Server alias name.

When adding the static multihomed entry for the Advanced Server alias name, you should enter the TCP/IP address of each node in the OpenVMS Cluster that is running the Advanced Server.

For more information about adding static entries to the WINS database, refer to your WINS product documentation.

You can configure the Advanced Server as a DNS client. This allows the Advanced Server to use a DNS server for NetBIOS name resolution. The Advanced Server uses DNS for name resolution as a last resort if all other methods fail to resolve a NetBIOS name.

For more information on how to use the Configuration Manager to configure the Advanced Server to use DNS, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide.

This chapter describes how to remove Advanced Server for OpenVMS software from your system.

If you have to reinstall the Advanced Server for OpenVMS software, you might first need to remove the Advanced Server for OpenVMS software.

For example, if the Installation Verification Procedure indicated that the software installation procedure failed, you must reinstall the software. But first you might need to remove the Advanced Server software.

• If the system has enough free disk space, you can install the server again without removing the Advanced Server.
• If the system does not have enough disk space, you must remove the Advanced Server before reinstalling it.

For more information about disk space requirements, see Section 1.8.9, Step 9: Check Disk Space Requirements.

This chapter consists of the following sections:

• Section 7.1, Advanced Server Deinstallation
• Section 7.2, Removing Advanced Server Configuration Parameters
• Section 7.3, Removing Advanced Server for OpenVMS Software
• Section 7.4, Sample Advanced Server Removal Procedure

You remove the Advanced Server using the PRODUCT REMOVE command. The removal procedure performs the following operations:

• Shuts down the server automatically.
• Prompts you to enter information necessary to complete the removal procedure.
• Attempts to start the OpenVMS Registry Server if registry services are not available.
• Removes all Advanced Server for OpenVMS images, support files, and logical names that are created during the installation procedure.
• Prompts you whether to remove all Advanced Server data files from the system. If you respond YES, it deletes the data files as well as all known Advanced Server keys and values in the OpenVMS Registry. If you respond NO, it creates a file that contains a list of all Advanced Server parameters that were in the OpenVMS Registry before removing the server software.
• Removes the Advanced Server user accounts if you delete the data files.
• Prompts you whether you want to remove clean up tools that are provided with the Advanced Server. These tools include PWRK$FIXACE and PWRK$DELETEACE. For more information about these tools, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide.
• Prompts you whether you want to save the NETBIOS image SYS$COMMON:[SYSEXE]NETBIOS.EXE (if it was installed) so that you can restore it if necessary. For example, you might discover later that it is needed by another product. (Older versions of the Advanced Server for OpenVMS and PATHWORKS for OpenVMS require the NETBIOS image.) Depending on your response to this prompt, the procedure saves or deletes several other related files. The saved files are stored in SYS$COMMON:[SYSUPD.PWRK$SAFETY].
• Removes the NETBIOS$ACCESS OpenVMS identifier, unless you choose to save the NETBIOS image.
• Removes Advanced Server DECnet objects, unless you choose to save the NETBIOS image.
• Deassigns all Advanced Server logical names.
• Removes any old Advanced Server files from SYS$SPECIFIC, such as patches, that might have been copied there.

When you remove the Advanced Server data files, the removal procedure will remove the server configuration parameters that are stored as values, and their keys, from the OpenVMS Registry.

To complete this operation, the removal procedure:

• Requires that registry services be available on the system. The Registry Server must be running on the system or in the cluster, and the registry database must be available on the system. If registry services are not available, the removal procedure will attempt to start the Registry Server. Registry services must be enabled on the system to run the Registry Server. For more information about ensuring that registry services are available, refer to the OpenVMS System Manager's Manual or the OpenVMS Connectivity Developer's Guide (included in the OpenVMS Documentation CD-ROM).
• Invokes the PWRK$REGUTL parameter management utility (described in the Compaq Advanced Server for OpenVMS Server Administrator's Guide).

To start the removal procedure and remove Advanced Server for OpenVMS software:

1. Ensure that you are logged in to the SYSTEM account.
2. Ensure that no processes are running the Advanced Server ADMINISTER command-line interface.
3. Start the removal command procedure, as follows:

   $ PRODUCT REMOVE ADVANCEDSERVER

Table 7-1, PRODUCT REMOVE Prompts, tells you how to respond to the prompts that the removal procedure displays.

Table 7-1 PRODUCT REMOVE Prompts

At this prompt...	If you want the removal procedure to...	Enter...
Do you want to continue? [YES]	Continue	[Return]
	Exit	NO
Information about the use of the Advanced Server may have accumulated in data files. Delete those files? [NO]:	Save the Advanced Server on-disk structure, including the security accounts database (SAM), the share database, and the server configuration parameters in the OpenVMS Registry (see Section 7.3.1, Server Configuration Parameters in the OpenVMS Registry)	[Return]
	Remove the Advanced Server on-disk structure, including the security accounts database (SAM), the share database, and the server configuration parameters	YES
Save clean up tools? [YES]	Save the PWRK$FIXACE and PWRK$DELETEACE tools	[Return]
	Delete these tools	NO
Save a copy of NETBIOS.EXE? [YES]	Save the NETBIOS image and related files so you can restore it later, if necessary.	[Return]
	Delete the NETBIOS image and related files	NO

7.3.1 Server Configuration Parameters in the OpenVMS Registry

When you are prompted whether to delete the Advanced Server data files:

• If you respond YES, in addition to deleting the data files (the Advanced Server directory structure and associated files created during installation), the procedure deletes all known Advanced Server keys and values from the OpenVMS Registry.
• If you respond NO, the procedure creates the following file:
  PWRK$LANMAN:SYS$REGISTRY.LIS
  This file contains a list of all Advanced Server parameters that were in the OpenVMS Registry before removing the Advanced Server. Once the Advanced Server product is removed, PWRK$REGUTL is no longer available for managing Registry parameters. To remove the Advanced Server parameters left in the OpenVMS Registry, use the OpenVMS Registry Control Program (REG$CP.EXE). See the PWRK$LANMAN:SYS$REGISTRY.LIS file to determine which keys and values are to be removed.

This is a sample of the removal procedure for Advanced Server software.

The following product has been selected: CPQ AXPVMS ADVANCEDSERVER V7.3 Layered Product Do you want to continue? [YES] YES [Return] The following product will be removed from destination: CPQ AXPVMS ADVANCEDSERVER V7.3 DISK$AXP0721:[VMS$COMMON.] Portion done: 0%...10%...20% Information about the use of the Advanced Server may have accumulated in data files. Delete those files? [NO] YES [Return] Some portions of Advanced Server may be useful even after Advanced Server is removed. Save clean up tools? [YES] NO [Return] If PCSI provided the image SYS$COMMON:[SYSEXE]NETBIOS.EXE and does not know of another product also using that image, then PCSI will remove that image. It is possible another program uses that image but PCSI does not know about it. This procedure can save the image so you can restore it in case it is needed. Several related files are also saved. Save a copy of NETBIOS.EXE? [YES] [Return] The OpenVMS Registry server is already started on this node. Removing Advanced Server registry parameter and keys Removing PWRK$DEFAULT and PWRK$GUEST OpenVMS accounts... Saving Advanced Server for OpenVMS NETBIOS component... Deleting Advanced Server data files... Deassigning Advanced Server for OpenVMS logical names... ...30%...40%...50%...60%...70%...80%...90%...100% The following product has been removed: CPQ AXPVMS ADVANCEDSERVER V7.3 Layered Product

Table A-1 summarizes the tasks that you need to perform to install and configure the Advanced Server. You can photocopy this table and use it as a checklist as you read about and complete the tasks in this book.

Table A-1 Installation and Upgrade Checklist

[]	1.	Prepare for the installation by completing all preinstallation tasks on the checklist in Section 1.8, Preinstallation Tasks, including the following: Check the part listing. Make sure that you have the required hardware. Log in to the SYSTEM account (or an equivalent account). Make sure your system has the required software. Check that OpenVMS registry services are available on the Advanced Server system. Read the release notes. Make sure that the system parameters GBLPAGES, GBLSECTIONS, PROCSECTCNT, and SCSNODE are set properly. Back up the system disks. Make sure that you have enough disk space to install the software. Make sure that the queue manager is running. Check the time zone configuration. Verify that DECnet (or DECnet-Plus) and TCP/IP, if needed, are running. Check for existing Compaq OpenVMS server images and files on the system. Check OpenVMS Cluster configuration, if installing on a Cluster.
[]	2.	Start the installation procedure and respond to installation prompts. You may choose to install the following: The complete Advanced Server The standalone License Server (if you chose not to install the Advanced Server) The standalone external authentication software (if you chose not to install the Advanced Server) Both the standalone License Server and external authentication software (if you chose not to install the Advanced Server)
[]	3.	Start the configuration procedure and respond to configuration prompts.
[]	4.	Run the Installation Verification Procedure (if you did not do so when you installed the Advanced Server).
[]	5.	Start the server (if you did not do so when you configured the Advanced Server).
[]	6.	Install Windows NT server administration tools (optional).

This appendix shows sample installation and configuration procedures for the Advanced Server when it is being installed for the first time on the system.

B.1 Sample Advanced Server Installation Procedure

The following example shows a sample installation dialog for the Advanced Server. The installation dialog differs slightly according to circumstances.

$ PRODUCT INSTALL ADVANCEDSERVER/SOURCE=DKA100:[000000] The following product has been selected: CPQ AXPVMS ADVANCEDSERVER V7.3 Layered Product Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. CPQ AXPVMS ADVANCEDSERVER V7.3: Advanced Server for OpenVMS Copyright 2000 Compaq Computer Corporation Advanced Server is sold by Compaq Computer Corporation Advanced Server requires PAK PWLMXXXCA07.03 for each client. This installation procedure requires that all the following conditions are satisfied: 1. This procedure is running on an Alpha processor. 2. The system is running OpenVMS 7.2 or later. 3. All required privileges are currently enabled. 4. No PATHWORKS or Advanced Server images are running on this node or anywhere in the cluster. 5. No files from a PATHWORKS (NetWare) kit are present on this system disk. 6. No files from any Pathworks or Advanced Server kit are in SYS$SPECIFIC on this system disk. This procedure checks if the conditions are satisfied. If they are satisfied, the procedure continues. If not, the procedure stops. Do you want to continue? [YES] [Return] Select one of the numbered options: 1 Install the complete Advanced Server [default] 2 Install only the License Server 3 Install only the external authentication images 4 Install both the License Server and the external authentication images Option: [1] [Return] This node contains a PWRK$STREAMSOS_V*.EXE execlet from a previous kit loaded into memory. A node that will not run this product does not have to be rebooted. A node that did not run a previous version of this product does not have to be rebooted. Only nodes that ran a previous version and will run the new version must be rebooted. Depending on the existing configuration and the desired configuration of a node it might be necessary to reboot a node before it can be configured, after it has been configured, or both. Both is rare. For complete information about the reasons a reboot might be necessary and how to avoid unnecessary reboots, see the Installation and Configuration Guide. Select an option: 1. Delay reboot as long as possible on all nodes. [default] 2. Prevent PWRK$CONFIG configuration on any node using this system disk until after reboot. 3. Prevent PWRK$CONFIG configuration on all nodes until after reboot. 4. Prevent startup on any node using this system disk until after reboot. 5. Prevent startup on all nodes until after reboot. Option: [1] [Return] User Accounts and User Identification Codes (UICs) -------------------------------------------------- The Advanced Server V7.3 for OpenVMS installation creates two OpenVMS accounts: a default account, PWRK$DEFAULT, and a guest account, PWRK$GUEST. The default UIC group number for both these new accounts depends on the following: o If you are installing the server for the first time, the default is the first unused UIC group number, starting with 360. o If a PCFS$ACCOUNT already exists, the default is the UIC group number associated with PCFS$ACCOUNT. o If a PWRK$DEFAULT or PWRK$GUEST account already exists, the default is the UIC group number associated with PWRK$DEFAULT or PWRK$GUEST, in preference to PCFS$ACCOUNT. However, the default UIC group number will not be used to change the UIC of any existing accounts. For more information about UIC group numbers, see the OpenVMS System Manager's Manual. Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST Group: [360] [Return] Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST PWRK$DEFAULT account already exists PWRK$GUEST account already exists * This product does not have any configuration options. Execution phase starting ... The following product will be installed to destination: CPQ AXPVMS ADVANCEDSERVER V7.3 DISK$AXP0721:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...60%...90% To automatically start Advanced Server V7.3 for OpenVMS at system startup, you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file. $ @SYS$STARTUP:PWRK$STARTUP Note: Add this line after the lines that start all the network transports, such as DECnet. Before starting Advanced Server V7.3 for OpenVMS on this node, be sure to configure the product (@SYS$UPDATE:PWRK$CONFIG) on each node in the cluster where the product will run. ...100% The following product has been installed: CPQ AXPVMS ADVANCEDSERVER V7.3 Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS ADVANCEDSERVER V7.3 ... Copyright Compaq Computer Corporation 1998, 2000. Starting Installation Verification Procedure for Advanced Server V7.3 for OpenVMS %PWRK-I-NORMAL, IVP completed successfully %PCSI-I-IVPSUCCESS, test procedure completed successfully $

B.2 Sample Advanced Server Configuration Procedure

The following example shows a sample configuration dialog for the Advanced Server.

$ @SYS$UPDATE:PWRK$CONFIG Advanced Server V7.3 for OpenVMS Configuration Procedure The Advanced Server stores and accesses the following types of data files: o Configuration parameter files o License Server data files o Log files o Printer spool files o Virtual memory section files You can specify any existing OpenVMS disk device that has at least 85,000 free blocks of disk space to store these data files. Note: The server frequently accesses the data files stored on the disk. If these files are stored on the system disk, it can degrade the performance of both the OpenVMS system and the server. Therefore, Compaq recommends that you specify a disk other than the system disk. Press RETURN to continue: If this OpenVMS cluster has multiple system disks, make sure that all nodes on which you plan to run the Advanced Server: o Use the same disk device to store and access Advanced Server data files. o Share the same SYSUAF.DAT file. In each system disk's startup file, define a system logical name that points all nodes to the shared SYSUAF.DAT file. For example: $ define/system/exec sysuaf pencil$dka300:[sys0.sysexe]sysuaf.dat The startup file is called SYS$MANAGER:SYSTARTUP_VMS.COM Enter disk device name where the Advanced Server data files will be stored [SYS$SYSDEVICE:]: [Return] Creating Advanced Server directory tree on PWROOT:... PWRK$LICENSE_SERVER_STATE.DAT already exists, not superseded. %CREATE-I-EXISTS, PWRK$COMMONROOT:[000000] already exists Checking to see if the OpenVMS Registry Services are available... %RUN-S-PROC_ID, identification of created process is 0000023B Populating OpenVMS Registry with required Advanced Server & NT parameters... Please wait, this may take one to two minutes to complete ... Required OpenVMS Registry file server keys and values have been created. Migrating LANMAN.INI parameters to the OpenVMS Registry... Verifying SAM database files... Creating Advanced Server directory tree... Copying client files to Advanced Server directory tree... Creating the Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT... Changing the server configuration parameters will allow you to modify this server's client capacity and select the transports to be used. SPEEDY is currently configured to + support 20 PC clients + use the following transport(s): DECnet If you want this server to be the primary domain controller, you should configure it to use all the transports used by the backup domain controllers and member servers in the domain. If you want this server to be a backup domain controller or member server, you should configure it to have at least one transport in common with the domain's primary domain controller, otherwise this configuration will fail. If you do not change the configuration parameters now, you may do so later by typing ADMIN/CONFIG. Do you want to change the server configuration parameters now? [YES]:Y [Return] ******* Advanced Server Configuration for node SPEEDY ********* * Options Help * * * * * * *Server's Client Capacity********************************** * * * * * * * * * * * ( ) Maximize Client Capacity Using AUTOGEN/Reboot * * * * (* ) Maximize Client Capacity Without AUTOGEN or Reboot * * * * ( ) User Supplied Client Capacity * * * * * * * * Client Capacity: 20 * * * * * * * *********************************************************** * * * * Percent of Physical Memory Used: 80 * * * * Data Cache Size (Kbytes): 12888 * * * * Maximum Concurrent Signons: 10 * * OpenVMS Process Priority: 9 * * * * ********** ******** *************** ***************** * * * Verify * * Quit * * Advanced... * * Transports... * * * ********** ******** *************** ***************** * * * * Enter data cache size in Kbytes ***************************** . . . Reading current configuration parameters ... Your Advanced Server for OpenVMS is presently configured to run as follows: 1. Run the License Server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: LANGROUP 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: SPEEDY 7a. Advanced Server OpenVMS Cluster alias: SPEEDY_ALIAS 8. Server announce comment: Advanced Server V7.3 for OpenVMS 9. Advanced Server language: English (USA) 10. Enable NT style printing: NO Enter item number, or RETURN to use these values [DONE]: 5 [Return] An Advanced Server domain is a collection of computers that share a common security database and policy. Each domain has a unique name. A network can have many domains. The Advanced Server domain name can be up to 15 characters long. The domain name must be different than the computer name. Enter Advanced Server domain name for this system [5]: SPUNKY.DOM [Return] Your Advanced Server for OpenVMS is presently configured to run as follows: 1. Run the License Server: NO 2. Enable Timesource service: NO 3. Enable Alerter service: YES 3a. Alert user names: Administrator 4. Enable Netlogon service: YES 5. Advanced Server domain: SPUNKY.DOM 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: SPEEDY 7a. Advanced Server OpenVMS Cluster alias: SPEEDY_ALIAS 8. Server announce comment: Advanced Server V7.3 for OpenVMS 9. Advanced Server language: English (USA) 10. Enable NT style printing: NO Enter item number, or RETURN to use these values [DONE]: [Return] Saving parameters to the OpenVMS Registry... Creating SAM datafiles... Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB ... New sharefile has been created. ADMIN$ added IPC$ added PWUTIL added PWLICENSE added PWLIC added The Advanced Server Administrator account is used to administer the server. The Administrator account is mapped by default to the OpenVMS SYSTEM account. The account password can be up to 14 characters long and the case of the characters used will be preserved. Enter Administrator account password: Re-enter to verify password: Changing password for Administrator account... Checking system resources... The current system configuration for SPEEDY will support 20 PC clients. The Advanced Server is configured to use DECnet, NetBEUI, TCP/IP. To automatically start the Advanced Server V7.3 for OpenVMS at system startup, you should add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file. $ @SYS$STARTUP:PWRK$STARTUP Note: Add this line below the lines that start all network transports (such as DECnet). Do you want to start the Advanced Server V7.3 on node SPEEDY now [YES]: [Return] The file server will use DECnet, NetBEUI, TCP/IP. Advanced Server mail notification will use DECnet. Process NETBIOS created with identification 00000248 Process PWRK$NBDAEMON created with identification 0000024A Process PWRK$KNBDAEMON created with identification 0000024C Process PWRK$LICENSE_R created with identification 0000024E Checking to see if the OpenVMS Registry Services are available... The Advanced Server is configured to support 20 PC clients. Process PWRK$MASTER created with identification 00000251 The master process will now start all other Advanced Server processes. $