FIX: Server for NIS Does Not Support Automount Maps

NIS clients that use automount maps cannot automount.

Automounting uses special auto.* maps, such as auto.home. Note the following about these maps:

• Maps have the mount point as the key.
• Maps have the mount options as the value.
• The key is not part of the value.
• A call to ypcat -k will return only the value.

However, because Server for NIS does not support maps whose key is not part of the value, when the ypcat -k command is called, the key is prepended to the value. When the result is used by the client in a mount command, the command returns an error and the mount is unsuccessful.

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next version that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

You can create automount maps by using either a command prompt or the Migration wizard.

Use a Command Prompt

To create automount maps from a command prompt, follow these steps:

1. Create the automount maps on Windows Server for NIS. For example, to create Auto.master, run the following command:
   nismap create -i 1 -g " " -y auto.master
   The -y option indicates that the key is not part of the value in this map.
2. Copy the map files from the existing NIS master to the Windows computer, for example, in the C:\Temp folder.
3. Rename the files by replacing the dot in the file name with an underscore. For example, rename Auto.master to Auto_master.
4. Migrate the UNIX maps to Server for NIS. For example, to migrate Auto.master, run the following command:
   nis2ad -y unixdomain -a w2kdomain -d C:\temp\ -s localhost -r yes -m auto_master
   nis2ad imports the Auto_master file into the auto.master map. It will be accessible as auto.master by NIS clients.

Use the Migration Wizard

To create automount maps by using the Migration Wizard, follow these steps:

1. Copy the map files from the existing NIS master to the Windows computer, for example, in the C:\Temp folder.
2. Rename the files by replacing the dot in the file name with an underscore. For example, rename Auto.master to Auto_master.
3. Start the Server for NIS Migration Wizard, and then click Next.
4. Type the NIS domain name, and then click Next.
5. Log on as the domain administrator if you have to, click Next, and then click New.
6. Type the map name with an underscore. For example, auto_master.
7. Enter the separator and the key field as appropriate for the map.
8. Clear the Key is part of value check box, click OK, and then click Next.
9. Type the name of the folder that you copied the map files into in step 1.
10. Complete the wizard as expected and click Next to continue. Click the Migrate and log option, and then click Finish.

Important After the map is created, you cannot modify it. Therefore, make sure that you either specify the -y option at the command prompt or you clear the check box in the wizard.

You do not have to change the NIS clients. The automount maps will appear as they appeared before the migration.

Problems That Are Resolved by This Update

This update also fixes the following problems:

1. When you open Windows Services for UNIX Administration, the NIS service stops responding and you receive an access violation error message. You have to restart the server to restore correct functioning of the NIS service.
2. You cannot modify NIS properties by using dsadmin if the user name contains a slash character (/).
3. The Server for NIS page of Windows Services for UNIX Administration does not successfully load because of a script error.
4. The sfusch utility cannot extend the Active Directory directory service schema if the domain name is made up of only a single term. The sfusch utility assumes that domain names have at least two parts that are separated by a dot (for example, microsoft.com).
5. When you use Dsa.msc to perform remote administration of a domain controller whose domain is different from the domain of the client, the UNIX Attributes tab displays incorrect information.