The Advanced Server for UNIX (ASU) software is a Tru64 UNIX layered application that integrates Tru64 UNIX and Windows environments. The ASU software implements Windows NT Server Version 4.0 services, security, and functionality on a system running the Tru64 UNIX operating system software. The Tru64 UNIX system on which the ASU software is running appears as a Windows NT Server to other Windows systems and to users of Windows systems, and can participate in a Windows NT and Windows 2000 domain.
You can use native Windows commands and utilities to manage the ASU software and to make UNIX based file systems and printers available to Windows users as shares. Windows users connect to shares without modification to their software. Once connected, the Tru64 UNIX directory or printer associated with a share appears as a transparent extension to a Windows user's local computing environment.
This chapter describes how to install or upgrade the ASU software and
describes the ASU environment.
1.1 Preinstallation Tasks
Before installing the ASU software, you must:
Review the ASU documentation
Ensure that the Tru64 UNIX system on which you will install the ASU software meets the ASU software requirements
Decide how to authenticate user account information
Decide which interface you will to use to administer the ASU software
1.1.1 Reviewing the ASU Documentation
You can find the ASU documentation on the Tru64 UNIX Associated
Products Volume 2 CD-ROM in Hypertext Markup Language (HTML) format and Portable
Document Format (PDF).
To access ASU documentation on the CD-ROM, open the
ASU documentation library file,
/Advanced_Server/doc/html/LIBRARY.HTM
, in a Web browser.
In addition to this document, the ASU documentation includes:
The Release Notes that contains the latest ASU information that may not be documented elsewhere.
The Concepts and Planning Guide guide that contains information to help you plan, implement, and administer the ASU software.
1.1.2 ASU Software and Hardware Requirements
The system on which you will install the ASU software must be running the Tru64 UNIX operating system Version 5.1A or higher.
If you plan to configure the ASU software for international support, ensure that the system is running with Unicode support installed. See Section 1.10 for more information on configuring the ASU software for international support.
See the Installation Guide if you need to upgrade your version of the Tru64 UNIX operating system software.
There should be at least 7 MB of free disk space in the file system
containing the
/usr/net
directory.
1.1.3 Determining a Method for User Account Authentication
By default, the ASU server and Tru64 UNIX operating system software must authenticate a user's name and password before a user can access an ASU share. Therefore, a Windows user must have a domain user account that the ASU server uses for user authentication and a Tru64 UNIX user account that the Tru64 UNIX operating system uses for user authentication.
By default, when you create a domain user account, the ASU server automatically
creates a Tru64 UNIX user account in the local
/etc/passwd
file if an account with the same name does not exit.
The Tru64 UNIX
operating system software uses the local user account information for authentication.
However, you can configure the Tru64 UNIX operating system software to
direct authentication requests to a Windows 2000 Server or to a Windows NT
Server Version 4.0.
The Windows 2000 Server or Windows NT Server Version 4.0
uses its user account information to authenticate users on behalf of the Tru64 UNIX
system.
This is useful if you have user account information stored on a Windows
2000 Server or on a Windows NT Server Version 4.0 and you do not want to create
a user account database on the Tru64 UNIX system.
1.1.3.1 Windows 2000 Server Authentication
To configure the Tru64 UNIX operating
system software to use a Windows 2000 Server to authenticate users, you must
install the Windows 2000 Single Sign On (SSO) Version 2.0 or higher software
on the Windows 2000 Server and on the Tru64 UNIX system on which the
ASU server is running.
On the Tru64 UNIX system on which the ASU server
is running, you must enable the
UseActiveDirectory
registry
entry before you start the ASU server.
See Security Administration for more information about the SSO software.
See
Chapter 2
for more information about registry entries
and
Section B.1.9
for more information about the
UseActiveDirectory
registry entry.
1.1.3.2 Windows NT Server Version 4.0 Authentication
To configure the Tru64 UNIX operating system software to use a Windows NT Version 4.0 Server to authenticate users, you must install and configure the ASU SIA software on the system running the Tru64 UNIX operating system software. The ASU SIA software is provided in a subset with the ASU software and requires that the ASU server and transports also be installed. This option is available only on systems running the Tru64 UNIX Version 5.0 or higher operating system software and not using enhanced security.
See
Table 1-2
for information about the
ASU SIA software.
See
Section 3.6
for information
about using Windows NT Server Version 4.0 authentication.
1.1.4 Overview of ASU Administrative Interfaces
To administer the ASU software you can use:
ASU commands
net
commands
Tru64 UNIX commands and graphical user interfaces (GUIs)
Windows GUIs
Note
If you plan to configure the ASU Server in a Windows 2000 domain, then you must administer the ASU server by using Windows 2000 interfaces, except for file replication which must be administered form a Windows NT system.
The ASU commands,
net
commands, and ASU options for Tru64 UNIX
commands and GUIs are only available on Tru64 UNIX systems on which the
ASU server is installed.
1.1.4.1 The ASU Commands
The ASU commands are Tru64 UNIX style commands that you can use
to display information about, administer, and troubleshoot the ASU server
and domain.
You enter ASU commands in lowercase at the Tru64 UNIX command
prompt on a system running the ASU software.
See
Appendix E
for more information on ASU commands.
1.1.4.2 The net Commands
The
net
commands are Windows style commands that
you can use to create shares, domain user accounts, and groups and to display
information about and administer the ASU server, domain, shares, domain user
accounts, and groups.
A
net
command begins with the word
net
followed by a keyword and options.
You enter
net
commands
in lowercase at the Tru64 UNIX command prompt on a system running the
ASU software in the following form:
#
net keyword [/option]
See
Appendix D
for more information on
net
commands.
1.1.4.3 The Tru64 UNIX Commands and GUIs
The Tru64 UNIX user and file system commands and GUIs provide additional
ASU-related options that you can use to create and administer shares and domain
user accounts.
See
System Administration
for information on administering the ASU
server using Tru64 UNIX commands and GUIs.
1.1.4.4 The Windows GUIs
You can use the following Windows based GUIs to administer the ASU server and domain:
The Server Manager creates, displays information about, and administers shares.
The User Manager for Domains creates, displays information about, and administers domain user accounts and groups.
The Policy Editor displays information about and administers the ASU registry.
The Event Viewer displays ASU-related application, security, and system events.
You can administer the ASU server by using the version of these Windows
GUIs that are provided with a Windows NT Server Version 4.0 or a Windows 2000
Server.
For a system running another type of Windows operating system software,
you must install the version of these Windows GUIs that are provided in the
ASUADMnnn
subset as described
in
Section 1.3, then install the GUIs as described in
Section 1.8.
1.2 Upgrading the ASU Software
You use the Tru64 UNIX
setld
command to
deinstall the ASU subsets, then reinstall new ASU subsets.
Note
Upgrading an earlier version of the ASU software to ASU Version 5.1 or higher converts the SAM database, the ACL database, and ASU share file to a new format that is not compatible with previous versions of the ASU software. If you deinstall the ASU Version 5.1 or higher software and reinstall an earlier version of the ASU software, you must recreate the shares or restore a back up copy of the SAM database, the ACL database, and ASU share file and reapply any changes that you made since the back up. The ASU files to restore are:
/usr/net/servers/lanman/domains/* /usr/net/servers/lanman/datafiles/* /usr/net/servers/lanman/sharefile
Follow these steps to upgrade the ASU software:
As root, display the installed ASU subsets, for example:
#
/usr/sbin/setld
-i
|grep ASU |grep
-v
not |grep installed
Enter the
/usr/sbin/setld -d
command followed
by the name of each subset to deinstall, for example:
#
/usr/sbin/setld
-d
ASUBASE501 ASUTRAN501 ASUMANPAGE501
While ASU subsets are deinstalled, you are prompted to save ASU configuration files and the user account and share databases. Save these files and databases if you want to reuse the previous ASU configuration.
If you do not save these files and databases on a PDC:
ASU shares created on that system are removed.
Domain user accounts that were created by the ASU software are removed.
If you do not save these files and databases on a BDC:
ASU shares created on that system are removed.
The copy of the domain user account database is removed.
Although ASU shares are removed from a system, their associated Tru64 UNIX directories are uneffected.
Use the
setld
command to install the new
ASU subsets.
See
Section 1.3
for more information.
1.3 Installing the ASU Software
To install the ASU software you use the Tru64 UNIX
setld
command to install the ASU subsets.
ASU subsets are categorized as either mandatory or optional. The ASU server will not operate properly if you do not install the mandatory subsets. The optional subsets provide information and tools that you use to manage the ASU server.
Table 1-1
describes the ASU mandatory subsets.
Table 1-2
describes the ASU optional subsets.
The nnn variable in the subset name represents the
ASU version number.
See the ASU
Release Notes
for the current version
number.
Table 1-1: ASU Mandatory Subsets
Subset Name | Provides |
ASUBASEnnn |
ASU server functions. |
ASUTRANnnn |
The NetBEUI and NetBIOS over TCP/IP transports that the ASU server uses for network communications. |
Table 1-2: ASU Optional Subsets
Subset Name | Provides |
ASUADMnnn |
English language version of the Nexus tools, which are interfaces based on Microsoft Windows that you use to administer the ASU server. |
ASUADMJPnnn |
Japanese language version of the Nexus tools, which are interfaces based on Microsoft Windows that you use to administer the ASU server. |
ASUMANPAGEnnn |
English language version of the reference pages that describe ASU commands. |
ASUMANJPnnn |
Japanese language version of the reference pages that describe ASU commands. |
ASUSIAnnn |
A Tru64 UNIX security mechanism that enables Tru64 UNIX to use a Windows NT Server Version 4.0 for authentication. This subset is available only on systems running the Tru64 UNIX Version 5.0 or higher operating system software and not using enhanced security. |
Follow these steps to install the ASU subsets:
As the root user, insert and mount, in read-only mode, the Tru64 UNIX Associated Products Volume 2 CD-ROM. For example, on a system running Tru64 UNIX Version 5.0 or higher, enter:
#
mount
-r
/dev/disk/device_name /mnt
On a system running Tru64 UNIX Version 4.X, enter:
#
mount
-r
/dev/device_name /mnt
Where
device_name
is the name of the CD-ROM drive.
Enter the following
setld
command and follow
the instructions on the screen, for example:
#
setld
-l
/mnt/Advanced_Server/kit .
Informational messages display while the ASU subsets are installed.
When the installation is complete, unmount the Tru64 UNIX Associated Products Volume 2 CD-ROM.
See
Appendix A
for a sample ASU subset installation
procedure.
1.4 Postinstallation Tasks
After you install the ASU subsets, you must run the
asusetup
utility.
The
asusetup
utility:
Prompts you for information that is required to start the ASU server.
Default values are provided from a previous ASU installation if you saved the configuration files or otherwise from the Tru64 UNIX system information.
Note
Default values are used if you reboot the Tru64 UNIX system after using the
setld
utility to install the ASU subsets and before running theasusetup
utility.
Runs the ASU Installation Verification Procedure (IVP) to verify that the ASU subsets were correctly installed.
Starts the ASU server.
You run the
asusetup
utility by entering:
#
/usr/sbin/asusetup
If you exit the
asusetup
utility by pressing
Ctrl/C
, the ASU configuration is incomplete and you must rerun the
asusetup
utility.
The following sections describe the
asusetup
procedure
in detail.
See
Appendix A
for sample output generated by the
asusetup
utility.
See
Chapter 6
if you are configuring the ASU software
in a TruCluster cluster.
1.4.1 Configuring ASU Network Information
The
asusetup
utility displays information similar
to the following that shows the default network controllers that the ASU server
will use and the methods that the ASU server uses to resolve a NetBIOS name
to a TCP/IP address in a wide area network (WAN):
Controllers: TCP/IP = tu0 NetBEUI = tu0 Use DNS: yes Sub Domains: asu.company.com Use lmhosts: yes lmhosts file: /usr/net/servers/lanman/datafiles/lmhosts Use NBNS: no Primary NBNS address: Secondary NBNS address: Would you like to use this network information?[y/n]?
To use the default values, enter
y
.
If you enter
n
, you must provide a value for each item as follows:
Controllers
The ASU server provides and can use either or both of the following networking transport software on any Ethernet, FDDI, and Token Ring controllers supported by the Tru64 UNIX operating system software:
NetBEUI transport, which is used exclusively for local area networking
NetBIOS over TCP/IP, which is used over the system's installed TCP/IP transport software for local and wide area networking
The remaining items define the method of NetBIOS name resolution that the ASU server uses to communicate with systems in different TCP/IP subnets in a WAN. You can use any or all of the following methods:
A domain name server (DNS).
The value for the
Sub
Domains
item are the DNS subdomains that the ASU server will use
to try to resolve the NetBIOS name as a TCP/IP node name.
See
Network Administration
for more information on DNS.
An
lmhosts
file.
If you choose to use an
lmhosts
file, the
asusetup
utility creates it by default in the
/usr/net/servers/lanman/datafiles
directory.
You must edit the
lmhosts
file to
add:
An entry that includes the TCP/IP name and address of each system that is located on a different TCP/IP subnet with which the ASU server must communicate.
A special entry for the primary domain controller (PDC).
The following is a sample
lmhosts
file where the
PDC is named Summer in a domain called summer.dom and BDCs are named Fall,
Winter, and Spring:
12.100.4.13 Spring #dom:summer.dom 12.100.5.17 Fall #dom:summer.dom 12.100.5.36 Winter #dom:summer.dom 12.100.5.42 Summer #dom:summer.dom 12.100.5.42 "summer.dom \0x1b" # PDC entry
Note that the domain name entry must be padded with extra spaces to
fill 15 characters, which is the maximum length for a domain name.
In the
previous example,
summer.dom
is 10 characters, followed
by 5 spaces, followed by
\0x1b
, all within double quotes.
Also note that each node does not require an entry for itself.
A NetBIOS Name Service (NBNS), which is also called Windows Internet Name Service (WINS). You can configure a primary and secondary NBNS. The ASU server uses the primary NBNS for name resolution. If primary NBNS is not available, the ASU server uses the secondary NBNS.
The value for the NBNS address item must be the TCP/IP address of the server running the NBNS.
See your Windows documentation for more information on NBNS.
1.4.2 Configuring ASU Server Information
The
asusetup
utility displays output similar to the
following that shows the default values for ASU server information:
Server Name: Domain Name: Domain Role: Primary Name of Domain's Primary: Enter Password for Administrator: Would you like to use this general server information [y/n]?
To use the default values, enter
y
.
If you enter
n
, you must provide a value for each item as follows:
Server Name
The name of the ASU server. This is the name that users and other ASU servers and Windows servers use to communicate with this ASU server. If you enter a server name, the name can contain up to 15 alphanumeric English language characters and the following symbols: ~ ! # $ % ^ _ ( ) . -
Domain Name
The name of the domain that the ASU server will create or join.
The
default is the server name followed by a
.dom
extension,
for example
servername.dom
.
If you enter a domain name, it must be different from the ASU
server or system name and can contain up to 15 alphanumeric English language
characters and the following symbols: ~ ! # $ % ^ _ ( ) .
-
Domain Role
The role of the ASU server in the domain. The ASU server can be a:
Primary domain controller (PDC). There is only one PDC per domain. A PDC stores and maintains the user account database. A PDC authenticates domain user logon requests. The default is a PDC.
You cannot configure the ASU server as a PDC in a Windows 2000 domain.
Backup domain controller (BDC). The PDC must running before you configure a BDC. There can be many BDCs in a domain. A BDC receives a copy of the user account database to authenticate domain user logon requests.
You can configure the ASU server as a BDC in a Windows 2000 Server domain only if the Windows 2000 Server is configured for mixed mode.
Member server. There can be many member servers in a domain. A member server participates in a domain; however, it does not receive a copy of the user account database and therefore does not authenticate domain user logon requests.
You can configure the ASU server as a member server in a Windows 2000 Server domain whether the Windows 2000 Server is configured for mixed or native mode.
Name of Domain's Primary
The name of the domain's PDC if the ASU server is not the PDC.
Password for Administrator
For a PDC, you must supply an administrative password. For a BDC, you must supply the name and password of an Administrator account on the PDC. Passwords can be up to 14 alphanumeric English language characters and are case sensitive.
1.4.3 Configuring Listen Names
The
asusetup
utility displays output similar to the
following that shows the default listen names for the ASU server:
The ASU server currently listens for, and responds to, messages sent to these network names: listenname : server1 ExtraListenNames: (none) You can define Extra Listen Names for the server to listen for via the Registry parameter ExtraListenNames. Do you want to modify the ExtraListenNames entry [y/n]?
A listen name is a unique name assigned to the ASU server to which it
responds on the network.
Users can use any of the assigned listen names when
connecting to the ASU server.
For example, if an ASU server is assigned a
listen name of
server1
and the extra listen names of
server2
or
server3
, users can specify
\\server1
,
\\server2
, or
\\server3
when connecting to its shares.
To use the default values, enter
n
.
If you enter
y
, you are prompted to enter another listen name for the ASU server
or to delete a listen name assigned to the ASU server.
You can also configure extra listen names by directly modifying the
ExtraListenNames
registry entry.
See
Section B.1.4
for more information.
1.4.4 Starting the ASU Server
The
asusetup
utility prompts you to start the ASU
server.
Do not start the ASU server if you plan to configure the ASU server to:
Communicate in a language other then English. See Section 1.10 for more information.
Change the default behavior that automatically creates Tru64 UNIX user accounts. See Chapter 3 for more information.
Create Tru64 UNIX user accounts using NIS. See Chapter 3 for more information.
Create Tru64 UNIX user account home directories under
a single-letter subdirectory of
/usr/users
.
See
Chapter 3
for more information.
Change the default behavior that automatically creates shares for NFS exported file systems. See Chapter 4 for more information.
Change the default behavior to automatically create personal shares. See Chapter 4 for more information.
To start the ASU server, enter
yes
at the prompt.
If you enter
no
, the
asusetup
utility
exits.
To start the ASU server at a later time, enter:
#
net start server
1.4.5 Verifying the ASU Software Installation
If you start the ASU server, the
asusetup
utility
prompts you to run the ASU installation verification procedure (IVP) to test
that the ASU software was correctly installed.
Status messages display on the screen while the IVP runs.
If the ASU IVP reports a failure, reinstall the ASU software as described in Section 1.2.
If the ASU IVP continues to report a failure, see Chapter 8 or contact your support representative.
You can run the ASU IVP at any time by entering:
#
asuivp
See
asuivp
(8)asuivp
command.
1.4.6 Reconfiguring the ASU Software
To reconfigure ASU network and general values, reenter the
asusetup
command or use the ASU commands in
Table 1-3.
Caution
If you reconfigure a PDC as a member server, the domain user account database is removed. If you reconfigure a member server as a BDC or PDC, the local user account database is removed.
Table 1-3: ASU Server-Based Commands
ASU Setting | ASU Command |
Server name |
Do not directly edit the
|
Domain | #
/usr/sbin/joindomain |
Domain name | #
/usr/sbin/setdomainname |
Administrative password | #
net password |
ASU server role | #
/usr/sbin/promote |
Transport controllers |
You must restart the transports to effect any changes. |
See
Appendix E
or the associated command reference
page for more information on these commands.
1.5 ASU Directories
The ASU installation creates the
/usr/net/servers/lanman
directory.
Beneath this directory are subdirectories that contain ASU-related
files and subdirectories.
1.6 ASU Services
The following services automatically start when the ASU server starts:
The
Alerter
service notifies selected clients
about administrator-defined ASU alerts that occur on a particular system.
The
Alerter
service requires that the
Messenger
service be started on the selected client.
The
Browser
service maintains an up-to-date
list of computers on the network and provides the list to applications upon
request.
The
Eventlog
service records system, security,
and application events in ASU event logs.
The
Netlogon
service performs authentication
of user account logons.
The
Replicator
service replicates files
(such as profiles and login scripts).
The
Server
service provides remote procedure
call (RPC) support, and file, print, and named pipe sharing.
To see which ASU services are running, enter:
#
net start
Information similar to the following is displayed showing which ASU services are running:
These Advanced Server for UNIX Systems services are started: BROWSER EVENTLOG NETLOGON ALERTER SERVER The command completed successfully.
The following list describes ASU processes:
The
lmx.ctrl
process is the master control
process and must be running.
The
lmx.ctrl
process:
Accepts requests from new clients and passes them to the
lmx.srv
process.
Creates new
lmx.srv
processes as necessary.
Reminds the
lmx.srv
process to check for
autodisconnect timeouts.
Polls for events on the network or from other processes.
Tracks the time of day.
Receives instructions from the operating system.
Handles administrative actions that are not associated with a single client.
Listens for and routes nonguaranteed datagram broadcasts.
Announces the presence of the ASU server to the domain and retains announcements from other servers.
Schedules printer start and stop activity.
Coordinates transactions between client and server applications.
At least one
lmx.srv
process must be running.
Each
lmx.srv
process services the needs of a set of clients.
The
lmx.srv
process polls for incoming server message
block (SMB) requests from clients and the
lmx.ctrl
process.
The ASU server starts additional
lmx.srv
processes
based on the number of supported clients, or based on the maximum number of
specified server processes.
As more client sessions are established, more
lmx.srv
processes might start.
The
lmx.dmn
process must be running.
The
lmx.dmn
process handles client logon requests and account replication.
The
lmx.repl
process provides import file
replication services.
This process runs only if the
Replicator
service is started.
The
lmx.alerter
process starts if the
Alerter
service starts.
The
lmx.browser
process handles browse
requests if the
Browser
service starts.
ASU-related processes start when the ASU server starts. To see which ASU processes are running, enter:
#
ps
-ef
| grep lmx
Information similar to the following is displayed showing which ASU processes are running:
root 17726 1 0 12:03:36 0:00 lmx.alerter root 17713 17461 0 12:03:32 0:00 lmx.srv -s 1 root 17722 17874 0 12:03:35 0:00 lmx.srv -s 2 root 17726 1 0 12:03:36 0:01 lmx.dmn root 17728 1 0 12:03:36 0:01 lmx.browser root 17744 1 0 12:03:28 0:00 lmx.ctrl
1.8 Installing the Windows Based Interfaces
A Windows NT Server Version 4.0 and a Windows 2000 Server provides the
administrative interfaces that you can use to administer the ASU server.
To
administer the ASU server from a system that is running any other type of
Windows operating system software, you must install the ASU supplied Windows
based interfaces on that system.
1.8.1 Installing or Running Administrative Interfaces on Windows NT
Follow these steps to install or run the Windows based administrative interfaces on a system running the Windows NT operating system software:
On the Tru64 UNIX system, ensure that the Client-based Advanced Server Administration Tools subset is installed, for example:
#
setld
-i
|grep ASUADM |grep
-v
not |grep installed
If
ASUADMnnn
is displayed, the subset is installed.
Otherwise, you must install the
ASUADMnnn
subset.
See
Section 1.3
for information on installing ASU subsets.
Connect a network drive to the
astools
disk share.
Select the folder that corresponds with the version of the
Windows NT operating system.
For example, select the
winnt.40
folder for Windows NT 4.0.
You can:
Start the interface you want by double-clicking on the appropriate file:
The
srvmgr.exe
file starts the Server Manager.
The
usrmgr.exe
file starts the User Manager
for Domains.
The
poledit.exe
file starts the Policy
editor.
Install the interfaces by running the
setup.bat
program.
The executable files for the interfaces are installed in the
C:\WINNT\SYSTEM32
directory.
Start an interface by double-clicking
on an executable as described above.
1.8.2 Installing Administrative Interfaces on a Windows 95 or Windows 98 System
Follow these steps to install the Windows based administrative interfaces on a system running the Windows 95 or Windows 98 operating system software:
On the Tru64 UNIX system, ensure that the Client-based Advanced Server Administration Tools subset is installed, for example:
#
setld
-i
|grep ASUADM |grep
-v
not |grep installed
If
ASUADMnnn
is displayed, the subset is installed.
Otherwise, you must install the
ASUADMnnn
subset.
See
Section 1.3
for information on installing ASU subsets.
Connect a network drive to the
astools
disk share.
Select the Add/Remove Program icon from the Control Panel.
Select the Windows Setup tab.
Click on the Have Disk button.
Use the Browse button and
click on the drive that specifies the connection to the
astools
directory to which you connected in Step 2.
Expand the
Win95
directory.
Select the
srvtools.inf
file and click
on the OK buttons in the Open window and in the Install From Disk window.
Install the interfaces by clicking in the box next to the Windows NT Server Tools entry and then on the Install button in the Have Disk window.
Click on the OK button after the files are copied.
If you plan to run the Server Manager interface, edit the
autoexec.bat
file to include
srvtools
to the
path and reboot the system.
For example, if you boot from drive
C
, either append
srvtools
to the
PATH
statement or, if there is no
PATH
statement,
enter:
SET PATH=%PATH%;C:\srvtools
Installing the administrative interfaces:
Copies the Windows NT Server Tools files to the
srvtools
directory on the boot drive
Adds
Windows NT Server Tools
to the Start
button Programs menu
Adds a
Windows NT Server Tools
program
group to the Program Manager, which is compatible with Windows 3.x
Adds extensions to the Windows Explorer so that you can change security settings when viewing disk and printer shares on a computer running the ASU, Windows NT Server, or Windows NT Workstation software
Note the following restrictions when administering ASU from a Windows 95 system:
Some administrative tasks require that you log on or enter your password for verification before you can perform an action.
You can create trust relationships between domains but you cannot verify them.
The following methods for selecting an object to administer do not work on a system running Windows 95:
Administering print queues through the Printers list in the My Computer window. These print queue objects represent print queues local to your Windows 95 computer, even if the queue is redirected to an ASU printer queue.
Using the Windows 3.x Printer Manager. The Printer Manager does not exist in Windows 95; the Printers icon in the Main group of the Program Manager is a shortcut to the Printers list in My Computer window.
Using the File Manager in the Program Manager window. Installing Windows NT Server Tools does not add a Security menu to the File Manager as it does for Windows 3.x.
ASU licenses are supplied in the form of a product authorization key
(PAK) called
ASDU-CONNECT
.
You load the
ASDU-CONNECT
PAK into the Tru64 UNIX License Management Facility (LMF).
One
ASDU-CONNECT
license is used when the user of
a Windows system browses or first connects to an ASU share.
The license allows
the user to browse and connect to shares for which they have permission.
The
Windows system retains the license until the user stops browsing and terminates
all connections to shares, at which time the license can be reassigned.
A
Windows system uses one
ASDU-CONNECT
license from each
ASU server to which the user browses or connects.
ASDU-CONNECT
PAKs are available in license units
of 10, 25, 50, 100, 250, 500, and 1,000.
You purchase
ASDU-CONNECT
PAKs based on the number of users.
For example, if you expect 275
domain users to access shares, then you should purchase one PAK for 25 licenses
and one PAK for 250 licenses.
The ASU software provides two free built-in licenses. You do not need to load these licenses into LMF, nor will you see them in LMF.
To list the number of available
ASDU-CONNECT
licenses,
enter:
#
asustat
-L
To list the client names that have a license, enter:
#
asustat
-c
To view the system event log to show if a client was issued or denied a license, enter:
#
elfread
-d
system | more
See
asustat
(8)elfread
(8)1.10 Configuring International Support
You can configure the ASU server to communicate in a language other than English. To do so, follow these steps:
Install and configure the ASU software as described in
Section 1.3.
Do not start the ASU server when prompted by the
asusetup
utility.
Use a text editor to set the
lang
parameter
in the [
lmxserver
] section of the
lanman.ini
file.
Add the
lang
parameter if it is not there.
The
lang
parameter sets the character set and locale
that the ASU server uses to communicate.
For example, if the Windows systems
are running the French edition of Windows, set the
lang
parameter to
fr_FR.ISO8859-1
, which is the Tru64 UNIX
French locale.
For example:
[ lmxserver ]
lang=fr_FR.ISO8859-1
The ASU server supports the Tru64 UNIX locales listed in the
l10n_intro
reference page except for Japanese SJIS and Traditional
Chinese.
See
l10n_intro
(5)
Install the Unicode support for the locale.
The Unicode support includes codeset converters that the ASU server uses to convert names between the Windows system and Tru64 UNIX character sets. The Unicode support is in the Tru64 UNIX Worldwide subsets. For information on installing codeset subsets, see the WLS installation procedure in the Installation Guide Advanced Topics.
Start the ASU server, for example:
#
net start server