User Management Admin v10.4B
User Management Admin v10.4B
User Management
For Version 10.4 or Later
Second Edition
K Apple Computer, Inc. Apple, the Apple logo, AirPort, AppleShare, AppleTalk,
© 2006 Apple Computer, Inc. All rights reserved. FireWire, iBook, Keychain, LaserWriter, Mac, Mac OS,
Macintosh, PowerBook, and QuickTime are trademarks
The owner or authorized user of a valid copy of of Apple Computer, Inc., registered in the U.S. and other
Mac OS X Server software may reproduce this countries. Extensions Manager, Finder, and SuperDrive
publication for the purpose of learning to use such are trademarks of Apple Computer, Inc.
software. No part of this publication may be reproduced
or transmitted for commercial purposes, such as selling Adobe and PostScript are trademarks of Adobe Systems
copies of this publication or for providing paid-for Incorporated.
support services.
Java and all Java-based trademarks and logos are
Every effort has been made to ensure that the trademarks or registered trademarks of Sun
information in this manual is accurate. Apple Computer, Microsystems, Inc. in the U.S. and other countries.
Inc., is not responsible for printing or clerical errors.
UNIX is a registered trademark in the United States and
Apple other countries, licensed exclusively through X/Open
1 Infinite Loop Company, Ltd.
Cupertino, CA 95014-2084
408-996-1010 Other company and product names mentioned herein
www.apple.com are trademarks of their respective companies. Mention
of third-party products is for informational purposes
Use of the “keyboard” Apple logo (Option-Shift-K) for only and constitutes neither an endorsement nor a
commercial purposes without the prior written consent recommendation. Apple assumes no responsibility with
of Apple may constitute trademark infringement and regard to the performance of these products.
unfair competition in violation of federal and state laws.
019-0638/02-14-06
1 Contents
3
Chapter 3 39 Getting Started with Workgroup Manager
39 Configuring the Administrator’s Computer and Account
40 Setting Up an Administrator Computer
40 Creating a Domain Administrator Account
41 Using Workgroup Manager
41 Working with Pre–Version 10.4 Computers from Version 10.4 Servers
41 Connecting and Authenticating to Directory Domains in Workgroup Manager
42 Major Workgroup Manager Tasks
43 Listing and Finding Accounts
43 Working with Account Lists in Workgroup Manager
44 Listing Accounts in the Local Directory Domain
44 Listing Accounts in Search Policy Directory Domains
45 Listing Accounts in Available Directory Domains
45 Refreshing Account Lists
46 Finding Specific Accounts in a List
46 Sorting User and Group Lists
46 Using the Search Button in the Toolbar
47 Shortcuts for Working with Accounts
47 Editing Multiple Accounts Simultaneously
47 Using Presets
48 Importing and Exporting Account Information
48 Backing Up and Restoring User Management Data
48 Backing Up and Restoring Directory Domain and Authentication Files
48 Backing Up Root and Administrator User Accounts
4 Contents
56 Deleting a Preset
57 Working with Basic Settings
57 Defining User Names
58 Defining Short Names
59 Choosing Stable Short Names
59 Avoiding Duplicate Names
60 Defining User IDs
61 Defining Passwords
61 Setting Password Options for Imported User Accounts
62 Assigning Administrator Privileges for a Server
62 Assigning Administrator Privileges for a Directory Domain
63 Working with Advanced Settings
63 Defining Login Settings
64 Choosing a Password Type and Setting Password Options
65 Creating a Master List of Keywords
66 Applying Keywords to User Accounts
66 Editing Comments
67 Working with Group Settings
67 Defining a User’s Primary Group
68 Adding a User to Groups
68 Removing a User from a Group
69 Reviewing a User’s Group Memberships
69 Working with Home Settings
69 Working with Mail Settings
70 Enabling Mail Service Account Options
71 Disabling a User’s Mail Service
71 Forwarding a User’s Mail
72 Working with Print Settings
72 Enabling a User’s Access to Print Queues that Enforce Quotas
73 Disabling a User’s Access to Print Queues that Enforce Quotas
73 Deleting a User’s Print Quota for a Specific Queue
73 Resetting a User’s Print Quota
74 Working with Info Settings
75 Choosing Settings for Windows Users
Contents 5
81 Creating Nested Groups
81 Upgrading Legacy Groups
82 Working with Read-Only Group Accounts
82 Deleting a Group Account
83 Working with Member Settings for Groups
83 Adding Users to a Group
84 Removing Users from a Group
84 Naming a Group
85 Defining a Group ID
86 Working with Group Folder Settings
86 Specifying No Group Folder
86 Creating a Group Folder
88 Designating a Group Folder for Use by Multiple Groups
6 Contents
107 Specifying No Home Folder
108 Creating a Home Folder for a Local User
109 Creating a Network Home Folder
110 Creating a Custom Location for Home Folders
113 Setting Disk Quotas
113 Choosing Default Home Folders by Using Presets
113 Moving Home Folders
113 Deleting Home Folders
Contents 7
143 About the Preferences Cache
144 Updating the Managed Preferences Cache at Intervals
144 Updating the Preference Cache Manually
145 Managing User Preferences
145 Managing Group Preferences
146 Managing Computer Preferences
147 Editing Preferences for Multiple Records
147 Disabling Management for Specific Preferences
148 Managing Access to Applications
148 Creating a List of Applications Users Can Open
149 Preventing Users from Opening Applications on Local Volumes
149 Managing Access to Helper Applications
150 Controlling the Operation of UNIX Tools
151 Managing Classic Preferences
152 Selecting Classic Startup Options
152 Choosing a Classic System Folder
153 Allowing Special Actions During Restart
154 Controlling Access to Classic Apple Menu Items
155 Adjusting Classic Sleep Settings
155 Maintaining Consistent User Preferences for Classic
156 Managing Dock Preferences
157 Controlling the User’s Dock
157 Providing Easy Access to Group Folders
158 Adding Items to a User’s Dock
159 Preventing Users from Adding or Deleting Items in the Dock
160 Managing Energy Saver Preferences
160 Using Sleep and Wake Settings for Desktop Computers
161 Working with Energy Saver Settings for Portable Computers
163 Displaying Battery Status for Users
163 Scheduling Automatic Startup, Shutdown, or Sleep
164 Managing Finder Preferences
165 Setting Up Simple Finder
166 Keeping Disks and Servers from Appearing on the User’s Desktop
166 Controlling the Behavior of Finder Windows
167 Hiding the Alert Message When a User Empties the Trash
167 Making Filename Extensions Visible
168 Controlling User Access to Remote Servers
168 Controlling User Access to an iDisk
168 Preventing Users from Ejecting Disks
169 Hiding the Burn Disc Command in the Finder
169 Controlling User Access to Folders
170 Removing Restart and Shut Down from the Apple Menu
170 Adjusting the Appearance and Arrangement of Desktop Items
8 Contents
171 Adjusting the Appearance of Finder Window Contents
172 Managing Internet Preferences
173 Setting Email Preferences
173 Setting Web Browser Preferences
174 Managing Login Preferences
175 Specifying How a User Logs In
176 Opening Items Automatically After a User Logs In
177 Providing Access to a User’s Network Home Folder
177 Providing Easy Access to the Group Share Point
178 Preventing Restarting or Shutting Down the Computer at Login
179 Using Hints to Help Users Remember Passwords
179 Enabling Multiple Simultaneous Users on a Client Computer
180 Enabling Automatic Logout for Idle Users
181 Enabling the Use of Login and Logout Scripts
182 Running a Login or Logout Script
183 Managing Media Access Preferences
184 Controlling Access to CDs, DVDs, and Recordable Discs
184 Controlling Access to Hard Drives and Disks
185 Ejecting Items Automatically When a User Logs Out
186 Managing Mobility Preferences
186 Creating a Mobile Account
187 Preventing the Creation of a Mobile Account
188 Removing Mobile Accounts from Client Computers
189 Choosing Folders to Synchronize at Login and Logout, or in the Background
190 Setting the Background Synchronization Frequency
191 Managing Network Preferences
191 Configuring Proxy Servers by Port
192 Allowing Users to Bypass Proxy Servers for Specific Domains
193 Managing Printing Preferences
193 Making Printers Available to Users
194 Preventing Users from Modifying the Printer List
194 Restricting Access to Printers Connected to a Computer
195 Setting a Default Printer
195 Restricting Access to Printers
196 Managing Software Update Preferences
197 Managing Access to System Preferences
198 Managing Universal Access Preferences
199 Adjusting the User’s Display Settings
200 Setting a Visual Alert
200 Adjusting Keyboard Responsiveness
201 Adjusting Mouse and Pointer Responsiveness
202 Enabling Universal Access Shortcuts
202 Allowing Devices for Users with Special Needs
Contents 9
203 Using the Preference Editor with Preference Manifests
204 Adding an Application to the Preference Editor’s Application List
204 Editing an Application’s Preferences with the Preference Editor
206 Disabling Management of an Application’s Preferences Using the Preference Editor
10 Contents
226 Users Can’t Log In with Accounts in a Shared Directory Domain
227 Users Can’t Access Their Home Folders
227 Users Can’t Change Their Passwords
227 Users Can’t Authenticate Using Single Sign-On or Kerberos
227 Solving Preference Management Problems
227 You Can’t Enforce Default Web Settings
227 You Can’t Enforce Default Mail Settings
228 Users Don’t See a List of Workgroups at Login
228 Users Can’t Open Files
228 Users Can’t Add Printers to a Printer List
229 Login Items Added by a User Don’t Open
229 Items Placed in the Dock by a User Are Missing
229 A User’s Dock Has Duplicate Items
230 Users See a Question Mark in the Dock
230 Users See a Message About an Unexpected Error
Glossary 245
Index 253
Contents 11
12 Contents
About This Guide
Preface
This guide explains how to use Workgroup Manager to set up
and manage home folders, accounts, preferences, and
settings for clients.
Mac OS X Server includes Workgroup Manager, a user management tool you can use to
create and manage accounts, share points, and network views. When managing
accounts, you can define core account settings like name, password, home folder
location, and group membership. You can also manage preferences, allowing you to
customize the user’s experience, granting or restricting access to his or her own
computer’s settings and to network resources.
Workgroup Manager works closely with a directory domain. Directory domains are like
databases, only specifically geared towards storing account information and handling
authentication.
13
 Preference manifests and preference editor. If you want fine-grained control of
preference settings, you can work with Workgroup Manager’s new preference editor,
which can use preference manifests. Preference manifests are files that describe the
structure and values of an application’s preferences. The preference editor can create
or edit any property list (plist) and incorporates preference manifests to thoroughly
describe preference settings that customize the behavior of applications and utilities.
For more information, see “Using the Preference Editor with Preference Manifests” on
page 203.
 User information. You can enter and edit personal data for each user, such as
addresses, phone numbers, iChat names, and webpage URLs. The Address Book
application can access this information. For more information, see “Working with Info
Settings” on page 74.
Note: Because Apple frequently releases new versions and updates to its software,
images shown in this book may be different from what you see on your screen.
On a computer running Mac OS X Server, you can access onscreen help after opening
Workgroup Manager or Server Admin. From the Help menu, choose one of these
options:
 Workgroup Manager Help or Server Admin Help displays information about the
application.
 Mac OS X Server Help displays the main server help page, from which you can search
or browse for server information.
 Documentation takes you to www.apple.com/server/documentation/, where you can
download server documentation.
You can also access onscreen help from the Finder, or from other applications on a
server or administrator computer. (An administrator computer is any Mac OS X
computer with server administration software installed on it.) Use the Help menu to
open Help Viewer, and then choose Library > Mac OS X Server Help.
To see the latest server help topics, make sure the server or administrator computer is
connected to the Internet while you’re using Help Viewer. Help Viewer automatically
retrieves and caches the latest server help topics from the Internet. When your
computer is not connected to the Internet, Help Viewer displays cached help topics.
www.apple.com/server/documentation/
Read Me documents—important updates and special information. Look for them on the
server discs.
Workgroup Manager
Workgroup Manager is a powerful tool that delivers features for comprehensive
management of Macintosh clients. You can use Workgroup Manager on a Mac OS X
Server computer, or you can install and use Workgroup Manager on a Mac OS X
computer.
You’ll use Workgroup Manager to create user accounts and set up groups to provide
convenient access to resources. You can add and configure computer lists, which can
selectively permit or deny privileges to users or groups for specific computers or
printers. You can manage user settings for mail, printing, and home folders. Workgroup
Manager allows you to configure and manage share points, which host home folders.
You can also use account settings and managed preferences to achieve the level of
administrative control you need, as well as establishing the most efficient user
experience.
19
By using Workgroup Manager with Mac OS X Server services, you can:
 Customize the working environments of network users, by organizing their desktop
resources and personal files.
 Enable services that require user accounts, such as mail, file sharing, iChat service,
and Weblog service.
 Share system resources such as printers and computers, maximizing their availability
