Windows NT Workstation 4.0
If you wish to install a number of servers automatically, you can install Advanced Server using response files. These files are created using the UNIX system pkgask utility. Response files allow the server to be installed with no user interaction.
For information about the pkgask utility, consult your UNIX system documentation.
Advanced Server includes an optional package of on-line manual pages which describe UNIX system commands and APIs.
In order to make these manual pages available to network users, you must install them on Advanced Server.
To install the Manual Pages Package
1. Log on to the UNIX system as root.
2. Insert the Advanced Server installation medium into the appropriate drive.
3. Type the following command and press ENTER:
pkgadd -d devicename
Replace devicename with the appropriate device name.
The system displays the installation menu.
4. Type the number that corresponds with asuman and press ENTER.
The system installs the UNIX system commands and API manual pages.
To verify that the Manual Pages Package has been installed, type the following command at the Advanced Server command prompt,
man NetServerGetInfo
For a list of UNIX system commands, see Chapter 4, "Administering Advanced Server at the Command Prompt."
For a list of UNIX system APIs, see the Advanced Server API Reference.
Advanced Server includes network-based administrative tools for use on the following Microsoft Windows client computers:
Windows NT Workstation 4.0
Windows NT Workstation 3.51
Windows 95
Windows for Workgroups
To install the Administrative Tools Package
1. Log on to the UNIX system as root.
2. Insert the Advanced Server installation medium into the appropriate drive.
3. Type the following command and press ENTER:
pkgadd -d devicename
Replace devicename with the appropriate device name.
The system displays the installation menu.
4. Type the number that corresponds with astools and press ENTER.
To verify that the Administrative Tools Package has been installed, type the following command at the Advanced Server command prompt:
net share
Advanced Server should display the ASTOOLS share.
For information on how to install client-based administrative tools, see Chapter 3, "Installing Network and Administrative Client Software."
Advanced Server includes the following Microsoft client software:
Microsoft Network Client for MS-DOS, Version 3.0
Microsoft LAN Manager for MS-DOS Client, Version 2.2c
Microsoft LAN Manager for OS/2 Client, Version 2.2c
TCP/IP 32 for Windows for Workgroups, Version 3.11
Windows for Workgroups, Version 3.11, Update Files
You must install this package on your server before you can create installable disks as described in Chapter 3, "Installing Network and Administrative Client Software."
To install the Microsoft client package
1. Log on to the UNIX system as root.
2. Insert the Advanced Server installation medium into the appropriate drive.
3. Type the following command and press ENTER:
pkgadd -d devicename
Replace devicename with the appropriate device name.
The system displays the installation menu.
4. Type the number that corresponds with msclients and press ENTER.
The system installs the client disk images. After copying all of the files to the Advanced Server, a shared resource named MSCLIENT is created. This shared resource contains the software for all three client types, as well as an upgrade to the Windows for Workgroups TCP/IP protocol, and updates for Windows for Workgroups clients.
This section describes how to remove Advanced Server from your UNIX system computer. During the removal procedure, you will be prompted to save data items and configuration files. These saved files can be used if you re-install the server.
The server must be stopped in order to remove the server software. If you do not stop the server, you will be prompted to do so. You may want to notify users that you plan to stop the server.
The system will determine whether any packages need to be removed before Advanced Server can be removed. If the server detects a dependency, it will indicate which packages need to be removed first.
To remove Advanced Server
1. Log on at the Advanced Server command prompt as root.
2. Type pkgrm and press ENTER.
3. Type the number that corresponds with asuserver and press ENTER.
Confirm that you want to remove the package when prompted.
If the server is running, the removal script prompts you to stop the server. You must stop the server in order to remove the Advanced Server software.
The system displays the following message:
If you are upgrading the Advanced Server for UNIX Systems, or think you may re-install in the future, there are certain data items you may wish to save:
- user files located in the public directories - customized print processor scripts - shared printers - list of shared directories (sharefile) - Advanced Server for UNIX Systems users and accounts - configuration files
- WINS database
Since this server is currently configured as a primary domain controller (PDC), it is strongly recommended that you save, at least, the Advanced Server for UNIX Systems users and accounts information if you plan on re-installing this server as a PDC in the same domain. If you remove the Advanced Server for UNIX Systems users and accounts information, you will need to reconfigure each machine in the domain.
Would you like to retain any of these data items [y/n]? y
4. Type y or n to save or remove data items and press ENTER.
If you respond n, the system deletes all of these files.
If you respond y, you will be prompted to save or delete each data item individually. If you decide to save any of these data items, the system automatically saves the Advanced Server configuration files.
When the removal process is complete, the system displays the following message:
Removal of <asuserver> was successful.
If an Advanced Server computer served as a backup domain controller in a domain, an account for it will remain in the database of the primary domain controller.
Use Server Manager to remove the account from the domain after you have removed the Advanced Server software.
Warning
Do not remove the backup domain controller account if you intend to re-install the backup domain controller in the same domain.
There may be occasions when an Advanced Server primary domain controller must be re-installed in an existing domain without the benefit of having saved data and configuration files.
If you re-install a primary domain controller without saved data, then the existing backup domain controllers no longer have machine accounts and security identification in the domain.
Use the following procedure to recover a primary domain controller in an existing domain.
To re-establish a primary domain controller in a domain
1. Promote a backup server in the domain to primary domain controller.
2. Re-install Advanced Server on the former primary domain controller as a backup server.
3. Promote the backup server to primary domain controller.
4. Demote the temporary primary domain controller to backup server.
A LAN Manager server can be part of an Advanced Server domain and can function as a backup domain controller. However, it cannot function as a primary domain controller in the Advanced Server domain.
For information on the differences between Advanced Server and LAN Manager, see Advanced Server Concepts and Planning.
Use the following procedure to move a LAN Manager server to an Advanced Server domain.
To move a LAN Manager server to an Advanced Server domain
1. On the Advanced Server primary domain controller:
Create a LAN Manager administrative account (admin) and password using User Manager.
Add the LAN Manager administrative account to the Domain Admins group in Advanced Server.
2. On the LAN Manager server:
Use the net accounts command to change the role of the LAN Manager server to standalone as follows:
net accounts /role:standalone
Stop the LAN Manager server.
If necessary, edit the lanman.ini file to change the domain of the LAN Manager server to the domain of the Advanced Server.
Start the LAN Manager server.
At the LAN Manager server console, log on to the Advanced Server domain using the LAN Manager administrative account and password.
At the LAN Manager server console, use the net accounts command to change the role of the LAN Manager server to backup domain controller as follows:
net accounts /role:backup
Changing the role of the LAN Manager server will result in the following events:
The SERVERS group will be created in Advanced Server and the LAN Manager machine account will be added as a member of that group.
The Advanced Server primary domain controller will replicate the user accounts database to the LAN Manager backup domain controller.
