HP OpenVMS Systems

HP Advanced Server for OpenVMS
Server Installation and Configuration Guide

The server configuration settings determine:

• Whether the License Server runs
  The License Server is a software program that you can run on your OpenVMS system to grant client-based licenses. Any client that wants to use server resources must have a valid license. Each local area network (LAN) needs only one License Server. The client license product authorization keys (PAKs) must be loaded on the system that runs the License Server.
  In an OpenVMS Cluster, the PAKs must be loaded in a shared license database available to all cluster members.
  The License Server runs only if you enable it with the configuration procedure.
  • If you are using client-based licensing, you must run the License Server. HP recommends that you run the License Server on a different system than the Advanced Server. See Section 1.3, About Licensing, for more information.
  • If you are using server-based licenses, you do not need to run the License Server.
  
  By default, the License Server does not run.
• Whether the Timesource service runs
  The Timesource service allows your server to act as a time server. Other servers on the network can synchronize with the time server to coordinate network events (for example, running batch programs on all computers the same time each day). Each LAN needs only one time server.
  By default, the Timesource service does not run.
• Whether the Alerter service runs
  The Alerter service sends messages called alerts to servers and clients that run the Messenger service.
  By default, the Alerter service runs.
• Names of the users who receive alert messages
  By default, alert messages are sent to the Administrator account.
• Whether the NetLogon service is enabled.
  In a domain, the NetLogon service distributes a domain-wide user accounts database to all domain controllers running NetLogon. The service allows for single domain-wide logon that enables users to access resources on any server in the domain. The NetLogon service is required for smooth operation of the domain; HP recommends that the NetLogon service always be enabled, even on a member server.
  By default, the NetLogon service runs.
• Domain name
  This is the domain in which your server is located. A domain is a subdivision of clients and servers on the network. For more information on domains, refer to the HP Advanced Server for OpenVMS Concepts and Planning Guide and the HP Advanced Server for OpenVMS Server Administrator's Guide.
  The default domain name is LANGROUP. You can specify a name that reflects your company or group.
• Role of the server
  This is the role of the server in the domain. You can designate an Advanced Server as either the primary domain controller (PDC), backup domain controller (BDC), or a member server. When you install the Advanced Server in a new domain, the new server becomes the PDC by default. In an OpenVMS Cluster, all nodes on the cluster have the same role: when you change the role of one, the change applies to all the servers on the cluster.
  For more details on configuring the server domain role, see Section 3.7, Configuring the Advanced Server Domain Role.
• Computer name
  This unique name identifies your server in the domain. You define this name or accept the default value when you run the configuration procedure.
  The PWRK$CONFIG procedure will not prevent you from specifying the same named PDC if another node or cluster has previously been defined and is running in that role. However, on the new (duplicate) PDC, the NetLogon service will not be started. The PDC must be unique in the domain.
  The default computer name is the same as the server's SCSNODE name.
• Advanced Server cluster alias
  If your server is a member of an OpenVMS Cluster, this is the name that all servers in the cluster share. The alias lets remote nodes (including clients) treat all server members in the cluster as a single server. For example, a client user can specify the Advanced Server cluster alias to connect to any server in the cluster; the user need not know the specific node in the cluster to which it is connected.
  If DECnet has been configured to run in the cluster, the default Advanced Server cluster alias is the same as the DECnet cluster alias. If a DECnet alias is not defined, the default Advanced Server cluster alias is nodename_ALIAS, where nodename is the SCSNODE name of the cluster member from which you initially run PWRK$CONFIG.

  Note HP strongly recommends that the Advanced Server cluster alias and the TCP/IP cluster alias (referred to as the TCP/IP impersonator cluster name) be different. Do not use the name of the domain as the Advanced Server cluster alias; if they are the same, the NetLogon service will fail to start.

• Server announce comment
  This is the text that the Advanced Server displays when it announces its presence on the network and when you display a list of available servers.
  The default server announce comment is "Advanced Server V7.3B for OpenVMS."
• Advanced Server language
  This determines the language and associated character set (one of several ISO-8859 character sets) that the Advanced Server uses for encoding text, such as file and share names, user names, description strings, and any content of ADMINISTER command displays.
  The default is English (USA). You can configure any one of over 40 languages, many which include support of extended character set characters. For an up-to-date list indicating which of these languages are officially supported, refer to the Software Product Description (SPD).

  Note The same language must be used by all servers in the domain. HP recommends that all clients that will access the server also be configured to use the same language; otherwise, names containing characters that are not supported by the server language might not appear to clients as expected.

  
  If your disk device includes ODS-2 file names (in specific, file names that include escape-encoded characters in the format __XX), you must first convert the file names to ODS-5 file names, as explained in Section 5.8, Converting Encoded File Names from ODS-2 to ODS-5. Section 3.8, Configuring the Server Language explains how to configure the Advanced Server language. For more information on languages, character sets, and Unicode, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide.