and making sure that disk space and printer usage remain equitably shared.
This guide provides instructions for user management tasks that you can complete
with Workgroup Manager. To get started with Workgroup Manager, see Chapter 3,
“Getting Started with Workgroup Manager,” on page 39.
Server Admin
The Server Admin application provides access to various tools and services that play a
role in server management. Once you have installed the Mac OS X Server software, set
up directory services, and established your network, you can user Workgroup Manager
to start creating and managing accounts. After setting up accounts and home folders,
you can use Server Admin to set up additional services to provide mail service, host
websites or share printers. Workgroup Manager can then be used to create share
points, allowing users to share folders and files.
For instructions on completing tasks using the many services managed through Server
Admin, see the service administration guides. The following table lists common server
administration tasks, and includes where to find related documentation.
NetBoot
Mac OS X computers can start up from a network-based NetBoot image, providing
quick and easy configuration of department, classroom, and individual systems, as well
as web and application servers, throughout a network. When you update a NetBoot
image, all computers using NetBoot have instant access to the new configuration.
You can set up multiple NetBoot images, to customize the computer setup for different
groups of clients.
NetBoot can simplify administration and reduce the support normally associated with
large-scale deployments of network-based Macintosh computers. NetBoot is ideal for
an organization with client computers that need to be identically configured. For
example, NetBoot can be a powerful solution for a data center that needs multiple,
identically configured web and application servers.
With NetBoot, you can quickly configure and update client computers by updating a
NetBoot image stored on the server. NetBoot images contain the operating system and
application folders for all clients on the server. Any changes made on the server are
automatically reflected on the clients when they restart. Systems that are compromised
or otherwise altered can be instantly restored by restarting them.
You use System Image Utility to create and modify NetBoot images and use NetBoot to
deploy NetBoot images.
For more information about these tools or about installing an operating system over a
network, see the system image and software update administration guide.
Network Install
Network Install is a centralized software installation service. It lets you selectively and
automatically install, restore, or upgrade network-based Macintosh systems anywhere
in your organization. Installation images can contain the latest version of Mac OS X, a
software update, site-licensed or custom applications, or configuration scripts.
You can use Network Install to upgrade operating systems, install software updates and
custom software packages, or reimage desktop and portable computers. You can
define custom installation packages for various departments in an organization, such as
marketing, engineering, and sales.
With Network Install you don’t need to use CDs or DVDs to configure a computer. All
the installation files and packages reside on the server and are installed on the client
computer together. With Network Install, you can run pre- and post-installation scripts
to perform system commands before or after the installation of a software package or
system image.
For more information about using these tools with Network Install, see the system
imaging and software update administration guide.
Accounts
In order to use Workgroup Manager to manage accounts, you use an administrator
account. With an administrator account, you can set up and manage three types of
accounts using Workgroup Manager: user accounts, group accounts, and computer
lists.
When you define a user account, you specify the information needed to prove the
user’s identity: user name, and password. You can also specify a user identification
number (user ID), which is useful for folder and file permissions. Other information in a
user’s account is needed by various services—to determine what the user is authorized
to do and perhaps to personalize the user’s environment. In addition to the accounts
you create, Mac OS X Server has some predefined user and group accounts, some of
which are reserved for use by Mac OS X.
Administrator Accounts
Users with server or directory domain administration privileges are known as
administrators. An administrator can be a server administrator, domain administrator,
or both. Server administrator privileges determine whether a user can view information
about or change the settings of a particular server. Domain administrator privileges
determine the extent to which the administrator can view or change the account
settings for users, groups, and computer lists in the directory domain.
Server Administration
Server administration privileges determine the powers a user has when logged in to a
particular Mac OS X Server. For example, a server administrator can use Server Admin
and can make changes to a server’s search policy using Directory Access.
When you assign server administration privileges to a user, the user is added to the
predefined group named “admin” in the local directory domain of the server. Many
Mac OS X applications—such as Server Admin, Directory Access, and System
Preferences—use the admin group to determine whether a particular user can perform
certain administrative activities with the application. The primary administrator defined
when using Server Assistant is user ID 501 in the server’s local directory domain.
You can allow certain users to manage specific accounts. For example, you may want to
make a network administrator the server administrator for all your classroom servers,
but give individual teachers the privileges to manage student accounts in particular
directory domains. Any user who has a user account in a directory domain can be
made a directory domain administrator (an administrator of that domain).
You can control the extent to which a directory domain administrator can use
Workgroup Manager to change account data stored in a domain. For example, you may
want to set up directory domain privileges so your network administrator can add and
remove user accounts, but other users can change the information for particular users.
Or you may want to designate multiple administrators to manage different groups.
When you assign directory domain administration privileges to a user, the user is
added to the admin group of the server on which the directory domain resides.
For more information about how to set up a directory domain administrator account,
see “Creating a Domain Administrator Account” on page 40.
User Accounts
Depending on how you set up your server and your user accounts, you can use
Mac OS X Server to support users who log in using Mac OS X computers, Windows
computers, or UNIX computers.
Most users have an individual account used to authenticate them and control their
access to services. When you want to personalize a user’s environment, you define user,
group, or computer preferences for that user. The term managed client or managed user
designates a user who has administrator-controlled preferences associated with his or
her account. Managed client is also used to refer to computer lists that have preferences
defined for them.
When a managed user logs in, the preferences that take effect are a combination of the
user’s preferences and the preferences set up for any workgroup or computer list the
user belongs to.
Guest Users
You may want to provide services for individuals who are anonymous—that is, they
can’t be authenticated because they don’t have a valid user name or password. These
users are known as guest users.
With some services, such as AFP, you can specify whether to let guest users access files.
If you enable guest access, users who connect anonymously are restricted to files and
folders with permissions set to Everyone. Instead of authenticating with a name and a
password, a guest user connects as a guest, not as a registered user.
Group Accounts
A group is simply a collection of users who have similar needs. For example, you can
add all English teachers to one group and give the group permission to access certain
files or folders on a volume.
Information in group accounts helps control user access to folders and files. See “Folder
and File Access by Other Users” on page 28 for a description of how this works.
Groups can be nested within groups. For example, a group can be a member of
another group. A group that contains another group is called a parent group, and the
group that is contained is called a nested group. Nested groups are useful for inheriting
access permissions, but they do not inherit managed preferences.
To learn more about how to set up group accounts, see Chapter 5, “Setting Up Group
Accounts.” To specify preferences for group accounts, see Chapter 10, “Managing
Preferences.”
Workgroups
When you define preferences for a group, it is known as a workgroup. A workgroup lets
you manage the working environment of group members.
Any preferences you define for a Mac OS X workgroup are stored in the group account.
See Chapter 10, “Managing Preferences,” on page 137 for a description of workgroup
preferences.
You can give individual users permission to write to a group folder, or to change group
folder attributes in the Finder.
Computer Lists
A computer list is composed of one or more computers that have the same managed
preferences and that are available to particular users and groups. You can create and
modify computer lists in Workgroup Manager.
To learn more about how to set up computer lists for Mac OS X client computers, see
Chapter 6, “Setting Up Computer Lists.” To specify preferences for Mac OS X computer
lists, see Chapter 10, “Managing Preferences.”
Guest Computers
Most computers on your network should be in a named computer list. If an unknown
computer (one that isn’t already in a computer list) connects to your network and
attempts to access services, that computer is treated as a guest. Settings chosen for a
Guest Computers list apply to these unknown guest computers.
Details of the user experience may vary depending upon the type of user, the
permissions set, the type of client computer (such as Windows or UNIX) currently in
use, whether the user is a member of a group, and whether preference management
has been implemented at the user, group, or computer level.
You’ll find information about the Mac OS X user experience in Chapter 9, “Client
Management Overview.” Basic information about authentication, identity validation,
and information access control is given in the sections that follow.
A Mac OS X computer can find user accounts that are stored in a directory domain of
the computer’s search policy.
 A directory domain stores information about users and resources. It is like a database
that a computer is configured to access in order to retrieve configuration
information.
 A search policy is a list of directory domains the computer searches when it needs
configuration information, starting with the local directory domain on the user’s
computer.
The following picture shows a user logging in to a Mac OS X computer that can locate
the user’s account in a directory domain within its search policy.
Log in to
Mac OS X
Directory domains
in search policy
After login, the user can connect to a remote server to gain access to its services, if the
user’s account can be located within the search policy of the server.
Connect to
Mac OS X Server
Directory domains
in search policy
If Mac OS X finds a user account containing the name entered by the user, it attempts
to validate the password associated with the account. If the password is validated, the
user is authenticated and the login or connection process is completed.
Mac OS X Server can validate passwords using Kerberos, Open Directory Password
Server, shadow passwords, and crypt passwords.
The Open Directory administration guide describes the different kinds of directory
domains and tells you how to configure search policies on any Mac OS X computer. It
also discusses different kinds of authentication methods and provides instructions for
setting up user authentication options.
Before Mac OS X version 10.4, Mac OS X exclusively used a particular data item in a
user’s account—the user ID—in conjunction with POSIX permissions to keep track of
folder and file permissions. In Mac OS X, all folders or files include POSIX permissions
for entities such as:
 the owner
 the group
 everyone else
Unlike using GUIDs, using POSIX permissions can cause file ownership and group
membership issues when there are multiple users with the the same short name or
user ID. The introduction of GUIDs does not change or remove POSIX permissions, and
thus it does not affect interoperability of Mac OS X with legacy UNIX systems or other
operating systems.
If you change a user’s user ID, the user may no longer be able to modify or even access
files and folders he or she created. Likewise, if the user logs in as a user whose user ID is
different from the user ID he or she used to create the files and folders, the user no
longer has owner permissions for them.
Every user belongs to a primary group. The primary group ID for a user is stored in the
user’s account. When a user accesses a folder or file and the user isn’t the owner, the file
system checks the file’s group permissions.
 If the user’s primary group ID matches the ID of the group associated with the file,
the user inherits group permissions.
 If the user’s primary group ID doesn’t match the file’s group ID, Mac OS X searches for
the group account that has permission to access the file. Once found, all members of
that group and of subsequent nested groups are given permission to that file.
 If neither of these cases applies, the user’s access permissions default to the generic
“everyone.”
Setup Overview
This section provides an overview of user management setup tasks, with the goal of
understanding the sequence in which an administrator would create a managed
environment. Not all steps are necessary in every case.
Set up the server so that it hosts or provides access to shared directory domains.
Shared directory domains (also called shared directories) contain user, group, and
computer information you want many computers to be able to access. Users whose
accounts reside in a shared directory are referred to as network users.
29
There are different kinds of shared directories. You can use Workgroup Manager to add
or modify accounts that reside in read/write directory domains such as the LDAP
directory of an Open Directory master, or a NetInfo domain. For read-only directory
domains such as LDAPv2, read-only LDAPv3, or BSD flat files, make sure they are
configured to support Mac OS X Server and that they provide needed account data.
You might have to add, modify, or reorganize information in a directory to make the
directory compatible.
Mac OS X offers a variety of options for authenticating users (including Windows users)
whose accounts are stored in directory domains on Mac OS X Server. In addition,
Mac OS X can access accounts in existing directories on your network, such as a
Windows server’s Active Directory.
Use file services to make resources visible throughout the network so that users can
access them from different computers. Key network-visible resources include network
home folders, group folders, and other shared folders.
If some of your users use Windows computers, you can also configure the server to
provide them with file services, domain login, and home folders.
There are several administration guides that describe these services in detail.
 For installation requirements and guidelines, see the getting started guide.
 For information about directory services and authentication, see the Open Directory
administration guide.
 For information about how to set up file services, see the file services administration
guide.
 For information about how to set up servers for managing Windows users, see the
Windows services administration guide.
Before you can use the administrator computer to create and manage accounts in a
shared directory, you need a user account in the shared directory and you need to be a
domain administrator. A domain administrator can use Workgroup Manager to add and
change accounts that reside in the LDAP directory of an Open Directory master, a
NetInfo domain, or another read/write directory domain.
You can set up network home folders so they can be accessed using either AFP or NFS.
You can also set up home folders for exclusive use by Windows users using SMB/CIFS:
 For instructions on setting up AFP or NFS share points for network home folders for
Macintosh users, see Chapter 7, “Setting Up Home Folders.”
 For information about setting up SMB/CIFS share points for Windows user home
folders, see the Windows services administration guide.
You can also create accounts on Mac OS X Server to manage Windows users and
provide Windows domain login, roaming user profiles, home folders, file services,
mail service, and so on. See the Windows services administration guide for instructions.
For Mac OS X computers, configure the search policy of the computers so that they can
locate shared directory domains. For instructions, see the Open Directory
administration guide.
For setup instructions for mobile Mac OS X computers that use AirPort to communicate
with Mac OS X Server, see Designing AirPort Extreme Networks (available at
www.apple.com/airportextreme/).
You can join Windows workstations to the Mac OS X Server primary domain controller
(PDC). This is similar to how you configure Windows workstations to join a Windows NT
server’s domain. For more information, see the Windows services administration guide.
If you have more than just a few Macintosh client computers to set up, consider using
Network Install to create a system image that automates client computer setup.
For instructions, see the system image and software update administration guide.
Note: If not all the domains have been finalized when you’re ready to start adding user
and group accounts, simply add the accounts to any directory domain that already
exists on your server. (You can use the local directory domain—it’s always available.)
You can move users and groups to another directory domain later by using your
server’s export and import capabilities. Exporting and importing account information
does not retain passwords. For more information, see Appendix A, “Importing and
Exporting Account Information.”
Determine the users, groups, and computers whose preferences you want to manage.
See Chapter 9, “Client Management Overview,” on page 127 and Chapter 10, “Managing
Preferences,” on page 137 for planning guidelines.
Users with local accounts typically have local home folders. When users save files in
local home folders, the files are stored locally. To save the files over the network, the
users have to connect to the network and upload the file. Using local home folders
gives you the least control over an individual user’s managed preferences. It also is not
inherently tied to a network account.
Users with network accounts typically have network home folders. When they save files
in their network home folders, the files are stored on the server. Additionally, whenever
users access their home folders, even for common tasks like caching webpages, users’
computers have to retrieve these files from the server. Using network home folders
gives you complete control over an individual user’s managed preferences. When users
are not connected to the network, they cannot access their accounts or home folders.
Users with mobile accounts have both local and network home folders, which combine
to form portable home directories. When users save files, the files are stored in a local
home folder. The portable home directory is a synchronized subset of a user’s local and
network home folders. You can configure which folders to synchronize and how
frequently to synchronize them. Mobile accounts also cache authentication information
and managed preferences. If you synchronize key folders, a user can work on and off
the network and experience a seamless work environment. If you choose to not
synchronize portable home directories, mobile accounts are very similar to local
accounts, except that mobile accounts have managed preferences.
A user’s network home folder doesn’t need to be stored on the same server as the
directory containing the user’s account. In fact, distributing directory domains and
home folders among various servers can help you balance your network load.
“Distributing Home Folders Across Multiple Servers,” on page 103, describes such a
scenario.
You may want to store home folders for users with last names from A to F on one
computer, G to J on another, and so on. Or you may want to store home folders on a
Mac OS X Server computer but store user and group accounts on an Active Directory or
LDAP server.
Pick a distribution strategy before creating users. If your distribution strategy fails while
using it, you can move home folders, but doing so may require changing a large
number of user records.
When determining the access protocol to use for home folders, you usually use AFP
because it offers the greatest level of security. If you are hosting home folders on UNIX
servers that do not support AFP, you may want to use NFS. If you are hosting home
folders on Windows servers, you may want to use SMB/CIFS. For more information
about how to use these protocols for home folders, see “About Home Folders” on
page 101.
Identifying Groups
Identify users with similar requirements and consider assigning them to groups.
See Chapter 5, “Setting Up Group Accounts.”
The domain administrator has the greatest amount of control over other users and
their privileges. The domain administrator can create user accounts, group accounts,
and computer lists, and assign settings, privileges, and managed preferences for them.
He or she can also create other server administrator accounts, or give some users (for
example, teachers or technical staff ) administrator privileges within certain directory
domains.
Give some thought to which users require domain administrator privileges. Managed
users can be given various administrator privileges also, allowing them to manage
specific groups of users or adjust certain account settings. A well-planned hierarchy of
administrators and users with special administrator privileges can help you distribute
system administration tasks and make workflow and system management more
efficient.
When you use Server Assistant to initially configure your server, you specify a password
for the owner/administrator. The password you specify also becomes the root password
for your server. Many server administrators don’t need to know the root password, but
sometimes it’s necessary when using command-line tools (such as CreateGroupFolder).
For administrators who don’t need root access, use Workgroup Manager to create an
administrator user with a password that is different from the root password.
The root password should be used with caution and stored in a secure location.
The root user has full access to the system, including system files. If you need to, you
can use Workgroup Manager to change the root password.
39
Setting Up an Administrator Computer
By installing Workgroup Manager and other administration tools on a remote
administrator computer, you do not need to physically access the server. Instead, you
use this administrator computer to connect to the server and perform any
administrative tasks you require.
In order to create and modify accounts, you also need to have a domain administrator
account.
You can only manage preferences for Mac OS 9 clients on Mac OS X Server v10.4
systems by using Macintosh Manager. To install Macintosh Manager, you must perform
an upgrade installation from Mac OS X Server version 10.2.8 or 10.3 to Mac OS X Server
v10.4.
Once you’ve edited a user record using Workgroup Manager on Mac OS X Server v10.4,
you cannot edit that record using any earlier version of Mac OS X Server.
 You can view a directory domain without authenticating (by choosing Server >
View Directories). You have read-only access to information displayed in Workgroup
Manager. To make changes in a directory, you must authenticate using a domain
administrator account. This approach is most useful when you’re administering
different servers and working with different directory domains.
After opening Workgroup Manager, you can open a Workgroup Manager window for a
different computer by clicking Connect in the toolbar or choosing Server > Connect.
Accounts list
There are several settings that influence the contents and appearance of the list:
 Workgroup Manager preferences control the maximum number of records shown,
and whether you want to enable the Inspector, which allows you to view or edit raw
directory data. Choose Workgroup Manager > Preferences to set up Workgroup
Manager preferences.
 The list reflects the directory you chose from the globe pop-up menu. If you connect
