Document revision date: 30 March 2001

Use the PWRK$CONFIG.COM configuration procedure to configure the Advanced Server to participate in a domain as a member server. You cannot use the ADMINISTER SET COMPUTER/ROLE command to change an Advanced Server for OpenVMS domain controller to a member server role or to change a member server to a domain controller role.

You can configure the Advanced Server as a member server if it is joining an existing domain that has a PDC in operation. If the domain consists of a native-mode Windows 2000 environment (also referred to as a pure Windows 2000 domain, this is a domain in which all domain controllers are Windows 2000 systems), the domain must first include at least one domain controller before you can configure an Advanced Server as a member server.

You may want to configure your Advanced Server for OpenVMS as a member server instead of a BDC (or PDC) for any of the following reasons:

• Member servers do not spend time validating logon requests. Thus, this role can be a good choice for servers that have heavy workloads or that perform extremely time-critical tasks.
• More important, configuring one or more servers as member servers rather than domain controllers can help decrease the network load, eliminating network traffic normally generated by domain controllers for replicating user databases and authenticating logon requests. When a client attempts to find a logon server to authenticate a request, all domain controllers respond to the request. In some environments, this can generate a significant load on the network.
• Configuring the Advanced Server for OpenVMS as a member server allows the Advanced Server for OpenVMS to participate in a native-mode Windows 2000 environment without interruption to that environment.
• If in the future your Advanced Server for OpenVMS server is moved to a different domain, it is simpler to move it as a member server from one domain to another.

The next two sections explain how to configure the Advanced Server as a member server: Section 3.7.1.1, Configuring a New Advanced Server for OpenVMS to Be a Member Server, and Section 3.7.1.2, Configuring an Existing Advanced Server for OpenVMS BDC As a Member Server.

3.7.1.1 Configuring a New Advanced Server for OpenVMS to Be a Member Server

While installing a new Advanced Server for OpenVMS in an existing domain, you can configure it as a member server during the PWRK$CONFIG.COM configuration procedure. The domain must include one active PDC; a native-mode Windows 2000 domain must include at least one domain controller.

The following PWRK$CONFIG.COM output shows how an Advanced Server for OpenVMS server might be configured as a member server. Preceding this part of the procedure, item 5 was selected to specify UPTIME as the domain. This example assumes the UPTIME domain is a native-mode Windows 2000 domain that already has one or more domain controllers.

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: UPTIME 6. Advanced Server role: PRIMARY 7. Advanced Server computer name: GRATDA 7a. Advanced Server OpenVMS Cluster alias: GRATDA_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]: 6 [Return] The Advanced Server role is the part the server will play in its domain. A primary domain controller maintains the domain's master user accounts database and validates logins. A backup domain controller receives copies of the master database, validates logins, and can be promoted to primary. A member server does not receive copies of the master database or validate logins. It relies on domain controllers to validate user credentials. Enter the role of this server (P)rimary/(B)ackup/(M)ember [P]: M [Return] Before joining a domain, the computer must be added to the domain. This can be done in one of two ways: - the administrator of the domain uses the administrative tools to add this computer to the domain, or - the computer is added automatically by this procedure; you must supply an administrator account and password Are you going to supply account/password information [Y]/N YES [Return] Enter the name of the primary domain controller for domain UPTIME: SUNDA [Return] Enter the name of the administrator account: [Administrator] [Return] Enter the account password in the required case: [Return] Re-enter to verify password: [Return] Process NETBIOS created with identification 206010B5 Process PWRK$NBDAEMON created with identification 206010B7 Process PWRK$KNBDAEMON created with identification 206010B9 Confirming domain name with SUNDA Successfully retrieved domain name from SUNDA ... 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: UPTIME 6. Advanced Server role: MEMBER 7. Advanced Server computer name: GRATDA 7a. Advanced Server OpenVMS Cluster alias: GRATDA_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... . . . The Advanced Server Administrator account is used to administer the server. The Administrator account is mapped by default to the OpenVMS SYSTEM account. The Administrator account password can be up to 14 characters long and the case of the characters used will be preserved. Enter a password for this Member Server's local Administrator account: [Return] Re-enter to verify password: [Return] Changing password for Administrator account... Setting character set information in databases as needed ... ... Setting share database character set information. ... Setting ACL database character set information. Checking system resources...

