Document revision date: 30 March 2001 | |
Previous | Contents | Index |
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 Compaq Advanced Server for OpenVMS Server Administrator's Guide.
3.3.4 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.5 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:
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.6, What Is the Domain Administrator Password?.
3.3.6 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.5, 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.4, What Do You Want the Administrator Account Password to Be?.
3.3.7 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.8 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,
Compaq 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.
$ @SYS$UPDATE:PWRK$CONFIG |
Table 3-1, Advanced Server Configuration Prompts, tells you how to respond to the prompts that PWRK$CONFIG displays.
Table 3-1 shows only the prompts PWRK$CONFIG displays; it does not show any informational messages. For a complete sample configuration script, see Appendix B, Sample Advanced Server Installation and Configuration. |
At this prompt... | If you want the configuration procedure to... | Enter... |
---|---|---|
Do you want to continue with configuration [YES]: 1 | Shut down the server or, if your server is part of an OpenVMS Cluster, all servers in the cluster | Press the Return key |
Abort the configuration procedure | NO | |
Enter disk device name where Advanced Server data files will be stored [ default_device]: |
Copy the Advanced Server on-disk structure to the default OpenVMS disk
device displayed
If you ran PWRK$CONFIG previously, the default disk device is the one you specified the last time you configured the server; otherwise, the default device is SYS$SYSDEVICE. |
Press the Return key |
Copy the Advanced Server on-disk structure to an OpenVMS disk device different from the default displayed | device_name | |
Do you want to change the server configuration parameters now? [YES]: | Access the Configuration Manager tool to change parameters affecting the system environment for the server |
Press the Return key
For detailed information about using the Configuration Manager, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide. |
Complete the configuration without entering the Configuration Manager | NO | |
Enter item number, or RETURN to use these values [DONE]: | Accept the server configuration parameters displayed (these are the ten or so parameters that directly affect or define the server software configuration) | Press the Return key |
Change the configuration settings displayed |
The number associated with a setting you want to change.
For detailed information on changing these default configuration settings, see Section 3.6, How to Change Server Configuration Settings. |
|
Are you going to supply account/password information? [YES]: 4 | Have the computer added automatically by PWRK$CONFIG, prompting you for a domain administrator account user name and password | Press the Return key |
Have the computer added manually (for example, by the domain administrator) so that the domain administrator's password need not be divulged | NO | |
Enter the name of the primary domain controller for domain domain-name 4 | Enter the name of the primary domain controller (PDC) for the domain your server is joining. | PDC-name |
Enter Administrator account password: 3 | Associate a password with the Administrator account |
password
Enter the password to be set for the domain's existing Administrator account. |
Do you want to enter a new Administrator account password [NO]: 2,3 | Keep the existing Administrator account password | Press the Return key |
Prompt you to enter a new Administrator account password | YES | |
Re-enter to verify password 3,4,5: | password | |
Enter a password for this member server's local Administrator account: 5 | Associate a password with the member server's local Administrator account |
password
Enter the password to be set for the member server's local Administrator account. |
Enter the account password in the required case 4 |
password
Enter the password in the proper case, matching the current domain account password. |
|
Do you want to start the Advanced Server V7.3 for OpenVMS on node node_name now [YES]: 6 | Start the server automatically after the configuration procedure completes | Press the Return key |
Not start the server | NO |
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.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]: |
Setting | Possible Values |
---|---|
1. Run the License Server: |
YES, to run the License Server.
NO, to use the default and not run the License Server. |
2. Enable Timesource service: |
YES, to enable the Timesource service.
NO, to use the default and not enable the Timesource service. |
3. Enable Alerter service: |
YES, to accept the default and enable the Alerter service.
NO, to disable the Alerter service. |
3a. Alert user names: 1 | A comma-delimited list of user names (each containing up to 20 characters), who can receive alert messages. |
4. Enable Netlogon service: 2 |
YES, to accept the default and enable the Netlogon service.
NO, to disable the Netlogon service. |
5. Advanced Server domain: |
A domain name of up to 15 characters.
Press the Return key to use the default. The default domain name is LANGROUP. You can specify a name that reflects your company or group. |
6. Advanced Server role: |
PRIMARY, to designate the server as the PDC
BACKUP, to designate the server as a BDC MEMBER, to designate the server as a member server. For more information on configuring the domain role, see Section 3.7, Configuring the Advanced Server Domain Role. |
7. Advanced Server computer name: |
A computer name of up to 15 characters.
Press the Return key to use the default. If this is the first time running the configuration procedure, the default is your system's SCSNODE name. |
7a. Advanced Server OpenVMS Cluster alias: 3 |
The Advanced Server cluster alias for the OpenVMS Cluster to which your
server belongs.
Press the Return key to use the default. If DECnet is configured to run, the default is the DECnet cluster alias. If DECnet is not configured to run, the default is nodename_ALIAS. |
8. Server announce comment: |
A text string of up to 48 characters that the server uses to announce
its presence on the network.
Press the Return key to use the default. |
9. Advanced Server language: |
The option number of the language to be used by the Advanced Server. The
default is English (USA).
Press the Return key to use the default. For more information on configuring the server language, see Section 3.8, Configuring the Server Language. |
10. Enable NT style printing: |
YES, to enable remote management of server printers from Windows NT.
NO, to use the default, managing server printers locally, using the ADMINISTER command interface. For more information on configuring Windows NT printer management, see Section 3.9, Configuring Windows NT Printer Management. |
Depending on the domain type, the Advanced Server can participate in a domain as either the PDC, a BDC, or a member server.
There are three kinds of domains that the Advanced Server may participate in:
Table 3-3, Server Roles in Each Type of Domain, lists for each type of domain the roles the server can take:
For Domain Type: | The Advanced Server Can Take These Roles: | ||
---|---|---|---|
PDC | BDC | Member Server | |
Windows NT | X | X | X |
Windows 2000 Mixed-Mode | X | X | |
Windows 2000 Native-Mode | X |
Each Windows NT domain must have one PDC. The PDC stores the domain's master copy of the security accounts database.
When you install the Advanced Server to create a new Windows NT domain, the new server becomes the PDC by default. When you install server software and specify an existing domain name, the server can join the existing domain only as a BDC or member server.
A domain does not have to have BDCs, but one or more are recommended. A BDC keeps a copy of the domain's master security accounts database. The copy of the security accounts database stored on BDCs is synchronized with the PDC's master database. PDCs and BDCs can validate logon requests in the domain.
A member server does not store a copy of the domain's security accounts database and does not validate logon requests. Member servers rely on domain controllers to validate credentials of users requesting access to member server shares. The advantages of configuring the Advanced Server as a member server are listed in Section 3.7.1, Configuring the Advanced Server As a Member Server.
In an OpenVMS Cluster, all nodes on the cluster must have the same role. If you change the role of one node, the other nodes are automatically changed to the same role.
When you configure the Advanced Server for the first time, you select the role your server will perform in the domain. There may be times when you need to change the role of your server. The method you use to change the server depends on the current role of the server and the role you want to change it to. To change the role of the server from a BDC to a PDC, or vice versa, use the ADMINISTER SET COMPUTER/ROLE command. To change a server BDC to a member server, you must use PWRK$CONFIG, as explained in Section 3.7.1, Configuring the Advanced Server As a Member Server. To change a PDC to a member server, you must first promote another BDC to a PDC; then the original PDC is demoted automatically to a BDC, after which you can use PWRK$CONFIG to change it to a member server. Use PWRK$CONFIG also to change a member server to a BDC. (This restriction is similar (but less restrictive) to that of Windows NT, which requires the operating system to be reinstalled to change a domain controller to a member server, or vice versa.) For more information on changing the role of the server from a BDC to a PDC, or vice versa, refer to the Compaq Advanced Server for OpenVMS Server Administrator's Guide. Table 3-4, Methods for Changing Server Roles, summarizes which role changes are allowed and disallowed by PWRK$CONFIG.
From: | To: | Method |
---|---|---|
BDC | PDC | Use ADMINISTER SET COMPUTER/ROLE command to promote the BDC to a PDC |
BDC | Member | Use PWRK$CONFIG |
Member | PDC | Use PWRK$CONFIG to change this server to a BDC, and then use the ADMINISTER SET COMPUTER/ROLE command to promote the BDC to a PDC |
Member | BDC | Use PWRK$CONFIG |
PDC | BDC | Use ADMINISTER SET COMPUTER/ROLE to promote a BDC in the domain to PDC; this promotion demotes the original PDC to a BDC |
PDC | Member | Use ADMINISTER SET COMPUTER/ROLE to promote an existing BDC to a PDC; this promotion demotes the PDC to a BDC so that you can change it to a member server, using PWRK$CONFIG |
If you reconfigure a BDC as a member server, PWRK$CONFIG automatically removes the domain controller's domain user account database. If you reconfigure a member server to a BDC, PWRK$CONFIG automatically removes the member server's local user account database. In either case, because of loss of local group information, access to some resources might be affected. If resource permissions have been set using local groups, those permissions will have to be reset. If resource permissions have been set using global groups or global user accounts, those permissions will remain in effect after the role change. |
Previous | Next | Contents | Index |
privacy and legal statement | ||
6540PRO_004.HTML |