to the directory server, the parent directory domain accounts are listed initially. If you
do not connect to the directory server, local accounts are listed initially.
To work with one or more of the accounts listed, select them. Settings for the selected
accounts appear in the pane to the right of the list. Available settings vary, depending
on which pane you’re currently viewing.
Available directory domains are not the same as directory domains in a search policy.
A search policy consists of the directory domains a server searches routinely when it
needs to retrieve, for example, a user’s account. However, the same server might be
configured to access directory domains that haven’t been added to its search policy.
See the Open Directory administration guide to learn how to configure access to
directory domains.
To select multiple accounts, hold down the Shift key while clicking to select a range of
accounts. You can also hold down the Command key and then click to select accounts
individually. You can also choose Edit > Select All, and then Command-click to deselect
particular accounts.
Alternatively, you can use the Search button in the toolbar to find records that match
your criteria. You can then select “Perform a batch edit on the search results.”
An example of how batch editing can save you time is when you need to change
preference settings for a large number of accounts. For more information, see “Editing
Preferences for Multiple Records” on page 147.
Using Presets
You can select settings for a user account, group account, or computer list and save
them as a preset. Presets work like templates, allowing you to apply predefined settings
to a new account. Using presets, you can easily set up multiple accounts with similar
settings.
You can use presets only during account creation. You can’t use a preset to modify an
existing account. You can use presets when creating accounts manually, or when
importing them from a file.
If you change a preset after it has been used to create an account, accounts already
created using the preset are not updated to reflect those changes.
For more information about how to create presets, see “Creating a Preset for User
Accounts” on page 55.
For more information, see Appendix A, “Importing and Exporting Account Information.”
To ensure that you can re-create these user IDs, periodically export the server’s user
and group information to a file. Exporting account information is described in
Appendix A, “Importing and Exporting Account Information.”
You can use Workgroup Manager to view, create, edit, and delete user accounts.
You can view user accounts in Workgroup Manager by clicking the Users button above
the accounts list.
Users button
Accounts list
49
You can use Workgroup Manager to work with accounts in all kinds of directory
domains, but you can update only the LDAP directory of an Open Directory master, a
NetInfo domain, or other read/write directory domain using Workgroup Manager.
For complete information about the different kinds of directory domains, see the Open
Directory administration guide.
To create users in an Active Directory domain, use Active Directory administration tools
on a Windows computer. Workgroup Manager can’t be used to create user accounts,
group accounts, or computer lists in a standard Active Directory domain. If you extend
the schema of the Active Directory domain, you can create computer lists in Active
Directory.
You can also use a preset or an import file to create a new user. For details, see “Using
Presets to Create New Accounts” on page 55 and “Using Workgroup Manager to Import
Users and Groups” on page 232.
Although you can simultaneously edit most account settings for multiple users, there
are several account settings that you can only change per user. For example, you
cannot assign the same name, short name, or user ID to multiple users. Workgroup
Manager disables fields where you are expected to provide unique values.
If you do not have this privilege, you have to authenticate to the directory domain with
the Directory Administrator account that gets created in Mac OS X Server when you
specify your server to be a directory master in the Server Admin utility. The UID, user
name, and password of the Directory Administrator account (which defaults to the
modifiable UID of 1000 and user name “diradmin”) is set by the server administrator at
the time of directory creation.
To modify accounts:
1 Use an administrator computer that has been set up (using the Services pane of
Directory Access) to access the server hosting the Open Directory master.
2 Open Workgroup Manager on the administrator computer.
3 When the login window appears, choose Server > View Directories.
4 Click the globe and choose Other from the pop-up menu.
5 Open the directory domain you want to administer, and then click the lock and enter
the name and password of a directory domain administrator.
Users who connect to a server anonymously are restricted to files, folders, and websites
with permissions set to Everyone.
Another kind of guest user account is a managed user account that you can define to
allow easy setup of public computers or kiosk computers. For more about these kinds
of user accounts, see Chapter 10, “Managing Preferences,” on page 137.
Renaming Presets
Name your presets to help remind you of the template settings or identify the type
of user account, group account, or computer list for which that preset is best suited.
You can rename your presets.
To rename a preset:
1 Open Workgroup Manager on the server where the preset has been defined.
2 Click Accounts.
3 Choose Rename Preset from the Presets pop-up menu.
4 Enter the new name and click OK.
Editing Presets
When you change a preset, existing accounts created using it are not updated to
reflect your changes.
To change a preset:
1 Open Workgroup Manager on the server where the preset has been defined.
2 Click Accounts.
3 Choose an item from the Presets pop-up menu.
4 After completing your changes, choose Save Preset from the Presets pop-up menu.
You can also change a preset while using it to create a new account by changing any of
the fields defined by the preset, and then saving the preset.
Deleting a Preset
If you no longer need a particular preset, you can delete it.
To delete a preset:
1 Open Workgroup Manager on the server where the preset has been defined.
In Workgroup Manager, you use the Basic pane in the user account window to work
with basic settings.
A user name can contain no more than 255 bytes. Since long user names support
various character sets, the maximum number of characters for long user names can
range from 255 Roman characters to as few as 85 characters (for character sets in which
characters occupy up to 3 bytes).
You can use Workgroup Manager to edit the user name of an account stored in the
LDAP directory of an Open Directory master, a NetInfo domain, or other read/write
directory domain. You can also use Workgroup Manager to review the user name in any
directory domain accessible from the server you’re using.
When Mac OS X creates a user’s local or network AFP home folder, it names the
directory after the user’s short name. For more information about home folders, see
Chapter 7, “Setting Up Home Folders.”
You can have as many as 16 short names associated with a user account. You might
want to use multiple short names as aliases for email accounts, for example. The first
short name is the name used for home folders and legacy group membership lists;
don’t reassign that name after you save the user account.
A short user name can contain as many as 255 Roman characters. However, for clients
using Mac OS X version 10.1.5 and earlier, the first short user name must be 8 characters
or fewer.
Use only these characters for the first short user name (subsequent short names can
contain any Roman character):
 a through z
 A through Z
 0 through 9
 _ (underscore)
You can use Workgroup Manager to edit the short name of an account stored in the
LDAP directory of an Open Directory master, a NetInfo domain, or other read/write
directory domain. You can also use Workgroup Manager to review the short name in
any directory domain accessible from the server you’re using.
After the user’s account has been saved, you can’t change the first short name, but you
can change others in a list of short names.
If you need to change the first short name, you can create a new account for the user
(in the same directory domain) that contains the new short name, but retains all other
information (user ID, primary group, home folder, and so forth). You can then disable
login for the old user account. Now the user can log in using the changed name, yet
have the same access to files and other network resources as before. See “Disabling a
User Account” on page 54 for information about how to disable use of an account for
login.
Mac OS X version 10.4 introduces globally unique identifiers (GUIDs) for determining
group membership. In previous versions of Mac OS X, group membership was
determined by the user’s first short name. If you delete a user and re-create the user
with the same short name, group memberships are not retained.
For more information about GUIDs, see Appendix B, “ACL Permissions and Group
Memberships Using GUIDs.”
If multiple user accounts have the same long user name on a Mac OS X computer, login
window displays the list of users for you to choose from. This functionality is new to
Mac OS X version 10.4. Previous versions of Mac OS X do not display this list.
If two users have the same first short user name, the login window only recognizes,
and authenticates the first matching user account it finds in the sequence of directory
domains specified by the computer’s search policy, as set in Directory Access. If a local
user and a network user have the same first short user name, the local user always take
precedence. This prevents the network user from logging in to the computer.
If you do not upgrade legacy groups, the groups still determine membership by only
the user’s first short name and GID. For instructions on upgrading legacy groups, see
“Upgrading Legacy Groups” on page 81. It is highly recommended that you avoid using
duplicate user short names, in order to allow users to log in to computers and to
ensure correct legacy group membership.
The user ID should be a unique string of digits from 500 through 2,147,483,648. It is
risky to assign the same user ID to different users, because two users with the same
user ID have identical directory and file permissions.
The user ID 0 is reserved for the root user. User IDs below 100 are reserved for system
use; users with these user IDs should not be deleted and should not be modified
except to change the password of the root user. If you do not want the user to appear
in the login window of computers with Mac OS X version 10.4 or later installed, assign a
user ID of less than 500.
In general, once user IDs have been assigned and users start creating files and folders,
you shouldn’t change user IDs. One possible scenario in which you may need to
change a user ID is when merging users created on different servers onto one new
server or cluster of servers. The same user ID may have been associated with a different
user on the previous server.
When you create a new user account in any shared directory domain, Workgroup
Manager automatically assigns a user ID; the value assigned is an unused user ID (1025
or greater) in the server’s search policy. (New users created using the Accounts pane of
System Preferences are assigned user IDs starting at 501.)
You can use Workgroup Manager to edit the user ID of an account stored in the LDAP
directory of an Open Directory master or a NetInfo domain. You can also use
Workgroup Manager to review the user ID in any directory domain accessible from the
server you’re using.
Defining Passwords
For information about defining passwords, see the Open Directory administration
guide.
For more information about importing user accounts, see “Understanding What You
Can Import and Export” on page 231. For additional information about Open Directory
passwords, see the Open Directory administration guide.
You can use Workgroup Manager to assign server administrator privileges to the LDAP
directory of an Open Directory master or a NetInfo domain. You can also use
Workgroup Manager to review the server administrator privileges in any directory
domain accessible from the server you’re using.
You can use Workgroup Manager to assign directory domain administrator privileges to
an account stored in the LDAP directory of an Open Directory master or a NetInfo
domain. You can also use Workgroup Manager to review these privileges in any
directory domain accessible from the server you’re using.
You can use Workgroup Manager to define login settings for an account stored in the
LDAP directory of an Open Directory master, a NetInfo domain, or other read/write
directory domain. You can also use Workgroup Manager to review login settings for any
directory domain accessible from the server you’re using.
Note: Simultaneous login is not recommended for most users. You may want to reserve
simultaneous login privileges for technical staff, teachers, or other users with
administrator privileges. (If a user has a network home folder, that’s where the user’s
application preferences and documents are stored. Simultaneous login may modify
these items; many applications don’t support such modification while they are open.)
You can only disable simultaneous login for users with AFP home folders.
6 Choose a shell from the Login Shell pop-up menu to specify the default shell for the
user when logging in to a Mac OS X computer.
Note: Terminal has a preference that lets the user override the default shell.
To enter a shell that doesn’t appear in the list, click Custom. To make sure a user can’t
access the server remotely using the command line, choose None.
When you set the password type to Shadow Password or Open Directory, you can set
several password policy options, including disabling login after a period of inactivity or
failed authentication attempts, or setting password restrictions such as requiring that
passwords be of a certain length or that they be changed at next login. If you set the
password type to Shadow Password, you can also set security options to control which
authentication methods are used when validating the user’s password.
For a detailed explanation of password types, password policy options, and security
options, see the Open Directory administration guide.
Before you begin adding keywords to user records, you must create a master keyword
list. The list of keywords shown in the Advanced pane for a selected user applies only
to that user.
Editing Comments
You can save a comment in a user’s account to provide whatever documentation might
help with administering the user. A comment can be as long as 32,676 characters.
You can use Workgroup Manager to define the comment of an account stored in the
LDAP directory of an Open Directory master, a NetInfo domain, or other read/write
directory domain. You can also use Workgroup Manager to review the comment in any
directory domain accessible from the server you’re using.
For information about how to administer group accounts, see Chapter 5, “Setting Up
Group Accounts.”
The ID of the primary group is used by the file system when the user accesses a file he
or she doesn’t own. The file system checks the file’s group permissions, and if the
primary group ID of the user matches the ID of the group associated with the file, the
user inherits group access permissions. The primary group offers the fastest way to
determine whether a user has group permissions for a file.
Warning: Although you can make a primary group a nested group, or a parent of
nested groups, the file permissions for the primary group do not propagate. If a user’s
primary group is a nested group or the parent of a nested group, the user is granted
file permissions only for the primary group. You should not rely on using primary
group membership when assigning file permissions.
You can use Workgroup Manager to define the primary group ID of an account stored
in the LDAP directory of an Open Directory master, a NetInfo domain, or other read/
write directory domain. You can also use Workgroup Manager to review the primary
group information for any directory domain accessible from the server you’re using.
You can use Workgroup Manager to add a user to a group, if the user and group
accounts are in the LDAP directory of an Open Directory master or a NetInfo domain.
In case the directory is implemented through NFS, a 16-group limitation is imposed by
the NFS architecture.
Note: There is no limit to the number of groups a user may belong to.
You can also add users to a group by using the Members pane of the group accounts
window.
Note: If a user is a direct member of multiple groups, the only way to acquire the
managed preferences of a group different from its primary group is at login time.
You can also add users to a group by using the Members pane of group accounts.
In Workgroup Manager, use the Mail pane in the user accounts window to work with a
user’s mail service settings.
In Workgroup Manager, use the Print Quota pane in the user accounts window to set a
user’s print quotas. Select:
 None (the default) to disable a user’s access to print queues enforcing print quotas
 All Queues to let a user print to all accessible print queues that enforce quotas
 Per Queue to let a user print to specific print queues that support quotas
You can also extend a user’s page limit without resetting the quota time period by
changing the number of pages allowed for the user. In this way, the time period for the
quota remains the same and is not reset, but the number of pages the user can print
during that period is adjusted for both the current and future print quota periods. To
extend or decrease a selected user’s page limit, type a new number in the “Limit to ___
pages” field and click Save.
Note: There is only one phone attribute, and that defaults to the work number in
Address Book.
For detailed instructions about how to use settings for users accessing Windows
computers, see the Windows services administration guide.
You can use Workgroup Manager to view, create, edit, and delete group accounts. You
can view group accounts in Workgroup Manager by clicking the Groups button above
the accounts list.
Groups button
Accounts list
A primary group is the user’s default group. Primary groups can expedite the checking
done by the Mac OS X file system when a user accesses a file.
77
Where Group Accounts Are Stored
Group accounts, as well as user accounts and computer lists, can be stored in any Open
Directory domain. A directory domain can reside on a Mac OS X computer (for
example, the LDAP directory of an Open Directory master or a NetInfo domain) or it
can reside on a non-Apple server (for example, an LDAP or Active Directory server).
You can use Workgroup Manager to work with accounts in all kinds of directory
domains. For complete information about the different kinds of Open Directory
domains, see the Open Directory administration guide.
Predefined
group name Group ID Use
admin 80 The group to which users with administrator privileges belong.
bin 7 A group that owns all binary files.
daemon 1 A group used by system services.
dialer 68 A group for controlling access to modems on a server.
kmem 2 A legacy group used to control access to reading kernel memory.
mail 6 The group historically used for access to local UNIX mail.
mysql 74 The group that the MySQL database server uses for its processes
that handle requests.
network 69 This group has no specific meaning.
nobody -2 A group used by system services.
nogroup -1 A group used by system services.
operator 5 This group has no specific meaning.
smmsp 25 The group used by sendmail.
sshd 75 The group for the sshd child processes that process network data.
staff 20 The default group into which UNIX users are traditionally placed.
sys 3 This group has no specific meaning.
tty 4 A group that owns special files, such as the device file associated
with an SSH or telnet user.
unknown 99 The group used when the system doesn’t know about the hard
disk.
utmp 45 The group that controls what can update the system’s list of
logged-in users.
uucp 66 The group used to control access to UUCP spool files.
You can also create group accounts on a non-Apple LDAPv3 server if has been
configured for write access.
You can also use a preset or an import file to create a new group. For details, see
“Creating a Preset for Group Accounts” and Appendix A, “Importing and Exporting
Account Information.”
Nested groups do not inherit managed preferences. Members of a nested group have
their preferences managed only by their chosen workgroup, and not by a parent group.
The access permissions of a parent group can be inherited. For example, if you set a
parent group’s ACL permissions so that the parent group cannot write to the folder,
you can propagate the ACL permissions so that nested groups also cannot write to the
folder.
In Workgroup Manager, you use the Members pane in the group account window to
work with member settings.
When the name of a user in the Members list appears in italics, the group is the user’s
primary group.
When you create a user account and assign the new user a primary group, the user is
automatically added to the group you specify; you don’t need to explicitly do so.
Otherwise, you explicitly add users to a group.
You can use Workgroup Manager to add a user to a group if the user and group
accounts are in the LDAP directory of an Open Directory master or a NetInfo domain.
Naming a Group
A group has two names: a long name and a short name.
 The long group name (for example, English Department Students) is used for display
purposes only and can contain no more than 255 bytes. Since long group names
support various character sets, the maximum number of characters for long group
names can range from 255 Roman characters to as few as 85 characters (for character
sets in which characters occupy up to 3 bytes).
 A short group name can contain as many as 255 Roman characters. However, for
clients using Mac OS X version 10.1.5 or earlier, the short group name must be eight
characters or fewer. Use only these characters in a short group name:
 a through z
 A through Z
 0 through 9
 _ (underscore)