3.7.1.2 Configuring an Existing Advanced Server for OpenVMS BDC As a Member Server

When you configure a BDC to become a member server, the script is similar to the one for configuring a new server as a member server. One exception is that the script will display the following lines:

Changing from backup domain controller to member server results in the re-creation of the Advanced Server SAM databases. If there is any problem with the configuration, your existing SAM databases will be restored.

The BDC's domain-wide account database is removed, and the member server's local database is created. Server-specific data is retained from the BDC's database. The configuration procedure saves the domain-wide account database in case you need to restore it later (for more information, see Section 3.10.3, If Problems Occur When Reconfiguring the Advanced Server).

The following two displays show the role of server LIONHEART before and after reconfiguration to the member server role. The display symbol for a member server is [SV].

LANDOFOZ\\TINMAN> SHOW COMPUTERS Computers in domain "LANDOFOZ": Computer Type Description ------- ------------------------ ----------------------------- [PD] TINMAN OpenVMS (NT 4.0) Primary Advanced Server V7.3 for OpenVMS [BD] LIONHEART OpenVMS (NT 4.0) Backup Advanced Server V7.3 for OpenVMS [BD] DOROTHY OpenVMS (NT 3.51) Backup Advanced Server V7.2A for OpenVMS Total of 3 computers [reconfigure server role] . . . LANDOFOZ\\TINMAN> SHOW COMPUTERS Computers in domain "LANDOFOZ": Computer Type Description ------- ------------------------ ----------------------------- [PD] TINMAN OpenVMS (NT 4.0) Primary Advanced Server V7.3 for OpenVMS [SV] LIONHEART OpenVMS (NT 4.0) Server Advanced Server V7.3 for OpenVMS [BD] DOROTHY OpenVMS (NT 3.51) Backup Advanced Server V7.2A for OpenVMS Total of 3 computers

3.8 Configuring the Server Language

By default, the language of the Advanced Server is "English (USA)". You can configure any one of over 40 languages for the Advanced Server. For an up-to-date list of the languages officially supported by the Advanced Server, refer to the Software Product Description (SPD).

3.8.1 Considerations Regarding the Server Language

Consider the following when configuring the server language:

• The same language should be used by all servers in a domain. All Advanced Servers in the same cluster automatically share the same language (they share the same registry database where the language is stored).
• Although you can change the server's language at any time (after stopping the Advanced Server), Compaq recommends that once a choice is made, you do not alter that choice.
  Certain objects might exist whose names include characters that are not included in the new language that you select. For example, after you select a new language, PWRK$CONFIG might convert (depending on the language) all text strings in the Security Account Manager (SAM), access control list (ACL), and share databases from the old character set (for the previous language) to the new set (for the new language).
  If one or more of these databases are converted, PWRK$CONFIG displays the following message:

  Setting character set information in databases as needed...

  
  In addition, a message will be displayed for each database affected, such as:

  ... Setting share database character set information.

  
  If any of these databases contain text strings that cannot be converted (that is, object names that contain characters not included in the newly configured Advanced Server language character set), the PWRK$CONFIG procedure reverts to the set of databases that existed prior to conversion attempt. Error messages will indicate the names that could not be converted, and the language is reset to the original language. You must rename (or remove) the objects that cannot be converted, and rerun PWRK$CONFIG to change the language.
  Note that for some languages, PWRK$CONFIG does not need to convert the text strings in the databases mentioned above --- it changes the client code page value only. (A client code page is an ordered set of 256 characters that extends the limits of ASCII (American Standard Code for Information Interchange) character sets to support the variety of characters used in languages internationally. Each language-specific code page overlays the same set of 8-bit values. For example, a specific 8-bit value in a code page used for the English language can be used for another character used for the Cyrillic language.)

