The manner in which the ASU server interoperates with the Tru64 UNIX operating system software depends on the values assigned to value entries stored in a central database called the ASU registry.
The ASU registry largely replaces the
lanman.ini
file, which was previously used to configure the ASU software.
Review the
/usr/net/servers/lanman/regfiles/reg.ini
file to see which
lanman.ini
parameters were moved to the ASU registry.
Not all parameters in the
lanman.ini
file moved
to the registry, and the
lanman.ini
file is still used
for some configuration parameters.
See
Appendix C
for information about the
lanman.ini
file.
This chapter describes how to view and change the value of value entries
in the ASU registry.
2.1 ASU Registry Overview
The ASU registry is a hierarchical database of subtrees, keys, subkeys, and value entries that define how the ASU server interoperates with the Tru64 UNIX operating system software.
You change the default behavior of the ASU server by changing a value assigned to a value entry. To locate a value entry you follow a registry path that begins with a subtree. The ASU registry has the following subtrees:
HKEY_LOCAL_MACHINE
, which contains information
about the local system.
HKEY_USERS
, which contains user profile
information.
Users on remote systems use the profiles that are loaded into
the registry on their own computers.
From a subtree you choose a key and perhaps several subkeys to locate
a value entry.
For example,
Figure 2-1
shows that the registry
path to value entries for the
UserServiceParameters
subkey
is in the
HKEY_LOCAL_MACHINE
subtree,
SYSTEM
key,
CurrentControlSet
subkey, then
Services
subkey.
This registry path is displayed as:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/ UserServiceParameters
Figure 2-1: Registry Path
Figure 2-2
shows some of the keys and subkeys for
the
HKEY_LOCAL_MACHINE
subtree.
Figure 2-2: HKEY_LOCAL_MACHINE Keys and SubKeys
Figure 2-3
shows some of the keys and subkeys for
the
HKEY_USERS
subtree.
Figure 2-3: HKEY_USERS Keys and SubKeys
A subkey usually has several value entries. Each value entry defines how the ASU server and the Tru64 UNIX operating system software interoperate for a specific task.
See Appendix B for a complete description of registry value entries.
The following is an example of a value entry:
The three parts of a value entry are:
Name - The value entry name.
Data type - The value entry class or type.
Value - The value assigned to the value entry. The type of value depends on the data type, as described in Table 2-1.
Table 2-1: Registry Data Types and Values
Data Type | Type of Value |
REG_SZ | A sequence of characters representing readable text.
The following example shows that the
UserComment
is
ASU :
UserComment:REG_SZ:ASU Enclose
multiple words in quotes.
The following example shows that the
UserComment
is
ASU user :
UserComment:REG_SZ:"ASU
user" |
REG_DWORD | A 4-byte number.
Value entries of this type display
in binary, hexadecimal, or decimal format.
The following example shows the
value entry that enables the mixed-case support:MixedCaseSupport:REG_DWORD:1 |
REG_EXPAND_SZ | An expandable data string, which is text that contains
a variable that is replaced when called by an application.
The following
example shows the value entry that replaces the string
%SystemRoot%
with the location of the directory containing the ASU system files:File:REG_EXPAND_SZ:%SystemRoot%\file.exe |
REG_MULTI_SZ | A multiple string in readable text, such as a list or
multiple values.
Entries are separated by NULL characters.
The following example
shows Administrator and peter are users who receive alert messages:
AlertNames:REG_MULTI_SZ:Administrator peter |
2.2 Viewing and Changing Registry Value Entries
Default values are assigned to value entries. You can change the default values; however, providing an incorrect value can cause unexpected results, including failure of the ASU software.
Use the following interfaces to view and change registry value entries:
The
regconfig
command, a Tru64 UNIX
command-line interface
The Registry Editor, a Windows based interface
The ASU Administrator, a Windows based interface
The System Policy Editor, a Windows based interface
Note
You must stop and restart the ASU server to effect most changes in the ASU registry.
The
regconfig
command is a command that you enter
at the Tru64 UNIX command prompt on a system that is running the ASU
software.
To display information about common keys, subkeys, and value entries, enter:
#
regconfig
-l
To display specific information about a key, subkeys, and value entries,
you must provide the full registry path.
For example, to display information
about the value entries for the
UserServiceParameters
subkey,
enter the following command.
The backslash (\) at the end of a line indicates
continuation.
Enter the entire command, then press the Enter key.
# regconfig System/CurrentControlSet/Services/\ AdvancedServer/UserServiceParameters
Output similar to the following is displayed that shows the name, data
type, and value for each value entry for the
UserServiceParameters
subkey:
CreatePersonalShare:REG_DWORD:1 CreateUnixHomeDirectory:REG_DWORD:0 CreateUnixUser:REG_DWORD:1 DeleteUnixHomeDirectory:REG_DWORD:0 Exclude:REG_SZ:0-100 ForceUniqueUnixUserAccount:REG_DWORD:0 GroupUpdateTime:REG_DWORD:3600 MapExistingUnixUser:REG_DWORD:1 MinUnixUid:REG_DWORD:32767 NewUserShell:REG_SZ:/bin/sh NISPasswordFile:REG_SZ:/var/yp/src/passwd PreserveCase:REG_DWORD:0 PreserveNumericUserName:REG_DWORD:0 SpreadUnixHomeDirectory:REG_DWORD:0 SyncUnixHomeDirectory:REG_DWORD:0 SyncUnixPassword:REG_DWORD:0 UseActiveDirectory:REG_DWORD:0 UseNIS:REG_DWORD:0 UserComment:REG_SZ:Advanced Server for UNIX user UserRemark:REG_SZ:Users Director
To change values for value entries, you must provide:
The full registry path to the value entry
The name of the value entry
The type of the value entry
The new value for the value entry
For example, to change the value of the
UserComment
to
ASU user
, enter the following command.
The
backslash (\) at the end of a line indicates continuation.
Enter the entire
command, then press the Enter key.
# regconfig System/CurrentControlSet/Services/\ AdvancedServer/UserServiceParameters UserComment \ REG_SZ "ASU user"
See
regconfig
(8)regconfig
command.
2.2.2 Registry Editor
The Registry Editor is a Windows based interface that you use on a system that is running the Windows NT operating system software.
Note
You cannot use the Windows 95 Registry Editor to remotely edit the ASU Registry.
Follow these steps to start the Registry Editor on a Windows NT system:
Log in to the Windows NT system using the ASU administrator account.
Run the
regedt32.exe
application, which
is in the
%SystemRoot%\system32
folder.
When the Registry Editor starts, a window is displayed for each subtree for the local computer's registry.
Choose the Select Computer item on the Registry menu.
Enter the name of the ASU server in the Computer: field.
Click on the OK button.
When you connect to an ASU registry, the
HKEY_USERS
and
HKEY_LOCAL_MACHINE
subtrees are displayed.
The Registry Editor displays registry information in two frames. Keys and subkeys are displayed in the left frame and their value entries are displayed in the right frame as shown in the following figure:
Follow these steps to change a value:
Double-click on a value entry.
The String Editor dialog box is displayed, as shown in the previous figure.
Type the new value in the string field.
Click on the OK button.
The System Policy Editor is a Windows based interface that you can use to view and manage policies that define the environment for specific Windows computers, users, or groups when logged in to a system running the ASU server.
Using the System Policy Editor you can set:
A user-specific policy that applies to each domain user or
group.
Most policies are user-specific.
User-specific policies are always
merged into the
HKEY_CURRENT_USER
key of the registry.
A machine-specific policy that applies to all users on a Windows
system and does not change according to user since it does not follow users
as they move between different systems.
Machine-specific policies are always
merged into the
HKEY_LOCAL_MACHINE
key of the registry.
The System Policy Editor saves settings in a single policy (.POL
) file.
When a user logs in, a program called the policy downloader
starts.
The policy downloader is installed on every Windows client.
The policy
downloader looks on the network for the policy file, opens the policy file,
looks for an entry using the local computer name or user name, and merges
the administrator's registry settings as defined in the policy file, into
the local registry.
If the downloader does not find an entry with the local
computer name or user name in the policy file, then it looks for the
DEFAULT USER
or
DEFAULT COMPUTER
entry and uses
those registry settings for the merge.
If there are no entries for a specific
user or computer and default entries do not exist, then no merge takes place.
The System Policy Editor is in the Client-based Advanced Server Administration Tools subset. See Section 1.8 for information on installing the Policy Administrator.
When the System Policy Editor starts, it displays icons for the users and computers with entries in the policy file.
See the System Policy Editor online help for more information on managing
policies.
2.2.4 ASU Administrator
The ASU Administrator is a Windows NT based interface.
Unlike the other
registry editors, the ASU Administrator only permits you to select or enter
allowable values to modify value entries, which prevents you from entering
an incorrect value in the registry.
2.2.4.1 Installing the ASU Administrator Interface
Follow these steps to install the ASU Administrator interface:
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.
Log in to the system that is running the Windows NT operating
system using the ASU administrator account that was created during the
asusetup
procedure.
Map a network drive to the
astools
disk
share.
Expand the
asuadm
folder.
Run the
setup.bat
program.
After you install the ASU Administrator interface, disconnect
the network drive to the astools disk share and create an icon for the ASU
Administrator interface (c:\winnt\system32\asuadm.exe
).
2.2.4.2 Using the ASU Administrator Interface
Follow these steps to use the ASU Administrator interface:
Log in to the Windows NT system using the ASU administrator
account that was created during the
asusetup
procedure.
Run the
asuadm.exe
application, which is
in the
%SystemRoot%\system32
folder on Windows NT systems.
The ASU Administrator interface starts and displays a Select Computer dialog box.
For the system for which you want to view or change registry values, either:
Enter the system name in the Computer field.
Click on system name in the Select Computer window.
Click on the OK button.
Click on the Policy tab. A policy is similar to a registry key or subkey.
In the Policy for: window, click on the policy for which you want to view or change value entries.
Click on the Properties button.
A Properties window is displayed for the policy. The Properties window displays descriptions. A description is similar to a value entry. Next to each description is its value.
Depending on the value type, you change values by either:
Clicking in a box to enable or disable a value entry. A check mark in a box indicates that the value entry is enabled.
Choosing a value from a list of items.
The following figure shows an ASU Administrator Properties dialog box:
The following list shows ASU Administrator policies and their related registry value entries:
Alerter Service
SYSTEM\CurrentControlSet\Services\Alerter\Parameters IncludeMessageHeader IncludeMessageHeader NotOnNetworkCacheTimeout
Computer Browser Service
SYSTEM\CurrentControlSet\Services\Browser\Parameters MasterUpdate BackupUpdate BackupRecovery MoreLog
Connected Clients
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters LogonQuery QueryDelay RelogonDelay
Connected Clients
SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters AutoDisconnect
File Name Space Mapping
SYSTEM\CurrentControlSet\Services\AdvancedServer\FileServiceParameters NameSpaceMapping UniqueSuffixLength MixedCaseSupport TruncatedExtensions MappingSeparator
Netlogon Service
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters Scripts Pulse (PDC only) Update (BDC only) Randomize (BDC only) SSIPasswdAge (BDC only)
Server Announcement
SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters Hidden SrvAnnounce SrvAnnounce
Tru64 UNIX Account Mapping
SYSTEM\CurrentControlSet\Services\AdvancedServer\FileServiceParameters CreateUnixUser
Tru64 UNIX File System Integration
SYSTEM\CurrentControlSet\Services\AdvancedServer\FileServiceParameters IgnoreUnixPermissions UnixDirectoryCheck UnixFilePerms UnixDirectoryPerms UseUnixGroups UseUnixLocks RootOwnsFilesCreatedOnNFS
UPS Service
SYSTEM\CurrentControlSet\Services\UPS\Parameters IgnoreSIGPWR PowerFailAddress PowerFailMessage PowerMessageInterval
Users Alerts
SYSTEM\CurrentControlSet\Services\AdvancedServer\AlertParameters AertAdminOnLicenseOverFlow AlertUserOnLicenseOverFlow
Users Alerts
SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters AccessAlert ErrorAlert LogonAlert