The short name, typically eight or fewer characters, may be used by Mac OS X to find
user IDs of group members when determining whether a user can access a file as a
result of his or her group membership. See Appendix B, “ACL Permissions and Group
Memberships Using GUIDs,” on page 239 for more information about group
membership.
You can use Workgroup Manager to edit the long or short names of a group account
stored in the LDAP directory of an Open Directory master, a NetInfo domain, or other
read/write directory domain. You can also use Workgroup Manager to review the
names in any directory domain accessible from the server you’re using.
Defining a Group ID
A group ID is a string of ASCII digits that uniquely identifies a group. The maximum
value is 2,147,483,648.
You can use Workgroup Manager to edit the ID for a group account stored in the LDAP
directory of an Open Directory master or a NetInfo domain, or to review the group ID
in any directory domain accessible from the server you’re using. The group ID is
associated with group privileges and permissions.
Group folders are not directly linked to workgroup management, but access and
workflow management can be improved by combining the use of group folders with
managed preferences for workgroups. For example, to set an multimedia lab computer
specifically for a movie-editing class, you could set Dock preferences for the movie-
editing workgroup to display only iMovie and the group folder. Because the group
folder is in the Dock, it provides an easily accessible location for students to store and
retrieve files.
In Workgroup Manager, you can also create group folders that don’t reside immediately
below a share point. For example, you may want to organize group folders into several
subfolders under a share point that you define. If Groups is the share point, you may
want to place student groups’ folders in /Groups/StudentGroups and teacher groups’
folders in /Groups/TeacherGroups. The full path to a group folder for second-grade
students could be /Groups/StudentGroups/SecondGrade.
Group folders are hosted on share points. For instructions on creating share points, see
“Setting Up a Local Share Point” on page 104.
The group folder is named using the short name of the group with which it is
associated.
When setting up these preferences, make sure the group is defined in a shared domain
in the search policy of the group member’s computer. See the Open Directory
administration guide for instructions on setting a computer’s search policy.
If you don’t automate group folder access, group members can access the group folder
using the “Connect to Server” command in the Finder’s Go menu to navigate to the
server where the group folder resides.
To configure more than one group to use the same group folder:
1 In Workgroup Manager, click Accounts.
2 Select the first group account you want to use the folder.
To select a group account, connect to the server where the account resides. Click the
globe and choose the directory domain where the group account is stored, click the
Groups button, and select the group.
3 Click Group Folder, select the folder you want the group to use, and click Save.
4 Repeat for each group you want to use the same group folder.
You can use Workgroup Manager to view, create, edit, and delete computer lists. To
view computer lists in Workgroup Manager, click the Computer Lists button above the
accounts list.
Accounts list
There are three preexisting computer lists: Guest Computers, Windows Computers, and
All Computers. These three lists, along with the computer lists that you set up, appear
on the left side of the Workgroup Manager window. Settings appear in the List, Access,
and Cache panes on the right side of the window.
89
Before you set up a computer list, determine the names and addresses of the
computers that you want to include. In this context, you customarily use the computer
name specified in a computer’s Sharing preferences. If you prefer, you can use a
descriptive name that you find more suitable.
A computer’s address must be the built-in Ethernet address, which is unique to each
computer. (A computer’s Ethernet address, or Ethernet ID, is also known as its MAC
address.) You can browse for a computer and Workgroup Manager enters the
computer’s name and Ethernet address for you. A client computer uses this data to find
preference information when a user logs in.
Note: For Windows Computers lists, you need to know the NetBIOS name of each
Windows client computer. This name is entered in the Windows Computer Name field.
You don’t need to know the Ethernet address of Windows client computers.
When a client computer starts up, Mac OS X tries to match the computer’s Ethernet
address with a computer record in a computer list. If a matching computer record is
found, the computer uses the managed preferences for that computer list. If no
matching computer record is found, the client computer uses the managed
preferences for the Guest Computers computer list.
To edit computer lists or computer list preferences, you must have domain
administrator privileges. You can have administrative privileges for all computer lists, or
for a specific set of computer lists. For instructions on assigning administrator privileges
for a directory domain, see “Assigning Administrator Privileges for a Directory Domain”
on page 62.
A Guest Computers list is automatically created for a server’s local directory domain. If
the server is an Open Directory master or replica, a Guest Computers list is also created
for its LDAP directory domain.
The Guest Computers list is not recommended for large numbers of computers; most
computers should belong to regular computer lists.
Note: You cannot add or move computers to the Guest Computers list, and you cannot
change the list name.
A computer cannot belong to more than one list, and you cannot add computers to
the Guest Computers list.
After you set up a computer list, you can manage preferences for it if you wish.
For more information about using managed preferences, see “Customizing the User
Experience” on page 129 and Chapter 10, “Managing Preferences.”
Settings in the List pane are specific to individual computers, and don’t apply to
presets.
After you create a preset, you can no longer change its settings, but you can change its
name or delete it. To change a preset’s name, choose the preset from the Presets pop-
up menu, and then choose Rename Preset. To delete a preset, choose a it from the
Presets pop-up menu, and then choose Delete Preset.
Note: A computer can belong to only one list. You can’t add computers to the Guest
Computers list.
Note: A user with an administrator account in a client computer’s local directory can
always log in.
Only users of the permitted groups are displayed in the login window and can log in.
Warning: Do not set the cache refresh to “0.” This would prevent the creation of the
cache and result in the computers becoming unmanaged when disconnected from
the network.
9 Click Save.
If you plan to supply individuals with their own portable computers (iBooks, for
example), you may want to make each user a local administrator for the computer.
A local administrator has more privileges than a local or network user. For example, a
local administrator can add printers, change network settings, or decide not to be
managed.
The easiest way to manage preferences for local users of a particular computer is to
manage preferences for the computer list to which the computer belongs, and make
sure you allow users with local-only accounts to use computers in the computer list.
You can use the Sharing pane in Workgroup Manager to configure folders for use as
home folder locations.
101
To set up a home folder for a user in Workgroup Manager, you use the Home pane in
the Accounts window.
You can also import user home folder settings from a file. For an explanation of how to
work with import files, see Appendix A, “Importing and Exporting
Account Information.”
A user’s home folder doesn’t need to be stored on the same server as the directory
domain containing the user’s account. In fact, distributing directory domains and home
folders among various servers can help you balance your workload among several
servers. “Distributing Home Folders Across Multiple Servers” on page 103 describes
several such scenarios.
The home folder that you designate in the Home pane can be used when logging in
from a Windows workstation or a Mac OS X computer. This can be useful for a user
whose account resides on a server that is a Windows primary domain controller. See
the Windows services administration guide for information about setting up home
folders for Windows workstation users.
Warning: If the absolute path from the client to the network home folder on the
server contains either spaces or more than 89 characters, certain types of clients
cannot connect. For example, a client using automount with an LDAP-based AFP
home folder may not be able to access its home folder. The “/” character counts as a
character.
There are additional limitations on the maximum path length depending on the
version of Mac OS X used by clients. For more information, see the Apple Service &
Support website article “Avoid Spaces and Long Names in Network Home Directory
Name, Path” at docs.info.apple.com/article.html?artnum=107695.
NFS file access is based not on user authentication, but on the user ID and the client IP
address, so it is generally less secure than AFP. Use NFS only if you need to provide
home folders for a large number of users who use UNIX workstations.
SMB/CIFS is a protocol used by Windows to access share points. You can setup a share
point for SMB/CIFS access only, so that Windows users have a network location for files
that can’t be used on other platforms. Like AFP, SMB/CIFS also requires authenticating
with a valid name and password to access files.
For more details about the SMB/CIFS protocol, including information about setting up
SMB/CIFS share points for hosting home folders, see the Windows services
administration guide.
Mac OS X Server
User accounts
When a user logs in, he or she is authenticated using an account stored in a shared
directory domain on the accounts server. The location of the user’s home folder, stored
in the account, is used to mount the home folder, which resides on one of the two
home folder servers.
Step 1: Create a shared domain for the user accounts on the accounts server
You create a shared LDAP directory domain by setting up an Open Directory master, as
described in the Open Directory administration guide.
Step 2: Set up an automountable share point for the home folders on each home
folder server
For instructions on how to set up automountable share points, see “Setting Up an
Automountable AFP Share Point for Home Folders” on page 105.
Step 3: Create the user accounts in the shared domain on the accounts server
Instructions later in this chapter explain how to set up accounts so that home folders
reside in one or the other of the automountable share points.
See the instructions in “Creating Mac OS X Server User Accounts” on page 51 to learn
how to set user account attributes. See subsequent sections of this chapter for details
specific to home folder setup.
Step 4: Set up the directory services of the client computers so their search policy
includes the shared directory domain on the accounts server
See the Open Directory administration guide for information about configuring search
policies.
When a user restarts his or her computer and logs in using the account in the shared
domain, the home folder is created automatically (if it hasn’t already been created) on
the appropriate server and is visible on the user’s computer.
Home folders for user accounts stored in shared directory domains, such as the LDAP
directory of an Open Directory master, can reside in any AFP share point that the user’s
computer can access. This share point must be automountable—that is, it must have a
network mount record in the directory domain where the user account resides.
Using an automountable share point ensures that the home folder appears in
/Network/Servers automatically when the user logs in to a Mac OS X computer
configured to access the shared domain. Additionally, users can access home folders on
any automountable share point with guest access enabled.
An automountable share point ensures that the client computer can locate the NFS
share point and the home folder. It also makes the share point’s server visible in
/Network/Servers automatically when the user logs in to a Mac OS X computer
configured to access the shared domain.
Home folders for local users should reside in share points on the server where the
users’ accounts reside. These share points do not have to be automountable (that is,
they do not require a network mount record).
A user’s network home folder can reside in any AFP, NFS, or SMB/CIFS share point that
the user’s computer can access. Mac OS X home folders typically reside in AFP or NFS
share points, while Windows home folders typically reside in SMB/CIFS share points.
For information about how to set up SMB/CIFS share points for Windows user home
folders, see the Windows services administration guide.
The share point must be automountable—that is, it must have a network mount record
in the directory domain. An automountable share point ensures that the client
computer can locate the share point and the home folder. It also makes the share
point’s server visible in /Network/Servers automatically when the user logs in to a
Mac OS X computer configured to access the shared domain.
You can use Workgroup Manager to define a network home folder for a user whose
account is stored in the LDAP directory of an Open Directory master or another read/
write directory domain accessible from the server you are using. You can also use
Workgroup Manager to review home folder information in any accessible read-only
directory domain.
When the user logs in using SSH to obtain command-line access to the server, the
user’s home folder is mounted.
You can use Workgroup Manager to define a custom location for the home folder of a
user whose account is stored in a server’s local directory domain or in a shared
directory domain. The shared directory domain must be accessible from the server that
you are using. The shared directory domain can be the LDAP directory of an Open
Directory master, or another read/write directory domain.
Important: The procedure described here requires Mac OS X Server version 10.4.3
or later.
This quota doesn’t apply to the home folder share point or to the home folder, but to
the entire partition within which the home folder share point and the home folder
reside. Therefore, when a user places files in another user’s folder, it can affect the user’s
disk quota:
 When you copy a file to a user’s AFP drop box, the owner of the drop box becomes
the owner of the file.
 In NFS, however, when you copy a file to another folder, you remain the owner and
the copy operation decrements your disk quota on a particular partition.
To set up a home folder share point disk quota using Workgroup Manager:
1 In Workgroup Manager, click Accounts.
2 Select the user account you want to work with.
To select an account, connect to the server where the account resides, click the globe
and choose the directory domain where the user account is stored, click the Users
button, and select the user account.
3 To authenticate, click the lock and enter the name and password of a directory domain
administrator.
4 Click Home.
5 Specify the disk quota using the Disk Quota field and the adjacent pop-up menu.
6 Make sure that disk quotas are enabled for the volume where the share point resides.
7 Click Sharing, and select the volume in the All list. Click General and choose “Enable
disk quotas on this volume.”
A mobile account includes both a network home folder and a local home folder.
By having these two types of home folders, clients can take advantage of features
available for both local and network accounts. You can synchronize specific folders of
these two home folders, creating a portable home directory.
Synchronization ensures that users access their most recently updated files whenever
they connect to the network. If a user modifies files on different computers, when the
user connects to the network and synchronizes, the user’s computer retrieves the most
recently synchronized file.
115
About Portable Home Directories
Portable home directories are a new feature of Mac OS X version 10.4. A portable home
directory is a synchronized subset of a user’s local and network home folders.
You can configure which folders to synchronize and how often to synchronize them.
Users can also initiate synchronization. By synchronizing key folders, a user can work on
or off the network and experience the same work environment. Since the user has a
local home folder, and only synchronizes periodically or at login and logout, the mobile
account reduces network traffic, expediting server connections for users who need to
access the server. Additionally, the computer locally caches temporary files. This
improves both network and individual computer performance because the user’s
computers locally caches files like web pages.
In Mac OS X version 10.3, mobile accounts did not synchronize local and network home
folders. Before the introduction of synchronization, portable home directories did not
exist. When you manage clients with Mac OS X version 10.3 installed, you can still give
them mobile accounts but they do not have synchronized home folders.
Users with accounts stored in an Active Directory domain can have mobile accounts.
Similar to mobile accounts for clients with Mac OS X version 10.3 installed, these mobile
accounts do not synchronize. Instead of synchronization, users must manually copy
files from their local home folders to their network home folders.
There are two ways to create mobile accounts: you use Workgroup Manager to enable
synchronization of user accounts, or let network users create mobile accounts
themselves. For instructions on using Workgroup Manager to enable synchronization,
see “Creating a Mobile Account” on page 186.
Users with network accounts who also have administrative access to their computers
can create mobile accounts, which creates a portable home directory. Because they
create the mobile accounts themselves, you do not have control over their
synchronization settings, unless you explicitly manage their mobile accounts. If you
want to prevent them from creating mobile accounts, you can choose not to show
Accounts in their System Preferences. For instructions on denying access to specific
System Preferences, see “Managing Access to System Preferences” on page 197. You can
also manage their Mobility preferences so that users cannot create mobile accounts.
For instructions on managing Mobility preferences, see “Preventing the Creation of a
Mobile Account” on page 187.
At the login window, the user with a mobile account selects his or her account and
then enters the correct password to complete login. If the user already has a mobile
account with a portable home directory, his or her folders might get synchronized
depending on the login and logout synchronization settings set in Workgroup
Manager. After this, the user’s desktop appears.
If the user does not have a mobile account with a portable home directory, one of two
things occur:
 If you deselected “Require confirmation before creating a mobile account,” the
computer automatically creates the mobile account. The local home folder then
synchronizes with the user’s network home folder before displaying the user’s
desktop.
 If you selected “Require confirmation before creating a mobile account,” the user
sees a confirmation dialog that allows them to create a portable home directory, put
it off until later, or not create the portable home directory and disable the dialog
until the user holds down the Option key during login.
Mobile accounts remain on the system even when the user logs out or disconnects
from the network. Even when disconnected, the user can log in to that account.
Carefully weigh the advantages and disadvantages of using mobile accounts and
strategize how you will configure them.
A background synchronization occurs at the frequency you set, or whenever the user
manually synchronizes. By default, when you enable background synchronization,
synchronization occurs every twenty minutes. When the local home folder starts
synchronizing with the network home folder, it checks the modification times for files
located in both home folders. If the files have different modification times, then the
newer file overwrites the older file.
Login and logout synchronization should be carefully managed because a user’s login
and logout is delayed while files are synchronizing. If a user has a slow network
connection or is synchronizing many files or large files, then the user must wait for
synchronization to complete before using the system. If you want to synchronize parts
of a user’s ~/Library folder, you must use login and logout synchronization.
Synchronizing the ~/Library folder retains users’ bookmarks and individual application
preferences,
Consider synchronizing smaller files like preference files at login and logout, while
synchronizing larger files like movies in the background. Doing this reduces login and
logout times (because only preference files synchronize) and movies synchronize
throughout a user’s session instead of while the user is trying to log out. You can
further reduce network traffic by not synchronizing the movie folder and thus require
users to only be able to access the movies folder locally. By balancing login and logout
synchronization with background synchronization, you can reduce the time required
for logging in and logging out while retaining consistent, synchronized home folders.
You can use the Guest Computers computer list to manage guest computers on your
network. This allows you to manage any portable computers with Mac OS X installed
that join your directory domain. The preferences you manage in Workgroup Manager
do not apply to Windows computers. If the users of guest computers log in using
network or mobile accounts, their user and group managed preferences and account
settings apply to them. For more information about how managed preferences interact
when applied to users, groups, and computer lists, see “Understanding Managed
Preference Interaction” on page 139.
When distributing portable computers, you can still retain some control over the
computer when the user logs in with a local account while off the network. To restrict
the user from full use of the computer, do not give him or her local administrator
privileges. You can also set parental controls to further control the computer while off
of the network. For more information about how to set parental controls, see Mac Help.
To restrict users from full access to the computer, create a local administrator account
and a local user account on the computer. Give the user the login information for the
local user account but not the local administrator account. With a non-administrator
account, the user can’t install software and can only save or delete files in his or her
own home folder.
If you make the user the local administrator of the computer, you can deny the user the
ability to turn off your management of the computer. However, in many cases, the local
administrator can still override management settings.
If local users want to share files with other users over the network, they can use their
~/Public folder after enabling Personal File Sharing in the Sharing pane of System
Preferences. Similarly, local users can connect to the computers of other users who
have Personal File Sharing enabled.
If users also have network accounts, you might still prefer that they log in through their
local accounts to reduce network traffic. They can connect to their network accounts
through the “Connect to Server” command in the Finder’s Go menu.
Another consideration when using a wireless mobile lab is that the total network
throughput is much more limited than a wired lab. If users have network accounts, any
time they open or save files, it requires using the network, possibly slowing the
network connections of other users. Although mobile accounts help alleviate these
issues, frequent synchronization can also slow the network. Creating mobile accounts
without any synchronized folders efficiently utilizes the network, but it can cause issues
involving home folder proliferation. Additionally, users still have to copy and store their
files in their network home folders.
To manage your cart’s iBooks, you might create identical generic local user accounts on
each computer (for example, all the accounts could use “Math” as the user name and
“student” as the password). You might want to create different generic local accounts
for each class, such as an account for a History class, one for a Biology class, and so on.
Each account has a local home folder but does not have administrator privileges. Use a
separate local administrator account on each computer to allow server administrators
(or other individuals) to perform maintenance tasks and upgrades, install software, and
administer the local user accounts.
After creating the local user accounts, add each of the computers to a computer list,
then manage preferences for that list. Because multiple users can store items in the
local home folder for the generic account, you may want to periodically clean out that
folder as part of your maintenance routine. Recommend to your students that they
save their files to a network drop box to ensure their files are not deleted by your
maintenance routine, and so that the students can access those files regardless of who
uses the computer next.
www.nsa.gov/snac/
Directory Services
The Directory Access application enables computers to access and use a directory
server. There are three types of directory access policies: you can get directory services
from a DHCP-supplied LDAP server, trusted binding, or untrusted binding. You should
disable access to DHCP-supplied LDAP servers for computers, because they trust any
directory domain they find when connecting to external networks. Untrusted binding
is more secure than binding to a DHCP-supplied binding, but portable computers trust
directory domains with the same DNS name or IP number as your directory server.
Trusted binding is the most secure. It requires that both the portable computer and the
LDAP directory server mutually authenticate.
For more information about how to choose and implement directory access policies,
see the Open Directory administration guide.
Warning: If you do not use AFP to encrypt your files, synchronized files will transfer
across your network in an unencrypted format. Copying files to network volumes will
also send files across your network in an unencrypted format.
For more information about FileVault, search for “FileVault” in Mac Help.
Computers Printers
and and
desktops volumes
Client management
Applications,
folders,
and files
Users and groups
You can also take advantage of two additional client management options—installing
and starting up client computers over the network (using NetBoot and Network Install)
and day-to-day computer administration (using Apple Remote Desktop).
This chapter introduces each of these client management topics as they apply to users
of Mac OS X computers.
127
Using Network-Visible Resources
Mac OS X Server lets you make various resources visible throughout your network,
so users can access them from different computers and various locations.
 Group folders. When you set up a group account for network users, you can
