When You Move User Maps from Windows Services for UNIX 2.0 to 3.0, You Must Set Primary Map Manually (322888)
The information in this article applies to:
- Microsoft Windows Services for UNIX 3.0
This article was previously published under Q322888 SYMPTOMS
If you move User Name Mapping maps from Windows Services for UNIX 2.0 to a Windows Services for UNIX 3.0 server, the primary maps are indicated incorrectly.
CAUSE
The primary maps in Windows Services for UNIX 2.0 Mapping Server have a caret (^) to indicate that they are primary. The backup file also stores the maps with a caret. However, a caret indicates secondary advanced maps in Windows Services for UNIX 3.0 Mapping Server. By default, Windows Services for UNIX 3.0 advanced primary maps should have an asterisk as an indicator.
Restore reads from the backup file and writes it into the registry. No version conversion is done.
RESOLUTION
After you use Restore to load the maps, use either Windows Services for UNIX Administrator or MAPADMIN to set the proper primary maps.
The following is a MAPADMIN syntax example:
mapadmin setprimary -wg WindowsGroup -ug UNIXGroup
mapadmin setprimary -wu WindowsUser -uu UNIXUser
These command-line examples are for running locally as the administrator. For syntax to use MAPADMIN against a remote Mapping Server, please see the Windows Services for UNIX Help file.
| Modification Type: | Major | Last Reviewed: | 6/3/2002 |
|---|
| Keywords: | kbenv kbprb KB322888 |
|---|
|