1    Advanced Server Version 5.1B Overview

The following sections describe new features, command improvements, and changes and corrections in this release.

1.1    New Features

The following sections describe new features in this release.

1.1.1    Creating A Personal Disk Share

There is a new registry entry, CreatePersonalShare, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/UserServiceParameters key. The CreatePersonalShare entry specifies whether or not the ASU server will automatically:

The ASU server creates a personal disk share as a hidden disk share mapped to the user's UNIX home directory. The ASU server will not create a personal disk share if the UNIX home directory does not exist or if there is an existing disk share with the same name. A hidden disk share has a name that ends with a dollar sign ($) and does not display when browsing the ASU server. For example, creating a Tru64 UNIX user account named peter will automatically create a personal disk share called peter$ mapped to peter's home directory. A user can connect to a hidden disk share by appending the dollar sign to the share name.

The default value is 0 (do not create, delete, or rename a personal disk share). If you enable the CreatePersonalShare entry, you must also enable the CreateUnixUser entry, which is enabled by default.

1.1.2    Creating User Home Directories

There is a new registry entry, CreateUnixHomeDirectory, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/UserServiceParameters key. The CreateUnixHomeDirectory entry specifies whether or not the ASU server creates a Tru64 UNIX home directory when it creates a Tru64 UNIX user account.

Not creating Tru64 UNIX home directories is useful if you want to create Tru64 UNIX user accounts to assign files and directories the proper Tru64 UNIX ownership, but do not want users to log directly in to the system.

The default value is 1 (create Tru64 UNIX home directory).

1.1.3    Hiding TruCluster Members

There is a new registry entry, HideClusterMember, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/Parameters key. The HideClusterMember entry specifies whether or not the Network Neighborhood interface and other browse functions display TruCluster members. The Network Neighborhood interface and other browse functions will display the cluster alias regardless of the value of the HideClusterMember entry.

The default value is 0 (do not hide TruCluster members).

1.1.4    Increasing Print Jobs

The Tru64 UNIX operating system software now supports more than 1000 print jobs in a queue. You can set the maximum number of print jobs on a per-queue basis by assigning a value to the mj entry in the /etc/printcap file. The ASU server supports the use of the mj entry through the use of the new registry entry, MaxPrintJobs, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/Parameters key. The MaxPrintJobs entry specifies the maximum number of print jobs allowed in any class queue created by the ASU server.

The MaxPrintJobs entry is only used when a queue is created and does not affect existing queues.

The default value is 1000 print jobs.

1.1.5    Print Job Names

There is a new registry entry, MaxPrintJobName, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/Parameters key. The MaxPrintJobName entry specifies the maximum number of characters for a print job name. Characters that exceed the value of the MaxPrintJobName entry are truncated.

The default value is 0 characters (do not truncate print job names)

1.1.6    Numeric Tru64 UNIX User Names

There is a new registry entry, PreserveNumericUserName, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/UserServiceParameters key. The PreserveNumericUserName entry specifies whether or not a Tru64 UNIX user account name is created with a pre-pended letter a when creating a domain user account whose first character is numeric.

Enabling this entry is useful if you want to create or map Tru64 UNIX user account names that start with a numeric character.

Default: 0 (pre-pend the letter a to Tru64 UNIX user account names)

1.1.7    TruCluster Server Licensing

There is a new registry entry, UseClusterLicensing, under the SYSTEM/CurrentControlSet/Services/AdvancedServer/Parameters key. The UseClusterLicensing entry specifies whether or not the ASU server uses cluster-wide licensing when configured in a TruCluster Server multi-instance cluster.

Default: 0 (do not use cluster-wide licensing)

1.1.8    Security Log Information

The ASU server logs the following message in the security log if a user attempts to log in to the ASU server, but the mapped Tru64 UNIX user name's password entry cannot be found (because the account was deleted, or the NIS database or Active Directory cannot be reached):

The mapped UNIX user name passwd entry cannot be found

1.2    Command Improvements

The following sections describe command improvements in this release.

1.2.1    The acladm Command

The acladm command now displays a more detailed report on any invalid security descriptors that it finds.