associate a group folder with the group. A group folder is a place for group members
to exchange information electronically. A group folder contains three folders by
default—Documents, Library, and Public; the Public folder contains a Drop Box folder.
Residing on the server for easy access throughout the network, a group folder can be
shown in the Dock for access from wherever a user wants to work on group
activities.
 Other shared folders. You can set up other folders on the server to provide users
access to applications, handouts, announcements, schedules, and other files.
Many factors, including user responsibilities and security issues, determine what
computer work environment a user should be presented with. In some cases, setting
up informal usage guidelines may be sufficient. In other cases, extensively controlling
the computer experience, with each system setting defined and locked and each
application controlled, may be necessary. The preferences you define should
implement system capabilities that best support your user and your business
requirements.
Other preferences are used to manage what a user can access and control. For
example, you can set up Media Access preferences to prevent users from burning CDs
and DVDs or making changes to a computer’s internal disk.
Here’s a summary of how preferences affect the appearance of the desktop and the
activities a user can perform:
The first user in this case is the local computer administrator. The next three are users
who have accounts that reside on the server, the last of whom has a mobile account.
All four of these users have network accounts. Additionally, by disabling the Restart and
Shut Down buttons, you prevent people who do not have network accounts from
shutting down, restarting, or putting your computers to sleep. This login window also
includes the message “Welcome to the Math Lab!,” which serves as both a welcome
and a warning to users that they are using math lab computers.
Network account users choose from workgroups in their directory domain, while local
users get their workgroups from their local directory. It’s possible for a user to belong
to a group that doesn’t appear in the list; it lists only workgroups that are allowed
access by the computer list. Local administrators also have the option to not choose a
workgroup and disable preference management.
Users can also select “Remember my choice,” whereby for future logins, the workgroup
picker is bypassed and the workgroup is automatically chosen for the users. Users can
still change their workgroup by holding down the Option key as their password is
being validated.
If the computer is associated with a computer list that supports local-only users, all
workgroups given access to the computer by the computer list are listed after a local
user logs in. The user can select any of them.
Any preferences that are associated with the user, the chosen workgroup, and the
computer being used take effect automatically.
To make specific applications easy to find, you can use Dock Items preferences to place
an alias for the My Applications folder in the user’s Dock. The My Applications folder
contains aliases to applications. Adding the My Applications folder might substantially
delay the required login time for managed users, because Mac OS X has to search
available disks to build the applications list every time the user logs in. For instructions
on creating aliases to My Applications and other folders in a user’s Dock, see “Adding
Items to a User’s Dock” on page 158.
You manage user access to local applications by creating lists of approved applications
in the Applications preference. To set up a list of approved applications, see “Creating a
List of Applications Users Can Open” on page 148. This list of approved applications
determines what users find in the My Applications folder located in the Dock.
To prevent users from opening a Finder window to easily browse to other applications,
use Simple Finder. For more information about using the Simple Finder, see “Setting Up
Simple Finder” on page 165.
If you have set up a group folder, you can set up quick access to it when a user logs in
to the workgroup with which the folder is associated. Users can use this group folder to
facilitate file sharing between group members. For instructions on creating an alias to
the group folder, see “Providing Easy Access to Group Folders” on page 157. To provide
access to the group volume, which contains the /Public folder and a drop box for the
group, see “Providing Easy Access to the Group Share Point” on page 177.
In addition to using managed preferences, you can also use network views to improve
workflow. Network views control what users see when they click the Network icon in a
Finder window. For more information about network views, see Chapter 11, “Managing
Network Views,” on page 207.
Mac OS X
Server
Network Install NetBoot
images images
You use Network Install images when you want to install software on computers or to
refresh a computer once. You use NetBoot images when you want student computer
environments to be refreshed every time the computer is started.
You can use the Preferences pane in Workgroup Manager to manage preferences.
For an overview of using managed preferences to customize the user experience, see
“The Power of Preferences” on page 130, and “Designing the Login Experience” on
page 131.
137
How Workgroup Manager Works with Mac OS X Preferences
With Workgroup Manager you can set and lock certain system settings for users on
their network. You can set preferences once and thereafter allow users to change them,
or you can keep preferences under administrative control at all times (or you can leave
preference settings unmanaged).
Workgroup Manager provides control over most major system and application
preferences, in addition to various settings for users, groups, and computer lists.
The preference editor controls the remainder of the applications that may require
management.
Energy Saver preferences and Login Window settings can be defined only for computer
lists, but other preferences can be defined for users, workgroups, and computer lists.
The illustration below shows how managed preferences interact when the same
preferences are set at multiple levels:
User
Computer
Group
Resulting
Relationship
 Printing, Login, Applications, and some Dock preferences (involving items that
appear in the Dock) are combined.
For example, if you define printing preferences for users and computers, a user’s
printer list includes printers set up for both the user and the computer being used.
Note: Managed System Preferences are combined, in that different settings defined
in Workgroup Manager act collectively at login.
 Other preference settings defined at more than one level may be overridden at login.
User Preferences
Computer Preferences
Group Preferences
When overriding preferences conflict, user preferences override both computer and
group preferences, while computer preferences override group preferences.
For example, let’s say you have different managed Dock preferences for users,
workgroups, and computer lists. The Dock preferences for the user would take
precedence, overriding and nullifying any Dock preferences set for workgroups or
computers. If you do not manage any Dock preferences for the user, the computer
list Dock preferences override and nullify any group Dock preferences.
An example of when overriding preferences is useful is in a school where you want
to prevent all students from using recording devices attached to a school computer,
except for students who serve as lab assistants. You could set up Media Access
preferences for workgroups or computer lists to limit all students’ access, but
override these restrictions for lab assistants using Media Access settings at their user
account level.
 Inherited preferences are preferences set at only one level.
In some cases, you may find it easier and more useful to set certain preferences at
only one level. For example, you could set printer preferences only for computers, set
application preferences only for workgroups, and set Dock preferences only for users.
In such a case, no overriding or combining occurs, and the user inherits the
preferences without competition.
In the Overview Preference panes, you can set the following preferences to Once:
Dock, Finder (Preferences and Views), Internet, Login (Login Items), Mobility (Login &
Logout Sync and Background Sync panes of Rules), and Universal Access. For all
other preferences, you must choose either Always or Never.
Note: When using the preference editor (the Details view within the Preferences pane),
you can set preferences to Often. Often settings are similar to Once settings, but are
reapplied at every login. This management setting is useful for training environments.
Users can customize their preferences to suit their needs during a session without any
risk of affecting a future user’s work experience. Additionally, some applications will
only respond to preference management if set to Often.
Caching Preferences
Preferences can be cached on Mac OS X computers, so they remain in effect even when
the computer is off the network:
 Computer preferences and preferences for any workgroups that can use the
computer are cached.
 User preferences are always cached for users who have mobile accounts.