During the PWRK$CONFIG.COM configuration procedure, you can configure an Advanced Server language other than the default by selecting option 9. The procedure lists the configurable languages. At the prompt, enter the number of the language you want to use.

In the following example, the Hebrew language is configured (character set ISO8859-8).

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: LANDOFOZ 6. Advanced Server role: MEMBER 7. Advanced Server computer name: LIONHEART 7a. Advanced Server OpenVMS Cluster alias: LIONHEART_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]: 9 [Return] ******************** W A R N I N G ************************ Although you can change the server's language at any time (after stopping the Advanced Server), Compaq recommends that once a choice is made, you do not alter that choice. Certain objects might exist whose names include characters that are not included in the new language that you select. Error messages will indicate the names that could not be converted, and the language will be reset to the original language. If you want to change the language, you must first rename (or remove) the objects that cannot be converted, and rerun PWRK$CONFIG to change the language. ***********************************************************" Do you want to continue with item number 9 (Y/[N]) Y [Return] 1) Afrikaans 16) French 31) Portuguese 2) Albanian 17) French (Ca. MS-DOS) 32) Portuguese (MS-DOS) 3) Basque 18) German 33) Romanian 4) Belarussian 19) Greek 34) Russian 5) Bulgarian 20) Greek (IBM) 35) Serbian (Cyrillic) 6) Catalan 21) Hebrew 36) Serbian (Latin) 7) Croatian 22) Hungarian 37) Slovak 8) Czech 23) IBM Cyrillic 38) Slovenian 9) Danish 24) Icelandic 39) Spanish 10) Dutch 25) Icelandic (MS-DOS) 40) Swedish 11) English (USA) 26) Indonesian 41) Turkish 12) English (USA)+Euro 27) Italian 42) Ukrainian 13) English (Other) 28) Nordic L. (MS-DOS) 43) Western Europe+ 14) Faeroese 29) Norwegian Euro 15) Finnish 30) Polish The Advanced Server language specifies the internal character set encoding for strings, character casing rules, and the client code page.

Enter Advanced Server language by number for this cluster [English(USA)]: 21 [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: LANDOFOZ 6. Advanced Server role: MEMBER 7. Advanced Server computer name: LIONHEART 7a. Advanced Server OpenVMS Cluster alias: LIONHEART_ALIAS 8. Server announce comment: Advanced Server V7.3 for OpenVMS 9. Advanced Server language: Hebrew 10. Enable NT style printing: NO Enter item number, or RETURN to use these values [DONE]: [Return]

3.9 Configuring Windows NT Printer Management

By default, printers shared by the server are managed locally using the ADMINISTER user interface. You can configure the server to support management of the printers from Windows NT. This allows you to take advantage of the Windows NT style of printer management, using the Windows NT print services dialog boxes, such as the Add Printer wizard for adding printers.

Administrators can then 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.

Before configuring your sever to support Windows NT printer management, be sure to familiarize yourself with the considerations noted in Section 3.9.1, Considerations Regarding Windows NT Printer Management.

3.9.1 Considerations Regarding Windows NT Printer Management

Consider the following before choosing to configure the Windows NT style of printer management. When you enable Windows NT printer management:

• Only limited functionality is available for managing printers with the ADMINISTER interface. (Similarly, when the default printer management style is enabled (using the ADMINISTER interface), limited functionality is available for managing the printers from Windows NT.)
• Printers or print queues that were already defined on the server are upgraded automatically so that clients can continue to share these printers and their queues. However, management of these upgraded printers from Windows NT is limited. To gain full Windows NT management functionality for these printers, use Windows NT print services to delete the printers and then to add the printers back onto the Advanced Server.

  Note When running PWRK$CONFIG to reconfigure the Advanced Server, printers that have been upgraded previously are not upgraded again.

• Once you configure the Windows NT printer management style, if you decide to reconfigure your server to the default local printer management style, all printers will be unusable. You will have to perform several, time-consuming tasks to make printers functional again.
• Be sure to refer to the Advanced Server V7.3 for OpenVMS Release Notes for more information on restrictions regarding Windows NT printer management.

During the PWRK$CONFIG.COM configuration procedure, you can configure Windows NT style printer management by selecting option 10. The procedure displays a warning and asks you if you are sure you want to make the change, as shown in the following example:

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: LANDOFOZ 6. Advanced Server role: MEMBER 7. Advanced Server computer name: LIONHEART 7a. Advanced Server OpenVMS Cluster alias: LIONHEART_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]: 10 [Return] ******************** W A R N I N G ************************ Before enabling this feature, make sure you are familiar with the Windows NT printer management restrictions documented in the Release Notes. Note that once you configure the Windows NT printer management style, if you reconfigure your server to the default local printer management style, all printers will be unusable. You will have to perform several time-consuming tasks to make printers functional again. ***********************************************************" Are you sure you want to enable Windows NT printer management? [Y/[N]] Y [Return] 10. Enable NT style printing: Y [Return]