• Enable NT style printing
  This gives you a choice of managing shared printers either from a remote Windows NT computer or locally using the ADMINISTER command interface at the server. When enabled, administrators can store the latest drivers for the printers on the Advanced Server. When new drivers are distributed, administrators have to update a single location only. When client users set up printers to use from their workstations, they are able to download the appropriate printer driver automatically.
  The default is local management of shared printers, using ADMINISTER commands. When you enable Windows NT printer management, only limited functionality is available for managing printers with the ADMINISTER interface. Before configuring Windows NT style printer management, see the considerations and restrictions in Section 3.9.1, Considerations Regarding Windows NT Printer Management. Section 3.9.2, Example of Configuring Windows NT Printer Management, includes a sample configuration script showing how to configure Windows NT style printer management.
  For more information about management of Advanced Server print shares, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide.

For more information about changing configuration settings, see Section 3.6, How to Change Server Configuration Settings.

For more information about each server configuration setting, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide.

3.3.7 What Do You Want the Administrator Account Password to Be?

If you are configuring a PDC, the configuration procedure prompts you to specify the password to be set for the domain Administrator account. If you are configuring a member server, the configuration procedure prompts you for the member server's local Administrator account password to be set. The member server's local Administrator account password gives access to the member server's local security account database. As with Windows NT, there may be situtations where you would like to allow certain people to manage a member server's local database without giving them the ability to manage the entire domain.

Passwords are case sensitive and can contain up to 14 characters. Valid characters are alphanumeric characters and any of the following special characters:

! # $ % & () - . ^ _ ` { } ~

3.3.8 Are You Going to Supply Account/Password Information?

If you are configuring your server to join an existing domain (as a BDC or member server), you can either:

• Have the computer added to the domain manually by the domain administrator
• Have the computer added by supplying an administrator account user name and password during execution of the configuration procedure

The former option is useful if the domain administrator does not wish to give out the user name and password of the Administrator account in the domain to the person configuring this server to join the domain. The domain administrator can use the ADMINISTER ADD COMPUTER command or the Windows NT Server Manager to add the computer to the domain. If this is the case, answer NO to this prompt, and you will not be prompted for account/password information.

With the latter option, the configuration procedure requests the domain's PDC to add the computer to the domain. You will be prompted for a domain administrator account user name and password, as explained in Section 3.3.9, What Is the Domain Administrator Password?.

3.3.9 What Is the Domain Administrator Password?

When you choose to have the computer added automatically by the configuration procedure, you are prompted for a domain administrator account user name and password. As noted in Section 3.3.8, Are You Going to Supply Account/Password Information?, the PDC is requested to add the computer to the domain. The PDC validates the account user name and password on behalf of the configuration procedure. Enter the password, observing the rules specified in Section 3.3.7, What Do You Want the Administrator Account Password to Be?.

3.3.10 Do You Want to Enter a New Administrator Account Password?

In certain cases, you are prompted whether you want to enter a new Administrator password. This gives you the opportunity to change the password.

3.3.11 Do You Want to Start the Server?

The configuration procedure asks you if you want to start the Advanced Server. If you do not want to start the Advanced Server at this time, you can do so later from the command line after the configuration procedure completes.

Before you start the server on any OpenVMS Cluster member, HP recommends that you configure the Advanced Server on each cluster member that you want to use as a server. You can then use the SYSMAN utility to start the server on all cluster members. If you choose to start the server individually on each cluster member, make sure that you do so from the SYSTEM account (or a similar account) on each server node. For more information, see Section 5.4.3, How to Start the Advanced Server in an OpenVMS Cluster.

3.4 How to Start the Advanced Server Configuration Procedure

After the installation procedure completes, the OpenVMS system prompt ($) is displayed.

1. Ensure that you are logged in to the SYSTEM account.
2. Start the configuration procedure by entering:

   $ @SYS$UPDATE:PWRK$CONFIG

Table 3-1, Advanced Server Configuration Prompts, tells you how to respond to the prompts that PWRK$CONFIG displays.

After you exit the Configuration Manager, the configuration procedure displays a list of server configuration settings and a prompt that lets you change them; for example:

  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:           COBRAZ
   7a. Advanced Server OpenVMS Cluster alias:   COBRAZ_ALIAS
   8.  Server announce comment:     Advanced Server V7.3B for OpenVMS
   9.  Advanced Server language:                English (USA)
   10. Enable NT style printing:                NO
  Enter item number, or RETURN to use these values [DONE]:

• To change a server configuration setting, enter the number of the setting you want to change. A prompt is then displayed that lets you change that setting. Table 3-2, Configuration Settings, describes possible values for each setting.
• To save the settings after you complete your changes or to accept the settings displayed, press the Return key to use the default answer DONE. For more information about server configuration, refer to the HP Advanced Server for OpenVMS Server Administrator's Guide.