When a client computer is off the network, only users with local accounts or network
users with mobile accounts on that computer can log in.
All preferences are stored in a record, which is either a user, group, or computer record.
At login time, the managed client picks those out and puts them in a location where
the final combined management list is applied to the user experience.
After user accounts, group accounts, and computer lists are created, you can start
managing preferences for them using the Preferences pane in Workgroup Manager.
To manage preferences for Mac OS X clients, you should make sure each user you want
to manage has either a network home folder or a local home folder on the server.
For information about how to set up set up home folders for users, see Chapter 7,
“Setting Up Home Folders.”
Note: When you manage preferences for a user, group, or computer, an arrow icon
appears next to the managed preference in the Preferences pane to indicate that you’re
managing that preference. You can select multiple users, groups, or computers to
review managed preferences. If the arrow icon is dimmed, it means managed
preference settings are mixed for the selected items.
The cached preferences can help you manage local user accounts on portable
computers even when they’re not connected to a network. For example, you can create
a list of computers you want to manage, and then manage preferences for the
computer list. Next, you can make these computers available to groups and then
manage preferences for the groups. Finally, you can set up local user accounts on the
computers. Now, if a user goes offline or disconnects from your network, he or she is
still managed by the computer and group preferences in the cache.
Note: When you modify an account or preference setting, the preferences cache is
updated automatically. New preferences take effect at the user’s next login. If the user
is already logged in while away from the network, the user must log out and log in
again to update the preference cache.
Warning: If you manually update the cache on the client computer while it is
disconnected from the network, its preferences cache is deleted and the computer
becomes unmanaged. The computer will become managed again when reconnected
to the network and a user logs in to the directory domain.
You should also consider which preferences you want to leave under user control. For
example, if you aren’t concerned about where a user places the Dock, you might want
to set Dock Display management to Never or Once.
If you adjust a mixed-state setting, every account has the new setting you choose.
For example, suppose you select three group accounts that each have different settings
for the Dock size. When you look at the Dock Display preference pane for these
accounts, the Dock Size slider is centered and has a dash on it. If you change the
position of the Dock Size slider to Large, all selected accounts will then have a large-
size Dock.
You can use the Once setting to create “default” settings. These are settings that, when
saved, take effect the next time users log in. Users can then modify their settings and
save their modified settings for future use. The Often setting does not allow users to
save their preferences for future use, but they can modify their preferences for their
current sessions.
Note: Applications are identified by their bundle ID. Since a clever user may change an
application’s bundle ID and thus defeat their access restrictions, the application
restrictions should not be considered a barrier that no user can overcome.
If you create a list of approved applications, users can open only the listed applications.
(You can, however, allow applications to open “helper applications” that are not listed.)
If you create a list of nonapproved applications, users can open any application that is
not in that list.
When you set up a list of approved applications, you can choose whether to allow
them to use helper applications that aren’t in the approved-items list.
If you choose not to allow access to these types of tools, some applications may not
function properly. Allowing this option enhances application compatibility and efficient
operation, but for more strict security, you may choose not to do so.
The table below describes what the settings in each Classic pane can do.
If multiple Mac OS 9 System Folders are available and you don’t enforce any settings in
the Startup pane of the Classic preference, users may choose from among available
Mac OS 9 System Folders if they have access to the Classic pane of System Preferences.
If an item is hidden, users cannot access that item from the Apple menu; however,
there may be alternative methods of access, such as starting the Chooser by navigating
to it within the Mac OS 9 System Folder. If you want to further limit user access to these
items, you can use the Applications preferences in Workgroup Manager to determine
which specific applications a user may or may not open. For more information, see
“Managing Access to Applications” on page 148.
Note: Disallowing access to the Chooser may affect what happens when a client
attempts to print from Classic if printer management is also enforced. If users cannot
access the Chooser, they cannot set up new printers or switch between types of
printers (such as PostScript and non-PostScript printers).
In some circumstances, you may need to use applications that operate in the
background without the user’s interaction or knowledge. If a background application is
in use when Classic enters sleep mode, that application suspends its activity. If you
want to keep the application running, you can set Classic’s sleep setting to Never.
If you choose not to use preferences in the user’s own Home folder, a user’s Mac OS 9
data is stored in the Mac OS 9 System Folder and is not kept separate from other user’s
data. In this case, users share preferences and any changes made by the last user are in
effect when the next user logs in.
The table below describes what the settings in each Dock pane can do.
If the group directory is not available when the user clicks the group folder icon, the
user must enter a user name and password to connect to the server and open the
directory.
Note: This preference setting applies only to groups. You cannot manage this setting
for users or computers.
If you change the location of the group share point, be sure to update the Dock item
for the group in Workgroup Manager.
You can configure Energy Saver preferences for desktop and portable computers.
Desktop computers and portable computers differ in that portable computers can run
on battery power.
The table below summarizes what you can control with the settings in each Energy
Saver pane.
You can use Workgroup Manager’s Energy Saver preference settings to put client
computers to sleep automatically after a specified period of inactivity. Other settings
enable you to wake or restart the computer when certain events happen.
To manually wake up a sleeping computer or display, the user can click the mouse or
press a key on the keyboard.
Users should be encouraged to use the computer’s adapter when possible to save
battery power.
To manually wake up a sleeping computer or display, users can click the mouse or press
a key on the keyboard.
Users should be encouraged to monitor battery status when roaming free and use a
power adapter when possible to maintain a fully charged battery.
In addition to using Workgroup Manager, you can set up Simple Finder on a client
computer (locally) using System Preferences. When you use Workgroup Manager to
apply the Simple Finder environment and the feature is not in use on the local
computer, only the client’s Finder is affected; Dock and Application access settings
must be managed separately. You can set up the Simple Finder on the local computer,
and use the application and Dock management features in Workgroup Manager to add
Dock items and application access.
Important: For client computers using Mac OS X versions 10.2 through 10.2.8, don’t
turn on Simple Finder for users who log in to a workgroup with its own group folder.
These users can’t use applications because Simple Finder prevents access to the group
folder.
These items still appear in the top-level folder when a user clicks the Computer icon in
a Finder window toolbar.
To prevent users from using or burning recordable CDs or DVDs, use settings in the
Media Access panes.
Only computers with a CD-RW drive, Combo Drive, or SuperDrive can burn CDs. The
Burn Disc command works only with CD-R, CD-RW, or DVD-R discs. Only a SuperDrive
can burn DVD-Rs.
As an additional preventive measure, you can make the Restart and Shut Down buttons
unavailable (dimmed) from the login window, by using settings in Login preferences.
For instructions, see “Managing Login Preferences” on page 174.
Default View settings control the overall appearance of all Finder windows. Computer
View settings control the view for the top-level computer folder, showing hard disks
and disk partitions, external hard disks, mounted volumes, and removable media (such
as CDs or DVDs).
The table below describes what the settings in each Internet pane can do.
The table below summarizes what you can do with the settings in each Login pane.
Scripts, Login Window, and Options can be managed for computers only, not for users
or groups.
Items open in the order they appear in Login Items preferences (you can specify the
order). As items open, they “stack” on top of one another; the last item is closest to the
top. For example, if you specify three items to open (and none is hidden), the user sees
the menu bar for the last item opened. If an application has open windows, they may
overlap windows from other applications.
A user can stop login items from opening by holding down the Shift key during login
until the Finder appears on the desktop; you can turn off this feature.
You should not provide access to a user’s network home folder to users with mobile
accounts on Mac OS X version 10.4 or later. Mac OS X version 10.4 introduces portable
home directories, which provide a synchronized subset of the user’s local and network
home folders. If a user modifies files in both the local and network home folders, when
the two home folders synchronize, the newer modifications take precedence, which
could surprise and confuse the user. Additionally, users could be confused by having
multiple folders titled with their user names and similarly named folders like
Documents, Music, and others.
Note: This preference setting applies only to groups. You cannot manage this setting
for users or computers.
When the user logs in, the computer connects to the group share point with the user
name and password given at login. If you manage Finder preferences and choose not
to show connected servers, the group volume’s icon does not appear on the desktop.
However, the user can find the volume by clicking Computer in a Finder window.
If you change the location of the group share point, be sure to update the login item
for the group in Workgroup Manager.
You may also want to remove the Restart and Shut Down commands from the Finder
menu. (For instructions, see “Managing Finder Preferences” on page 164.) Check the
Commands pane of Finder preferences and make sure Restart and Shut Down are not
selected.
Note: Login Window settings are available only for computer lists.
If a password hint has been created for a local user, the hint is always displayed after
three failed attempts, even if Show Password Hint is not selected. Password hints are
not used for network user accounts.
Fast User Switching can be convenient for computers used by small, consistent groups.
Note: This feature is for clients running Mac OS X version 10.3 and later.
When enabling the use of login and logout scripts, you can set a trust value for the
client. Trust values determine the required level of authentication before a client will
trust a server enough to run its scripts. Most trust values directly correlate to LDAP
security policy settings you configure in Directory Access. The trust value of DHCP
correlates not to a security policy but rather to whether Directory Access is configured
to use a DHCP-supplied LDAP server. The trust value of Authenticated requires you to
set up trusted binding to an LDAP directory.
For more information about how to use Directory Access to enable LDAP security
policies, using DHCP-supplied LDAP, or setting up trusted binding, see the Open
Directory administration guide.
The following table lists valid trust values and describes their requirements. The table is
in increasing trust order, where the bottommost entry requires the highest level of
trust.
To set the minimum required trust level, you set a client setting called MCXScriptTrust.
If the client’s MCXScriptTrust setting is an equal or lower level of trust than the actual
trust value, the client will trust the server and run its login and logout scripts. If the
client’s MCXScriptTrust setting is a higher level of trust than its actual trust value, the
client will not trust the server and will not run its scripts. The default trust value is
FullTrust.
Replace www.apple.com with the address of your LDAP directory. Running this
command displays a line similar to the following:
TrustInformation: Authenticated FullTrust
In this example, the current trust level is FullTrust. The trust level is also Authenticated.
When two trust levels are listed, the higher trust level takes precedence.
6 Set the “EnableMCXLoginScripts” key in ~root/Library/Preferences/
com.apple.loginwidow.plist to TRUE. Type the following command in Terminal:
sudo defaults write com.apple.loginwindow EnableMCXLoginScripts -bool TRUE
7 To change the trust value from FullTrust, set the “MCXScriptTrust” key in ~root/Library/
Preferences/com.apple.loginwidow.plist to a valid trust value. For example, enter the
following command in Terminal:
sudo defaults write com.apple.loginwindow MCXScriptTrust -string
PartialTrust
This command sets the trust value to PartialTrust. To set other trust values, replace
PartialTrust with other trust values. If you enter an invalid trust value, the trust value
is reset to FullTrust.
Whenever you enable login and logout scripts or change the trust value, you should
readd login and logout scripts in Workgroup Manager. For more information about
how to use Workgroup Manager to add login and logout scripts, see “Running a Login
or Logout Script”.
If a computer has the appropriate hardware, you can control whether users can “burn”
discs—that is, write information to a recordable disc such as a CD-R, CD-RW, or DVD-R.
Users can burn CDs on computers with a CD-RW drive, Combo Drive, or SuperDrive.
Users can burn DVDs only on computers with a SuperDrive.
Note: Behavior for internal hard disks may vary slightly between clients running
Mac OS X 10.2 (Jaguar) and 10.3 (Panther). For consistent results, set access privileges
for internal disks and partitions on individual clients by using Ownership and
Permissions settings in the Finder.
The table below describes what you can do with the settings in each Mobility pane.
For planning information and other considerations with mobile accounts, see
Chapter 8, “User Management for Portable Computers.”
Changes are applied to a mobile account the next time the client computer connects
to the network.
Note: When a mobile account is enabled, it appears in the login window and in the
Accounts pane of System Preferences with the label Mobile. When the account is
selected in the Accounts pane, most settings appear dimmed.
If you do not manage Mobility preferences and you allow the user to access the
Accounts pane of System Preferences, network users can create their own mobile
accounts.
If a user previously created his or her mobile account, he or she still has a local home
folder after removing the account from the directory domain. You can delete the local
home folders to save hard disk space. For instructions on deleting the local home
folders, see “Removing Mobile Accounts from Client Computers” on page 188.
Removing the account from the client computer changes the user’s account type from
a mobile account to a network account.
Login and logout synchronization should be carefully managed because a user’s login
and logout is delayed while files are synchronizing. Using background synchronization
can also cause users to load outdated files from the network, especially when
synchronization is set to occur at long intervals. Also, you cannot synchronize ~/Library
in the background.
For detailed information about things you should consider when choosing folders to
synchronize and how to synchronize them, see “Strategies for Synchronizing Content”
on page 120.
Carefully set the background synchronization frequency. If you set it to a short interval
and you have many concurrent users, you might overload the server. In this situation,
the server could become backlogged by the frequent, continual comparing of file
modification dates. If you set the frequency to a very long interval, you run a higher risk
of users loading older, outdated files. If users save files and log off before the
background files synchronize, when the users load the same file on another computer,
they may get either an older synchronized file or no file at all.
The server administrator manages which users or groups get these proxies and
specifies the proxy they are allowed to access in the Preferences pane of Workgroup
Manager. Only one proxy server per type can be specified for a user or a group.
If you haven’t already set the management settings of Network preferences to Always
and enabled a proxy server, you need to do so before choosing which hosts and
domains to bypass.
The table below describes what the settings in each Printing pane can do.
The preferences that appear in Workgroup Manager are those installed on the
computer you’re currently using. If your administrator computer is missing any
preferences that you would like to disable on client computers, you should either install
the applications related to those preferences, or use Workgroup Manager on a
computer that includes those preferences.
Universal Access
preference pane What you can control
Seeing The visual display and desktop zooming
Hearing The visual alert for users
Keyboard How the keyboard responds to keystrokes and key combinations
Mouse How the pointer responds, and whether users can use the numeric
keypad instead of a mouse
Options Shortcut key combinations, the use of assistive devices, and
whether the computer reads text in the Universal Access
preference pane
Note: If display settings are managed once, users can toggle between the zoom or
color options using keyboard shortcuts. If the management setting is Always, users
cannot toggle between options.
To further customize the user’s display, you can use Finder View preferences to control
the size of icons in Finder windows and use Dock Display preferences to enlarge or
magnify icons in the user’s Dock.
To allow the use of an assistive device on a specific computer, such as a screen reader,
click Preferences, select a computer list, click System Preferences, click Universal Access,
click Options, click Always, and select “Enable access for assistive devices.”
Note: If you enable Universal Access Shortcuts, a user can press the Shift key five times
to turn Sticky Keys on or off.
If the keyboard is too responsive for some users, causing problems with repeated
keystrokes, you can use Slow Keys to increase the delay in response to a pressed key.
The computer can respond to pressed keys with a “click” sound to provide some
feedback to the user.
Note: If you enable Universal Access Shortcuts, a user can press the Option key five
times to turn Mouse Keys on or off.
If the pointer moves too quickly for some users, you can adjust how soon the pointer
begins to move and how fast it moves.
Before using the preference editor to manage an application’s preferences you must
add the application to the preference editor’s application list. For instructions on
adding an application to the application list, see “Adding an Application to the
Preference Editor’s Application List” on page 204.
You use the Network pane in Workgroup Manager to create and manage network
views.
207
About Network Views
A network view is a list of network resources that you customize to enhance a user’s
browsing and resource discovery experience. You can add network resources to what a
user already sees, or specify exactly which items a user sees. You can customize
network views for a single computer, a group of computers, or an entire subnet.
You can create network views that contain one or more of these components:
 A neighborhood, which is a collection of network resources that are grouped for easy
access. A neighborhood looks like a folder in the network view. A neighborhood can
contain computers, other neighborhoods, and dynamic lists.
 A computer is any computer on the network. You can add computers directly to a
network view or you can add them to a neighborhood within a network view.
 A dynamic list gives you the ability to automatically generate a list of network
resources for display inside a neighborhood. For example, you can define a
neighborhood called Marketing and show within it any active computer on the
marketing subnet.
Default and Public views should keep their automatically created names of “Default”
and “Public.” These are reserved names that should be not be changed. By changing
their names, you effectively change them into named views, which must be associated
with specific client computers. Additionally, you should not rename named views to
“Default” or “Public” unless you want them to become Default or Public views.
Warning: If you click Delete in the toolbar or choose Server > Delete, you will delete
the network view, not the neighborhood.
8 If you think you may have deleted objects inadvertently, click Revert. Otherwise, click
Save.
Before adding a computer to the directory domain, ensure that it is not already in the
directory domain. Although you can add the same computer to a directory domain
multiple times, this can have unintended consequences. To display a list of the
computers already added to the directory domain, choose Show Computers from the
Add (+) pop-up menu. Double-click a listed computer to display its information.
Warning: If you click Delete in the toolbar or choose Server > Delete, you will delete
the network view, not the neighborhood.
7 If you think you may have deleted a computer inadvertently, click Revert. Otherwise,
click Save.
Mac OS X and Mac OS X Server can use Open Directory to discover network services,
such as file servers, that make their locations known with AppleTalk, Bonjour, SLP, or
SMB/CIFS service discovery protocols. You use Directory Access on the server hosting
your network views to enable or disable the various service discovery protocols you
may want to use to provide dynamic lists.
Warning: If you click Delete in the toolbar or choose Server > Delete, you will delete
the network view, not the neighborhood.
7 If you think you may have deleted a list inadvertently, click Revert. Otherwise, click
Save.
If the computer doesn’t find a computer record with an assigned network view, it
searches through the directories in its search policy for a network view whose name
matches one of the following criteria, in the order listed:
 The computer’s Ethernet address
 The computer’s IP address
 The computer’s subnet string
If a network view matching one of these criteria is found, the computer uses that view
and stops searching. But if no network view is found, the computer searches through
directories in its search policy for a view named Default. The first Default view found is
used.
The client computer first searches through all directories in its search policy. If it cannot
find a suitable network view, the client computer then searches all directories it is
configured to access, including those not in its search policy. For each directory
domain, if it finds a Public network view, it displays it in a folder named after the server
hosting the directory domain. If it doesn’t find a Public view but does find a Default
view in the directory domain, the Default view is displayed in a named folder.
Make sure that the authentication search policy of the computer is configured to
access the directory domain in which the view is stored.
If you’ve named a network view using a subnet mask in Classless Inter Domain Routing
(CIDR) notation and want to avoid showing the view on any particular computer in the
subnet, assign a different named view to the computer record for the computer. The
view you assign can be Default, Public, or a view named using an Ethernet or IP
address.
Although you can add your network view to the Finder’s network resources list, you
cannot use this method to add more than one network view on the client computer.
For example, if you make views named after both a client computer’s Ethernet address
and IP address, the client computer only displays the Ethernet address. For more
information, see “How a Computer Finds Its Network Views” on page 216.
For more information about NTP, DNS, or DHCP, see the network services administration
guide.
You can send the following commands by using the ssh command. You can also test
and correct a computer’s time settings in System Preferences. Both of these methods
allow you to test and correct only one computer at a time, whereas by using Apple
Remote Desktop, you can test and correct many computers simultaneously.
All of your computers should be on the same time zone. If they are not on the same
time zone, send the following UNIX command:
221
sudo systemsetup -settimezone ‘US/Pacific’
For other time zones, see the man page for systemsetup. For instructions on sending
UNIX commands through Apple Remote Desktop, see the Apple Remote Desktop
administration guide.
2 In Apple Remote Desktop, send the following UNIX command to all of your computers:
sudo systemsetup -gettime
All of your computers should have times within a few minutes of each other. If they
have a wide range of times, send the following UNIX command:
sudo systemsetup -settime current_time
Replace current_time with the current time in military format, using HH:MM:SS (hour,
minute, second) notation.
If you have Apple Remote Desktop installed, you can quickly test your entire network.
In Apple Remote Desktop, create a scanner that displays computers with IP addresses
within the range distributed by your DHCP server. If a computer is switched on, is not
in sleep mode, and is connected to your network, the computer should be in this list.
This list displays the IP address given to the computer, and the computer’s host name.
Computers that are not assigned host names by the DNS service are listed without host
names. If a computer is listed and has an appropriate IP address and host name, the
computer is receiving DHCP and DNS service. For more information about how to use
scanners in Apple Remote Desktop, see the Apple Remote Desktop administration
guide.
If you do not have Apple Remote Desktop installed, you can perform the following task
to test a single computer’s ability to receive DNS service.
Note: Instead of using Network Utility, you can use the dig tool in Terminal. Enter the
following command in Terminal:
dig name_or_address
Replace name_or_address with the domain name or the IP address of your Open
Directory master server. The resulting log should have an “answer” section with either
the correct IP address or domain name.
If you have Apple Remote Desktop installed, you can quickly test your entire network.
In Apple Remote Desktop, create a scanner that displays computers with IP addresses
within the range distributed by your DHCP server. If a computer is switched on, is not
in sleep mode, and is connected to your network, the computer should be in this list.
This list displays the IP address given to the computer, and the computer’s host name.
Computers that are not assigned host names by the DNS service are listed without host
names. If a computer is listed and has an appropriate IP address and host name, the
computer is receiving DHCP and DNS service. For more information about how to use
scanners in Apple Remote Desktop, see the Apple Remote Desktop administration
guide.
If you do not have Apple Remote Desktop installed, you can perform the following task
to test a single computer’s ability to receive DHCP service.
The login window lists network users only if managed preferences are set, as described
in “Specifying How a User Logs In” on page 175.
Users can log in to Mac OS X Server if you reconnect the Password Server’s computer to
the network. Alternatively, while the Password Server’s computer is offline, users can
log in with user accounts whose password type is crypt password or shadow password.
Users with mobile user accounts can still log in to the Mac OS X computers they used
previously. And users affected by these problems can log in by using a local user
account defined on the computer, such as the user account created during initial setup
after installing Mac OS X.
If a user with a local account doesn’t see a list of workgroups at login, add the user’s
computer to a computer list with multiple workgroups. Select “Local-only accounts pick
workgroups from the above list.” Your client computers must use Mac OS X version 10.4
or later to be able to select from these workgroups. For more information about how to
set access settings for computer lists, see “Using Local User Accounts” on page 98.
For example, suppose the default application for viewing PDF files is Preview. A user
logs in and double-clicks a PDF file on his or her desktop. If the management settings
that apply to that user don’t provide access to Preview, the file does not open. If the
user has access to a different application that can handle PDF files, the user can open
that application and then open the file.
To make sure commonly used applications are available to users, groups, or lists of
computers, use Workgroup Manager to add the application to the list of permitted
applications in the Applications pane of Preferences.
Note: If “Allow user to modify the printer list” is not selected, an administrator
password is required to add or remove printers in Printer Setup Utility.
If you select Always, a user can add additional login items if you select “User may add
and remove additional items.” Selecting Always removes any existing items from the
user’s login items list and replace them with the items you list. It also prevents the user
from disabling the items you list.
If you select Once, you can select “Merge with user’s items,” which causes one of two
effects depending on whether the user already has items in their login list:
 If the user already has items listed in their login list, either from the user adding them
or from having items previously added through preference management, merging
only opens login items that appear on both the user’s list and your list.
 If the user’s login list does not include any items, all managed login items open.
