| »
General
questions
»
Licensing
questions
»
Administrative
questions
General
questions
|
 |
|
Q.
What is ASU?
A. ASU is a Tru64
UNIX layered application that integrates Tru64
UNIX and Windows environments. The ASU software
implements Windows NT Version 4.0 Server services
and functionality on a system running the Tru64
UNIX Version 4.0F or higher operating system software.
The Tru64 UNIX system on which ASU is running
appears as a Windows NT Version 4.0 server to
other Windows systems and to users of Windows
systems.
You use 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 access
the shares without modification to their software.
Q.
Can I try the ASU software?
A. Yes! Included
with the ASU software are two complimentary connects.
See Two
Free Connects for more information
Q.
Where is the ASU software?
A.
.
Licensing
questions
|
|
|
Q.How
is ASU licensed?
A. 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).
ASDU-CONNECT PAKs are available
in license quantities of 10, 25, 50, 100, 250,
500, and 1,000. You purchase ASDU-CONNECT
PAKs based on your needs. For example, if you
expect 275 Windows users to access disk and printer
shares, then you should purchase one PAK for 25
licenses and one PAK for 250 licenses.
One ASDU-CONNECT license is used
by each Windows client that browses or first connects
to a share on the Tru64 UNIX system on which the
ASU software is running. The license allows the
client to browse and connect to disk and printer
shares offered by that ASU server. The client
retains the license until it stops browsing and
terminates its connections, at which time the
license can be reassigned. A client uses an ASDU-CONNECT
license from each ASU server to which it browses
or connects.
Q.
How do I purchase ASU license PAKs?
A. You can purchase ASDU-CONNECT
PAKs from your HP
sales representative or authorized business
partner.
The following table lists the quantities
and part numbers for ASDU-CONNECT PAKs:
| 1 |
QL-5U29M-3B |
| 10 |
QL-5U29M-3C |
| 25 |
QL-5U29M-3D |
| 50 |
QL-5U29M-3E |
| 100 |
QL-5U29M-3F |
| 250 |
QL-5U29M-3G |
| 500 |
QL-5U29M-3H |
| 1000 |
QL-5U29M
3J |
Q..
What do I do after I have ASU license PAKs?
A. When you have the ASDU-CONNECT
PAK, you must:
- Load the PAK into the License Management Facility
(LMF).
- Install and configure the ASU software.
See the ASU Release
Notes, Concepts
and Planning, and Installation
and Administration guides for more information.
Administrative
questions
|
|
|
Q.
How do I install the ASU software?
A. The ASU software has mandatory
and optional subsets. You use the I UNIX setld
utility to install the ASU subsets.
After the installation you run a
configuration utility to provide information that
the ASU software requires to start.
Q.
How do I configure the ASU software?
A. The ASU software is configured
by values assigned to value entries stored in
a central database, called the ASU registry, and
by values assigned to parameters in the lanman.ini
configuration file.
Registry value entries and lanman.ini
parameters are assigned default values, which
you can change.
See the ASU Installation
and Administration guide for more information
about the ASU registry and the lanman.ini file.
Q.
What
is a disk share?
A. A disk share is a file
system that is made available through the ASU
software. Windows users map a network drive
to connect to the disk share. If the user
is granted access to the disk share, the disk
share appears as a transparent extension to the
user's local computing environment.
Q.
What is a printer share?
A. A printer share is a network
printer that is made available through the ASU
software. If the user is granted access
to the printer share, the user can configure their
system to use the printer share, which then becomes
a transparent extension to the user's local computing
environment.
Q.
How does the ASU software implement
security?
A. By default, Windows NT
and Tru64 UNIX security policies are enforced
when a Windows user requests access to a share.
A Windows user must pass the following three levels
of security before they can access a share:
- Windows NT share level security
- Windows NT File System (NTFS) security
- Standard UNIX file and directory
security
You can configure the ASU software
to only use Windows NT security.
Q.
Do I have to create user accounts?
A. Yes. You must create a
domain user account for each user. A domain user
account is used to authenticate Windows NT security
policies. If Tru64 UNIX security policies
are enforced, users must also have one of the
following accounts to authenticate Tru64
UNIX security policies:
- A Tru64 UNIX user account located in
the local /etc/passwd file or network information
service (NIS). By default, when you create the
domain user account, the ASU server will create
a user account in the local /etc/passwd file
or NIS if an account with the same name does
not exist.
- A user account on a Windows 2000 or Windows
NT Server Version 4.0. 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 store user
account information on a Windows 2000 Server
or on a Windows NT Server Version 4.0 and you
do not want to store user account information
on the Tru64 UNIX system.
Q.
What is a domain?
A. A domain is a group of
ASU and Windows NT servers that share a central
database that contains information about domain
user accounts and groups of domain user accounts.
Servers sharing the database eliminates the need
of users having accounts on each server.
Each domain includes one server that is configured
as the primary domain controller (PDC), which
maintains the master copy of the database, and
usually one or more backup domain controllers
(BDCs) to which the PDC replicates database changes.
BDCs provide fault tolerance in case the PDC is
unavailable and participates in user domain log
in authentication. Once authenticated, users can
access the disk and printer shares to which you
have granted them access.
You can establish trust relationships between
domains where the controllers in one domain trusts
the authority of another domain's database.
Trust relationships expands users access to include
the disk and printer shares that are offered by
servers in the domains that are participating
in the trust relationship.
Q.
Can I use Windows-based tools
to manage the ASU software?
A. Yes, you use the:
- Windows-based User Manager for Domains utility
to create and manage domain user accounts and
groups.
- Server Manager utility to create and manage
domain user account and group access to disk
shares.
- Add Printer Wizard to create and manage printer
shares.
Q.
Can I manage ASU from UNIX?
A. Yes, you can administer
the ASU software using net commands on a system
running the Tru64 UNIX Version 4.0F or
higher software on which the ASU software is installed.
You can also use the default Tru64
UNIX Motif-based GUI tools (such as dxaccounts,
dxfileshare, or dxprint) on a system running the
Tru64 UNIX Version 5.0 or higher software
on which the ASU software is installed.
Q.
How many client can connect to the ASU server?
A. Several thousand clients
have connected to a single ASU server however,
the answer to this question depends on the size
of the server on which the ASU software is running
and the amount of network activity between the
clients and server.
|
