Upgrading a LAN Manager 2.2 backup domain controller to an
Advanced Server/9000 backup domain controller is performed in two
stages.
First, the Advanced Server/9000 software is installed on the
backup domain controller and previously-saved configuration files
are upgraded. Following the completion of the software installation,
the primary domain controller automatically replicates the user
accounts database to the backup domain controller.
When replication is completed and the backup domain controller
is able to display the accounts, the upgrade procedure is completed
by executing the lmu_upgrade command manually.
To upgrade a LAN Manager 2.2 backup domain controller to an
Advanced Server/9000 backup domain controller
Install the Advanced Server/9000 product files as described
in the section "Loading Advanced Server/9000 Software"
in chapter 1 of this manual.
Verify that the primary domain controller is active
on the network and that the administrative account and password
exist on the primary domain controller.
If the primary and backup domain controllers are on different
subnets and you have a Windows NT Server, you can use WINS to locate
systems easily on remote networks.When using WINS, you will need
to configure NetBIOS so that it can contact a WINS server-- refer
to the Advanced Server/9000 Administrator's Guide
for details. If you don't have a Windows NT WINS server,
and the primary and backup domain controllers are on different subnets,
you will need to use nbutil to load the NetBIOS
name-to-IP address mappings as described in the Advanced
Server/9000 Administrator's Guide.
Run the utility to configure Advance Server/9000:
/opt/asu/lanman/bin/asu_inst
Log in at the Advanced Server/9000 system console
as root.
The system begins the installation process which includes
incorporating and updating the saved files and adding the server
to the protocol stack.
The system displays the following message:
Advanced Server for UNIX provides a NETLOGON service which simplifies the administration of multiple servers. A single user accounts database can be shared by multiple servers grouped together into an administrative collection called a domain. Within a domain, each server has a designated role. A single server, called the primary domain controller, manages all changes to the user accounts database and automatically distributed those changes to other servers, called backup domain controllers, within the same domain. You may now supply a server name (the name which this server will be known on the network), the role that this server will perform in that domain (primary or backup), and a domain name. Enter the name of the server or press Enter to select 'uname': |
Enter the name of the server or just press ENTER
to accept the default name. The default is the server name of the
old LAN Manager 2.2 backup domain controller.
For more information about entering a server name, see "Data
Needed during Installation" in Chapter 1 of this guide.
The system displays the following message:
Each server must be given a role in a domain. The possible roles are: primary domain controller: Administration server. Distributes user accounts information to backup domain controllers. Validates network logon requests. There can be only one primary domain controller per domain. backup domain controller: Receives user account information from the primary domain controller. Validates network logon requests and can be promoted to primary if the primary domain controller is not accessible. Enter role (primary or backup): |
Type backup and press ENTER.
The system displays the following message:
This installation will configure the server as a backup controller for you. You will be prompted to enter the name of the primary domain controller, and an administrative account name on the primary along with its password. In order for this configuration to complete successfully, the primary domain controller must be running and connected to the network. Enter the name of the primary domain controller or press Enter to select <old-pdc.serve>: |
Enter the name of the Advanced Server/9000 primary
domain controller. (The default that is displayed is the old LAN
Manager 2.2 primary domain controller.)
The system then prompts you for the name of the administrative
account on the primary domain controller:
Enter the name of an administrative account on <primary
domain controller> or press Enter to select 'administrator':
Enter the name of an administrative account and
press ENTER.
Enter the password for the administrative account.
This password must be the same as the password for the administrative
account on the primary domain controller.
The system then contacts the primary domain controller in
the Advanced Server/9000 domain and asks you to confirm your choices.
Type y and press ENTER.
The system then creates an Advanced Server/9000 database and
restores any customized print processor scripts, upgrades the share
list file, and restores the configuration file. The maxauditlog
and maxerrlog configuration parameters are removed from the lanman.ini
file because they are not valid in the Advanced Server/9000 environment.
The system starts the Advanced Server/9000. The installation
portion of upgrading a LAN Manager 2.2 server to backup domain controller
is complete. However, you must perform the steps in the following
procedure to upgrade your files.
Completing a LAN Manager 2.2 BDC Upgrade |
 |
To complete the upgrade of a LAN Manager 2.2 BDC server to
an Advanced Server/9000 BDC server, you must run the lmu_upgrade
command.
Type the following command at the HP-UX system console to
determine whether all of the user accounts were replicated from
the primary domain controller:
net user
Change to the /opt/asu/lanman/upgrade_bin
directory and type the following command to update the saved data
and configuration files:
lmu_upgrade -A
The lmu_upgrade -A command is used
to upgrade LAN Manager 2.2 access control files to the Advanced
Server/9000.
For complete information about the lmu_upgrade
command, see the section in this chapter.
Checking the Configuration |
|
After completing a LAN Manager 2.2 upgrade to the Advanced
Server/9000, you should check the server's lanman.ini
file and registry to determine whether modifications are needed.
Check the path displayed in the registry file to verify that
the logon scripts path is correct. This path uses as its base the
/var/opt/lanman/shares/asu directory and
will display in the scripts keyword as repl/import/scripts
or repl/export/scripts. If the role of the
server was changed during the upgrade or the server has been changed
from an import computer to export server, this path will need to
be changed.
Check the parameters in the [replicator] section to verify
whether the replicate, exportlist, (importlist), and exportpath
(importpath) keywords are valid.
LAN Manager 2.2 servers automatically enable the Directory
Replicator service. The Advanced Server/9000 requires the administrator
to assign a special account to this service. The Advanced Server/9000
does not start the Directory Replicator service automatically. The
account must be created and assigned to the Directory Replicator
service manually.
For more information about the Directory Replicator service,
see the Advanced Server/9000 Concepts and Planning Guide
and the Advanced Server/9000 Administrator's Guide.
Printable version