If you do not select “Merge with user’s items,” all login items on either list open.
If you select Once, a user can remove any items added to their login list.
For detailed instructions on managing automatically opened items, see “Opening Items
Automatically After a User Logs In” on page 176.
If you deselect “Merge with user’s Dock,” all Dock items you place will override users’
Dock items settings. Users cannot add additional items to their Docks if you select
Always and deselect “Merge with user’s Dock.” Users cannot remove items from their
Docks if you select Always.
For more information about how to add Dock items, see “Adding Items to a User’s
Dock” on page 158.
This behavior does not affect any Dock items; all of them work as expected when
selected. You may be able to correct this behavior by removing Dock item settings
from all affected accounts, and then respecifying them.
If you add items to a user’s Dock that are only located on the server and not the user’s
hard disk or other volume mounted on the user’s computer, the items appear as
question mark icons. Clicking these icons does not open the items. If you add an item
that is located on both the server and the user’s computer, clicking the icon opens the
item located on the user’s computer or a mounted volume.
Users are not allowed to access the control panels mentioned above when Classic
preferences are managed. Users may also see the message if you have selected “Hide
Chooser and Network Browser” and they attempt to use the Chooser.
The message also appears when a user tries to open an unapproved application (one
that is not listed in the Items pane of the Applications preference in Workgroup
Manager) in either the Classic environment or Mac OS X.
You cannot use an import file to change these predefined users: daemon, root, nobody,
unknown, or www. Nor can you use an import file to change these predefined groups:
admin, bin, daemon, dialer, mail, network, nobody, nogroup, operator, staff, sys, tty
unknown, utmp, uucp, wheel, or www. However, you can add users to the wheel and
admin groups.
You can use the dsimport tool to import any number of records from a text-delimited
file.
See the Open Directory administration guide for descriptions of common record types
and attributes. For a more complete list of attributes, enter man
DirectoryServiceAttributes, or view the DirServicesConst.h file.
231
Limitations for Importing and Exporting Passwords
When creating new records or when overwriting existing records, you need to reset
passwords for user accounts with Open Directory passwords or shadow passwords.
Importing passwords generally works only if the password is a plain text string in the
import file. Additionally, you need to set the AuthMethod attribute so that Workgroup
Manager can import the password. Encrypted passwords that are in hash format in the
import file cannot be recovered.
Passwords cannot be exported using Workgroup Manager or any other method. If you
are importing user accounts from an export file, remember to manually set passwords
or set default passwords to a known value. Before exporting user accounts (or after
importing them), you can set up a password policy that requires that users change
their password at first login. For instructions on configuring password options, see
“Choosing a Password Type and Setting Password Options” on page 64.
For more information and instructions on archiving the Open Directory master, see the
Open Directory administration guide.
Before trying to import accounts using Workgroup Manager, you should create a
character-delimited or XML file containing the accounts to import, and place it in a
location accessible from the computer on which you use Workgroup Manager. The
LDAP directory of an Open Directory master supports files with up to 200,000 records,
while local NetInfo databases support files with up to 10,000 records.
Important: Workgroup Manager can only import files that use UNIX line breaks. When
editing import files, use a text editor that supports UNIX line breaks.
For information about how to create files to import, see the following topics:
 “Using XML Files Created with Mac OS X Server Version 10.1 or Earlier” on page 234
 “Using XML Files Created with AppleShare IP 6.3” on page 235
 “Using Character-Delimited Files” on page 236
You can use the dsimport tool to import any number of records from a text-delimited
file. For more information about these attributes, open Terminal and type man
DirectoryServicesAttributes.
See the Open Directory administration guide for a list of record types, their standard
attributes, and the accepted values of the attributes.
The following group account attributes might be present in these XML files. If there are
group accounts present, then the required group attributes must be included.
 group name (required)
 group ID (required)
 one member’s short name (required)
 other members’ short names
The following user account attributes are exported into these XML files. An error occurs
when you import a file with missing required attributes.
 name (required, mapped to a long name)
 inetAlias (mapped to a short name)
 comment
 indication of whether user can log in
 password format (required) and password text (required)
 Apple mail data
 indicator for whether the user is a server administrator, password change data, and
indicator for forcing a password to change (this data is ignored)
The following group account attributes might be present in these XML files:
 group name (required)
 one member’s short name (required)
 other members’ short names
The dsimport tool generates group IDs when you import this XML file, using the -r
parameter to determine the group ID to start with and incrementing each
subsequently imported group’s ID by one. When you import using Workgroup
Manager, group IDs are generated using the information you provide for primary group
IDs in the import dialog.
The first entry in the file is a record description that characterizes the format of each of
the accounts listed in the file. The entries in the file describe user or group accounts,
encoded in the format described by the first entry.
You can use Workgroup Manager to import accounts without record descriptions.
When you import an account without a record description, Workgroup Manager
displays a dialog that allows you to map attributes found in the imported file. If the
imported file has a record description, you do not see this dialog.
To write the record description, use the following elements in the order specified,
separating them with a space:
 End-of-record indicator (in hex notation)
 Escape character (in hex notation)
 Field separator (in hex notation)
 Value separator (in hex notation)
For user accounts, the list of attributes must have a record name and should include
the following in order to be complete:
 RecordName (the user’s short name)
 RealName (the user’s long name)
 NFSHomeDirectory
 Password
 UniqueID (the user ID)
 PrimaryGroupID