3.10 Troubleshooting Configuration Procedure Problems

This section describes how to:

• Troubleshoot Registry Server startup problems
• Ensure sufficient resources will be available to support clients

For proper operation of the PWRK$CONFIG.COM configuration procedure and the file server, registry services must be available on the system running the Advanced Server.

In an OpenVMS Cluster environment, the OpenVMS Registry can be configured so that the Registry Server does not run on the server node but rather on another node in the cluster. However, Compaq recommends that the OpenVMS Registry be configured to run the Registry Server on every Advanced Server node. This ensures that registry services are available to the file server. For instructions on starting the Registry Server and enabling registry services, see Section 1.8.5, Step 5: Start the OpenVMS Registry Server.

• If registry services are not available, the PWRK$CONFIG.COM procedure attempts to start the OpenVMS Registry Server. If the attempt is successful, the procedure displays the following message:

  Checking to see if the OpenVMS Registry Services are available ... %RUN-S-PROC_ID, identification of created process is 0000023B

• If the SYS$REGISTRY logical is not defined, the OpenVMS Registry will not start. In this case, the PWRK$CONFIG.COM displays the following messages and terminates:

  Checking to see if OpenVMS Registry Services are available... SYS$REGISTRY must be defined to start the VMS Registry %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for this system %PWRK-F-CONFIGERR, severe error encountered during configuration OpenVMS Registry Services are not available on this system. Some file server parameters are stored in the OpenVMS Registry. For the file server or file server utilities to be able to access these parameters, OpenVMS Registry Services must be available on this system. Since the file server requires access to the OpenVMS Registry, it is recommended that OpenVMS Registry Services be started as part of system start-up, before the file server is started. For instructions on how to start OpenVMS Registry Services please refer to the file server release notes. This configuration is incomplete and cannot continue. You must execute @SYS$UPDATE:PWRK$CONFIG again. Please configure and start the OpenVMS Registry Services before doing so.

  
  You must enable registry services and start the Registry Server, then run the PWRK$CONFIG.COM procedure again. For more information about enabling and starting the Registry Server, refer to the OpenVMS System Manager's Manual or the OpenVMS Connectivity Developer's Guide (included in the OpenVMS Documentation CD-ROM).

The Advanced Server requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for use by processes other than the Advanced Server, and these resources have already been consumed when the Advanced Server is started, there may be insufficient resources left for the Advanced Server to support the desired number of clients.

To ensure sufficient resource allocation to support clients, make sure that all software that will run concurrently with the Advanced Server is installed and started before you run the the Advanced Server configuration procedure (PWRK$CONFIG.COM). If TCP/IP is selected as a transport, make sure that the TCP/IP product is loaded before you run the PWRK$CONFIG procedure.

After you successfully configure the Advanced Server, it may not start, reporting that there are insufficient resources to support any clients. In this case, examine the following file to determine the system resource that needs to be increased (nodename is the name of the server node):

PWRK$LOGS:PWRK$CONFIG_ERROR_nodename.LOG

To increase the resource, make the appropriate modifications to the MODPARAMS.DAT file and then run AUTOGEN.

	privacy and legal statement
6540PRO_005.HTML