6. Mac OS X ServerAdding users to Mac OS X 10.2 - 10.5 Leopard servers If you don't already have users in Mac OS X Server, you can import tab-delimited text and set the parameters for Export. For moving Macintosh Manager account Preferences to <account>/Library/Classic/Preferences, see 8. Migration Topics on this page: General Tab, Home Directories, Groups, Mail, Windows, Duplicate Checking, Importing into Server, Macintosh Manager Names/Usernames and Short Names The "Username" in Passenger is used to populate the "Name" or "Real Name" in OS X Server. The short name is formulated separately in the short name concatenation in Passenger. See Name Concatenation for more information. With users imported, select Mac OS X Server in the lower right menu of the Passenger window and press the setup button to get the setup dialog. If you choose to have Passenger create the User ID numbering, any imported User IDs won't be used for User IDs but imported User IDs will still be used if you specified their use in any concatentions. If you do not select for Passenger to create User IDs starting with a specific number, imported User IDs will be used instead. If not User IDs were imported, none will be exported and MOSXS will create the User IDs. For 10.2 and higher, choose whether to use Basic 'crypt' passwords or Password Server (Open Directory). If you choose Basic, Passenger will encrypt the passwords. If you choose Password Server, make sure you are running a password server (Open Directory for instance) and test it in the Workgroup Manager to make sure that manually created users can have passwords created this way. For 10.3 and newer, if you leave the fields blank and did not import Server URL or NFS Path, the home directories will be the default on the server. Otherwise, follow the directions below for 10.2. Server URL (the afp://servername), URL Path, and NFS Path can be imported formatted exactly as they would successfully be typed in the MOSXS setup in Passenger. Passenger will do the colon translation automatically to any path imported or entered in the interface since colons are used as delimiters in the MOSXS import/export format. For 10.2.x, select the home tab. If you leave a field blank in either NFS or AFP fields and did not import Server URL or NFS Path, no directory will be specified in the exported file. If your server has a share point for use with 10.x clients, make sure that it is set for automount in the Workgroup Manager for 10.2 or in 10.3 and newer set the Network Mount as AFP for User Home Directories. For the server URL use the entire path starting with the IP name or number and follow the path right to where the home directories would be. Leave the path field blank unless your home directories are embedded futher down than the mount point. Passenger will fill in the rest of the directory information with short names or usernames. I suggest short names. There are 4 replacement tags that you can use inside any path: <igroup> = imported group, <dept> = imported department, <org> = imported organization, and <building> = imported building. In 10.2, the objective is to have the Users home directory show up on the Network tab after import. For 10.3-10.5.x servers, you want to see the proper home directory path selected for your users. Try creating a user manually and setting the home directory to the network button share point. Then use the example screenshot below to figure out what to put in Passenger to make it show up properly. Home directories this way should work with both OS 9 (MM) and X clients.  Home directories on 10.2.x
Group setting can be set on the Groups tab. Setting users to workgroups for Macintosh Manager is explained further below. Passenger will export the groups you enter and any groups you imported. The importing of groups is limited to one group per user. You will need to set a separate file name for the group export file which you will later import into the Workgroup Manager to set the group assignments after you've imported your users into the Workgroup Manager. Incrementing the Group ID number is only used for groups that were imported into Passenger. The group name used in Passenger will be either matched to an existing Group Short Name or if that Group Short name doesn't exist, a new group will be created with a Group Short Name but no Group Name. You may need to add the Group Name manually in the Workgroup Manager. To assign users to existing groups on the server, use the Group Short Name and leave the Group ID blank. To import groups into OS X Server you must first have imported the users into the Workgroup Manager. You will use the same procedure as is used for importing users which is to set the Workgroup Manager to Use Record Description in File in 10.2 and just import in 10.3 - 10.5.x. In most cases you will also want to select append to existing for duplicate handling when importing into the Workgroup Manager since the group may already exist and you are just adding users to the group. The mail tab resembles that of the server. Imported forward addresses will be exported unless you decide to use the LDAP email address in which case it will be the email address you imported or the email address that is concatenated using the option on the Passenger window in the concatenation area. Given the base paths for the different Windows paths, passenger will add short names to those paths and export them. The only difference between this and home directories is that currently base Windows paths cannot be imported so only what you set in this setup dialog can be used. There are 4 replacement tags that you can use inside any path: <igroup> = imported group, <dept> = imported department, <org> = imported organization, and <building> = imported building. After finishing with all the MOSXS setup information, you can select to check for duplicates against Open Directory and NetInfo on the Mac on which Passenger is running. Passenger does two different duplicate checks: 1. A mandatory check for duplicates that may occur in the data you are working in for User IDs, Short names and Names. 2. The optional check for duplicates that may occur between the data in Passenger and Open Directory and NetInfo on the server on which Passenger is running for User IDs, Short names and Names.  Importing into the server (Workgroup Manager) For 10.2.x server, open the Workgroup Manager, select the proper domain and select import from the File menu. For Record Format, you must select "Use record description in file". If you will be importing a group assignments file, use the same record format for that. For 10.3. and newer servers, select the proper domain and select import from the File menu and choose the file you exported from Passenger. Getting the same users into Macintosh Manager 2.x This section is for
Macintosh Manager, which can be used for OS 8-9 clients. Macintosh
Manager is not for OS X client computers and help for it below is
mostly only kept for historical purposes since it is removed from the
later versions of Mac OS X Server. If you just got done exporting for Mac OS X Server, you can continue and export for Macintosh Manager 2.x. Otherwise, you can export the users from Mac OS X Server and import them into Passenger. The advantage of using Passenger to do this, instead of the Import All button in the Macintosh Manager admin, is that you can set workgroups. Workgroups in Macintosh Manager are not derived from the groups in Mac OS X Server. There is no other real reason to use the Macintosh Manager export. If you would rather set the workgroups in the Macintosh Manager Admin then skip this step. Passenger will only export Macintosh Manager if workgroups are exported with it. If you imported groups, you can choose to export those as workgroups or you can add your own.  Using the last name for the workgroup name might be useful if you want to setup workgroups for students for each class and you've imported the teachers names as names and not groups. Macintosh Manager 2.x import can match up either a short name, full name (username) or User ID (Macintosh Manager 2.x only needs one of these) to assign the user's to the appropriate workgroups. If you already have this information in a tab or comma-delimited text file, you don't need Passenger. From the File Menu of the Macintosh Manager 2.x Admin, select Import Users List and match up the data. Name #1 to username or short name, or User ID to User ID, and Workgroup to Workgroup. This will assign the found usernames, short names or User IDs to the Workgroups contained in that file. If you don't have matching criteria of username, short name or User ID, but you have a full name or first and last name with the Workgroup name, you can use Passenger to formulate the username or short name so that it will match what is already in Mac OS X Server. If you don't have Workgroup assignments to import, you can assign them explicitly using the above dialog. This might be useful if you have one file for each workgroup. You could then set the workgroup explicitly for every file you import and export. Import the file with name and workgroup, setup formulation to match and then export MM. From the File Menu of the MM admin, select Import Users List and match up the the short name or username to Name #1 and the Workgroup to the Workgroup. That will do the assigning of workgroups for you. Passenger exports the same file for use in Macintosh Manager 1.x and 2.x. The file may include information that is not necessary in the version of Macintosh Manager you are using. Macintosh Manager 2.x cannot import passwords but 1.x can. Macintosh Manager 1.x cannot import User IDs but 2.x can match up workgroups using User IDs. An Example of Macintosh Manager structure for Elementary Schools  |