The acladm -C command now looks for missing standard ACLs. If a standard ACL is missing, it will create a new standard ACL if requested.

The acladm -T command now trims redundant ACLs that contain Creator Owner ACEs.

The acladm command has a new -i option that you can use with the -M option (move acls) to restore ASU ACLs from a backup copy of an ACL store. You do not need to stop the ASU server to restore ASU ACLs from backup. For example, suppose you restored the /usr/temp file from backup, and want to restore the corresponding ASU ACLs. You would:

  1. Restore the /usr/net/servers/lanman/datafiles/acl file from the same date as the backed up file to a different filename, for example may10.acl.

  2. Enter the following command to restore the ASU ACLs:

    # acladm -M -i may10.acl -v /usr/temp
    

1.2.2    The blobadm Command

Using the -v option with the blobadm -R -S command now displays the name of the registry key along with the offset and size of the registry key blob record.

1.2.3    The elfread Command

The elfread has two new options:

1.2.4    The lmshare Command

The lmshare command now supports share names that contain spaces.

The lmshare has the following new options:

1.2.5    The lmstat Command

The lmstat command has a new -h option that displays hash table statistics.

The lmstat -l command now displays the name of the process (if any) that is holding a shared memory lock.

1.2.6    The lsacl Command

The lsacl command has the following new options:

1.2.7    The mapuname Command

The mapuname command has the following new options:

1.2.8    The nbstat and nbstatus Commands

Previously, entering the following command on the ASU server would display the message No response for cluster_alias_name. Now, this command displays the NetBIOS names registered data on one of the TruCluster members that received the request.

# nbstatus cluster_alias_name

Previously, entering either of the following commands on a PC would display the message Host not found. Now, these commands display the NetBIOS names registered data on one of the TruCluster members that received the request.

# nbtstat -a cluster_alias_ame

# nbtstat -A cluster_alias_ip_address

1.2.9    The net perms Command

The net perms command now displays an internal name if the user or group name for a permission cannot be translated, instead of not displaying anything at all. This avoids the impression of disappearing permissions if a trust is temporarily broken or if the domain controller of the trusted domain is off the network.

1.2.10    The rmacl Command

The rmacl command now removes orphaned ACLs for files and directories that were deleted through Tru64 UNIX instead of through Windows.

1.2.11    The samcheck Command

The samcheck command now repairs a SAM database on a backup domain controller (BDC) that is only missing standard mappings of domain users to Tru64 UNIX user names.

1.3    Changes and Corrections

The following sections describe changes and corrections in this release.

1.3.1    NFS Disk Shares

Previously, the ASU server did not maintain update information about NFS export entries. To account for updates, the ASU server deleted and recreated NFS disk shares for each export entry when it started. This caused the NFS shares to be temporarily unavailable.

With this release, when the ASU server starts, it synchronizes the ASU disk shares with NFS export entries without unnecessarily deleting the NFS shares first. If an exports entry does not have a corresponding disk share, the ASU server creates the disk share. If an exports entry no longer exists or is not supported (root=0), the ASU server deletes the corresponding disk share. If the NFS permissions for an NFS export entry changed, the ASU server updates the permissions on the corresponding disk share.

1.3.2    Printer Entry Changes

If you configured the ASU server to recognize the printer attached to a PC, you must change the enties in the lprsetup.dat file as follows:

1.3.3    Break oplock Messages

If server debug logging is enabled, break oplock messages are now logged in addition to the regular SMB commands and responses.

1.3.4    Changing Printer Drivers

Previously, if a printer was not shared, the driver would be incorrect, and it was not possible to change it from a Windows client or by using the net commands.

This problem has been corrected.

1.3.5    Setting the Tru64 UNIX Group on File Systems Mounted nogrpid

If a file system is mounted with the nogrpid option and the UseUnixGroups registry entry is enabled (it is disabled by default), the file and directories that the ASU server creates on the file system will be assigned the default group id (gid) of the mapped Tru64 UNIX user.

If the file system is not mounted with the nogrpid option or if the UseUnixGroups registry entry is disabled, the file or directory will inherit the parent directory's gid.