You can omit UniqueID if you specify a first user ID when importing. You can omit
PrimaryGroupID if you specify a default primary group ID when importing.
The record consists of values, which are delimited by colons. Use a double colon (::) to
indicate a missing value.
The method for setting an imported user’s password type to Open Directory requires
that the imported data actually have a password value. If the password value is missing
for a user, then the corresponding user record is created with a password type of crypt
or shadow password.
Then insert the following in the formatted record (in this example, the user ‘s password
is “pw”):
dsAuthMethodStandard\:dsAuthClearText:pw
Note: In this example, the colon (:) is the field separator. Because there is a colon in the
description for this attribute, the escape character must be used to indicate that the
colon should not be treated as a delimiter. The backslash ( \ ) is the escape character in
this example. If the field separator is anything other than the colon, the escape
character is not needed.
This is an example of a header from a standard users import file with users who have
Open Directory passwords. Although presented here on multiple lines, in an import file
it must be one line of text in which the elements are separated by spaces and without
line breaks.
0x0A 0x5C 0x3A 0x2C dsRecTypeStandard:Users 8
dsAttrTypeStandard:RecordName dsAttrTypeStandard:AuthMethod
dsAttrTypeStandard:Password dsAttrTypeStandard:UniqueID
dsAttrTypeStandard:PrimaryGroupID dsAttrTypeStandard:Comment
dsAttrTypeStandard:RealName dsAttrTypeStandard:UserShell
This is an example of a formatted record with the following attributes and values:
<Attribute>: <Value>
Record Name (short name): tuser
Authentication Method: dsAuthClearText
Password: pw
Unique ID: 1242
Primary Group ID: 20
Comment: <blank>
Real Name (long name): Terri User
User Shell: /bin/tcsh
tuser:dsAuthMethodStandard\:dsAuthClearText:pw:1242:20::Tom User:/bin/tcsh
Note: This example also uses the colon (:) as the field separator and the backslash (\) as
the escape character.
By introducing globally unique identifiers (GUIDs), Mac OS X version 10.4 can now
augment standard POSIX file system permissions with access control lists (ACLs). GUIDs
also enable nested group membership in Mac OS X version 10.4.
GUIDs do not remove or change POSIX permissions, nor do they affect interoperability
of Mac OS X with legacy UNIX systems or other operating systems.
Understanding GUIDs
Beginning with Mac OS X version 10.4, a universal ID called a globally unique identifier
(GUID, pronounced GOO-id) provides user and group identity for ACL file system
permissions. The GUID also provides membership for a user to groups and nested
groups.
The administration tools in Mac OS X Server version 10.2 and later automatically assign
a new GUID to every new user account and to every user account that’s imported, but
Mac OS X version 10.4 is the first version to use GUIDs and to include GUIDs in export
files.
Two users can have identical long names, short names, UIDs, and GIDs, but they have
different GUIDs. Thus they can have different ACL permissions and can belong to
different groups. Since their GUIDs are 128-bit values, it is extremely unlikely to have
duplicate GUIDs.
239
As an administrator, you must now make sure you can restore user accounts with
GUIDs intact. Restoring user accounts with UID, GID, and short name but no GUID does
not restore ACL permissions or group membership in Mac OS X version 10.4 or later.
For more information about how to maintain and restore GUIDs, see “Maintaining
GUIDs When Importing from Earlier Versions of Mac OS X Server” on page 242.
Mac OS X version 10.4 verifies group and nested group membership by checking
GUIDs. A group’s GUID is also used by file system ACLs and is stored on disk in the
access control entry (ACE). Legacy user short names are used only if there are no GUIDs
present in the group record.
Every file and folder always has POSIX permissions. Unless an administrator assigns ACL
permissions, the POSIX permissions continue to determine user access in a Mac OS X
version 10.4 system. If you assign ACL permissions, they take precedence over the
standard POSIX permissions.
If a file has ACL permissions but none apply to the user, the POSIX permissions will
determine user access. If a file has multiple ACEs that apply to a user, the first
applicable ACE listed takes precedence and the following ACEs are ignored.
For more information about ACL and POSIX permissions, see the file services
administration guide.
Portable Home Directories (PHDs) rely on a user having the same GUID in the local user
account on the user’s computer and in the network user account on an Open Directory
server. This ensures that file permissions are the same whether the user logs in using
the local user account (while disconnected from the network) or the network user
account.
If a user account moves to a different Active Directory domain, it gets a new SID but
not a new GUID. The user still has the access permissions assigned to old SIDs, because
Active Directory keeps track of SID history in user accounts. This allows Mac OS X
systems to work seamlessly with Windows systems.
You can have groups composed of users with earlier versions of Mac OS X and
Mac OS X version 10.4 installed. When you use Workgroup Manager on Mac OS X Server
version 10.4 to add a member to a group, you add both the user’s short name and
GUID. Adding both attributes ensures backward-compatibility.
Consider replacing all of your existing account backup files with updated backup files
to ensure that the GUIDs transfer correctly.
After upgrading or migrating your server to Mac OS X Server version 10.4, you should
back up your accounts by exporting existing user and group accounts, which now have
GUIDs. If you need to restore user or group accounts in the future, this new export file
enables you to import the users and groups with their GUIDs intact.
To make sure that GUIDs and their relationship to specific users and groups remain the
same if you need to reimport the same users and groups, create a new export file on
Mac OS X Server version 10.4 and use this file instead of the export file created using an
earlier server version.
If you lose user accounts and create new accounts with the same UID, GID, and short
names as the lost accounts, the replacement accounts have new GUIDs assigned. A
user’s new GUID won’t match the previous GUID, so the user won’t retain prior ACL
permissions or group memberships. Similarly, If you import users or groups from a file
that doesn’t include the GUID attribute, Mac OS X Server assigns new GUIDs to every
imported user and group.
Viewing GUIDs
GUIDs are stored in the directory domain and are not immediately visible in Workgroup
Manager. To view GUIDs, you must first enable the Inspector in Workgroup Manager.
For instructions on using the Inspector, see the Open Directory administration guide.
Warning: Although you can use the Inspector to edit GUIDs, you should not edit
GUIDs because doing so destroys existing group memberships and file permissions
for that user ID.
Glossary
This glossary defines terms and spells out abbreviations you may encounter while
working with online help or the various reference manuals for Mac OS X Server.
References to terms defined elsewhere in the glossary appear in italics.
ACL Access Control List. A list maintained by a system that defines the rights of users
and groups to access resources on the system.
Active Directory The directory and authentication service of Microsoft Windows 2000
Server and Windows Server 2003.
administrator computer A Mac OS X computer onto which you’ve installed the server
administration applications from the Mac OS X Server Admin CD.
AFP Apple Filing Protocol. A client/server protocol used by Apple file service on
Macintosh-compatible computers to share files and network services. AFP uses TCP/IP
and other protocols to communicate between computers on a network.
automount To make a share point appear automatically on a client computer. See also
mount.
child A computer that gets configuration information from the shared directory
domain of a parent.
computer list A list of computers that have the same preference settings and are
available to the same users and groups.
245
DHCP Dynamic Host Configuration Protocol. A protocol used to dynamically distribute
IP addresses to client computers. Each time a client computer starts up, the protocol
looks for a DHCP server and then requests an IP address from the DHCP server it finds.
The DHCP server checks for an available IP address and sends it to the client computer
along with a lease period—the length of time the client computer may use the
address.
directory domain hierarchy A way of organizing local and shared directory domains.
A hierarchy has an inverted tree structure, with a root domain at the top and local
domains at the bottom.
directory services Services that provide system software and applications with
uniform access to directory domains and other sources of information about users and
resources.
disk image A file that, when opened, creates an icon on a Mac OS desktop that looks
and acts like an actual disk or volume. Using NetBoot, client computers can start up
over the network from a server-based disk image that contains system software. Disk
image files have a filename extension of either .img or .dmg. The two image formats
are similar and are represented with the same icon in the Finder. The .dmg format
cannot be used on computers running Mac OS 9.
DNS Domain Name System. A distributed database that maps IP addresses to domain
names. A DNS server, also known as a name server, keeps a list of names and the IP
addresses associated with each name.
drop box A shared folder with privileges that allow other users to write to, but not
read, the folder’s contents. Only the owner has full access. Drop boxes should be
created only using AFP. When a folder is shared using AFP, the ownership of an item
written to the folder is automatically transferred to the owner of the folder, thus giving
the owner of a drop box full access to and control over items put into it.
everyone Any user who can log in to a file server: a registered user or guest, an
anonymous FTP user, or a website visitor.
export In the Network File System (NFS), a way of sharing a directory with clients on a
network. TBD for RAID context.
246 Glossary
filter A “screening” method used to control access to a server. A filter is made up of an
IP address and a subnet mask, and sometimes a port number and access type. The IP
address and the subnet mask together determine the range of IP addresses to which
the filter applies.
firewall Software that protects the network applications running on your server. IP
firewall service, which is part of Mac OS X Server software, scans incoming IP packets
and rejects or accepts these packets based on a set of filters you create.
FTP File Transfer Protocol. A protocol that allows computers to transfer files over a
network. FTP clients using any operating system that supports FTP can connect to a file
server and download files, depending on their access privileges. Most Internet browsers
and a number of freeware applications can be used to access an FTP server.
group A collection of users who have similar needs. Groups simplify the administration
of shared resources.
group folder A directory that organizes documents and applications of special interest
to group members and allows group members to pass information back and forth
among themselves.
guest computer An unknown computer that isn’t included in a computer list on your
server.
guest user A user who can log in to your server without a user name or password.
GUID Globally unique identifier. A hexadecimal string that uniquely identifies a user
account, group account, or computer list. Also used to provide user and group identity
for access control list (ACL) permissions, and to associate particular users with group
and nested group memberships. GUIDs are 128-bit values, which makes the generation
of duplicate GUIDs extremely unlikely.
home directory A folder for a user’s personal use. Mac OS X also uses the home
directory, for example, to store system preferences and managed user settings for
Mac OS X users.
HTML Hypertext Markup Language. The set of symbols or codes inserted in a file to be
displayed on a World Wide Web browser page. The markup tells the web browser how
to display a webpage’s words and images for the user.
HTTP Hypertext Transfer Protocol. The client/server protocol for the World Wide Web.
The HTTP protocol provides a way for a web browser to access a web server and
request hypermedia documents created using HTML.
Glossary 247
idle user A user who is connected to the server but hasn’t used the server volume for a
period of time.
IP Internet Protocol. Also known as IPv4. A method used with Transmission Control
Protocol (TCP) to send data between computers over a local network or the Internet.
IP delivers packets of data, while TCP keeps track of data packets.
ISP Internet service provider. A business that sells Internet access and often provides
web hosting for ecommerce applications as well as mail services.
Kerberos A secure network authentication system. Kerberos uses tickets, which are
issued for a specific user, service, and period of time. Once a user is authenticated, it’s
possible to access additional services without retyping a password (this is called single
sign-on) for services that have been configured to take Kerberos tickets. Mac OS X
Server uses Kerberos v5.
load balancing The process of distributing client computers’ requests for network
services across multiple servers to optimize performance.
local domain A directory domain that can be accessed only by the computer on which
it resides.
local home directory A home directory that resides on disk on the computer a user is
logged in to. It’s accessible only by logging directly in to the computer where it resides
unless you log in to the computer using SSH.
local hostname A name that designates a computer on a local subnet. It can be used
without a global DNS system to resolve names to IP addresses. It consists of lowercase
letters, numbers, or hyphens (except as the last characters), and ends with “.local” (For
example, bills-computer.local). Although the name is derived by default from the
computer name, a user can specify this name in the Network pane of System
Preferences. It can be changed easily, and can be used anywhere a DNS name or fully
qualified domain name is used. It can only resolve on the same subnet as the computer
using it.
long name The long form of a user or group name. See also user name.
248 Glossary
managed network The items managed clients are allowed to “see” when they click the
Network icon in a Finder window. Administrators control this setting using Workgroup
Manager. Also called a “network view.”
mount (verb) In general, to make a remote directory or volume available for access on
a local system. In Xsan, to cause an Xsan volume to appear on a client’s desktop, just
like a local disk.
name server A server on a network that keeps a list of names and the IP addresses
associated with each name. See also DNS, WINS.
NetBoot server A Mac OS X server on which you’ve installed NetBoot software and
have configured to allow clients to start up from disk images on the server.
NFS Network File System. A client/server protocol that uses Internet Protocol (IP) to
allow remote users to access files as though they were local. NFS exports shared
volumes to computers according to IP address, rather than user name and password.
NTP Network time protocol. A network protocol used to synchronize the clocks of
computers across a network to some time reference clock. NTP is used to ensure that
all the computers on a network are reporting the same time.
Open Directory The Apple directory services architecture, which can access
authoritative information about users and network resources from directory domains
that use LDAP, NetInfo, or Active Directory protocols; BSD configuration files; and
network services.
Open Directory master A server that provides LDAP directory service, Kerberos
authentication service, and Open Directory Password Server.
Glossary 249
owner The owner of an item can set Read & Write, Read only, or No Access permissions
for Owner; Group; and Others. The owner also can assign ownership of an item to
another user, and Group privileges to another group. By default the owner has Read &
Write permissions.
POP Post Office Protocol. A protocol for retrieving incoming mail. After a user retrieves
POP mail, it’s stored on the user’s computer and is usually deleted automatically from
the mail server.
portable home directory A portable home directory provides a user with both a local
and network home folder. The contents of these two home folders, as well as the user’s
directory and authentication information, can be automatically kept in sync.
predefined accounts User accounts that are created automatically when you install
Mac OS X. Some group accounts are also predefined.
preference manifest A file that describes the structure of and default values for an
application’s preferences (for example, what the various preference keys do).
Workgroup Manager’s preferences editor uses these files to make it easier for an
administrator to edit an application’s managed preferences.
preferences cache A storage place for computer preferences and preferences for
groups associated with that computer. Cached preferences help you manage local user
accounts on portable computers.
presets Initial default attributes you specify for new accounts you create using
Workgroup Manager. You can use presets only during account creation.
primary group A user’s default group. The file system uses the ID of the primary group
when a user accesses a file he or she doesn’t own.
print queue An orderly waiting area where print jobs wait until a printer is available.
The print service in Mac OS X Server uses print queues on the server to facilitate
management.
privileges The right to access restricted areas of a system or perform certain tasks
(such as management tasks) in the system.
250 Glossary
proxy server A server that sits between a client application, such as a web browser,
and a real server. The proxy server intercepts all requests to the real server to see if it
can fulfill the requests itself. If not, it forwards the request to the real server.
RTSP Real Time Streaming Protocol. An application-level protocol for controlling the
delivery of data with real-time properties. RTSP provides an extensible framework to
enable controlled, on-demand delivery of real-time data, such as audio and video.
Sources of data can include both live data feeds and stored clips.
scope A group of services. A scope can be a logical grouping of computers, such as all
computers used by the production department, or a physical grouping, such as all
computers located on the first floor. You can define a scope as part or all of your
network.
share point A folder, hard disk (or hard disk partition), or CD that’s accessible over the
network. A share point is the point of access at the top level of a group of shared items.
Share points can be shared using AFP, Windows SMB, NFS (an “export”), or FTP
protocols.
short name An abbreviated name for a user. The short name is used by Mac OS X for
home directories, authentication, and email addresses.
SID Security Identifier. A unique value that identifies a user, group, or computer
account in a Windows NT-compatible domain.
Simplified Finder A user environment featuring panels and large icons that provide
novice users with an easy-to-navigate interface. Mounted volumes or media to which
users are allowed access appear on panels instead of on the standard desktop.
SLP DA Service Location Protocol Directory Agent. A protocol that registers services
available on a network and gives users easy access to them. When a service is added to
the network, the service uses SLP to register itself on the network. SLP/DA uses a
centralized repository for registered network services.
SMB/CIFS Server Message Block/Common Internet File System. A protocol that allows
client computers to access files and network services. It can be used over TCP/IP, the
Internet, and other network protocols. Windows services use SMB/CIFS to provide
access to servers, printers, and other network resources.
Glossary 251
SSL Secure Sockets Layer. An Internet protocol that allows you to send encrypted,
authenticated information across the Internet. More recent versions of SSL are known
as TLS (Transport Level Security).
subnet A grouping on the same network of client computers that are organized by
location (different floors of a building, for example) or by usage (all eighth-grade
students, for example). The use of subnets simplifies administration. See also IP subnet.
TCP Transmission Control Protocol. A method used along with the Internet Protocol
(IP) to send data in the form of message units between computers over the Internet. IP
takes care of handling the actual delivery of the data, and TCP takes care of keeping
track of the individual units of data (called packets) into which a message is divided for
efficient routing through the Internet.
UID User ID. A number that uniquely identifies a user within a file system. Mac OS X
computers use the UID to keep track of a user’s directory and file ownership.
URL Uniform Resource Locator. The address of a computer, file, or resource that can be
accessed on a local network or the Internet. The URL is made up of the name of the
protocol needed to access the resource, a domain name that identifies a specific
computer on the Internet, and a hierarchical description of a file location on the
computer.
user name The long name for a user, sometimes referred to as the user’s “real” name.
See also short name.
user profile The set of personal desktop and preference settings that Windows saves
for a user and applies each time the user logs in.
virtual user An alternate email address (short name) for a user. Similar to an alias, but
it involves creating another user account.
VPN Virtual Private Network. A network that uses encryption and other technologies
to provide secure communications over a public network, typically the Internet. VPNs
are generally cheaper than real private networks using private lines but rely on having
the same encryption system at both ends. The encryption may be performed by
firewall software or by routers.
workgroup A set of users for whom you define preferences and privileges as a group.
Any preferences you define for a group are stored in the group account.
XML An extensible markup language, similar to HTML but more formal and more
flexible.
252 Glossary
Index
Index
A AFP (Apple Filing Protocol)
access encrypting files 126
CDs and DVDs 184 hosting home folders 36
to disk and server icons 166 setting up share points using 105
to folders 169 Apple menu 154
to group share point 177 Apple Remote Desktop 136
hard drives and disks 184 Applications preferences
to iDisks 168 about 148
to media 183 denying access 149
to menu items (Restart, Shut Down) 170 helper applications 149
network home folder 177 providing access 148
POSIX and GUIDs 27 UNIX, access to 150
to remote servers 168 authenticating 41
access settings automatic logout 180
about 97
allowing access 98 B
restricting access 97 backup
accounts administrator accounts 48
See also user accounts, group accounts, computer directory domain 48
lists basic settings
batch editing 47 defining short names 58
finding specific 46 defining user names 57
mobile accounts 115 overview 57
overview 22 battery status 163
refreshing the list of 45 Burn Disc command 169
searching 46
sorting 46 C
ACEs (access control lists) 240 Classic preferences
ACLs (access control lists) about 151
about 27 access to Apple menu 154
GUIDs 239 Classic startup 152
nested groups 81 consistent preferences 155
restricting access 125 restarting and rebuilding 153
administrator accounts System Folder 152
determining requirements 37 Classic System Folder 152
directory domain 23, 37, 40 client management
local 22 about 127
overview 22 managing preferences 143
privileges 62 comments
server 22 for computer lists 92
administrator computer editing 66
overview 30 computer address 90
setting up 40 computer lists
253
about 89 Finder preferences
adding computers to 94 about 164
All Computers list 90 desktop appearance 170
creating 92 displaying disks and servers 166
deleting 96 filename extensions 167
Guest Computers 90 Finder window behavior 166
moving computers 95 Finder window contents 171
overview 25 folder access 169
preexisting 89, 90 hiding Burn Disc 169
preference management 146 hiding Trash alert 167
presets 93 iDisk 168
removing computers from 95 preventing disk ejection 168
searching for 96 remote servers 168
using a preset 93 removing Restart and Shut Down 170
for Windows computers 90 Simple Finder 165
Windows Computers list 90 Finder windows 171
computers finding accounts
See also computer lists accounts list 43
editing information about 95 available directory domains 45
local directory domain 44
D search policy 44
desktop appearance 170
DHCP (Dynamic Host Configuration Protocol) 223 G
DNS (Domain Name System) 222 globe 42
Dock preferences group accounts
about 156 about 77
adding items 158 adding users to 68, 83
basic control 157 creating 79
controlling modification 159 defining IDs for 85
group folders 157 deleting 82
dsimport tool 234 editing 80
legacy 81
E member settings 83
ejecting disks naming 84
automatic 185 nested 81
prevention 168 overview 24
email preferences 173 predefined 78
Energy Saver preferences preference management 145
about 160 presets 80
automatic startup 163 primary group 67
battery status 163 read-only 82
portable computers 161 removing users from 68, 84
sleep 160 reviewing membership 69
exporting account information storage 78
about 231 group folders
AppleShare IP XML files 235 about 128
character-delimited files 236 Dock preferences 157
limitations 232 in an existing share point 86
Server Admin XML files 234 in a share point subfolder 86
using GUIDs 242 making accessible to multiple groups 88
with Workgroup Manager 43, 232, 233 overview 25
setting up 86
F specifying no group folder 86
Fast User Switching 179 group settings 67
filename extensions 167 guest computers
254 Index
about 25 email 173
portable computers 122 web browser 173
working with 91
guest users 24 K
GUIDs (globally unique identifiers) Keyboard preferences 201
about 239 keywords
ACLs 240 applying 66
duplicate names 59 master list, editing 65
file permissions 241
group membership 241 L
importing and exporting 241 lock 42
maintaining when importing 242 Login preferences
SIDs 241 about 174
synchronization 241 automatically opening items 176
using for importing and exporting 242 automatic logout 180
viewing 243 enabling scripts 181
group share point 177
H login window 175
Hearing preferences 200 network home folder 177
help 15 password hints 179
home folders preventing restart and shut down 178
about 101 running scripts 182
across multiple servers 103 simultaneous multiple users 179
AFP 105 login settings 63
creating for local users 108
custom 110 M
default 113 Macintosh Manager 41
deleting 113 mail settings
distribution 36 disabling service 71
having none 107 enabling service 70
Mac OS X clients 102 forwarding 71
moving 113 overview 69
network 109, 128 managed preferences
NFS 106 See also preference management
other clients 103 about 143
proliferation 119 caching 142
setting disk quotas for 113 interaction 139
setting up 101 permanence 141
structure 35 Media Access preferences
for Windows computers 102 about 183
automatic ejection 185
I CDs and DVDs 184
importing account information hard drives and disks 184
about 231 mobile accounts
AppleShare IP XML files 235 about 115
character-delimited files 236 advantages 117
dsimport tool 234 alternatives 122
limitations 232 creating 186
maintaining GUIDs 242 disadvantages 119
Server Admin XML files 234 logging in 116
using GUIDs 242 network accounts 118
with Workgroup Manager 43, 232 portable home directories 116
info settings 74 preventing creation 187
Internet preferences removing 188
about 172 setting up 121
Index 255
synchronization frequency 190 renaming 210
synchronizing 120 types 208
synchronizing folders 189 update rate 219
mobile clients NFS (Network File System)
security 124 setting up share points using 106
without mobile accounts 122 UNIX servers 36
Mobility preferences NTP (Network Time Protocol) 221
about 186
creating mobile accounts 186 O
preventing mobile account creation 187 Open Directory
removing mobile accounts 188 account storage 49
synchronization frequency 190 archiving 232
synchronizing folders 189 server setup 30
Mouse preferences 201
P
N password options 61, 64
NetBoot passwords
images 129 hints 179
overview 21 importing and exporting 232
starting up computers 135 unable to modify 224
Network Install password type 64
images 129 PDC (Primary Domain Controller) 31
installing software 135 permissions
overview 21 AFP 24
Network preferences anonymous users 54
about 191 groups 83
bypassing proxy servers 192 portable computers
proxy server ports 191 configuring 121
network traffic Energy Saver settings for 161
reducing 118 multiple local accounts 123
synchronizing 121 one primary local user 123
network views unknown 122
about 13, 208 portable home directories
adding clients 217 about 13, 116
adding computers 212 synchronizing 120, 189, 190, 241
adding dynamic lists 215 POSIX 240
adding neighborhoods 211 preference editor
computer 208 about 14, 142, 203
creating 209 adding applications 204
Default view 208 disabling management 206
deleting 211 editing application preferences 204
deleting computers 214 preference management
deleting dynamic lists 215 Applications preferences 148–151
deleting neighborhoods 212 cache 143, 144
disabling visibility 219 Classic preferences 151–156
dynamic list 208 computer lists 146
editing computers 214 customizing the user experience 129
enabling or disabling 211 disabling 147
Finder behavior 220 Dock example 130
finding 216 Dock preferences 156–159
named view 208 editing multiple records 147
naming 217 Energy Saver preferences 160–164
neighborhood 208 Finder preferences 164–172
Public view 208 group accounts 145
removing clients 218 icon indicator 143
256 Index
Internet preferences 172–174 FileVault 126
login example 131 preventing access 125
Login preferences 174–183 Seeing preferences 199
Media Access preferences 183–185 Server Admin
Mobility preferences 186–190 overview 20
Network preferences 191–192 setup overview 29
Printing preferences 193–196 share points
Software Update 196 AFP 105
System Preferences 197 local 104
Universal Access preferences 198–202 NFS 106
user accounts 145 overview 31
workflow example 134 working with 43
preference manifest 14, 203 SIDs (security identifiers) 241
preferences cache Simple Finder 165
about 143 sleep settings 160
updating 144 Software Update preferences 196
presets startup and shutdown settings 163
about 47 strategies
computer lists 93 duplicate names 59
creating 55 home folder distribution 36
deleting 56 home folder structure 35
editing 56 mobile accounts 117
for group accounts 80 NetBoot and Network Install 135
renaming 56 planning 33
using 55 preference management 134
Printing preferences security 125
about 193 service allocation 34
access to printers 193, 194 share points 34
default printer 195 short names 59
preventing printer list modification 194 synchronizing 120
restricting access 195 System Preferences 197
print settings
deleting print quota 73 T
disabling queue access 73 troubleshooting 221–230
enabling queue access 72 adding printers 228
overview 72 administrator privileges 225
resetting queue 73 authentication 225
privileges common network issues 221
directory domain administrator 62 DHCP 223
server administrator 62 DNS 222
Dock question mark icon 230
R duplicate Dock items 229
record description 236 home folders 227
requirements LDAP 224
directory services 33 logging in 225
server and storage 34 login items 229
login window 224
S login workgroup list 228
scripts mail settings 227
enabling 181 missing Dock items 229
running 182 NTP 221
search policy 44 Open Directory password 224, 225
security opening files 228
about 124 passwords 227
directory services 126 Password Server 226
Index 257
shared directory domain 226 predefined 50
unexpected error message 230 preference management 145
users and groups 224 primary group 67
web settings 227 read-only 53
storage 49
U user IDs 60
Universal Access preferences user information
about 198 about 14
assistive devices 202 editing 74
Hearing preferences 200
Keyboard preferences 200 W
Mouse preferences 201 web browser preferences 173
Seeing preferences 199 Windows computers
shortcuts 202 configuration 30
UNIX home folders 102
controlling access to UNIX tools 150 PDC 31
and GUIDs 27 Windows Computers list 90
home folders 36 Workgroup Manager 75
upgrading 41 Workgroup Manager
user accounts accessing accounts 43
batch editing 52 batch editing 147
comments 66 exporting users and groups 233
creating 51 importing users and groups 232
deleting 54 managed preferences 138
disabling 54 overview 19
editing 52, 53 using 42
guest users 54 workgroups
keywords 66 See also group accounts
local 98 overview 24
overview 23, 49
258 Index