MacOS Admin

Centrify Suite
Mac OS X Administrators Guide

November 2011
Centrify Corporation
Legal notice
This document and the software described in this document are furnished under and are subject to the terms of a license agreement or a non-disclosure agreement. Except as expressly set forth in such license agreement or non-disclosure agreement, Centrify Corporation provides this document and the software described in this document as is without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Some states do not allow disclaimers of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of Centrify Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of Centrify Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. Centrify Corporation may make improvements in or changes to the software described in this document at any time. 2004-2011 Centrify Corporation. All rights reserved. Portions of Centrify DirectControl are derived from third party or open source software. Copyright and legal notices for these sources are listed separately in the Acknowledgements.txt file included with the software. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the governments rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement. Centrify, DirectAudit, DirectControl and DirectSecure are registered trademarks and DirectAuthorize and DirectManage are trademarks of Centrify Corporation in the United States and other countries. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Centrify Suite is protected by U.S. Patents 8,024,360 and 7,591,005. The names of any other companies and products mentioned in this document may be the trademarks or registered trademarks of their respective owners. Unless otherwise noted, all of the names used as examples of companies, organizations, domain names, people and events herein are fictitious. No association with any real company, organization, domain name, person, or event is intended or should be inferred.
Contents
About this guide
7
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Using this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Conventions used in this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Where to go for more information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Contacting Centrify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 1
Installing the Centrify DirectControl Agent for Mac OS X
11
Preparing for installation on Mac OS X computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installing the Centrify DirectControl Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Logging on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2
Creating home directories
17
Understanding home directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Configuring a local home directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Configuring a network home directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Configuring a portable home directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 3
Working with Mac OS X
29
Specifying the Macintosh users home directory location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Setting shared directory permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Enabling access to SMB shares on a Windows server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Enabling users to manage their print queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Setting up authenticated printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Setting up local and remote administrative privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Querying user information for Active Directory users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Migrating from Open Directory to Centrify DirectControl Active Directory. . . . . . . . . . . . . . . . . . . . 47 Converting a local user to a Centrify DirectControl Active Directory user . . . . . . . . . . . . . . . . . . . . . 49 Migrating a user from Apples Active Directory plugin to Centrify DirectControl Active Directory . . 50 Mapping local user accounts to Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring 802.1X wireless authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 4
Understanding group policies for Mac OS X users and computers
59
Understanding group policies and system preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Installing Mac OS X group policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Setting Mac OS X group policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Applying standard Windows policies to Mac OS X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configuring Mac OS X-specific parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 5
Setting computer-based policies for Mac OS X
72
Setting computer-based policies for Mac OS X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Map /home to /Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 802.1X Wireless Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 App Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 EnergySaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Internet Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Remote Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Scripts (Login/Logout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Software Update Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Chapter 6
Setting user-based policies for Mac OS X
110
Setting user-based policies for Mac OS X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 802.1X Wireless Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Application Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Automount Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Desktop Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Dock Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Finder Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Folder Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Import Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Login Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Administrators Guide
Media Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Mobility Synchronization Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Scripts (Login/Logout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 System Preference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Chapter 7
Configuring a Mac OS X computer for smart card login
191
Understanding smart card login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Configuring smart card login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Using smart card login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Troubleshooting smart card log in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Chapter 8
Troubleshooting tips
199
Using common account management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Enabling logging for the Centrify DirectControl Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Enabling logging for the Mac Directory Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Using DirectControl on a dual-boot system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Using adgpupdate appropriately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Understanding delays when logging on the first time with a new user account. . . . . . . . . . . . . . 203 Understanding delays logging on when a computer is disconnected from the network . . . . . . 203 Configuring single-sign on to work with non-Mac OS X machines . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Restricting login using FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Logging on using localhost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Changing the password for Active Directory users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Logging in if Directory Service or Security Agent crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Disabling Apples built-in Active Directory plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Showing the correct status of the Centrify DirectControl plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Opening a support case online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Collecting information for support cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Chapter 9
Using sctool
213
Displaying usage information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Understanding sctool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Appendix A
Installing and removing DirectControl and joining and leaving a domain
217
Installing using the install.sh command-line program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Contents
Installing remotely using Apple Remote Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Removing Centrify DirectControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Joining an Active Directory domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Leaving an Active Directory domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Viewing the results from joining or leaving a domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Index
230
About this guide

CentrifyTM DirectControlTM delivers secure access control and centralized identity management by seamlessly integrating UNIX, Linux, and Mac OS X computers, and J2EE and web platforms with Microsoft Active Directory. With DirectControl, organizations can improve IT efficiency, better comply with regulatory requirements, and move toward a more secure, connected infrastructure for their heterogeneous computing environment.
Intended audience
This Administrators Guide provides information for managing users, groups, computers, and zones with Centrify DirectControl for Mac OS X system administrators. The focus of this guide is two fold: It provides installation instructions and step-by-step instructions for configuring Mac OS X machines to join an Active Directory domain through Auto Zone, which essentially creates one large zone for all Mac OS X computers. Auto Zone requires minimal configuration and is appropriate for most Mac OS X environments. If your environment is larger, or more complex, and doesnt easily fit into Auto Zone, you must consult the DirectControl Planning and Deployment Guide for detailed information on how to move your Mac OS X users and machines to Active Directory and use DirectControl zones to structure your environment.
It also explains how to handle issues and tasks that are specific or unique to a Mac OS X environment.
This guide does not, however, cover planning or Centrify DirectControl tasks handled through the Centrify DirectControl Administrator Console. For more information about these topics, see the appropriate Centrify DirectControl guide. This guide assumes you have a working knowledge of performing administrative tasks in a Mac OS X environment.
Using this guide

Depending on your environment and role as a Centrify DirectControl administrator or user, you may want to read portions of this guide selectively. The guide provides the following information: Chapter 1, Installing the Centrify DirectControl Agent for Mac OS X, describes the steps for installing Centrify DirectControl.
Conventions used in this guide
Chapter 2, Creating home directories, describes how to create local home, network home, and portable home directories on Mac OS X computers. Chapter 3, Working with Mac OS X, describes common tasks and issues that are specific to Centrify DirectControl running in the Mac OS X environment. Chapter 4, Understanding group policies for Mac OS X users and computers, provides an overview to using the Centrify DirectControl group policies for Mac OS X computers and users. Chapter 5, Setting computer-based policies for Mac OS X, describes the Centrify DirectControl group policies for Mac OS X computers. Chapter 6, Setting user-based policies for Mac OS X, describes the Centrify DirectControl group policies for Mac OS X users. Chapter 7, Configuring a Mac OS X computer for smart card login, describes how to configure smart card login for Mac OS X computers. Chapter 8, Troubleshooting tips, describes how to solve some common issues when using Centrify DirectControl on Mac OS X Computers. Chapter 9, Using sctool, provides a reference to the sctool command. Appendix A, Installing and removing DirectControl and joining and leaving a domain, describes other methods of installing DirectControl besides the standard method using the package installer (DMG file).
In addition to these chapters, an index is provided for your reference.
Conventions used in this guide

The following conventions are used in this guide: Fixed-width font is used for sample code, program names, program output, file names, and commands that you type at the command line. When italicized, the fixed-width font is used to indicate variables. In addition, in command line reference information, square brackets ([ ]) indicate optional arguments.
Bold text is used to emphasize commands, buttons, or user interface text, and to introduce new terms. Italics are used for book titles and to emphasize specific words or terms. The variable release is used in place of a specific release number in the file names for individual Centrify DirectControl software packages. For example, centrifydc-releasemac10.7-x86_64.tgz in this guide refers to the specific release of the Centrify DirectControl Agent for Intel-based Mac machines running Mac OS X 10.7 or later, available on the Centrify DirectControl CD or in a Centrify DirectControl download package. On the CD or in the download package, the file name indicates the Centrify
Where to go for more information
DirectControl version number. For example, if the software package installs Centrify DirectControl version number 5.0.1, the full file name is centrifydc-5.0.1-mac10.7x86_64.tgz.
Where to go for more information

The Centrify DirectControl documentation set includes several sources of information. Depending on your interests, you may want to explore some or all of these sources further: Centrify DirectControl Release Notes provides the most up-to-date information about the current release, including system requirements and supported platforms, and any additional information, specific to this release, that may not be included in other Centrify DirectControl documentation.
Centrify DirectControl Quick Start provides a brief summary of the steps for installing Centrify DirectControl and getting started so you can begin working with the product right away. For more detailed information about installing Centrify DirectControl, see the Centrify DirectControl Planning and Installation Guide. Centrify DirectControl Evaluation Guide provides information to help you set up an evaluation environment and use Centrify DirectControl to test typical authentication and authorization scenarios, such as resetting user passwords for UNIX computers, preventing a user from accessing unauthorized UNIX computers, or enforcing specific lockout policies when users attempt to log on to UNIX computers using Centrify DirectControl. Centrify DirectControl Planning and Deployment Guide provides guidelines, strategies, and best practices to help you plan for and deploy Centrify DirectControl in a production environment.This guide covers issues you should consider in planning a Centrify DirectControl deployment project. This guide should be used in conjunction with the information covered in the Administrators Guide. Centrify DirectControl Administrators Guide describes how to perform administrative tasks using the Centrify DirectControl Administrator Console and command line programs to help you use Centrify DirectControl to manage UNIX computers, users, groups, and zones through Active Directory. Centrify DirectControl Group Policy Guide describes the Centrify DirectControl group policies you can use to customize user-based and computer-based configuration settings. Centrify DirectControl Configuration Parameters Reference Guide provides reference information for the Centrify DirectControl configuration parameters that enable you to customize your environment. Centrify DirectControl Authentication Guide for Apache describes how to use Centrify DirectControl with Apache servers and applications to provide authentication and authorization services through Active Directory. If you are using Centrify DirectControl
About this guide
Contacting Centrify
with Apache, you should refer to this supplemental documentation for details about how to configure your Apache server to use Centrify DirectControl and Active Directory.
Centrify DirectControl Authentication Guide for Java Applications describes how to use Centrify DirectControl with J2EE applications to provide authentication and authorization services through Active Directory. If you are using Centrify DirectControl with Java servlets, such as Tomcat, JBoss, WebLogic, or WebSphere, you should refer to this supplemental documentation for details about how to configure your applications to use Centrify DirectControl and Active Directory. Individual UNIX man pages for command reference information for Centrify DirectControl UNIX command line programs.
In addition to the Centrify DirectControl documentation, you may want to consult the documentation for your Windows or Mac OS X operating system, or the documentation for Microsoft Active Directory. This information can help you get the most out of Centrify DirectControl.
Contacting Centrify
If you have questions or comments, we look forward to hearing from you. For information about contacting Centrify with questions or suggestions, visit our Web site at www.centrify.com. From the Web site, you can get the latest news and information about Centrify products, support, services, and upcoming events. For information about purchasing or evaluating Centrify products, send email to [email protected].
10
Chapter 1
Installing the Centrify DirectControl Agent for Mac OS X

This chapter provides step-by-step instructions for installing the Centrify DirectControl Agent on a Mac OS X computer. The following topics are covered: Preparing for installation on Mac OS X computers
Installing the Centrify DirectControl Agent Logging on
Preparing for installation on Mac OS X computers

The Centrify DirectControl Agent needs to be installed on each computer you want to manage through Centrify DirectControl and Active Directory. You can check the Centrify DirectControl Release Notes included with the software, or visit the Centrify Web site (scroll to Supported Platforms and click the Details tab) to verify that each computer where you plan to install is running a supported version of the mac os x operating system. The installation package also contains a utility, ADCheck, which verifies that each of your Mac OS X machines is ready for installation of the DirectControl Agent. ADCheck confirms that a machine is running a supported OS, has sufficient disk space to install the DirectControl Agent, and that the domain you intend to join has functioning domain controllers and DNS servers. Information about running ADCheck is included in the installation instructions.
Note
Before installing the DirectControl Agent on your Mac OS X computers, be certain that the Centrify Suite has been installed on a Windows computer in the domain. Centrify Suite includes the DirectControl Administrator Console, which is the primary management console for performing ongoing Centrify Suite operations, including the application of group policies. Always install this console unless you are installing and running Centrify Suite Express Edition, which does not contain a Console component. For information about other Centrify Suite components, such as DirectManage Deployment Manager and Zone Provisioning Agent, which are useful in mid-size to large deployments, see the Centrify Suite Planning and Deployment Guide and the Centrify Suite Administrators Guide.
11
Installing the Centrify DirectControl Agent
Deciding when and how to join a domain

Following installation, you will be prompted to join a domain. Whether to join a domain depends primarily on how you intend to join. DirectControl provides two ways to join a domain: Through Auto Zone, which is the recommended method for installations with 1500 or fewer users. When joined through Auto Zone, all users and groups defined in Active Directory for the forest as well as all Active Directory users defined in a forest with a two-way, cross-forest trust relationship to the forest of the joined domain automatically become valid users and groups on the Mac OS X machine.
By connecting to a specific DirectControl zone, which is the recommended method for installations with 1500 or more users, or for installations in which fine-tuned access control is needed. A zone is similar to an Active Directory organizational unit (OU) and allows you to organize the computers in your organization in meaningful ways to simplify account and access management and the migration of information from existing sources to Active Directory.
The assumption of this guide is that you are joining Auto Zone. After installation, you can follow the instructions to join the domain and with a few configuration steps all of your Active Directory users will be able to log into this machine.
Note If you have a set of Apple Open Directory users, you should migrate them following installation but before joining a domain.
On the other hand, if your environment requires a zone structure you must create that structure before joining a domain. Therefore, after installing DirectControl, consult the Centrify Suite Planning and Deployment Guide and the Centrify Suite Administrators Guide, which explain in detail how to plan, create, and maintain an Active Directory installation of nonWindows machines with Centrify DirectControl.

The Centrify DirectControl Agent for Mac OS X computers can be installed in several different ways. The procedure in this section shows how do so by double-clicking the Centrify DirectControl Installer package (DMG) and following the instructions displayed on the screen. This installation method is recommended for most users when installing on a single computer or a limited number of computers. When you use the Centrify DirectControl package installer, you will be prompted to join the domain. You may also join the domain after installation using either the adjoin command-line program or the Centrify DirectControl Directory Access plug-in. Centrify DirectControl provides a number of other ways to install the DirectControl Agent:
12
By executing the Centrify DirectControl installation script, install.sh in a Terminal window on a Mac OS X machine and following the instructions displayed by the script. If you are an experienced UNIX administrator and are familiar with UNIX command-line installations, running install.sh is a good method to use. When you install using the install.sh script, you can automatically join an Active Directory domain as part of the installation process; see Installing using the install.sh command-line program on page 218 for details.
By installing remotely, without user interaction, using Apple Remote Desktop. This is a good method to use if you are generally using Apple Remote Desktop for software distribution. With Apple Remote Desktop you can add pre- and post-installation scripts that allow you to join the remote computer to a domain after installation; see Installing remotely using Apple Remote Desktop on page 219 for details. By installing remotely with the DirectManage Deployment Manager. Deployment Manager runs as a Windows Console and allows you to analyze a non-Windows machine, download the appropriate version of the DirectControl Agent from the Centrify Download Center, and install it on the target machine. This installation method is recommended for larger installations in which you must install the Agent on multiple Mac OS X machines. See the Planning and Deployment Guide and the Deployment Manager Administrators Guide for more information.
To install the Centrify DirectControl Agent on a Mac OS X computer using the graphical user interface:
Before installing the Centrify DirectControl Agent, disable Apples built-in Active Directory plug-in, and remove Active Directory from the Authentication, and Contacts search paths. For more information, see Disabling Apples built-in Active Directory plug-in on page 209.
Notes
In addition, be certain that the Apple Directory Utility is closed.

1 Log on with the Administrator account. 2 Navigate to the directory on the CD or your local network where the Centrify
DirectControl Agent package is located. For example, if you are installing from the Centrify DirectControl CD, open the MacOS directory.
3 Double-click the DMG file, for example:
centrifydc-release-mac10.7-x86_64.dmg
4 Double-click ADCheck to open the ADCheck utility.
ADCheck
performs a set of operating system, network, and Active Directory checks to
Chapter 1 Installing the Centrify DirectControl Agent for Mac OS X
13
verify that the Mac OS X computer meets the system requirements necessary to install the Centrify DirectControl Agent and join an Active Directory domain.
5 Enter the domain you intend to join with the Mac OS X computer and click AD Check;
for example:
6 Review the results of the checks performed. If the target computer, DNS environment,
and Active Directory configuration pass all checks with no warnings or errors, you should be able to perform a successful installation and join the specified domain. If you receive errors or warnings, correct them before proceeding with the installation; see the DirectControl Administrators Guide for more information about ADCheck.
7 Double-click the CentrifyDC package to open the Installer:
8 Review the information in the Welcome page, then click Continue. 9 Review or print the terms of the license agreement, then click Continue; click Agree
to agree to the terms of the license agreement. Then click Install (note that you cannot change the volume on which DirectControl is installed it must be on the same volume as Mac OS X).
10 If prompted, enter the administrator name and password, and click Install Software to
begin installing the Centrify DirectControl Agent.
If you see the following warning box, click OK. If you did not have Directory Utility running during the installation, you can ignore the warning. If Directory Utility was open, you can quit and restart it to show the correct status of the Centrify DirectControl
14
plug-in.
11 You will be prompted to join the domain. You can choose to do so now or manually after
completing installation. To join now, enter a domain name and select the Auto Zone option, which is appropriate for most Mac OS X environments.
Note
If you know that you want to use DirectControl zones in your environment, exit the installer now. Obviously, you must create zones first, before you can join to one. Start with the Planning and Deployment Guide, which provides detailed information about migrating your existing users and computers to DirectControl Active Directory.
Note
You can click Show log to see the installer log.
12 Click Join Domain and enter the Active Directory password for the domain when
prompted.
13 Click Close to close the installer.
Chapter 1 Installing the Centrify DirectControl Agent for Mac OS X
15
Logging on
Logging on
When using Auto Zone, all Active Directory users in the domain become valid users on a joined machine. To verify that DirectControl is working properly, you can simply log into the Mac OS X machine by using an Active Directory account. On the Mac OS X login screen, select Other and enter an AD username and password:
16
Chapter 2
Creating home directories

This chapter explains how to create different types of home directories for a Mac OS X machine. The following topics are covered: Understanding home directories
Configuring a local home directory Configuring a network home directory Configuring a portable home directory
17
Understanding home directories
Understanding home directories

Whenever an Active Directory user logs in to a Mac OS X machine, a home directory is created for the user. Mac OS X provides three possible styles of home directory, which can be configured by an administrator to fit the type of user who will be using the machine, the type of machine, and the use to which the machine will be put. Auto Zone supports each of these styles: Local home directory The users home directory is created on the local machine in the Users folder with the users login name (/Users/username).
Network shared directory The users home directory is created on a network share. Portable home directory The users home directory is created on a network share and copied and synchronized to the local machine.
When you join a machine to a domain by connecting to Auto Zone, the home directory is created based on the following: Active Directory user settings; for example, an administrator can specify a network home directory in the Profile for an Active Directory user.
Auto Zone default values; by default, Auto Zone is configured to support the creation of home directories in the Users folder on the local machine. Auto Zone parameters set in the Centrify configuration file, /etc/centrifydc/centrifydc.conf by an administrator or by a group policy. See the Centrify DirectControl Configuration Parameters Reference Guide for a description of all Auto Zone parameters.
The following sections explain in detail how to set up each type of user home directory.
Configuring a local home directory

In general, you do not need to explicitly configure local home directories for your Active Directory users because Auto Zone is configured to work for Active Directory users exactly as if they were local users. That is, by default, an Active Directory user who logs in to a Mac OS X machine that is joined to a domain through Auto Zone is given a local home directory at /Users/username. For example, for a user, Glen Morris, whose login name is gmorris, the Mac OS X local home directory is set to: /Users/gmorris. Although it generally isnt necessary to explicitly configure DirectControl for local home directories, in some situations you might want to do so. For example, if a Windows user has a local home directories defined in their Active Directory profile, that home directory will be assigned when the user attempts to log in and may prevent the user from logging in. DirectControl provides a configuration parameter (auto.schema.use.adhomedir)that you can set to ignore home directories in an Active Directory profile and always set the home directory to the default (/Users/username).
18
Configuring a network home directory
To explicitly configure a machine for local home directories: 1 On the Mac OS X machine, edit the DirectControl configuration file,
/etc/centrifydc/centrifydc.conf.
2 Add the following two parameters:

auto.schema.use.adhomedir: false auto.schema.homedir: /Users/%{user}
Setting auto.schema.use.adhomedir to false configures the local machine to ignore any home directories that are set for users in Active Directory. This parameter is set to true by default. Setting auto.schema.homedir: /Users/%{user} configures the local machine to set the home directory to /Users/username, where username is the user logon name defined in the users Active Directory account. Note that this parameter is set to this value by default on all Mac OS X machines.
Note
If you plan to configure network-home or portable-home directories for this machine, you must set auto.schema.use.adhomedir to true, the default value, otherwise, DirectControl will ignore the network home directories that you specify for users in Active Directory.
3 Save and close the file.

For each user whom you want to have a network home directory, you must specify the location in Active Directory. If you plan to use portable home (mobile home) directories, you must first create network home directories as explained in this procedure.
Configuring a network home directory for a user connected to Auto Zone: 1 Create a network share to host the home directory.
For example, on the dc-demo server (acme.com domain), create a network share called MacUsers. You must assign appropriate permissions to the network shared directory so the Active Directory account is able to write to the users home directory. One way to do this is to assign read/write permissions to Authenticated Users on the network share. Each home directory that is created inherits permission from the network share so the account of the logged-in user is granted write permission its network home directory. See Setting shared directory permissions for more details about properly setting and find-tuning network share permissions.
2 On a domain controller in the forest to which the Mac OS machine is joined, open Active
Directory Users and Computers.
Chapter 2 Creating home directories
19
3 Select Users, select the user, then right-click the user and click Properties. 4 Click the Profile tab, then under Home folder select Connect.
5 In Connect...To type the location of the share you created in Step 1 by using the
following format:
//Server/share/path
For example:
//dc-demo.acme.com/MacUsers/rdavis
6 Click OK to save the user profile. 7 (Optionally) By default, Centrify DirectControl is configured to use the Active Directory
home folder if one is specified in a users profile. However, to be explicit, you can edit the DirectControl configuration file and add the following parameter:
auto.schema.use.adhomedir: true
Save and close the file. If you are running Mac OS X 10.5.1 or 10.5.2, Microsoft Windows group policies may prevent access to SMB shares. Follow the steps in Enabling access to SMB shares on a Windows server on page 36 to verify that these group policies are not enabled or to disable them if they are. If you are running Mac OS X 10.5.3 or later, the Windows policies do not prevent access so you can skip this procedure.
Note
8 Specify the type of share to mount for the network home directory on the Mac OS X
machine, SMB, or AFP. By default, the Mac OS X machine will attempt to mount an SMB share for the network home. If you specified an AFP share, you must set the following parameter in the
20
Configuring a portable home directory
DirectControl configuration file:

auto.schema.remote.file.service:AFP
Or enable the Computer Configuration > Centrify Settings > DirectControl Settings > Adclient Settings > Auto Zone remote file service group policy to specify SMB (the default) or AFP for all Mac OS X machines.
9 Optionally, if you want the network home directory automatically mounted on the users
machine, enable the following group policy: User Configuration > Centrify Settings > Mac OS X Settings > Automount Settings > Automount users Windows home. When the specified user next logs onto the Mac OS X machine, the home directory will be created on the specified share. On the Mac OS X machine, you should see the server and share under SHARED in the Finder.

After you set up Active Directory users with their home directory on a network share, you can create a mobile local home directory and synchronize that directory with the share defined in their Centrify Profile. You can synchronize to /SMB/, /AFP/, or /Network/Servers (NFS) shares. You use group policies to configure synchronization. These group policies perform the same function as the Mobility preferences that you can manage through Workgroup Manager. The following sections step you through the process of specifying the options for creating mobile accounts, and for specifying the options for synchronizing mobile accounts with the network home directory. Before you begin you should have the following in place: A Group Policy Object that applies to a domain or OU that includes Mac OS X users.
A good understanding of the synchronization rules that you want to apply. The procedures in the following sections explain the group policies and options that you can enable, but you should consult the Mac OS X Server documentation for strategies about which options to apply.
Creating mobile user accounts

To automatically create mobile user accounts: 1 In Active Directory Users and Computers, create or select the Active Directory user
account to work. Click the Profile tab to define a network home for the new user. For example, in the
21
Profile tab select Connect, a drive letter, and a home path, such as \\dcdemo.acme.com\MacUsers\rdavis
where: is the Windows network server, including the domain name is a shared folder on the server rdavis is the users home directory on the server.
dc-demo.acme.com MacUsers
Click OK to save the user information and create the network home directory. This directory must exist for folder synchronization. Only users with their home directory set to a /SMB/ or /AFP/ network share in their Centrify Profile can have a mobile account created and synchronized. Users with a local home directory are not prompted to create a mobile account and will not have one created for them unless you create it manually. For users with their home directory set to /Network/Servers, the shared directory must already exist on the NFS server before users login because DirectControl cannot create the directory automatically at login. If the shared directory exists, DirectControl will synchronize it at login. Therefore, for users whose mobile-home directory is on an NFS share, be certain to create all mobile-user home directories on the network share before users log into the Mac OS X machine.
Note
2 (For NFS shares only) Configure the NFS share as an automount point. Skip this step for
an SMB or AFP share. Go to Configuring an automount point for an NFS share on page 27. After configuring the automount point, return to the current procedure and go to the next step.
3 Set appropriate permissions for the shared directory; see Setting shared directory
permissions on page 32 for details on how to do this.

4 Edit the Group Policy Object that is applied to a domain or organizational unit that
includes Mac OS X users.

5 Open User Configuration Policies > Centrify Settings > Mac OS X Settings >
Mobility Settings > Use version specific settings. Click Enable, then OK. Mobility settings are specific to the version of Mac OS X that you are using. Set this policy so you can use version-specific settings that will exactly match the OS X version that you are running. This example assumes 10.7 settings.
6 Double-click Mac OS X 10.7 Settings to use settings specific to Mac OS X 10.7. If you
are running a different version of OS X, select one of the other folders, such as Mac OS X 10.6 Settings. If your environment contains machines running multiple versions, you need to configure the policies for each version. These group policies correspond to the Mobility preferences you can manage using the Mac OS X Workgroup Manager.
22
7 Double click the Configure mobile account creation group policy. Click Enabled
and select the following options: Create mobile account when user logs in to network account to automatically create a mobile account when the user logs in.
Require confirmation before creating a mobile account option if you want the user to be prompted to confirm the creation of the mobile account.
Click Apply, then click Next Setting to go to the Configure mobile account options policy.
8 In the Configure mobile account options policy, check the following:
Encrypt contents with FileVault to encrypt the mobile home directory using the Mac OS X FileVault system.
Note
FileVault protection can only be applied when a new mobile user is created at login. FileVault protection cannot encrypt an existing mobile-user home directory.
Select one of the computer master password options. The computer master password is a safety feature that allows you to unlock the FileVault disk image if the Active Directory user forgets their password: Use computer master password, if available With this option checked, the mobile account will be created and FileVault protection applied whether or not a computer master password is available. Require computer master password With this option checked, the mobile user account will only be created if a master password is available for the computer.You can create a master password by clicking: System Preferences > Security > FileVault > Set Master Password.
Click OK to apply this group policy and close the properties page. If you want to test the creation of the mobile user account before configuring synchronization rules, you can log on to a Mac OS X computer using the Active Directory
23
user you created or selected in Step 1. When you are prompted to create a mobile account, click Yes. Centrify DirectControl will then create a local copy of the remote network home directory according to the rules you have defined with the group policies in the Synchronization Rules: Background Sync category. After this initial synchronization, when you successfully log on as a valid user, Centrify DirectControl begins synchronizing the files and folders you have defined with the group policies in the Synchronization Rules: Login & Logout Sync category between the local home directory and the network share home directory. For information about defining synchronization rules, items to be synchronized, and the items to skip during background updates, see Configuring background synchronization rules and interval on page 25. For information about defining synchronization rules, items to be synchronized, and the items to skip when users log in and log out, see Configuring login and logout synchronization rules on page 24.
Configuring login and logout synchronization rules

If you enable the creation of mobile accounts, you should use the group policies in the Synchronization Rules: Login & Logout Sync category to define the folders that should be synchronized when users with mobile accounts login and logout. You can also use the Skip these items group polices to define criteria for folders or items that should not be synchronized when mobile users login and logout. To control which items are synchronized when users log in and log out:
1 Open User Configuration > Policies > Centrify Settings > Mac OS X Settings
> Mobility Settings > Synchronization Rules: Login & Logout Sync.
2 Select the Enable/disable login & logout synchronization rules group policy,
right-click, then click Properties.

3 Click Enabled to activate synchronization rules each time users log in and log out.
Select Merge with users settings if you want items selected by the user to be included to the synchronization list. If you select this option, be aware that any items users add locally for synchronization override any settings you make with the Skip these items group policies. Therefore, if you want to enforce restrictions on what to exclude for synchronization, you should uncheck this option. Select Skip preset items if you want to skip a preset list of items in the ~/Library directory and items that start with IMAP- and Mac- in their names.
4 Click Next setting to select the Items that will be synchronized at login and
logout group policy to specify items to be synchronized.

5 Click Enabled, then click Show. 6 Click Add, then type the tilde character (~) to synchronize all items you do not
specifically exclude, then click OK.
24
7 Click OK to close the Show Contents dialog box, then click OK to apply the group policy
settings.
> Mobility Settings > Synchronization Rules: Login & Logout Sync > Skip these items. Use the Skip Items group policies to define the specific items you want to exclude from synchronization. For example, if you want to prevent all of the files and folders contained in the ~/Music, ~/Movies, and ~/Pictures directories from being synchronized to the server, you would do the following:
Enable the Enable/disable login & logout synchronization group policy and uncheck Merge with users settings and Skip preset items. Enable the Items that will be synchronized at login and logout group policy and specify ~ as the path. Enable the Skip items whose partial path matches group policy, then click Add and specify the ~/Music, ~/Movies, and ~/Pictures directories. For example:
Click OK when you are finished adding the items you want to skip. Click OK to close the Show Contents dialog box. You can click Previous Setting or Next Setting to add other items you want to exclude using another criteria.
Using the Skip items whose full path is group policy to specify a directory, such as ~/Music, only prevents items in the specified directory from being synchronized. It does not apply to items in subdirectories of the specified directory. Therefore, you should use the Skip items whose partial path matches group policy to exclude items contained within subdirectories because this policy matches any directory or subdirectory that includes the specified string in its path not just directories whose path matches exactly. For example, to prevent items in ~/Music/Rap and ~/Music/Classical from being synchronized, use Skip items whose partial path matches: ~/Music.
Note
9 Click OK to apply the group policy settings.
Configuring background synchronization rules and interval

If you enable the creation of mobile accounts, you should also use the group policies in the Synchronization Rules: Background Sync category to define the folders that should be synchronized in the background. You can also use the Skip these items group polices to define criteria for folders or items that should not be synchronized. To control which items are synchronized in the background:
25
> Mobility Synchronization Settings > Synchronization Rules: Background Sync.

2 Select the Enable/disable background synchronization rules group policy,
right-click, then click Properties.

3 Click Enabled to activate background synchronization rules. In most cases you should
use the following settings: Uncheck Merge with users settings if you want to prevent users from adding items to the synchronization list and overriding items you do not want to be synchronized. Select Synchronize users home directory to have the home directory automatically synchronized at a regular interval.
Uncheck Skip preset items if you want to explicitly define the items or directories to skip.
4 Click Next Setting to select the Items that will be synchronized in the
background group policy.

5 Click Enabled, then click Show. 6 Click Add, then type the tilde character (~) to synchronize all items you do not
specifically exclude, then click OK.

7 Click OK to close the Show Contents dialog box, then click OK to apply the group policy
settings for the files and folders to be synchronized in the background.

8 Open User Configuration Policies > Centrify Settings > Mac OS X Settings >
Mobility Synchronization Settings > Synchronization Rules: Background Sync > Skip these items. Use the Skip Items group policies to define the specific items you want to exclude from synchronization. For example, if you want to prevent all of the files and folders contained in the ~/Music, ~/Movies, and ~/Pictures directories from being synchronized to the server, you would enable the Skip items whose partial path matches group policy, click Show, then Add, and add the ~/Music, ~/Movies, and ~/Pictures directories, one at a time, to the list of items you want to skip, then click OK to close the Show Contents dialog box. You can click Previous Setting or Next Setting to add other items you want to exclude using another criteria, for example, items that start with a specific string.
9 Click OK to apply the group policy settings for the files and folders to skip during
synchronization.
> Mobility Synchronization Settings > Synchronization Rules: Options.
26
11 Select the Manually/automatically synchronize background folders group
policy, right-click, then click Properties.

12 Click Enabled to activate background synchronization options, then select whether to
synchronize background folders automatically or manually. If you select manually, users should periodically select Sync Now from the Accounts page of System Preferences. If you select automatically to allow items to be synchronized in the background automatically, you should also set the interval for synchronizing background folders. In most cases, you should use the following settings:
Select automatically to have items synchronized automatically in the background at a regular interval. Set the interval in minutes for periodically synchronizing folders in the background. Folders can be synchronized from every 5 to every 60 minutes, but synchronization can only take place if there is a connection to the network. In selecting an interval, you should consider the size and number of files and folders to be synchronized and the level of network traffic.
13 Click OK to apply the group policy settings for synchronizing files and folders in the
background.
Next steps
Configuring an automount point for an NFS share

If you are configuring mobile-home-directory synchronization (Setting shared directory permissions on page 32) for an NFS share, you must configure the NFS share as an automount point (see Step 2 on page 22). This section explains how to do this.
To configure an automount point: 1 With a text editor, create or edit /etc/fstab and add a line similar to one of the
following, depending on how you are configuring the NFS mount:

nfs_server:/nfs_share dummy_mountpoint nfs net 0 0
For example:
rhes.acme.com:/nfsshare/ dmpoint nfs net 0 0
or
nfs_server:/nfs_share dummy_mountpoint url net,automounted,url==nfs://nfs_server:/nfs_share 0 0
For example:
rhes.acme.com:/nfsshare/ dmpoint url net,automounted,url==nfs://192.168.1.70:/nfs_share 0 0
27
You can specify any directory for the mount point as it will be under /Network/Servers in any case.
Note
2 Run the automount command to reload automount settings:

automount -c
If you are configuring automount for NFS as part of setting up a mobile user account, return to Step 3 on page 22 to complete the procedure.
28
Chapter 3
Working with Mac OS X

This chapter describes the unique characteristics or known limitations that are specific to using Centrify DirectControl on a computer with the Apple Macintosh OS X operating environment. The following topics are covered: Specifying the Macintosh users home directory location
Enabling access to SMB shares on a Windows server Enabling users to manage their print queues Setting up authenticated printing Setting up local and remote administrative privileges Querying user information for Active Directory users Migrating from Open Directory to Centrify DirectControl Active Directory Converting a local user to a Centrify DirectControl Active Directory user Migrating a user from Apples Active Directory plugin to Centrify DirectControl Active Directory Mapping local user accounts to Active Directory Configuring 802.1X wireless authentication
Specifying the Macintosh users home directory location

If you configure NFS, SMB, or AFP network file sharing for your Mac OS X computers, you can automatically mount and log on to file shares using Active Directory credentials.
To enable Mac OS X users to log on to file shares when the network is configured with NFS, SMB, or AFP network sharing: 1 Open Active Directory Users and Computers or the Centrify DirectControl
Administrator Console.
2 Select the user account for which you want to enable automounting, right-click, then
click Properties.
3 Click the Centrify Profile tab and set the Home directory path to use one of the
following formats:
to set the users home directory to the default home directory location for all user home directories on Mac OS X computers.
/Users/user_login_name
29
/SMB/server_name/share[/path] to automount a file share on the SMB server_name
you specify. Be certain to use the fully-qualified domain name for server_name, or the IP address. The short name does not work. For example:
/SMB/myHost.acme.com/Users/isuzuki
to automount a file share when you are using Fast User Switching on the SMB server_name you specify. Be certain to use the fully-qualified domain name for server_name, or the IP address. The short name does not work. For example:
/SMB/unix_username/server_name/share[/path] /SMB/isuzuki/myHost.acme.com/Users/isuzuki /AFP/server_name/share[/path]
to automount a file share on the Apple
server_name
you specify.
/AFP/unix_username/server_name/share[/path]
to automount a file share when you are using Fast User Switching on the Apple server_name you specify.
In specifying the remote SMB or AFP file share, you must use the uppercase letters SMB or AFP at the beginning of the path. If you use lowercase letters (smb or afp), automounting fails. If you plan to use Fast User Switching to switch between Active Directory users on the same computer, you should use the /SMB/unix_username/server_name/share[/path] or /AFP/unix_username/server_name/share[/path] format to specify the users home directory to prevent conflicts between users logging on using the same share. If you want to automount a share on an Apple file server using the Apple File Protocol (AFP), however, you must use Centrify DirectControl 3.0.1 or later.
Note
4 In Step 3, if you specified a network directory, make certain that the Active Directory
user logon name (pre-Windows 2000), also known as the samAccountName, matches the Mac OS X login name (UNIX name). Otherwise, the login is not guaranteed to work on all Mac OS X systems. The name must be 8 characters or less because the UNIX name is automatically truncated to 8 characters and wont match if the Active Directory name is longer. The Active Directory name is defined in the Accounts tab. For example, if you open
30
the Properties page for a user and select Account:
Select the Centrify Profile tab to see the UNIX name:
5 For the shared directory you specified in Step 3 (for example, Users), set full
permissions for authenticated users. See the next section, Setting shared directory permissions, for details on how to do this.
6 Verify that the machine on which the shared directory resides is configured on the DNS
server with forward and reverse lookup zones by running the following commands in a terminal window:
nslookup machineName.domainName
Chapter 3 Working with Mac OS X
31
Setting shared directory permissions
for example:
nslookup QA1.acme.com Server: acme.com Address: 192.168.1.139 Name: QA1.acme.com Address: 192.168.1.139
nslookup ipAddress
for example:
nslookup 192.168.1.139 Server: acme.com Address: 192.168.1.139 Name: QA1.acme.com Address: 192.168.1.139
If you get an error message such as

Cant find server name for address 192.168.1.139
it means a reverse lookup zone is not configured for the specified server. To configure DNS forward and reverse lookup zones, see the Microsoft Knowledge base article 323445.

All users who are set up with a network home or portable home directory must have proper permissions to the shared directory in which the home directories are created. Initially, you can provide access to the shared directory through the Windows built-in security group, Authenticated Users. Later on, you can fine tune permissions for this group based on your companys file sharing needs. For example, if an administrator pre-creates home directories for each user before they log in, users only need Read access to the shared directory in order to access their home directories.
32
To set permissions for the shared directory for network home and portable home directories: 1 On the network share machine, select the directory to share (for example, MacUsers).
Right-click, click Properties and click the Sharing tab; then click Advanced Sharing; for example:
2 Make certain that Share this folder is selected. Click Permissions, then click Add:
33
3 Type auth and click OK to return the Authenticated Users group. Select
Authenticated Users, then click Allow for Full Control. Click OK to set permissions for authenticated users, then OK again to close the properties page.
4 Verify that Authenticated Users have proper permissions on the Security tab as well as
on Share Permissions. Ordinarily, this is automatic because the Active Directory Users group, which includes authenticated users, inherits Full Control to the shared folder, but if permissions were altered on the Security tab, and are not sufficient, users may not be able to log in. Click the Security tab and select Authenticated Users (or click Add to add it if it is not already in the Group or user names box).
5 Select Full control and click OK to save and close the Properties page.
Assigning permissions to Authenticated Users on the network home share directory means that each home folder will inherit the proper permissions to allow logged-in users to access their home directories. It also means that every user will have access to every other users home directory. To change this, you can set permissions on the individual home directories. See Limiting users access to other users home folders on page 34 for information about fining tuning permissions for individual users.
Limiting users access to other users home folders
The previous section showed how to assign permissions to the network home shared folder that are inherited by the home folders created in the shared folder. Because permissions are inherited, all each user has equal access to every other users home folder. This section shows how to fine-tune permissions to limit users access to their own home folder.
34
Limiting users access to their own home directory 1 Select the network share you assigned permissions to in the previous section. 2 Select one of the user home directories in the network share. 3 Click the Security tab. Then click Advanced and Change Permissions. Deselect
Include inheritable permissions from the objects parent and click Remove when prompted.
4 Click Add and type users and click Return. Select the following permissions for Users:
Traverse folder / execute file Read Attributes Read Extended Attributes Create files / Write Data Create Folder / Append Data
5 Click OK, and OK again until you have saved all the open dialogs and closed the
Properties page.
Populating the home directory on a network share

If you configure users to automount a network share when they log on, you must determine whether a home directory already exists on the network share for those users. If the individual users home directory does not exist on the network share, Centrify DirectControl creates the home directory automatically the first time the user logs on.
Note For NFS shares, Centrify DirectControl cannot create the home directory on the network share, so you must create the directory before users log in for the first time.
For example, assume you have defined the home directory in a users Centrify Profile as:
/SMB/demo-dc.acme.com/home/thomas
For the server name, be certain to use the fully-qualified domain name, as in the example (demo-dc.acme.com), not the short name (demo-dc).
Note
This indicates that there is an SMB share on the server demo-dc and a shared folder named home on which the user thomas has permission to list folders and create folders. When the zone user thomas logs on for the first time, Centrify DirectControl then creates the new home directory thomas and populates it with the standard Mac OS X files and folders. If the home directory specified in the Centrify Profile for a zone user exists prior to the users first logon, Centrify DirectControl assumes that the directory is valid and contains the appropriate files and does not populate it with additional Mac-specific folders.
35
Enabling access to SMB shares on a Windows server
Defining a home directory in the Active Directory profile

When you are configuring a network home directory for remote Mac OS X users, the home directory is created automatically when users first log on and should not exist prior to that initial log on unless you want to prevent Centrify DirectControl from creating the home directory. Therefore, you should not define a home directory connection point in the Profile properties for new Active Directory users or new mobile user accounts. Instead, you should allow Centrify DirectControl to create and populate the remote home directory. If you need to synchronize a network home directory from a local home directory as part of your migration process, however, the network home directory must exist prior to migration. If you are synchronizing from a local home directory to a remote share, you can create the remote home directory manually or click the Profile tab, and set the connection path. For example:
Set this option if migrating and synchronizing folders

For any Mac OS X users to access SMB shares on a Windows server when running Mac OS X 10.5.2 or earlier, you need to disable the Windows group policies that prevent this access. If you are running Mac OS X 10.5.3 or later, the specified policies do not prevent access so you can skip this section. In Mac OS X versions previous to 10.6.1, Apple supplies an older version of Samba that does not support single-sign on to an SMB share located on a Windows 2008 server. This limitation is documented in Apple bug 6745915, which has been fixed in Mac OS X 10.6.1 by updating the Samba version to one that supports Windows 2008 Server.
Notes
If you have a version of Max OS X prior to 10.6.1, you may work around this issue by saving the credentials in the keychain when you are prompted for the username and password. Users will not be asked again to verify their credentials until they change their password.
36
To check and disable, if necessary, the Windows group policies that prevent access to SMB shares: 1 Open Active Directory Users and Computers, select the domain, right-click, then select
Properties.
2 Click the Group Policy tab.
If the Default Domain Controller Policy is linked to this domain, click Edit, then click Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options, then double-click and disable the following two policies: Microsoft network server: Digitally sign communications (always) Microsoft network server: Digitally sign communications (if client agrees)
If the Default Domain Policy is linked to this domain, click Edit, then click Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options, then double-click and disable the following two policies: Microsoft network server: Digitally sign communications (always) Microsoft network server: Digitally sign communications (if client agrees)
If these group policies are not currently defined, you can leave them not configured. If either policy is enabled and linked to the domain, however, Mac OS X computers will not be able to use SMB connections to automount the Windows file shares.
3 If you change these policies on the domain controller, run the gpupdate command to
refresh the group policies before logging on to Mac OS X computers. You can verify that these group policies are disabled on a server by checking the following registry entries in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ LanManServer\Parameters registry:
EnableSecuritySignature RequireSecuritySignature
Both of these registry keys should have a value of zero (0x00000000). For example:
Check these key values to verify that signing is disables
37
Enabling users to manage their print queues
Enabling users to manage their print queues

On Mac OS X computers, DirectControl Active Directory users are unable to manage their own print jobs. For example, if they attempt to pause, stop, or resume one of their own print jobs, they are prompted to supply the name and password of a user in the Print Operator group, otherwise, they cannot continue. supplies group policies to enable all Mac OS X users who are authenticated through Active Directory to manage their printers. The DirectControl group policy, Map zone groups to local group, gives members of a specified zone group (an AD group, or AD group that has been added to a DirectControl zone) the privileges that belong to members of a local group on the local group. For example, as explained in the following procedure, mapping an AD group to the local _lpoperator and _lpadmin groups, provides members of the AD group with the privileges to manage print jobs on the local Mac OS X machine when they log in.
To map a zone group to local _lpoperator and _lpadmin groups:
This procedure assumes that you will create a specific group (MacPrint) and add the users who you want to manage printers on Mac OS X machines. You could
1 On a Windows machine, open Active Directory Users and Computers, select Users and
right-click and select New > Group.

2 Enter a name for the group, such as MacPrint and select Global and Security. 3 Double-click the group, select the Members tab, then click Add and browse for and
add the AD users who you want to have printing privileges on the Mac OS X machine.
4 Open the DirectControl Console, expand the zone hierarchy and expand the zone
containing Mac OS X machines. Expand UNIX Data, select Groups, then right-click and select Create UNIX Group.
5 Browse for and select the AD group you crated (MacPrint) and click OK to add it to the
zone.
6 Open the Group Policy Management Editor and select the GPO that you use for
Mac OS X machines. Click Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Accounts, then double-click Map zone groups to local group.
7 Click the Policy tab and click Enabled. Click Add and do the following:
a In Local Group, type _lpoperator to add the printer operators group. b In Zone Group: click Browse then search for and select the AD zone group you created (MacPrint), then click OK to map MacPrint to the printer operators group. c Click Add again and in Local Group type _lpadmin to add the printer admin group.
38
Setting up authenticated printing
d In Zone Group: click Browse then search for and select MacPrint again to map MacPrint to the printer admin group.
8 Click OK to save the policy.
The first time a user attempts to manage their printer, for example by pausing the printer, they will be prompted for credentials for a user in the Printer Operator group. They can simply enter their own name and password. Subsequently, they can manage the printer without supplying credentials.

In a Windows Active Directory environment that requires authentication for printing services, Mac OS X users who are already authenticated must provide credentials again when using a Windows network printer. To provide single-sign on when using printers, the DirectControl Agent for Mac OS X computers includes an authenticated printer plug-in that enables users to send print jobs to printers on the Windows network without requiring them to enter credentials again. This plug-in uses the user identifier (UID) of the user printing a job to find the user account to authenticate, then validates the users Kerberos credentials through Active Directory. If the users credentials are not available, the print job will fail.
Understanding printing on Mac OS X

Mac OS X uses the Common UNIX Printing System (CUPS) to manage printing services. Although you can access the CUPS facility directly to manage printers, in general you do not need to do so. Printers are managed through the Print and Scan system preference, which uses the CUPS facility. For example, when you add a printer through Print and Scan, the CUPS facility does the following: Creates a Postscript Printer Description (PPD) file that defines the printer. The file is given the name of the printer and resides in the /etc/cups/ppd directory; for example, /etc/cups/ppd/laserjet2.ppd.
Modifies the CUPS configuration file, /etc/cups/printers.conf, with information about the new printer.
One method to set up authenticated printing for all Mac OS X machines in your environment is to configure an authenticated printer on one (template) machine, then export the CUPS files that define the authenticated printer (printerName.ppd and printers.conf) to each of your Mac OS X machines. As noted, when you configure a printer in the Print and Scan system preference, CUPS creates the PPD and configuration files. You can use group policy to export these files to all your Mac OS X machines. You can also configure printing directly with CUPS commands. To set up authenticated printing for multiple printers you can do the following:
39
To set up authenticated printing using the DirectControl plug-in:
To begin this procedure, identify the printer to configure, including the server that hosts it; for example, HPLaserJet2.@dc01.
1 On the Mac OS X machine that you will use to define an authenticated printer template,
open System Preferences > Print & Scan (Print & Fax on older systems), then click the plus sign (+) and select Add Other Printer or Scanner.
2 Double-click the Advanced icon in the toolbar.
If the Advanced option is not showing, press and hold the Option and Apple keys and right-click in the open area in the toolbar next to the Windows icon and select Customize Toolbar. Drag the Advanced icon to the toolbar and click Done. Then double-click it.
Note
The Advanced option does not appear on Mac OS X 10.5 either. Press and hold the Option and Apple keys and the oval key at the top right of the window. Then drag the Advanced icon to the toolbar and click Done.
3 Scroll in the Type drop-down list and select Windows Printer via Centrify
DirectControl from the list. Note that after you make this selection, the URI scheme in the Device URI window changes to cdcsmb://, which specifies the DirectControl plugin.
4 Type the complete URI specification for the printer in the form:
scheme://hostname/printers/name
for example:
cdcsmb://dc01.acme.com/printers/hplaserjet2
Note
A URI specification does not accept spaces. If the printer name contains spaces, you must replace them with %20 (ASCII code for space); for example, to specify the HP Color LaserJet 4 printer:
cdcsmb://dc01.acme.com/printers/HP%20Color%20LaserJet%204
5 Type a name for the printer; for example HPLaserJetMac.
When you type the URI for the printer, the first part of the name automatically appears in the Name field. You can change that name now. This is the name that will appear in the list of printers in the Print and Scan system preference and in the list of available printers when a user prints a document. It is also the name of the PPD (Postscript Printer Description) file that the CUPS facility creates for each printer that is added to your
40
Printer preferences. Type an optional description in Location to assist users in locating the printer.
6 In the Print Using window, specify the type of the printer, which enables you to
properly manage the printer. For example, if you have drivers installed for the printer, click Select Printer Software and select the appropriate item such as HP Laserjet 4300, then click OK. You can also specify Generic Postscript Printer, or click Other to browse for drivers or printer software. Click the Add button to add the printer to the list of available printers.
7 Repeat this procedure for as many printers as you want to make available for
authenticated printing. You can now use the Copy Files group policy to copy the new printerName.ppd file and updated CUPS configuration file (printers.conf) to the appropriate locations on each of your Mac OS X machines in the domain.
To copy printer files to other machines 1 In the Finder on the Mac OS X template machine, navigate to the /etc/cups directory by
clicking Go > Go to Folder, then type /etc/cups and click Go.

2 Select printers.conf and copy it to the desktop. When prompted, enter your
administrator password to copy the file.

3 Open the ppd folder (/etc/cups/ppd). Select the files for all the authenticated printers
you defined in the previous procedure and copy them to the desktop.
4 On the desktop, change the file permissions for the printers.conf and *.ppd files so you
can copy them to sysvol: a Select the files and click File > Get Info. b For each open dialog box, expand Sharing & Permissions, then click the lock icon and provide administrator credentials for making changes. Set the permissions for everyone to Read only. c Reset the lock and close all the open dialogs.
5 On the Windows domain controller create a sub-directory for the printer file in
SYSVOL. SYSVOL is a well-known shared directory on the domain controller that stores server copies of public files that must be shared throughout the domain. You can use it to copy the printer definition and configuration files to all Mac OS X computers that join the domain. SYSVOL is located at:
41
C:\Windows\SYSVOL\sysvol\domainName\
For example, assuming the domain is acme.com, and using the name MacPrinters for the directory, create the following directory:
C:\Windows\SYSVOL\sysvol\acme.com\MacPrinters
6 On the Mac OS X machine, copy the files from the desktop to SYSVOL on the Windows
domain controller. If you are connected to the domain, you should see the domain controller in the Finder. If the domain controller is not visible in the Finder, connect to it: a Click Go > Connect to Server and select the domain controller. b When prompted select SYSVOL; for example:
c Navigate to the MacPrinters directory you created, for example by clicking acme.com then MacPrinters. d Drag the printer files to MacPrinters.
7 Configure the Copy Files group policy.
a On the Windows domain controller, open the Group Policy Management Editor and select the GPO that is used to manage Mac OS X computers. b Navigate to Computer Configuration > Policies > Common UNIX Settings and double-click Copy Files. c In Copy file policy setting, select Enabled. d Click Add, then Browse. Double-click to open the directory you created for the printer files in Step 5 (for example, MacPrinters). e Select the printers.conf file. Filename now shows MacPrinters/printers.conf. f In Destination, type /etc/cups. This group policy will copy printers.conf to the /etc/cups directory of each machine that joins the domain. g Select Use destination file ownership and permissions. The file will be assigned the default ownership and permissions: owner: root (0)
42
group: lp (26) permission 0600 (rw- --- ---) h Select OK to add the printers.conf file.
8 Click Add again and browse to MacPrinters to add the PPD files.
a Select one of the PPD files you copied to the MacPrinters directory. b In Destination, type /etc/cups/ppd. c Select Use destination file ownership and permissions. The file will be assigned the default ownership and permissions: owner: root (0) group: lp (26) permission 0644 (rw- r-- r--) d Click OK to add the file.
9 Repeat the sub-steps in Step 8 for each of the PPD files that you have defined, then click
OK to enable the policy. This group policy will copy each printerName.ppd file to the /etc/cups/ppd directory of every machine to which the policy applies and that is joined to the domain.
10 Run the adgpupdate command on each target Mac OS X machine to trigger an update of
group policies and execute the new Copy Files policy. By default, group policies are updated automatically every 90 minutes, so you can skip this step and wait for the automatic update if you wish. You should also log out and back in again on each machine to update the printer configuration dialogs.
Removing a printer definition from client machines

This section explains how to remove printer definitions that you created for Mac OS X machines in the domain. It assumes that you set up the Copy Files group policy to add printer definitions to each of your joined Mac OS X machines (as explained in Setting up authenticated printing on page 39).
To remove a printer definition from machines in a domain 1 Identify the name of the PPD file to delete in /etc/cups/ppd; for example,
laserjet4300.ppd.
2 On the Mac OS X template machine (the machine on which you originally defined the
authenticated printer), open System Preferences > Print & Scan. Select the printer to delete, click the minus (-) button, then click Delete Printer. Deleting the printer removes the printer from the list, updates the /etc/cups/printers.conf file by removing the definition of the deleted printer, and removes the printerName.ppd file from the /etc/cups/ppd directory.
43
3 Copy the updated printers.conf file to the desktop and change the permissions to
everyone: Read only.

4 Copy the updated printers.conf file to the SYSVOL and replace the existing file; also
remove the PPD file for the deleted printer. SYSVOL is a well-known shared directory on the domain controller that stores server copies of public files that must be shared throughout the domain. When authenticated printing was set up, the CUPS configuration file, printers.conf was placed in the SYSVOL/acme.com/MacPrinters folder. SYSVOL is located at:
C:\Windows\SYSVOL\sysvol\domainName\
If you are connected to the domain, you should see the domain controller in the Finder. If the domain controller is not visible in the Finder, connect to it: a Click Go > Connect to Server and select the domain controller. b When prompted, select SYSVOL; for example:
c Navigate to the directory you created (domainName/sub-directory), for example by clicking acme.com then MacPrinters. d Drag the printer configuration file to this directory. e Remove the PPD file for the deleted printer.
5 Remove the deleted printerName.ppd file from the Copy Files policy.
a On the Windows domain controller, open the group policy editor and select the policy to edit, such as Default Domain Policy. b Navigate to Computer Configuration > Policies > Common UNIX Settings and double-click Copy Files. c Select the file to delete and click Remove. d Click OK to save the updated policy.
44
Setting up local and remote administrative privileges
6 Configure the Specify commands to run group policy to remove the deleted
printerName.ppd
file from all the Mac OS X machines in the domain. a In the same folder of the group policy editor (Common UNIX Settings), open the Specify commands to run policy and select Enabled. b Click Add. c In Run command, enter a command similar to the following to remove the printerName.ppd file from the /etc/cups/ppd directory on each machine:
rm /etc/cups/ppd/printerName.ppd; for example: rm /etc/cups/ppd/laserjet4300.ppd
d Click OK to save the policy. The next time group policy is updated on machines in the domain (every 90 minutes by default), the following occurs: The Copy Files group policy copies the updated printers.conf file to each machine.
The Specify commands to run group policy removes the specified PPD file on each machine.
Setting up local and remote administrative privileges

Centrify DirectControl provides two group policies to set administrative privileges on the local machine: Map zone groups to local admin groups allows you to specify one or more zone groups to map to the local admin group. Members of the specified group are given administrative privileges on Mac OS X machines managed by DirectControl.
Enable administrator access groups allows users in the zone group ard_admin to access a machine via Apple Remote Desktop with full privileges.
This section shows you how to use these policies together to enable local and remote administrative access to Mac OS X machines. To enable remote and local access for a group:
1 Create an Active Directory group, for example, My_Mac_Admins, and add users who you
want to have administrative privileges.

2 Create an Active Directory group that is a Domain Local Security group. For
convenience, name it ard_admin.

3 Add My_Mac_Admins as a member of ard_admin. 4 Create a DirectControl zone group, My_Mac_Admins and map it to the Active Directory
group My_Mac_Admins.
Note
If the local machine is connected to the domain through Auto Zone, you cannot create a zone group because there are no zones. However, all Active Directory groups
45
Querying user information for Active Directory users
are valid for the joined machine, so you can map any group, such as My_Mac_Admins, to the local admin group, but you need to know the groups UNIX name, which you can retrieve on the local machine, by using the adquery command, as follows
[root]#adquery group -n
For example, the following shows an adquery command and the name it returns:
[root]#adquery group -n |grep -i Mac_Admins my_mac_admins
5 Create a zone group, ard_admin, and map it to the Active Directory group ard_admin.
Note
This zone group must be named ard_admin.
6 In the Group Policy Editor, edit the group policy for the domain, then click Centrify
Settings > Mac OS X Settings > Accounts > Map zone groups to local admin group.
7 Open the policy, select Enable, then click Add. Enter My_Mac_Admins (or the name
retrieved from the adquery
-n
command in Step 4), then click OK.
This step maps My_Mac_Admins to the admin group on the local machine and gives members of My_Mac_Admins all privileges.
8 Click Centrify Settings > Mac OS X Settings > Remote Management > Enable
administrator access groups.

9 Open the policy and select Enable.
This step allows members of ard_admin to access a machine via Apple Remote Desktop with full privileges. In Step 7, you effectively gave members of My_Mac_Admins administrative privileges. Since My_Mac_Admins includes members of ard_admin, members of ard_admin now have full local and remote administrative access.
Querying user information for Active Directory users

When you run commands or use applications that look up user information in the directory, the local Mac OS X directory service is always consulted first before the look-up request is made to Active Directory. If a local user exists with the same name as a UNIX profile name that has been defined for the zone, a lookup request such as id username will return the UID and GID associated with the local user account from the local directory service rather than the information associated with the UNIX profile defined in Active Directory. For example, if you have a UNIX profile in Active Directory for the user mia with the UID of 10024 and the users primary group is mia with the GID of 10024 and the user is also a member of the Active Directory group users and GID of 10001, running the id mia command returns the following information from Active Directory:
uid=10024(mia) gid=10024(mia) groups=10024(mia), 10001(users)
46
Migrating from Open Directory to Centrify DirectControl Active Directory
However, if there is also a local user account with the same user name of mia, but with a UID of 502 and a primary group named mia with a GID of 502, running id mia returns the information for the local user retrieved from the Mac OS X directory service, then any additional group membership information retrieved from Active Directory. For example:
id mia uid=502(mia) gid=502(mia) groups=502(mai), 10001(users)
Because the Mac OS X directory service is queried first, the information for the local user mia takes precedence over the information defined in Active Directory. To avoid retrieving the information for a local user instead of the UNIX profile defined in Active Directory, you should make sure that the UNIX profile user names in Active Directory are different from the local user or disable local user accounts.

If you install Centrify DirectControl in an environment where existing Mac OS X users and computers are managed with Open Directory, you may need to migrate the account information and home directories for those users from the Open Directory environment to Centrify DirectControl Active Directory. Open Directory and Active Directory support three types of users: Local users
Network home users Portable home, or mobile home, users
For example, you may need to migrate existing mobile user accounts from Open Directory to Active Directory or migrate local home directories to a network share. To migrate users with existing mobile accounts from Open Directory to Active Directory:
1 Create a copy of the users local home directory in a temporary location if you have
enough disk space to do so. This copy can serve as a backup to restore the users home directory if you run into any synchronization problems.
2 Log on to the Mac OS X client as an administrator. 3 Disable the LDAP service.
On Mac OS X 10.5 and later, open the Directory Utility and select the Services tab; then deselect LDAPv3 and click Apply. On Mac OS X 10.4 open Applications > Utilities > Directory Access; then deselect LDAPv3 and click Apply.
4 Open a Terminal window and run the following Directory Service command to delete
the users record:

dscl /Local/Default -delete /Users/userName
where userName is a local user; for example, to delete the record for cain:
47
dscl /Local/Default -delete /Users/cain
5 Navigate to the /Users/user_name/Library/Mirrors directory and delete this folder. 6 Join the Mac OS X computer to an Active Directory domain and restart the computer to
shut down and restart services.

7 Create an Active Directory user account for the Open Directory user account, if one does
not already exist. If you are creating a new Active Directory user, use Active Directory Users and Computers to add the user account.
8 Add the Active Directory user to the Mac OS X computers zone and define the Centrify
Profile for the user:
Use the same user name, UID, and GID as the Open Directory user account. You can change this information later with the adfixid program, but for migration you must use the same values. Set the home directory for the user to the appropriate network share using the /SMB/share/path or /AFP/share/path syntax. For example, /SMB/cain/server2003.myDomain.com/Users/cain.
Note
For synchronizing new mobile user accounts, the empty home directory must exist on the network share. If the user home directories are on the same network share as you previously used with Open Directory, logging on with the new Active Directory account should not affect the files available on the share. Because GID values of 0 to 99 are usually reserved for system accounts, you may see a warning message when you save the users profile if the users primary GID value is less than 99.
9 Create a Group Policy Object and link it to an organizational unit that includes the Active
Directory users and enable the following policies: Enable/disable synchronization to create a new mobile account for the users. Enable/disable background synchronization rules to activate background synchronization rules. Items that will be synchronized in the background, then click Show > Add, and type the tilde character (~) to synchronize the home folder. Enable/disable login & logout synchronization rules and Items that will be synchronized at login and logout to activate login and logout synchronization rules.
10 Log on to the Mac OS X computer with the Active Directory or zone user account name
and password to create a mobile account for this user. If prompted to confirm the creation of the a portable home directory, click Yes. If logging in is successful and the mobile account is created, the files and folders you have specified using the User Configuration > Policies > Centrify Settings > Mac OS Settings > Mobility Synchronization Settings > Synchronization Rules: Background Sync group
48
Converting a local user to a Centrify DirectControl Active Directory user
policies are synchronized from the /Users/user_name folder to the network share you have defined. For example, /SMB/cain/server2003/Users/cain. After the initial synchronization of background items, any files and folders you have specified using the Items that will be synchronized at login and logout group policy are synchronized from the /Users/user_name folder to the network share folder. If you have Open Directory users that do not have mobile accounts or portable home directories and you want to synchronize their local home directories with their network home, you should first use the Workgroup Manager to create mobile accounts for those users to establish a portable home directory. You can then follow the steps above to synchronize the portable home directories with their network home directory. If you dont want to synchronize the local home directory with the home directory on the network share, you can simply create Active Directory accounts for the Open Directory users and remove the local user records; see Mapping local user accounts to Active Directory on page 53 for information about removing local user records.
Converting a local user to a Centrify DirectControl Active Directory user

Although local user accounts can co-exist with Active Directory user accounts, in some cases, you may want to convert some or all of your local accounts to Active Directory user accounts. Converting local users to Active Directory users simplifies account management, but requires you to take some steps manually. On Mac OS X computers, the local account database is normally checked for authentication before Active Directory. If a local user has the same profile (user name, UID, and GID) as an Active Directory user, the local user account is used for authentication. If the local users password is different from the Active Directory users password and you are logging on using the Mac login window, you must use the local user password for authentication to succeed. If the local users password is different from the Active Directory users password and you are logging on remotely (for example, using telnet or ssh), you must use the Active Directory users password for authentication. In most cases, you should remove or convert local user accounts to avoid conflicts between Active Directory and local user accounts and to ensure Active Directory password and configuration policies are enforced. If you need to keep local user accounts, you should ensure the logins are distinguishable from Active Directory accounts. For more information about removing local user accounts, see Mapping local user accounts to Active Directory on page 53.
Note
To convert a local Mac OS X user to an Active Directory user:

1 Open a Terminal window and run the following Directory Service command to delete
the users record:

49
Migrating a user from Apples Active Directory plugin to Centrify DirectControl Active Directory
Although the user record is deleted, the home directory for the user (/Users/cain), including all sub-directories and files, still exists. When you create an Active Directory user with the same name, this user will have access to everything in the existing local home directory.
Note
2 On a Windows machine, use Active Directory Users and Computers to create an Active
Directory user account for the local user account (for example, cain), if one does not already exist.
3 In the Centrify DirectControl Console add the Active Directory user to the appropriate
zone and define the Centrify Profile for the user. Set the home directory for the user: The default home directory for Mac users is the /Users directory, unlike most UNIX systems where /home is the default by convention. To a local home directory: /Users/userName; for example, /Users/cain. To an appropriate network share using the /SMB/share/path or /AFP/share/path syntax. For example, /SMB/cain/server2003.myDomain.com/Users/cain.
Note
4 (Optionally) If you wish to create a mobile account for the user and synchronize the
users folders the next time the user logs on, create a Group Policy Object and set the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Mobility Synchronization Settings group policies.
5 Reboot the Mac OS X machine, then log in as the new Active Directory user.
When you create an Active Directory user by using the Mac Directory Utility Active Directory plug-in it creates numeric user (UID) and group (GID) identifiers. When you migrate a current Active Directory user to Centrify DirectControl, the Centrify DirectControl Console creates a UID and GID that are different than the current UID and GID. When an Active Directory user attempts to log in after DirectControl is installed, the changed UID and GID cause ownership and permission problems with the users home directory. There are two basic approaches to solving this problem: Make the DirectControl UIDs and GIDs match the existing values.
Change ownership on the users primary group to match the value in DirectControl Active Directory.
50
Changing the DirectControl UIDs and GIDs

To change the UID and GID values in DirectControl Active Directory to match the existing values:
1 Log in to the Mac OS X machine as a local administrator. 2 Open a terminal session. 3 Open the users home folder and type:
ls -ln total 32 -rw-r--r--@ -rw-r--r--@ -rw------drwx------@ drwx------@ 1 505 1 505 1 505 3 505 3 505 505 505 505 505 505 505 505 505 505 505 505 3 Mar 26 6148 Mar 26 74 Mar 26 102 Mar 26 102 Mar 26 646 Mar 26 102 Mar 26 102 Mar 26 136 Mar 26 136 Mar 26 170 Mar 26 2007 .CFUserTextEncoding 2007 .DS_Store 2007 .bash_history 2007 Desktop 2007 Documents 2007 Library 2007 Movies 2007 Music 2007 Pictures 2007 Public 2007 Sites
drwx------@ 19 505 drwx------@ drwx------@ drwx------@ drwxr-xr-x@ drwxr-xr-x@ 3 505 3 505 4 505 4 505 5 505
The third column shows the UID (505 in this example) and the fourth column shows the GID (also 505).
4 On the Windows workstation, open the DirectControl Console. Expand the zone,
expand users, and double-click the user to open the property page.
5 Type 505 for the UID. 6 To change the GID, you need to either change the GID of the group to which the user
belongs (which will change for all users who belong to that group) or create a new group. To create a new group: Open ADUC. Then right-click Users > New > Group. Enter a name for the group and click OK. In the DirectControl Console, right click Groups > Create UNIX Group. Search for the group you created. Change the GID to the desired value (for example, 505) and click OK.
7 To change the GID of the existing group to which the user belongs, expand Groups and
double-click the group name. Change the GID to the desired value (for example, 505). Click Yes on the warning message.
51
Modifying the Mac UID and GID to match DirectControl

To change the existing UID and GID to match the values in DirectControl Active Directory depends on whether you have a local home directory, a network home directory, or a mobile home directory.
To change the existing UID and GID if you have a local home or network home directory: 1 Log in to the Mac OS X machine as a local administrator. 2 Open Applications > Directory Utility > Services. Double-click Active
Directory, then click Unbind. Enter your administrator name and password if necessary.
3 Use the ADJoin tool (either the GUI or the command-line version) to connect to an
Active Directory domain.

4 Open a terminal session and type the following:
id userName
Note the primary group. For example:

id cain ... gid=10000(support)
5 Type:
chown -R userName:primaryGroupName /Users/userName
For example, for a local home directory:

chown -R cain:support /Users/cain
For example, for a network home directory:

chown -R cain:support /SMB/Users/cain
To change the existing UID and GID if you have a mobile home directory: 1 Be certain the local home directory is synchronized with the network home directory. 2 Log in to the Mac OS X machine as a local administrator. 3 Open Applications > Directory Utility > Services. Double-click Active
Directory, then click Unbind. Enter your administrator name and password if necessary.
4 Use the ADJoin tool (either the GUI or the command-line version) to connect to an
Active Directory domain.

5 Open a terminal session and type the following Directory Service command to delete the
cached local user:

dscl . -delete /Users/userName
For example:
52
Mapping local user accounts to Active Directory
dscl . -delete /Users/cain
6 Then type the following commands to remove the home directory so that it syncs again
from the network and remove the local copy of mcx so you are prompted to create a mobile account:
rm -rf /Users/userName rm -rf /Library/Managed\ Preferences/userName
7 On the Windows Active Directory machine, set the User Configuration > Policies
> Centrify Settings > Macintosh Settings > Mobility Synchronization Settings group policie.
Mapping local user accounts to Active Directory

In most environments, you can map local user accounts to Active Directory accounts to manage the passwords for local users using your Active Directory password policies. Although you can map local Mac OS user accounts to Active Directory accounts with the User Map group policy, Mac OS users can still log on using their local account password, so you cannot effectively use Active Directory to enforce your password policies for local Mac OS user accounts. If a local user has the same profile (user name, UID, and GID) as an Active Directory user but a different password, the local user account is used for authentication when logging on using the Mac login window. If you are logging on remotely (for example, using telnet or ssh), you must use the Active Directory users password for authentication.
Note
To enforce Active Directory password policies for Mac users, you need to delete the local user accounts to prevent those local account names and passwords from being used to log on. There are different ways to delete local accounts that will impact how those users home directories are handled. To delete local user accounts on Mac OS X computers, do one of the following: Click Systems Preferences > Accounts, select the account and click the minus (-) sign, then click OK. Deleting the user account in this way moves local users home directory to /Users/Deleted Users/localuser.dmg and the user account and home directory are made inactive. If you click Delete Immediately instead of OK, the home directory will not be saved in the /Users/Deleted Users folder.
Open a Terminal window and run the following Directory Service command to delete the users record:
53
Configuring 802.1X wireless authentication
Deleting the user account in this way leaves the users home directory in place. If the Active Directory user you enable for UNIX is configured with the same UID and GID as the deleted local user, the Active Directory user will assume ownership of the home directory.

This section explains how to configure Active Directory and Mac OS X to authenticate Active Directory users by using a Microsoft RADIUS server with the 802.1X PEAP (MSCHAPv2) protocol over a wireless network from a Mac OS X machine. On Mac OS X, 802.1X wireless authentication does not rely on Centrify DirectControl or Apple's Active Directory plugin but is configured primarily through group policies that apply to the Windows server and the Mac OS X machines.
System configuration for 802.1X wireless authentication

The following table summarizes the environment that is needed for 802.1X wireless authentication:
Environment Components / Configuration Windows Server 2003 R2 Enterprise Edition Domain Controller (supports PEAP) with Internet Authentication Service (IAS) installed; on Windows server 2003, RADIUS server is part of IAS. or Windows Server 2008 R2 Enterprise Edition Domain Controller (supports PEAP/TLS) with Network Policy Server (NPS) installed; on Windows Server 2008, Radius server is part of NPS. Active Directory on the Windows Server Group Policy Management Console (GPMC), which is required to configure 802.1x group policies and deploy certificates. Certificate Services, which is required to obtain the required certificates. DirectControl Console 5.0.1-171 or later, which is required to set group policies that apply to Mac OS X machine.
Windows side
54
Environment
Components / Configuration Mac OS X 10.5.x or 10.6.x; Note that Mac OS X 10.6.x is more reliable for 802.1X wireless authentication. Note Configuring 802.x wireless authentication for Mac OS X 10.7 is not covered in this document as Mac OS X 10.7 has changed the way that it controls 802.1x authentication such that the current group policies do not work and the configuration steps are entirely different. DirectControl Agent 5.0.1-171 or later to enforce group policies on the Mac OS X machine.
Mac side
Wireless access point device
Supports 802.1x wireless authentication through one of these protocols: WPA Enterprise WPA2 Enterpirse 802.1X WEP (the name can be different, for example, RADIUS)
Note Although it is possible to configure other RADIUS servers for 802.1X wireless authentication, or use other protocols, this document focuses on the Microsoft RADIUS server and the PEAP and TLS protocols.
Configuring the Windows server

This section summarizes the certificates that you need to create and deploy on your Windows server to support 801.X wireless authentication for Mac OS X users. You need to do or verify the following A root CA certificate was created and deployed to the domain through Windows group policy.
A certificate was obtained for the RADIUS Server to identify itself. This can be a Domain Controller Certificate or an RAS and IAS Server certificate. Certificates are configured for auto enrollment through group policy, which enables DirectControl to auto-enroll them Mac OS X machines. For TLS authentication, a Mac computer certificate, configured for auto enrollment, and a private key are required.
Of course, there are other configuration steps that are required to set up a RADIUS server, such as: Configure the RADIUS client
Configure a remote access policy
However, the important consideration for Mac OS X 802.1X authenticated is that the specified certificate and private key have been created and deployed to the domain. When a Mac OS X machine joins a Windows domain, DirectControl automatically finds certificates on the Domain Controller and adds them as trusted certificates to Keychain Access on the Mac OS X machine.
55
Configuring Mac OS X
This section explains how to configure Mac OS X machines to authenticate Active Directory users by using a Microsoft RADIUS server with the 802.1X PEAP (MSCHAPv2) protocol over a wireless network from the Mac OS X machine. Before configuring your Mac OS X environment, be certain that the RADIUS server is configured as described in System configuration for 802.1X wireless authentication. This configuration includes a domain root CA certificate or RAS/IAS server certificate, as well as a private key that are required to be trusted on the Mac OS X machine. However, there are no manual steps that you must perform to trust these certificates on your Mac OS X machines. As mentioned previously, when a machine is joined to a domain, DirectControl automatically looks for certificates on the domain controller, and adds these certificates and the private key to the system Keychain on the Mac OS X machine. To create profiles that support 802.1X authentication you only need to configure one or two group policies as explained in the next sections.
Understanding 802.1X profiles
Mac OS X controls 802.1X wireless authentication through profiles in System Preferences > Internet and Wireless > Network. You could configure profiles through the Network system preferences for each Mac OS X machine in your environment, but DirectControl provides a set of group policies that enable you to configure profiles for all of your Mac OS X machines at one time.
Note
802.1X settings work for both DHCP and static IP.
Mac OS X has three types of 802.1X profiles, and DirectControl provides a corresponding group policies to configure each type: System Profile is based on network location; one network location can have only one System Profile. The wireless network will always be connected whether a user is logged in or not. A user will not see an 802.1X authentication prompt and all AD users will have access to the wireless network. This profile is recommended for TLS authentication. Set a system profile with the Computer Configuration ... Mac Os X Settings > 802.1X Settings > Specify System Profile policy.
Login Window Profile is based on network location, however, one network location can have multiple Login Window Profiles. The wireless network will be connected at login time and will be disconnected after logout. Login takes longer because it needs to authenticate against the RADIUS server first. A user will not see any 802.1X authentication prompt. A Login Window Profile only works for AD users. Local users will simply ignore this profile. Login Window Profile can only be created by admin user. Generally, this profile is recommended for use in an AD environment with PEAP authentication. However, it does not work for TLS, so you should use the System Profile
56
for TLS. Set login window profiles with the Computer Configuration ... Mac Os X Settings > 802.1X Settings > Specify Login Window Profiles policy.
User Profile is independent of network location and network device. If you add a System Profile for AirPort, then it won't appear in Ethernet settings; however, if you add a User Profile for AirPort, it will also appear in Ethernet settings. When using PEAP, a user needs to enter username/password credentials to establish connection after login. When using TLS, a connection will be established automatically after login. Wireless networks will be disconnected after logout. This profile is generally recommended for temporary use as any user can create a user profile. Set login window profiles with the User Configuration ... Mac Os X Settings > 802.1X Settings > Specify User Profiles policy.
These profiles are transparent to the RADIUS server, which means the RADIUS server does not know which profile the Mac OS X machine is using. If multiple profiles are defined, the login window profile overrides the user profile, and the system profile overrides the login window profile.
Setting a profile
You use Mac OS X Settings group policies to choose a profile. The System and Login Window profile policies are in Computer Configuration; the User profile policy is in User Configuration.
To specify a profile 1 In Group Policy Management Console (GPMC), open a GPO that applies to Mac OS X
machines.
2 Navigate to Computer Configuration (or User Configuration for user policies) /
Policies / Mac OS X Settings / 802.1X Settings.

3 Right-click the policy of choice, for example, Specify Login Window Profiles. Click
Enable, then Add. Enter the following information, separated by semi-colons (;): Network name.

Security type (802.1X WEP, WPA Enterprise, WPA2 Enterprise). Authentication method; you can specify multiple methods separated by commas (TTLS, PEAP, TLS, EAP-FAST, LEAP, MD5). User for 802.1X authentication; (only for the System Profile, not Login or User profile). The specification will fail if you add a user field to a Login or User profile. The user name cannot contain \ or ' characters For Login Profile, Mac OS X will use the AD users name and password automatically. For User Profile, username and password are stored in the login keychain, which GP mapper cannot access.
57
Optional password (only for System Profile), which is transferred without encryption. You can also specify the password in System Preferences on the Mac OS X machine, but note that a password is required for a system profile to work correctly so if you do not specify a password here, you must do so in System Preferences. It cannot contain \ or ' characters.
You can specify only one system profile, but multiple login or user profiles. The following are examples of valid system profiles:
Office1;WPA Enterprise;PEAP;user Office12;802.1X WEP;TTLS,PEAP;user Office3;WPA Enterprise;PEAP;user;passwd
4 Select Automatically turn on AirPort to automatically turn on AirPort device if this
type of profile is specified. Otherwise, the status of the AirPort device will not change.
5 Click OK to save the policy.
Verifying profiles
The 802.1X Settings policies add the specified profiles to the Network system preference on the 802.1X pane.
To check 802.1X profiles 1 On a Mac OS X machine, open System Preferences > Internet and Wireless >
Network.
2 Select AirPort, click Advanced, then select the 802.1X tab and verify that all the
profiles you specified in the 802.1X Settings policies are shown and configured correctly.
58
Chapter 4
Understanding group policies for Mac OS X users and computers

Centrify DirectControl group policies allow administrators to extend the configuration management capabilities of Windows Group Policy Objects to managed Mac OS X computers and to users who log on to Mac OS X computers. This chapter provides an overview to using the Centrify DirectControl Mac OS X group policies that can be applied to Mac OS X computers and users. Group Policy Object (GPO) that is specific for Mac OS X machines. Install can stay here and be repeated in GP Guide, Mac Computer and Mac User chapters. Windows policies? Here or one of the chapters? Mac OS X specific parameters can stay here, but maybe in a different place. The following topics are covered: Understanding group policies and system preferences
Installing Mac OS X group policies Setting Mac OS X group policies Applying standard Windows policies to Mac OS X Configuring Mac OS X-specific parameters
For reference information about the Mac OS X-specific computer and user policies that you can set, see: Chapter 5, Setting computer-based policies for Mac OS X,
Chapter 6, Setting user-based policies for Mac OS X,
For more complete information about creating and using group policies and Group Policy Objects, see your Windows or Active Directory documentation. For information about adding and using other Centrify DirectControl group policies that are not specific to Mac OS X computers and users, see the Centrify DirectControl Group Policy Guide.
Understanding group policies and system preferences

In many organizations, administrators who have both Windows and Mac OS X computers in their organization want to manage settings for their Windows and Macintosh computers and users using a standard set of tools. In a Windows environment, the standard method for managing computer and user configuration settings is through Group Policy Objects applied to the appropriate site, domain, or organizational unit (OU) for different sets of computer and user accounts.
59
Centrify DirectControl provides this capability for Mac OS X computers and users through a group policy extension. The Centrify DirectControl administrative template for Mac OS X (centrify_mac_settings.xml or centrify_mac_settings.adm) provides group policies that can be applied from a Windows server to control Mac OS X settings and behavior. These group policies can be applied to Mac OS X computers and to users who log on to those computers. Through the Centrify DirectControl administrative template for Mac OS X, Windows administrators using the Group Policy Object Editor can centrally access and control native Mac OS X system preferences. In the current Centrify DirectControl administrative template for Mac OS X, Centrify DirectControl group policies control settings for Personal, Hardware, Internet & Network, and System preferences, including: Accounts, (General) Appearance, Desktop & Screen Saver, Dock, Energy Saver, Network, Security & Privacy, Sharing, Software Update, and so on.
Security Settings group policies control settings in this system preference
When you enable a group policy in a Windows Group Policy Object, you effectively set a corresponding system preference on the local Mac OS X computer where the group policy is applied. For example, if you enable the DirectControl group policy Computer Configuration > Centrify Settings > Mac OS X Settings > Security > Require password to unlock each secure system preference, it is the same as selecting the General tab of the Security & Privacy system preference, then clicking the Require an administrator password to access system preferences with lock icons option on a local Mac OS X computer. Once the group policy is enabled in the Windows Group
60
Policy Object and updated on the local Mac OS X computer, the corresponding option is checked:
Enabling the group policy sets this option on a Mac OS X computer where the policy is applied
In addition to the system preferences that are typically set on individual computers, there are many Mac OS X configuration settings that are typically set from a Mac OS X server using the Workgroup Manager. These workgroup policies control application or media access, synchronization rules for mobile user accounts, the look and operation of the Dock, and other settings. The Centrify DirectControl administrative template for Mac OS X
Chapter 4 Understanding group policies for Mac OS X users and computers
61
provides centralized access to many of these Workgroup Manager settings, including . Applications, Dock, Media Access, Mobility, Software Update. and System Preferences
Dock Settings group policies control settings in this Workgroup Manager preference
Note Not all group policies apply to all versions of the Mac OS X operating environment or all Macintosh computer models. If a particular system preference doesnt exist, isnt applicable, or is implemented differently on some computers, the group policy setting may be ignored or overridden by a local setting. For example, the policy Enable firewall provides a setting to block all incoming connections, but it is only effective on computers running Mac OS X 10.6 and later; it has no effect on Mac OS X 10.5. If you enable this group policy and apply it to an organizational unit that includes computers with Mac OS X 10.7, 10.6, and 10.5, the computers running 10.7 and 10.6 block incoming traffic, but those running 10.5 do not block traffic unless you manually block it on the local computer.
Once the Centrify DirectControl administrative template for Mac OS X is installed as described below, the Windows administrator can use Active Directory MMC snap-ins or the Group Policy Management Console to create and link Group Policy Objects to sites, domains, or organizational units that include Mac OS X computers that are joined to an Active Directory domain. Administrators can then use the Group Policy Object Editor to enable and configure the specific policies they want to enforce on Mac OS X computers that are joined to the Active Directory domain. For more information about using Active Directory Users and Computers or the Group Policy Management Console to create and link Group Policy Objects to sites, domains, or OUs, see the Centrify DirectControl Group Policy Guide. You can also refer to the Centrify DirectControl Group Policy Guide for more information about how to add other Centrify DirectControl administrative templates to a Group Policy Object.
62
Installing Mac OS X group policies
Assigning a Group Policy Object

To apply group policies to Mac OS Computers, you can assign an existing group policy that you are using for Windows or UNIX machine, or create a new group policy, to link to a domain or OU that contains your Mac OS X machines. In general, it is recommended that you create an OU specifically for your Mac OS X machines and link a new GPO to that OU. However, there is no problem adding the Mac OS X group policies to an existing GPO and configuring policies for Mac OS X machines. Mac OS X-specific policies that are applied to Windows or UNIX machines are simply ignored.

Centrify DirectControl group policies for Mac OS X consist of two components: The Centrify DirectControl Agent for Mac OS X and its associated configuration and system plug-in files that reside on the Mac OS X computer. The Centrify DirectControl Agent and related files determine the policies that have been applied to the local computer, or to the user who is logging on, and implement the policy through system preferences or other local configuration settings. This guide assumes that you have installed the Centrify DirectControl Agent on your Mac OS X machines.
An administrative template (.xml or .adm file) that describes the policy settings available to the Group Policy Object Editor. The administrative template must be installed on a Windows computer that has the Group Policy Object Editor and the Centrify DirectControl Group Policy Editor Extension. The Group Policy Object Editor and the Centrify DirectControl Group Policy Editor Extension must be available for you to enable and configure policies. See the Centrify DirectControl Administrators Guide for more information.
Installing the administrative template

Notes DirectControl provides templates in both XML and ADM format. In most cases it is best to use the XML templates, which provide greater flexibility, such as the ability to edit settings after setting them initially, and in many cases contain validation scripts for the policies implemented in the template.
However, in certain cases, you may want to add templates by using the ADM files. For example, if you have implemented a set of custom tools for the Windows ADM-based policies, and want to extend those tools to work with the DirectControl policies, you can implement the DirectControl policies by adding the ADM template files as explained in To install the Centrify DirectControl ADM administrative template for Mac OS X group policies: on page 65To install the Centrify DirectControl ADM administrative template for Mac OS X group policies:.
63
The ADM templates do not support extended ASCII code for locales that require double-byte characters. For these locales, you should use the XML templates.
To install the Centrify DirectControl XML administrative template for Mac OS X group policies:
This procedure assumes that you are using the Group Policy Management Console and have created a Mac OS X-specific GPO. For information about using a different console, such as ADUC, see the Centrify DirectControl Group Policy Guide.
1 Open the Group Policy Management Console and select the Group Policy Object that
you are using for Mac OS X computers, right-click, then click Edit to open the Group Policy Object Editor.
2 Expand Computer Configuration > Policies and select Centrify Settings. Right
click and click Add/Remove Templates.

3 Click Add, then navigate to the directory that contains the Centrify DirectControl
centrify_mac_settings.xml
administrative template. By default, Centrify DirectControl administrative templates are located in the C:\Program Files\Centrify\Centrify DirectControl\group policy\policy folder.
4 Select the centrify_mac_settings.xml file, then click Open to add this template to the
64
list of Policy Templates.
5 Click OK.
You should now see the categories of Mac OS X group policies listed as Mac OS X Settings under Centrify Settings in the Group Policy Object Editor. For example:
To install the Centrify DirectControl ADM administrative template for Mac OS X group policies:
This procedure assumes that you are using the Group Policy Management Console and have created a Mac OS X-specific GPO. For information about using a different console, such as ADUC, see the Centrify DirectControl Group Policy Guide.
1 Open the Group Policy Management Console and select the Group Policy Object that
you are using for Mac OS X computers, right-click, then click Edit to open the Group
65
Policy Object Editor.

2 In the Group Policy Object Editor, expand Computer Configuration or User
Configuration, select Administrative Templates, right-click, then click Add/Remove Templates.
Select Administrative Templates, then right-click and select Add/Remove Templates
3 In the Add/Remove Templates dialog box, click Add.
4 Navigate to the directory that contains the Centrify DirectControl ADM administrative
templates. By default, ADM templates are located in the following local directory:
C:\Windows\inf
5 If necessary, scroll to see the DirectControl templates and select the template
centrifydc_mac_settings.adm,
then click Open to add the template to the list of Current Policy Templates, then click OK.
66
Setting Mac OS X group policies
If you update Centrify DirectControl to a new version, new templates may be included with the installation. To make any new policies included in the templates available for use, you must reapply each template by following the steps in one of these procedures. If you see the message, The selected XML (or ADM) file already exists. Do you want to overwrite it?, click Yes. This action overwrites the template with any new or modified group policies. It does not affect any configuration in the template that has been applied; that is, any policies that you have enabled remain enabled.
Note
Setting Mac OS X group policies

Like other group policies, policies for Mac OS X users and computers are organized into categories within the Group Policy Object Editor under Computer Configuration > Policies > Centrify Settings > Mac OS X Settings (Setting computer-based policies for Mac OS X) or User Configuration > Centrify Settings > Mac OS X Settings (Setting user-based policies for Mac OS X). In general, these categories map directly to different types of Mac OS X system preferences and individual policy settings within the categories map to specific settings within the system preference. Normally, once enabled, policies get applied at the next group policy refresh interval, after the user logs out and logs back in, or after the computer has been rebooted. Some Mac OS X group policies, however, require the user to log out and log back in or the computer to be rebooted. The description of each group policy indicates whether the policy can be applied dynamically at the next refresh interval or requires a re-login or a reboot. You may also update group policies manually by running the adgpupdate command on an individual machine. See Updating configuration policies manually on page 67.
Note The system preference updated on an individual computer must be closed, then reopened for the group policy setting to be visible.
In most cases, group policies can be Enabled to activate the policy or Disabled to deactivate a previously enabled policy. Changing a policy to Not Configured has no effect for any Mac OS X group policies. Once a group policy is set on a local computer, it remains in effect even if the computer leaves the Active Directory domain. The administrator or users with an administrative account can change settings manually at the local computer, but any manual change are overwritten when the group policy is applied.
Updating configuration policies manually

Although there are Windows group policy settings that control whether group policies should be refreshed in the background at a set interval, Centrify DirectControl also provides a command line program to manually refresh group policy settings at any time. This command line program, adgpupdate, forces the adclient daemon to contact Active Directory and collect group policy settings. With the adgpupdate command, you can
67
Applying standard Windows policies to Mac OS X
specify whether you want to refresh computer configuration policies, user configuration policies, or both. When you run the adgpupdate command, the adclient daemon does the following: Contacts Active Directory for computer configuration policies, user configuration policies, or both. By default, adclient collects both computer and user configuration policies.
Determines all of the configuration settings that apply to the computer, the current user, or both, and retrieves those settings from the System Volume (SYSVOL). Writes all of the configuration settings to a virtual registry on the local computer. Starts the runmappers program to initiate the mapping of configuration settings using individual mapping programs for user and computer policies. Resets the clock for the next refresh interval.
For more information about using the adgpupdate command, see the adgpupdate man page or Using adgpupdate in the Centrify DirectControl Administrators Guide.
Applying standard Windows policies to Mac OS X

Every Group Policy Object includes several default Windows-based group policy categories and default Windows-based administrative templates for user and computer configuration. Most of the settings in the default Windows policies and administrative templates only apply to Windows computers and Windows user accounts. However, some of the common Windows configuration settings for password enforcement, such as the policies for minimum password length and complexity, do apply to Mac OS X computers. If these settings are enabled for a Group Policy Object applied to a site, domain, or OU that includes Mac OS X computers, the settings are enforced for Mac OS X users and computers. The following table describes the standard Windows group policies can be applied to Mac OS X computers and users and where to find these policies when viewing a Group Policy Object in the Group Policy Object Editor:
To set this policy for Mac OS X Turn off background refresh of Group Policy Group Policy refresh interval for computers Global Configuration Settings MaxPollInterval Enable Windows NTP Client Configure Windows NTP Client Select this Windows object Computer Configuration > Administrative Templates > System > Group Policy Computer Configuration > Administrative Templates > System > Windows Time Service > Time Providers Computer Configuration > Administrative Templates > System > Windows Time Service > Time Providers
68
Configuring Mac OS X-specific parameters
To set this policy for Mac OS X Interactive logon: Message text for users attempting to log on Interactive logon: Prompt user to change password before expiration
Select this Windows object Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
Enforce password history Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy Maximum password age Minimum password age Minimum password length Password must meet complexity requirements Store passwords using reversible encryption Group Policy refresh interval for users User Configuration > Administrative Templates > System > Group Policy
Synchronizing time
By default, the local Network Time Protocol (NTP) Client is enabled and synchronizes your computers clock to the Domain Controller. If you do not want your local NTP service to synchronize to the NTP service on the Domain Controller, explicitly disable the (Windows) Enable Windows NTP Client group policy. You can also synchronize to a different NTP server by specifying one in the Configure Windows NTP Client group policy. To set these policies, in the Group Policy Editor, click Computer Configuration > Administrative Templates > System > Windows Time Service > Time Providers.

Most configuration parameters apply to both Mac OS X or only to actual UNIX or Linux systems. All these parameters are described in the Centrify DirectControl Configuration Parameter Guide. However, the following parameters apply only to Mac OS X and are described in this section: adclient.autoedit.mac.netlogin
adclient.mac.map.home.to.users
69
adclient.autoedit.mac.netlogin
System Preferences > Users & Groups (Accounts) has a login option: Allow network users to log in at login window:
If this option is deselected, Active Directory users will not be able to log into the machine. The configuration parameter adclient.autoedit.mac.netlogin controls whether this option can be deselected by users. By default, the parameter is true in the /etc/centrifydc/centrifydc.conf file:
adclient.autoedit.mac.netlogin: true
In this case, even if a user deselects the box, the box is selected again when adclient is restarted, effectively preventing a user from deactivating network login. If you want to allow a user to deactivate network login, set the parameter to false. If a user deselects network login in System Preferences > Accounts, the next time adclient starts, network users will be unable to log in to the machine.
adclient.mac.map.home.to.users
On Mac OS X 10.5, /home is an automount point. If a zone users home directory is set to /home/username, the operating system cannot create the home directory and the user cannot log in. Therefore, you should not specify /home/username as the home directory for any Mac OS X users, but since this is a typical UNIX home directory, there may be Active Directory users who have a /home/username home directory. To avoid potential problems, you can configure Centrify DirectControl to change /home/username to /Users/username (the default Mac OS X home directory), in one of two ways: Enable the group policy, Map /home to /Users.
Set this parameter, adclient.mac.map.home.to.users to true to enable the change for the local machine only; for example:
70
adclient.mac.map.home.to.users:true
71
Chapter 5

Centrify DirectControl group policies allow administrators to extend the configuration management capabilities of Windows Group Policy Objects to managed Mac OS X computers and to users who log on to Mac OS X computers. This chapter provides reference information for the Centrify DirectControl Mac OS X group policies that can be applied specifically to Mac OS X computers. The following topics are covered: Setting computer-based policies for Mac OS X
Map /home to /Users 802.1X Wireless Settings App Store EnergySaver Firewall Internet Sharing Network Remote Management Scripts (Login/Logout) Security Services Software Update Settings
The computer-based group policies are defined in the Centrify DirectControl Mac OS X administrative template (centrify_mac_settings.xml) and accessed from Computer Configuration > Policies > Centrify Settings > Mac OS X Settings. See Chapter 4, Understanding group policies for Mac OS X users and computers, for general information about how DirectControl uses group policies to manage Mac OS X settings and for information on how to install the group policy administrative templates. For reference information about user-based policies, see Chapter 6, Setting user-based policies for Mac OS X. For information about applying standard Windows policies to Mac OS X, see Applying standard Windows policies to Mac OS X on page 68 and for information about Mac OS Xspecific parameters, see Configuring Mac OS X-specific parameters on page 69. For more complete information about creating and using group policies and Group Policy Objects, see your Windows or Active Directory documentation. For more
Note
72
information about adding and using other Centrify DirectControl group policies that are not specific to Mac OS X computers and users, see the Centrify DirectControl Group Policy Guide.
Chapter 5 Setting computer-based policies for Mac OS X
73

The following table provides a summary of the group policies you can set for Mac OS X computers. These group policies are in the Centrify DirectControl Mac OS X administrative template (centrify_mac_settings.xml) and accessed from Computer Configuration > Policies > Centrify Settings > Mac OS X Settings.
Use this policy Map /home to /Users To do this Map the /home/username directory to /Users/username. This is a Mac OS X-specific policy but defined in the Direct Control Settings > Adclient Settings folder using the centrifydc_settings.xml template. Create login and system profiles for wireless authentication. These group policies correspond to 802.1X Options in the Networks system preference. Control the look and operation of the login window on Mac OS X computers and map zone groups to the local administrator group. These group policies correspond to Login Options in the Accounts system preference. Control the users and groups who can access the App Store. These group policies correspond to settings in the Sleep and Options panes in the Energy Saver system preference. Control sleep and wake-up option on Mac OS X computers. These group policies correspond to settings in the Sleep and Options panes in the Energy Saver system preference. Control the firewall configuration on Mac OS X computers. These group policies correspond to settings in the Firewall pane of the Sharing system preference. Manage Internet connections on Mac OS X computers. These group policies correspond to settings in the Internet pane of the Sharing system preference. Control DNS searching and proxy settings. These group policies correspond to settings in the TCP/IP and Proxies panes of the Network system preference. Control Apple Remote Desktop access for zone users. These group policies correspond to the Manage > Change Client Settings options in Apple Remote Desktop. Control security settings on Mac OS X computers. These group policies correspond to settings in the Security system preferences.
802.1X Wireless Settings
Accounts
App Store
EnergySaver
Firewall
Internet Sharing
Network
Remote Management
Security
74
Use this policy Services
To do this Control access to various services on Mac OS X computers. These group policies correspond to settings in the Services pane of the Sharing system preference. Control the options for automatic software updates on Mac OS X computers. These group policies correspond to settings in the Software Update system preference.
Software Update Settings
For information about specific policies and how to set them, see the policy description (Explain text) or the corresponding discussion of the specific system preference or individual setting in the Mac OS X Help.
75
Map /home to /Users
Map /home to /Users

The Mac OS X group policy, Map /home to /Users is defined in the centrifydc_settings.xml file, not in centrify_mac_settings.xml, and is in DirectControl Settings, not in Mac OS X Settings. To enable or disable this policy, click Computer Configuration > Centrify Settings > DirectControl Settings > Adclient Settings. On Mac OS X 10.5, /home is an automount point. If a zone users home directory is set to /home/username, the operating system cannot create the home directory and the user cannot log in. Therefore, you should not specify /home/username as the home directory for any Mac OS X users, but since this is a typical UNIX home directory, there may be Active Directory users who have a /home/username home directory. To avoid potential problems, enable this group policy, Map /home to /Users, to configure Centrify DirectControl to change /home/username to /Users/username (the default Mac OS X home directory). If you do not enable this policy, the change does not take effect. This policy modifies the adclient.mac.map.home.to.users parameter in the DirectControl configuration file.
76

Use the Computer Configuration > Centrify Settings > Mac OS X Settings > 802.1X settings to create profiles for wireless network authentication. The profiles you
77
specify with these group policies are created in the Network system preferences pane.
78
Use this policy Specify Login Window Profiles
To do this Enable this policy to specify 802.1X System Profile for wireless network authentication. System profile can establish wireless connection without user login. Setting must follow this format: Network;Security Type;Authentication Method,username;[password] where each field is separated by a semicolon (;). Network is the wireless network name Security type is one of 802.1X WEP, WPA Enterprise, WPA2
Enterprise
Authentication method is one or more of the following, separated by commas: TTLS, PEAP, TLS, EAP-FAST, LEAP, MD5 Username is the user for 802.1X authentication. It cannot contain \ or 'characters. Password is optional and is transferred without encryption. You can also specify the password in System Preferences on the Mac OS X machine, but note that a password is required for a system profile to work correctly so if you do not specify a password here, you must do so in System Preferences. It cannot contain \ or ' characters. For example:
OFFICE1;WPA Enterprise;PEAP;user OFFICE2;802.1X WEP;TTLS,PEAP;user;passwd
Automatically turn on Airport; to automatically turn on AirPort device if this type of profile is specified. Otherwise, the status of the AirPort device will not change. Once enabled, this policy takes effect dynamically at the next group policy refresh interval.
79
Use this policy Specify System Profile
To do this Enable this policy to specify 802.1X Login Window Profiles for wireless network authentication. Login window profiles can establish a network connection automatically after a user enters a username and password in the login window. To add a login window profile, enable the policy and click Add to enter the profile name and setting. Type a name for the profile. Setting must follow this format: Network;Security Type;Authentication Method, where each field is separated by a semi-colon (;). Network is the wireless network name Security type is one of 802.1X WEP, WPA Enterprise, WPA2
Enterprise
Authentication method is one or more of the following, separated by commas: TTLS, PEAP, LEAP, MD5 For example:
OFFICE1;WPA Enterprise;PEAP OFFICE2;802.1X WEP;TTLS,PEAP
80
Accounts
Accounts
Use the Computer Configuration > Centrify Settings > Mac OS X Settings > Accounts settings to manage the options from the Accounts ( ) system preference on Mac OS X computers and to enable a group for administrative access to managed machines.
Manage login options

Use the Login window settings policy to configure login options on a computer.
Use this policy Set login window settings To do this Configure the Login Options on a computer. If you enable this policy, you can configure the Login Window to: Display a text string as a login banner. The Banner you specify is displayed when the user is prompted to log on. Display a List of Users or a Name and Password field. Displaying the Name and Password requires users to provide their account name and password, and is more secure than displaying a list of user names. Show the Restart, Sleep, and Shut Down buttons. Show the Input menu in the login window to allow users to change the current Keyboard Layout. Show password hints in the login window. Use VoiceOver at the login window. Enable fast user switching. Enabling the options in this group policy is the same as clicking Login Options in the Accounts system preference and setting the corresponding login window options. Note If you click Enable Fast User Switching, this setting does not take effect until the Login Options in the Accounts system preference is opened manually by a user on the local host. This step is required to display the list of users in the upper-right corner of the menu bar. After users log on, the user's full name, short name, or icon identifier is displayed in the menu bar. If you want to change how users are displayed in the menu, you also must do so manually from the Login Options in the Accounts system preference. Once enabled, this group policy takes effect when users log out and log back in or when the computer is rebooted.
81
Accounts
These group policies correspond to the options displayed when you select the Accounts system preference, then click Login Options. For example:
Specify group for administrative access

Use the following group policy to specify a group whose members have administrative access to a local machine. See Setting up local and remote administrative privileges on page 45 for information on how to use this group policy with the Enable ARD administrator
82
Accounts
group policy to enable both local and remote administrative access for the same group of
83
Accounts
users.
84
Accounts
Use this policy
To do this
Map zone groups to local admin group Specify one or more zone groups to map to the admin group on the local machine. Members of the groups you specify here have administrative privileges on the local machine, including: The use of sudo command in a shell The ability to unlock and make changes to System Preferences. Be certain to create a zone group in Centrify DirectControl and add users who you want to have administrative privileges on Mac OS X machines managed by DirectControl. Note If the local machine is connected to the domain through Auto Zone, you cannot create a zone group because there are no zones. However, all Active Directory groups are valid for the joined machine, so you can map any group to the local admin group, but you need to know the groups UNIX name, which you can retrieve on the local machine, by using the adquery command, as follows
To set this policy:

1 Open the policy and select Enabled. 2 Click Add. 3 Enter the name of a zone group in the box (or the UNIX group name if connected through Auto Zone). Then click OK.
Map zone groups to local group
Specify one or more zone groups to map to a Mac local group on the local machine. Members of the zone groups you specify here will be given the privileges of the local group on the local machine; for example,: If you map to the _lpadmin and _lpoperator local groups, members of the zone group can manage printer settings on the local machine. If you map to the admin local group, members of the zone group obtain administrator privileges on the local machine. Note To obtain administrator privileges for a zone group, you can either map to the local admin group with this policy, or use the Map zone groups to local admin group policy. However, do not do both as the results are unpredictable. Be certain to create a zone group in Centrify DirectControl and add users who you want to have administrative privileges on Mac OS X machines managed by DirectControl. Note If the local machine is connected to the domain through Auto Zone, you cannot create a zone group because there are no zones. However, all Active Directory groups are valid for the joined machine, so you can map any group to the local admin group, but you need to know the groups UNIX name, which you can retrieve on the local machine, by using the adquery command, as follows
To set this policy:

1 Open the policy and select Enabled.. 2 Click Add.. 3 Enter the name of a local group and of a zone group in the respective boxes (or the UNIX group name if connected through Auto Zone). Then click OK.. You can repeat this step multiple times to map the zone group to more than one local group.
85
App Store
App Store
Use the Computer Configuration > Centrify Settings > Mac OS X Settings > App Store > Prohibit Access to App Store group policy to control access to the App Store. By default, all users can access the App Store. Enable this group policy to prohibit access to App Store to all users except the root user and those you specifically authorize with the options, Allow these users to access App store, and Allow these groups to access App Store. You can set the following options with this policy:
Use this policy Allow these users to access App Store To do this The names of local or AD users who are allowed to access the App Store. When this policy is enabled, only users on this list and the root user are allowed to access the App Store.
Allow these groups to access App Store The names of local or AD groups that are allowed to access the App Store. When this policy is enabled, only users in the specified groups, and the root user, are allowed to access the App Store.
This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
86
EnergySaver
EnergySaver
Use the Computer Configuration > Centrify Settings > Mac OS X Settings > EnergySaver settings to manage sleep and wake-up options from the Energy Saver ( ) system preference on Mac OS X computers. For example:
You can configure power options or schedule startup and shutdown times.
Configuring power options

Open the appropriate folder to set power options when running on AC power or battery power. Each folder has the identical set of group policies: On AC power
On battery power
To do this Allow the power button to sleep the computer. Enabling this group policy is the same as selecting the Allow power button to sleep the computer option in the Options pane of Energy Saver system preference. This policy can take effect dynamically at the next group policy refresh interval. Put computer hard disks to sleep when they are inactive. Enabling this group policy is the same as selecting the Put the hard disk(s) to sleep when possible option in the Sleep pane of Energy Saver system preference. This policy can take effect dynamically at the next group policy refresh interval.
Use this policy Allow power button to sleep the computer
Put the hard disk(s) to sleep when possible
87
EnergySaver
Use this policy Restart automatically after a power failure
To do this Enable to set the computer to automatically restart after a power failure. Enabling this group policy is the same as selecting the Restart automatically after a power failure option in the Options pane of Energy Saver system preference. This policy can take effect dynamically at the next group policy refresh interval. Specify the number of minutes of inactivity to allow before automatically putting a computer into the sleep mode. If you enable this group policy, the period of inactivity you specify applies only when the computer is using its power adapter. If the computer is inactive for the number of minutes you specify, it is put in sleep mode. Enabling this group policy is the same as selecting a time using the Put the computer to sleep when it is inactive for slider in the Sleep pane of Energy Saver system preference. This policy can take effect dynamically at the next group policy refresh interval. Specify the number of minutes of inactivity to allow before automatically putting the display into the sleep mode. If you enable this group policy, the period of inactivity you specify applies when the computer is using its power adapter. If the computer is inactive for the number of minutes you specify, the display is put in sleep mode. Enabling this group policy is the same as selecting a time using the Put the display to sleep when it is inactive for slider in the Sleep pane of Energy Saver system preference. This policy can take effect dynamically at the next group policy refresh interval. Automatically take a computer out of sleep mode when the modem detects a ring. This group policy allows a computer that has been put to sleep to remain available to answer the modem. On Mac OS X 10.4, enabling this group policy is the same as selecting the Wake when the modem detects a ring option in the Options pane of Energy Saver system preference. On Mac OS X 10.5, enabling this group policy has no effect. This policy can take effect dynamically at the next group policy refresh interval. Automatically take a computer out of sleep mode when the computer receives a Wake-on-LAN packet from an administrator. This group policy allows a computer that has been put to sleep to remain available to network administrator access. Enabling this group policy is the same as selecting the Wake for Ethernet network administrator access option in the Options pane of Energy Saver system preference. This policy can take effect dynamically at the next group policy refresh interval.
Set computer sleep time
Set display sleep time
Wake when the modem detects a ring
Wake for Ethernet network administrator access
88
EnergySaver
Scheduling startup and shutdown times
To configure sleep/shutdown times and startup times, open the Scheduled events folder (Computer Configuration Policies > Centrify Settings > Mac OS X Settings > EnergySaver > Scheduled events).
Use this policy Set machine sleep/shutdown time To do this Specify a time to shut down or put the machine to sleep. Enabling this group policy is the same as selecting the Schedule button in the Energy Saver system preference, then specifying times and days to shut down or put the machine to sleep. After enabling this policy, specify values for the following: Action: Select sleep or shutdown Set machine sleep/shutdown time: Enter a time in the format HH:mm using a 24 hour clock; for example, to shut down or put the machine to sleep at 10:05 P.M.:
22:05
Sleep/shutdown machine on every: Select the days of the week on which to shut down or sleep the machine at the specified time. All days are selected by default. This policy can take effect dynamically at the next group policy refresh interval. Set machine startup time Specify a time to start up the machine. Enabling this group policy is the same as selecting the Schedule button in the Energy Saver system preference, then specifying times and days to start up the machine. After enabling this policy, specify values for the following: Set machine startup time: Enter a time in the format HH:mm using a 24 hour clock; for example, to start up the machine at 7:55 A.M.:
7:55
Start machine on every: Select the days of the week on which to start the machine at the specified time. All days are selected by default. This policy can take effect dynamically at the next group policy refresh interval.
89
Firewall
Firewall
Use the Computer Configuration > Centrify Settings > Mac OS X Settings > Firewall settings to manage the firewall options on Mac OS X computers. Enabling the Centrify firewall group policies is the same as setting options from System Preferences > Security > Firewall. With the Centrify Firewall Group Policies, you can allow all incoming connections, or limit connections to the specified services and applications. You cannot block all connections:
Note
90
Firewall
In addition group policies are available for the Advanced firewall settings, Enable Firewall Logging, and Enable Stealth Mode.
Use this policy Enable Firewall To do this Prevent incoming network communication to all services and ports other than those explicitly enabled for the services specified in the Services pane of the Sharing system preferences. This group policy turns on default firewall protection. The following check boxes apply to Mac OS X 10.6 and later only: Block all incoming connections: Block all incoming connections except those required for basic Internet services, such as DHCP, Bonjour, and IPSec. Automatically allow signed software to receive incoming connections: Allows software signed by a valid certificate authority to provide services accessed from the network. This setting will not take effect if Block all incoming connections is selected. On 10.6 and later, this policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. On Mac OS X 10.5, this policy takes effect when the computer is rebooted. On Mac OS X 10.5, enabling this group policy is the same as clicking Limit incoming connections to specific services and applications in System Preferences > Security > Firewall to prevent network communication to all services and ports other than those shown in the box. On Mac OS X 10.5, the policies to allow iChat, iTunes, and iPhoto have no effect, so when you enable the firewall, those services are not allowed through. On Mac OS X Servers, enabling his policy has no effect. On Mac OS X 10.5, and Mac OS X Servers, enabling this policy has no effect. If the firewall is enabled, the iChat service is not allowed through the firewall. If the firewall is enabled, enabling this group policy is the same as clicking the On checkbox to allow communication through the firewall for iChat Bonjour. If you do not enable this group policy, traffic for iChat Bonjour will be blocked from the local computer. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. On Mac OS X 10.5, and Mac OS X Servers, enabling this policy has no effect. If the firewall is enabled, the iPhoto Sharing service is not allowed through the firewall. If the firewall is enabled, enabling this group policy is the same as clicking the On checkbox to allow communication through the firewall for iPhoto Bonjour Sharing. If you do not enable this group policy, traffic for iPhoto Bonjour Sharing will be blocked from the local computer. Users will be able to access iPhoto collections on other computers, but the local computer cannot be used to serve any iPhoto collections. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
(Enable Firewall continued)
Enable iChat
Enable iPhoto Sharing
91
Firewall
Use this policy Enable iTunes Music Sharing
To do this Enabling this group policy is the same as clicking the On checkbox to allow communication through the firewall for iTunes Music Sharing. On Mac OS X 10.5, and Mac OS X Servers, enabling this policy has no effect. If the firewall is enabled, the iTunes Music Sharing service is not allowed through the firewall. If you do not enable this group policy, traffic for iTunes Music Sharing will be blocked from the local computer. Users will be able to access iTunes collections on other computers, but the local computer cannot be used to serve any iTunes collections. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. On Mac OS X 10.5, and Mac OS X Servers, enabling this policy has no effect. If the firewall is enabled, the Network Time service is not allowed through the firewall. If the firewall is enabled, enabling this group policy is the same as clicking the On checkbox to allow communication through the firewall for Network Time. If you do not enable this group policy, traffic from the Network Time service will be blocked. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Enabling this group policy is the same as clicking the Block UDP Traffic checkbox in the Advanced firewall settings. This group policy does not block UDP communications that are related to requests initiated on the local computer. On Mac OS X 10.5, enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
Enable Network Time
Block UDP Traffic
92
Firewall
Use this policy Enable Firewall Logging
To do this Log information about firewall activity, including all of the sources, destinations, and access attempts that are blocked by the firewall. The activity is recorded in the secure.log file on the local computer. Enabling this group policy is the same as clicking the System Preferences > Security > Firewall then clicking Enable Firewall Logging in the Advanced firewall settings. On Mac OS X Servers, enabling this policy has no effect. On Mac OS X 10.6 and later, this policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. On Mac OS X 10.5, this policy takes effect when the computer is rebooted. Prevent uninvited traffic from receiving a response from the local computer. Enabling this group policy is the same as clicking the System Preferences > Security > Firewall then clicking Enable Stealth Mode in the Advanced firewall settings. If you enable this group policy, the local computer will not respond to any network requests, including ping requests. Because the computer will not reply to ping requests, using this policy may prevent you from using network diagnostic tools that require a response from the local computer. On Mac OS X Servers, enabling this policy has no effect. On Mac OS X 10.6 and later, this policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. On Mac OS X 10.5, this policy takes effect when the computer is rebooted.
Enable Stealth Mode
93
Internet Sharing
Internet Sharing
Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings >Internet Sharing group policy to prevent any kind of Internet sharing on the local computer. This group policy can only be used to prevent Internet sharing. Although this group policy corresponds to a setting on the Internet pane of the Sharing ( ) system preference, you can not use it to start Internet sharing, configure the shared connection, or set any other options. For example:
Use this policy Disallow all Internet Sharing
To do this Prevent any kind of Internet sharing on the local computer. Enabling this group policy is the same as clicking Stop to prevent other computers from sharing an Internet connection on a local computer in the Internet pane of the Sharing system preference. For this group policy, clicking Disabled or Not Configured has no effect. If you have previously Enabled the group policy, Internet sharing will remain off until you manually start it on the local computer. On Mac OS X Server 10.4 and 10.5, enabling this policy has no effect. Once enabled, this group policy takes effect when users log out and log back in, or dynamically at the next group policy refresh interval without rebooting the computer.
94
Network
Network
Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Network settings to manage DNS search requests and proxy settings. These group policies correspond to settings in the TCP/IP and Proxies panes of the Network ( ) system preference on Mac OS X computers. For example:
Use this policy Adjust list of DNS servers
To do this Control the list of DNS servers when performing DNS lookups. To use this policy, click Enabled, then click Add, type the IP address for a DNS server, then click OK to add the server to the list of DNS servers. Add as many servers as you want in this manner. When you are finished adding the servers, click OK to close the dialog box. At any time while the policy is enabled, you can select an address in the list and click Edit to change the address, or Remove to remove it as a DNS server. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Control the list of domains to search when performing DNS lookups. To use this policy, click Enabled, then click Add, type a domain name, then click OK to add the domain to the list of domains to search. Add as many domains as you want in this manner. When you are finished adding the domains to search, click OK to close the dialog box. At any time while the policy is enabled, you can select a domain in the list and click Edit to change the name, or Remove to remove it as a domain to be searched. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Configure proxy servers to provide access to services through a firewall.
Adjust list of searched domains
Configure Proxies
95
Network
Configure Proxies
Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Network > Configure Proxies settings to manage settings on the Proxies panes of the Network system preference. For example:
These group policies enable you to configure the host names (or IP addresses) and port numbers for the computers providing specific services, such as File Transfer Protocol (ftp), Hypertext Transfer Protocol (http), and HTTP over Secure Sockets Layer (https), through a firewall. A proxy server is a computer on a local network that acts as an
96
Network
intermediary between computer users and the Internet to ensure the security and administrative control of the network.
Use this policy Enable Proxies To do this Configure the host name (or IP address) and port number for the computers providing specific services. Within this category, you can enable the following proxy servers: Use the Enable FTP Proxy policy to configure the host name and port number for the FTP proxy server (FTP protocol). Use the Enable Web Proxy policy to configure the host name and port number for the Web proxy server (HTTP protocol). Use the Enable Secure Web Proxy policy to configure the host name and port number for the Secure Web proxy server (HTTPS protocol). Use the Enable Streaming Proxy policy to configure the host name and port number for the Streaming proxy server (RTSP protocol). Use the Enable SOCKS Proxy policy to configure the host name and port number for the Streaming proxy server (SOCKS protocol). Use the Enable Gopher Proxy policy to configure the host name and port number for the Gopher proxy server. Use the Enable Streaming Proxy policy to configure the host name and port number for the Streaming proxy server (RTSP protocol). Use the Enable Proxies using a PAC file policy to configure proxy servers from a proxy configuration file. These policies can take effect dynamically at the next group policy refresh interval without rebooting the computer. Prevent requests to unqualified host names from using proxy servers. If you enable this policy, users can enter unqualified host names to contact servers directly rather than through a proxy. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Use the FTP passive mode (PASV) to access Internet sites when computers are protected by a firewall. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
Exclude simple hostnames
Use Passive FTP Mode (PASV)
Bypass Proxy settings for these Hosts & Specify fully-qualified host names and domains for which you want to Domains bypass proxy settings. You should use this policy to define the hosts or domains that should never be contacted by proxy. To use this policy, click Enabled, then click Show to display the Show Contents list of hosts and domains. Click Add, type a host or domain name, then click OK to add the entry to the Show Contents list. Each host or domain should be listed as a separate line in the Show Contents list. For each host or domain, click Add, type the host or domain name, and click OK to add the host or domain as a new entry in the list. When you are finished adding items to the list, click OK to close the Show Contents dialog box. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
97
Remote Management
Remote Management
Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Remote Management settings to control Apple Remote Desktop access for zone users. You can use these group policies to give Active Directory group members permission to remotely control Mac OS X computers without physically having to activate the Apple Remote Desktop on the remote Mac OS X computer. The Remote Management group policies correspond to the Manage > Change Client Settings options in Apple Remote Desktop and are similar to access privileges defined on a client computer using the Sharing system preference. For example:
Click Add to add remote users and control the tasks remote users can perform
Tasks remote users are allowed to perform
Because the group policies correspond to the Manage > Change Client Settings options in Apple Remote Desktop, the group policy settings are not displayed in the local system preference on the Mac OS X client. Although the tasks you can assign to different groups by group policy correspond to tasks you can assign using the local Sharing system preference on a Mac OS X client computer, the group policy settings do not update the local
Note
98
Remote Management
system preference to display check marks for the tasks that the remote users have been given permission to perform.
Use this policy Enable administrator access groups To do this Allow all users who are members of the following Apple Remote Desktop administrator groups to access this computer using Apple Remote Desktop. Before enabling this group policy, you should create each Active Directory security group you intend to use and add a UNIX profile for each group to the zone, using the exact UNIX group names (ard_admin, ard_reports, ard_manage, ard_interactive). Note Creating UNIX profiles with these group names displays a warning message because the names are longer than 8 characters. You can safely ignore this warning message. Enabling this policy allows users in the following groups to manage Mac OS X computers through Apple Remote Desktop: ard_admin gives all members of the group the ability to remotely control the computer desktop. ard_reports gives all members of the group the ability to remotely generate reports on the computer. ard_manage gives all members of the group the ability to manage the computer using Apple Remote Desktop. Users in this group can perform the following tasks by using Apple Remote Desktop: Generate reports Open and quit applications Change settings Copy Items Delete and replace items Send text messages Restart and shut down ard_interactive gives all members of the group the ability to interactively observe or control the computer using Apple Remote Desktop. Users in this group can perform the following tasks by using Apple Remote Desktop: Send text messages Observe Control This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. See Setting up local and remote administrative privileges on page 45 for information on how to use this group policy with the Map zone groups to local admin group policy to enable both local and remote administrative access for the same group of users.
99
Scripts (Login/Logout)
Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Scripts (Login/Logout) > Specify multiple login scripts group policy to deploy login scripts that run when an Active Directory or local user logs on. When you use this group policy, the login scripts are stored in the Active Directory domains system volume (sysvol) and transferred to the Mac OS X computer when the group policies are applied. Login scripts are useful for performing common tasks such as mounting and shares This policy is also available as a user policy. If you specify scripts using both the computer and user policies, the computer scripts are executed first.
Use this policy Specify multiple login scripts To do this Specify the names of one or more login scripts to execute when an AD or local user logs on. The scripts you specify run simultaneously in no particular order. Note This policy works on Mac OS X 10.5 and later. Before enabling this policy, you should create the scripts and copy them to the system volume (sysvol) on the domain controller. By default, the login scripts are stored in the system volume (SYSVOL) on the domain controller in the directory:
\\domain\SYSVOL\domain\Scripts \scriptname1 \scriptname2
...
After enabling this policy, click Add and enter the following information: Script: The name of the script and an optional path, which are relative to \\domain\SYSVOL\domain\scripts\. For example, if the domain name is ajax.org and you enter a script name of mlogin.sh, the script that gets executed on the domain controller is:
\\ajax.org\SYSVOL\ajax.org\Scripts\mlogin.sh
You can specify additional relative directories in the path, if needed; for example, if you type sub\mlogin.sh, the file that gets executed is:
\\ajax.org\SYSVOL\ajax.org\Scripts\sub\mlogin.sh
Parameters: An optional set of arguments to pass to the script. These arguments are interpreted the same way as in a UNIX shell; that is, space is a delimiter, and backslash is an escape character. You can also use $USER to represent the current user's name. For example:
arg1 arg2 arg3 arg1 'a r g 2' arg3
Note Be certain authenticated users have permission to read these files so the scripts can run when they log in. Once this group policy is enabled, it takes effect when users log out and log back in.
100
Security
Security
Use the Computer Configuration > Centrify Settings > Mac OS X Settings > Security settings to manage the options from the Security ( ) system preference on Mac OS X computers. These group policies correspond to the options displayed on the Security pane. For example:
Use this policy Disable automatic login
To do this Disable the automatic login setting. If you enable this group policy, it overrides the Login Options set in the Accounts system preference. For this group policy, clicking Disabled or Not Configured has no effect. Mac OS X 10.5, when you manually unset the option, the option remains checked. You must then manually configure a user for automatic login in the Accounts system preference. On Mac OS X Server 10.4 and 10.5, enabling this policy has no effect. Once enabled, this group policy takes effect when the computer is rebooted.
101
Security
Use this policy Enable smart card support
To do this Enable users to logon with smart cards. If you enable this group policy, it adds smart card support to the /etc/authorization file on Mac OS X 10.4 or later machines that are linked to the group policy object. This policy also creates a text file named /etc/cacloginconfig.plist on each machine. This configuration file directs the Mac OS X smart card log-in to look for a user in Active Directory with a user principal name (UPN) that is the same as the NT Principal Name attribute in the smart card log-in certificate. See Chapter 7, Configuring a Mac OS X computer for smart card login, for details. If you later disable this policy, the smart card support strings are removed from the /etc/authorization file, and the /etc/cacloginconfig.plist file is deleted. Note Changing this policy to Not configured does not remove the smart card support strings nor remove the plist file. Once this policy is enabled, you must select Disabled to do this. Once enabled, this group policy takes effect when the computer is rebooted. Specify the number of minutes of inactivity to allow on a computer before automatically logging out the current user. The default value is 5 minutes. Setting the value to less than 5 minutes disables automatic logout. If you plan to disable automatic logout, it is recommended that you set the value to 0 to preserve backward compatibility. Note Disabling this policy does not disable automatic logout. On Mac OS X Server 10.4 and 10.5, enabling this policy has no effect. This policy takes effect when users log out and log back in after the next group policy refresh.
Log out after number of minutes of inactivity
Require password to unlock each secure Lock sensitive system preferences to prevent users who arent system preference administrators from changing them. This group policy requires users to provide an administrators password to unlock each secure system preference before they can make changes. If you enable this policy, users must provide an administrator password to access any secure system preference. If the current user is logged on as an administrator and this policy is not configured or disabled, the user can access and change secure system preferences without providing the administrator password. On Mac OS X Server 10.4 and 10.5, enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval.
102
Security
Use this policy Require smart card login
To do this Require all users to log in with a smart card. When this policy is enabled, no users can log in to the machine simply with a username and password. Note To require smart card login for a specific user rather than all users on the machine, in the users Active Directory account properties, specify the option, Smart card is required for interactive logon. The Enable smart card support policy must also be enabled in order for this policy to take effect. Once enabled, this group policy takes effect when the computer is rebooted. Prevent passwords from being recoverable from virtual memory. Any time a password is entered, it is possible for system to write that password in a block of memory that it dumps to a file in /var/vm, making the password recoverable. Enabling this group policy ensures that the virtual memory /var/vm files are encrypted, preventing any passwords written there from being recovered. On Mac OS X Server 10.4 and 10.5, enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval.
Use secure virtual memory
103
Services
Services
Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Services settings to manage access to the service options from the Sharing ( ) system preference on Mac OS X computers. These group policies correspond to the options displayed on the Services pane. For example:
Use this policy Enable Personal File Sharing
To do this Allow users on other Mac OS X computers access to Public folders on the local computer. If you enable this group policy, all users can access files in the Public folder through the Apple File Sharing protocol. Users with appropriate permission can also access other folders on the local computer if properly authenticated. On Mac OS X 10.6 and 10.7, enabling this group policy is the same as opening the Sharing system preference, selecting File Sharing, then clicking the Options button and selecting the Share Files and Folders using AFP option. On Mac OS X 10.5, enabling this group policy is the same as selecting the Personal File Sharing system preference, clicking the Options button, then selecting the Share Files and Folders using AFP option. To enable file sharing for FTP applications, see Enable FTP Access; to enable Windows file sharing (SMB/CIS file shares), see Enable Windows Sharing. On Mac OS X Servers, enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
104
Services
Use this policy Enable Windows Sharing
To do this Allow users on Windows computers access to shared folders on the local computer through SMB/CIFS file shares. On Mac OS X 10.6 and 10.7, enabling this group policy is the same as opening the Sharing system preference, selecting File Sharing, then clicking the Options button and selecting the Share Files and Folders using SMB option. On Mac OS X 10.5, enabling this group policy is the same as selecting the Personal File Sharing system preference, clicking the Options button, then selecting the Share Files and Folders using SMB option. To enable file sharing for FTP applications, see Enable FTP Access; to enable personal file sharing using the Apple File Protocol (AFP), see Enable Personal File Sharing. On Mac OS X Servers, this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Allow users on other computers to view Web pages in each users sites folder on the local computer. Enabling this group policy is the same as opening the Sharing system preference and selecting the Web Sharing option. On Mac OS X Servers, enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Allow users on other computers to access this computer using SSH. Enabling this group policy is the same as opening the Sharing system preference and selecting the Remote Login option. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Allow users on other computers to exchange files with this computer using FTP applications. On Mac OS X 10.6 and 10.7, enabling this group policy is the same as opening the Sharing system preference, selecting File Sharing, then clicking the Options button and selecting the Share Files and Folders using FTP option. On Mac OS X 10.5, enabling this group policy is the same as selecting the Personal File Sharing system preference, clicking the Options button, then selecting the Share Files and Folders using FTP option. To enable personal file sharing using the Apple File Protocol (AFP), see Enable Personal File Sharing; to enable Windows file sharing (SMB/CIS file shares), see Enable Windows Sharing. On Mac OS X Servers enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
Enable Personal Web Sharing
Enable Remote Login
Enable FTP Access
105
Services
Use this policy Enable Apple Remote Desktop
To do this Allow others to access this computer using the Apple Remote Desktop program. Enabling this group policy is the same as opening the Sharing system preference and selecting the Remote Management option. If you enable this group policy, you can set the following access privileges: Allow guest users to request permission to control the screen Prevent VNC viewers from controlling the screen. Because allowing VNC viewers to control the screen requires setting a password to take control of the screen and this behavior presents a potential security issue, this group policy can only be used to disallow VNC access. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Allow applications on other Mac OS X computers to send Apple Events to the local computer. Enabling this group policy is the same as opening the Sharing system preference and selecting the Remote Apple Events option. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Allow other people to use printers connected to the local computer. Enabling this group policy is the same as opening the Sharing system preference and selecting the Printer Sharing option. On Mac OS X Servers, enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer. Allow clustered Mac OS Xgrid controllers to distribute tasks to the local computer for completion. Enabling this group policy is the same as opening the Sharing system preference and selecting the Xgrid Sharing option. On Mac OS X Servers enabling this policy has no effect. This policy can take effect dynamically at the next group policy refresh interval without rebooting the computer.
Enable Remote Apple Events
Enable Printer Sharing
Enable Xgrid
106

Use the Computer Configuration > Policies > Centrify Settings > Mac OS X Settings > Software Update group policies to manage software updates. The group policies in this category enable you to set the interval for checking for software updates and to identify a specific server from which updates should be received. These group policies correspond to settings you make using the Software Update ( ) system preference on client Mac OS X computers and the Software Update preference in the Workgroup Manager on Mac OS X servers. For example, the interval for checking for software updates is typically configured Software Update system preference on client Mac OS X computers:
Identifying a software update server to use for downloading updates is configured on a Mac OS X server using the Software Update preference in the Workgroup Manager. For example:
Note
107
The software update group policies are machine policies, applied as the root user, and apply to all users of the machine. Setting these group policies updates the plist files for individual users with the group policy parameters, such as update server URL, update interval, and so on. However, to prevent local users from using Software Update in System Preferences to manually set software update server parameters, an administrator should also limit access to the Software Update Preferences Pane by setting the group policy, Limit items shown in System Preferences, and then enabling the group policy, Enable System Preferences Pane: System > Enable Software Update. Otherwise, you may see anomalous behavior, For example, a user can open Software Update and change parameters, such as disabling software updates (by deselecting Check for updates). If the user then re-enables software updates, the update server resets to the Apple software update server, not the server specified in the software update server group policy. However, at the next login, or at the next adgpupdate period, the Server URL and other group parameters will be re-applied. The Software Update Settings contain separate folders that allow you to specify a different update server for each Mac OS X version that you are running. For example, if have Mac OS X 10.5, 10.6, and 10.7 machines in your environment, you can specify a different update server for each one by enabling the Specify software update server policy in each of the version-specific folders. In order to do this you must enable Use version specific settings. If you do not enable Use version specific settings, Legacy Settings are used instead. If you applied Software Update Settings to machines running previous versions of DirctControl, those settings are in Legacy Settings, though you may update them if you wishe.
108
The Automatically download and install software updates policy applies to all machines, regardless of version.
Note Use this policy Automatically download and install software updates To do this Periodically check for updated versions of the software installed on the local computer and automatically download and install newer versions. If you enable this group policy, the Mac OS X computer will automatically check for software updates on a weekly basis by default. Enabling this group policy is the same as selecting Check for updates in the Software Update system preference. This policy has two parts: checking for updates, and downloading and installing. Checking for updates can take effect dynamically at the next group policy refresh interval. Downloading and installing requires a relogin of an AD user to the computer and running the adgpupdate command. Enable the use of version-specific settings. You can then set platform-specific preferences settings for each platform in your environment, which enables you to specify a different update server depending on the version of Mac OS X running on a machine. For example, if you have only 10.5 machines, you can enable this policy then use Mac OS X 10.5 settings. If you have 10.5, 10.6, and 10.7 machines, or any two of these, enable this policy, then configure the version-specific policies as appropriate: Mac OS X 10.5 Settings Mac OS X 10.6 Settings Mac OS X 10.7 Settings If this policy is disabled or not configured, Legacy Settings are used instead of version-specific settings. Likewise, DirectControl versions prior to 4.4.2 always use Legacy Settings and ignore this policy setting. If you configured Software Update Settings with a version of DirectControl prior to 4.4.2, these settings are saved to Legacy Settings when you upgrade to the current DirectControl version. You can keep or edit these settings as you wish.
Use version specific settings (Preferences)
Specify software update server (Legacy, Note that there are actually separate versions of this policy in version10.5, 106, 10.7) specific folders. This enables you to specify a separate update server based on the version of the Mac OS X machine. Type the URL that identifies the computer you are using as the software update server. It is recommended that you specify the hostname of the server rather than the IP address; for example:
http://myHost.local:8088
In addition, to ensure that DNS associates the hostname of the update server with the IP address, add a line such as the following to the /etc/hosts file:
192.168.2.79 myHost.local
where: 192.168.2.79 is the IP address of the update server and myHost.local is the hostname. This policy can take effect dynamically at the next group policy refresh interval.
109
Chapter 6

Centrify DirectControl group policies allow administrators to extend the configuration management capabilities of Windows Group Policy Objects to managed Mac OS X computers and to users who log on to Mac OS X computers. This chapter describes the Centrify DirectControl Mac OS X group policies that can be applied to Mac OS X users. The following topics are covered: Setting user-based policies for Mac OS X
802.1X Wireless Settings Application Access Settings Automount Settings Desktop Settings Dock Settings Finder Settings Folder Redirection Import Settings Login Settings Media Access Settings Mobility Synchronization Settings Scripts (Login/Logout) Security Settings System Preference Settings
The user-based group policies are defined in the Centrify DirectControl Mac OS X administrative template (centrify_mac_settings.xml) and accessed from User Configuration > Policies > Centrify Settings > Mac OS X Settings. See Chapter 4, Understanding group policies for Mac OS X users and computers, for general information about how DirectControl uses group policies to manage Mac OS X settings and for information on how to install the group policy administrative templates. For reference information about computer-based policies, see Chapter 5, Setting computer-based policies for Mac OS X. For information about applying standard Windows policies to Mac OS X, see Applying standard Windows policies to Mac OS X on page 68 and for information about Mac OS Xspecific parameters, see Configuring Mac OS X-specific parameters on page 69.
110
For more complete information about creating and using group policies and Group Policy Objects, see your Windows or Active Directory documentation. For more information about adding and using other Centrify DirectControl group policies that are not specific to Mac OS X computers and users, see the Centrify DirectControl Group Policy Guide.
Note
Chapter 6 Setting user-based policies for Mac OS X
111

The following table provides a summary of the group policies you can set for Mac OS X users. These group policies are in the Centrify DirectControl Mac OS X administrative template (centrify_mac_settings.xml) and accessed from User Configuration > Policies > Centrify Settings > Mac OS X Settings.
Note If your users and computers are in different organizational units, be certain to link the Group Policy Object to both OUs. Otherwise, if you link only to the computers OU, user policies will not be applied. Use this policy 802.1X Wireless Settings To do this Create user profiles for wireless authentication. This group policy corresponds to 802.1X Options in the Networks system preference. Control the specific applications users are either permitted to use or prohibited from using. These group policies correspond to Applications preferences set in the Workgroup Manager. Control the desktop and screen saver options for users on Mac OS X computers. These group policies correspond to settings in the Desktop & Screen Saver system preference. Control the look and operation of the Dock displayed on the users desktop. These group policies correspond to Dock preferences set in the Workgroup Manager. Specify whether to use the standard Mac OS X Finder, or the Simple Finder, which restricts users to applications and folders in the Dock. Redirect specified network home folders to the local machine to improve performance. Specify plist files to import preferences from another machine. This group policy corresponds to the import plist functionality in Workgroup Manager. Specify frequently used applications, folders, and server connections to open when a user logs in. This group policy corresponds to the login functionality in Workgroup Manager. Control the specific media types users are either permitted to use or prohibited from using. These group policies correspond to Media Access preferences set in the Workgroup Manager. Control the synchronization rules applied for users access services from mobile devices. These group policies correspond to Mobility preferences set in the Workgroup Manager.
Application Access Settings
Desktop Settings
Dock Settings
Finder Settings Folder Redirection Import Settings
Login Settings
Media Access Settings
Mobility Synchronization Settings
112
Use this policy Scripts (Login/Logout) Security Settings
To do this Specify login and logout scripts that run when Active Directory users log on or log out. Control the secure login options for users on Mac OS X computers. These group policies correspond to settings in the Security system preference. Control the specific system preferences displayed for users. These group policies correspond to System Preferences set in the Workgroup Manager.
System Preference Settings
113

Use the User Configuration > Centrify Settings > Mac OS X Settings > 802.1X settings to create profiles for wireless network authentication. The profiles you specify with these group policies are created in the Network system preferences pane.
Use this policy Specify User Profiles To do this Enable this policy to specify 802.1X User Profiles for wireless network authentication. Hwn using a user profile, a user will be prompted for username and password to authenticate to a wireless network after login. To add a user profile, enable the policy and click Add to enter the profile name and setting. Type a name for the profile. Setting must follow this format: Network;Security Type;Authentication Method, where each field is separated by a semi-colon (;). Network is the wireless network name Security type is one of 802.1X WEP, WPA Enterprise, WPA2
Enterprise
Authentication method is one or more of the following, separated by commas: TTLS, PEAP, TLS, EAP-FAST, LEAP, MD5 For example:
OFFICE1;WPA Enterprise;PEAP OFFICE2;802.1X WEP;TTLS,PEAP
114

Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Application Access Settings group policies to manage the applications Mac OS X users are allowed to open or prevented from opening.
Use this policy Permit/Prohibit access to applications To do this Select the applications that users are permitted to access or prohibited from accessing. You must enable this policy for any other application access group policies to take effect. Once enabled, only the applications explicitly specified in Application List policies are permitted or prohibited. If you enable this policy, in Access mode, select one of: Users can only open these applications to grant access only to the applications you select with the other application access policies. Users can open all applications except these to prevent access only to the applications you select with the other application access policies. You can also set the following options in this group policy: Select User can also open all applications on local volumes to allow access to applications on a computers local hard drive. If selected, users can access any local applications in addition to the applications explicitly approved using the other application access policies. If you uncheck this option, users can only access applications on CDs, DVDs, or external disks that have been explicitly approved. Select Allow approved applications to launch non-approved applications to allow approved applications to open applications that aren't explicitly approved. For example, if users click a link in an email message, this option allows the email application to open a browser to display the Web page even if the browser is not listed as an approved application. To prevent approved applications from opening applications that arent explicitly approved, uncheck this option. Select Allow UNIX tools to run to allow applications or the operating system to run tools, such as the QuickTime Image Converter, without explicitly listing them as approved applications. These tools usually operate in the background, but can be run from the command line. If you want to prevent access to these tools, do not check this option. Once enabled, this group policy takes effect when users log out and log back in.
115
Use this policy Permit/prohibit access to application list: Applications
To do this Select the specific applications in the Finders Applications folder that users are permitted to use if you selected Users can only open these applications, or not allowed to use if you selected Users can open all applications except these. This policy is only effective if the Permit/prohibit access to applications group policy is enabled. If the Permit/prohibit access to applications group policy is not configured or disabled, this group policy is ignored. On Mac OS X 10.5, selecting the following applications has no effect, that is, these applications cannot be specifically permitted or prohibited: Internet Connect Quick Time Broadcaster Sherlock Once enabled, this group policy takes effect when users log out and log back in. Select the specific applications in the Finders Applications/Utilities folder that users are permitted to use if you selected Users can only open these applications, or not allowed to use if you selected Users can open all applications except these. This policy is only effective if the Permit/prohibit access to applications group policy is enabled. If the Permit/prohibit access to applications group policy is not configured or disabled, this group policy is ignored. On Mac OS X 10.5, selecting the following applications has no effect, that is, these applications cannot be specifically permitted or prohibited: AirPort Admin Utility AirPort Setup Assistant Directory Utility Installer NetInfo Manager Printer Setup Utility Once enabled, this group policy takes effect when users log out and log back in. Select the specific applications in the Finders Applications/Server folder that users are permitted to use if you selected Users can only open these applications, or not allowed to use if you selected Users can open all applications except these. This policy is only effective if the Permit/prohibit access to applications group policy is enabled. If the Permit/prohibit access to applications group policy is not configured or disabled, this group policy is ignored. In addition, this policy is only applicable for Mac OS X Server computers. Once enabled, this group policy takes effect when users log out and log back in.
Permit/prohibit access to application list: Utilities
Permit/prohibit access to application list: Server
116
Use this policy Permit/prohibit access to application list: AppleScript
To do this Select the specific applications in the Finders Applications/AppleScript folder that users are permitted to use if you selected Users can only open these applications, or not allowed to use if you selected Users can open all applications except these. This policy is only effective if the Permit/prohibit access to applications group policy is enabled. If the Permit/prohibit access to applications group policy is not configured or disabled, this group policy is ignored. Once enabled, this group policy takes effect when users log out and log back in. Select the specific applications that are not in the Finders Applications folder but provide key functionality typically available on Mac OS X servers, such as AppleFileServer, JarLauncher, or BluetoothUIServer. Users are permitted to use the applications if you selected Users can only open these applications, or not allowed to use them if you selected Users can open all applications except these. This policy is only effective if the Permit/prohibit access to applications group policy is enabled. If the Permit/prohibit access to applications group policy is not configured or disabled, this group policy is ignored. On Mac OS X 10.5, selecting the following applications has no effect, that is, these applications cannot be specifically permitted or prohibited: BOMArchiveHelper Conflict Resolver Crash Reporter IM Plugin Converter mcxd MirrorAgent syncuid Once enabled, this group policy takes effect when users log out and log back in.
Permit/prohibit access to application list: Miscellaneous
117
Use this policy Permit/prohibit access to the userspecific applications
To do this Define a list of additional applications that users are permitted to run if you selected Users can only open these applications, or not allowed to use if you selected Users can open all applications except these. If enabled, you must specify the CFBundleIdentifier to identify the application; for example, for the Firefox browser, the CFBundleIdentifier is: org.mozilla.firefox. To find the CFBundleIdentifier complete the following steps:
1 In the Finder, locate the application to control. 2 Control-click or right-click the application, then select Show Package Contents. 3 If necessary, expand the Contents folder, then open info.plist with a text editor. 4 Find the string: <key>CFBundleIdentifier</key>. On the next line is the applications CFBundleIdentifier; for example: <string>org.mozilla.firefox</string> 5 Use org.mozilla.firefox to identify the Firefox browser.
To add an application to the list, select Enabled, then click Add and enter the CFBundleIdentifier and click OK. You may also control access to system preference panes by using the CFBundleIdentifier. You can find the CFBundleIdentifier for system preference panes in /System/Library/PreferencePanes. You can specify any application object that has a CFBundleIdentifier in its info.plist file. Note Some applications may not have a CFBundleIdentifier (when you right-click the application name, there is no Show Package Contents menu item). In this case, you cannot add the application to the list of permitted or prohibited applications. This policy is only effective if the Permit/prohibit access to applications group policy is enabled. If the Permit/prohibit access to applications group policy is not configured or disabled, this group policy is ignored. Once enabled, this group policy takes effect when users log out and log back in.
These group policies correspond to settings you can make using the Applications preference in the Workgroup Manager. For example, on a Mac OS X server with the Workgroup
118
Manager installed, you would open the Workgroup Manager, click View > Preferences, then click the Applications icon to display these settings:
119
Automount Settings
Automount Settings
Use the Automount Settings to automatically mount network shares and the users Windows home directory when a user logs in.
Use this policy Automount network shares To do this Specify the network shares to automatically mount when a user logs in. This policy creates links to network shares on the users desktop and dock. This policy supports SMB, AFP, and NFS shares. To add a share, click Enabled, then click Add and enter the share in one of the following formats: keyword://server/share where: keyword is one of smb, nfs, afp server is the name or IP address of the server and can include a user or user and password in the form: user:@server or user:password@server. share can include spaces and be followed by a subdirectory. For example, the following are all valid share specifications;:
smb://acme.com/MacUsers smb://acme.com/Mac Users smb://acme.com/MacUsers/Shared_resources smb://jsmith:[email protected]/MacUsers afp://acme.com/Users_server nfs://acme.com/MacUsers nfs://192.168.0.1/MacUsers
Once enabled, this policy takes effect when a user logs out and back in to a machine. Automount users Windows home Automatically mount the users Windows home directory when the user logs in. Specify the Windows home directory by using the Profile tab for a user in Active Directory Users and Computers (ADUC). Once enabled, this policy takes effect when a user logs out and back in to a machine.
120
Desktop Settings
Desktop Settings
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Desktop Settings group policy to manage the start time for the screen saver from the Desktop & Screen Saver ( ) system preference on Mac OS X computers. This group policy corresponds to the Start screen saver option displayed on the Screen Saver pane. For example:
Use this policy Set computer idle time for starting screen saver
To do this Select the length of time to wait before starting the screen saver. If you enable this group policy, you can specify the number of minutes to wait while a computer is not in use before starting the screen saver. For example, if you want the screen saver to start after a computer has been idle for 10 minutes, you can set Start screen saver to 10 minutes. Note Disabling this policy does not disable the screen saver. To disable the screen saver, enable this policy and set the value to 0. Note Although you may specify values greater than 60 minutes, and the screen saver works appropriately, the Macintosh Screen Saver dialog box shows values that are greater than 60 as Never. Enabling this group policy is the same as selecting when to start the screen saver using the Start screen saver slider in the Desktop & Screen Saver system preference. Once enabled, this group policy takes effect when users log out and log back in.
121
Dock Settings
Dock Settings
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Dock Settings group policies to manage the characteristics of the Dock for Mac OS X users. These settings correspond to the Dock preferences you can manage using the Workgroup Manager. In the Workgroup Manager, the Dock Items pane controls the items placed in the Dock and whether the workgroup Dock is merged with the users Dock, and
122
Dock Settings
the Dock Display pane controls attributes such as the Dock size, magnification, position, and animation. For example:
Use this policy Add other folders to the Dock
To do this Add icons for the other commonly-used folders to the Dock. You can choose to add the following folder icons to the Dock: My Applications Documents The My Applications folder contains aliases to all approved applications you have defined in the Application list. If you do not manage access to applications, all available applications are included in the My Applications folder. If you enable Simple Finder, you should display the My Applications folder. The Documents folder is the Documents folder found in the users home folder. For example, the /Users/username/Documents folder for local user accounts. Once enabled, this group policy takes effect when users log out and log back in. Set the approximate size of Dock icons in pixels. The valid settings for the Dock size range from 16 pixels (small) to 128 pixels (large). The default size is 80 pixels. Note This setting is approximate because the actual size of Dock icons depends on screen resolution and the number of icons in the Dock. Once enabled, this group policy takes effect when users log out and log back in.
Adjust the Docks icon size
123
Dock Settings
Use this policy Adjust the Docks magnified icon size
To do this Set the level of magnification to use for items in the Dock. If you enable this group policy, icons in the Dock are magnified to display in a larger size as the pointer moves over them. The valid settings for Dock magnification range from 16 pixels for minimum magnification to 128 pixels for maximum magnification. The default size is 80 pixels. If you do not configure or disable this group policy, icons in the Dock are not magnified when the pointer moves over them. Once enabled, this group policy takes effect when users log out and log back in. Specify the location for displaying the Dock on the screen. If you enable this group policy, you can position the Dock on the left, bottom, or right of the screen. The default location for displaying the Dock is at the bottom of the screen. Once enabled, this group policy takes effect when users log out and log back in. Specify the effect to use when a window or application is minimized and placed in the Dock. The valid effects are: Genie Scale Suck Once enabled, this group policy takes effect when users log out and log back in. Animate application icons so that the icon displayed in the Dock bounces when the user opens the application. Once enabled, this group policy takes effect when users log out and log back in.
Adjust the Docks position on screen
Adjust the effect shown when minimizing the Dock
Animate opening applications
Automatically hide and show the Dock Hide the Dock from view automatically. If you enable this policy, the Dock is hidden during normal operation. The Dock is then automatically displayed again if the pointer moves over the position on the screen where the Dock is located. Once enabled, this group policy takes effect when users log out and log back in. Lock the Dock Lock the applications displayed in the Dock. If you enable this policy, icons cannot be moved into or out of the Dock. Once enabled, this group policy takes effect when users log out and log back in.
124
Dock Settings
Use this policy Place applications in Dock
To do this List the applications to include in the Dock. After you enable this policy, click Add to enter the path to the application you want included in the Dock. Then click OK. You can click Add again to add additional applications. For example, to add Firefox and Chess icons to the Dock, type the application paths:
/Applications/Firefox.app
Click OK. Then click Add and enter:

/Applications/Chess.app
The icons for the applications you specify are placed to the left or above the separator line in the Dock in the order you enter them, up to 10 items. if you add more than 10 the order may be random. If the path to an application is incorrect, a question mark (?) is displayed in the Dock in place of the applications icon. Note This group policy does not sort icons from the initial system list. To sort these items, such as the Mail application icon, you can add the item to the list. Once enabled, this group policy takes effect when users log out and log back in. Place documents and folders in Dock List the documents or folders to include in the Dock. After you enable this policy, click Add to enter the path to the folder or document you want to include in the Dock. Then click OK. You can specify additional folders or documents by clicking Add again. For example, to add the Users folder and the Copyright.txt document to the Dock, type the paths to each:
/Users
Click OK, then click Add and type:

/Documents/Copyright.txt
The icons for the items you specify are placed to the left or above the separator line in the Dock. Items are sorted in the order you enter them up to 10 items. If you specify more than 10 items the order may be random. If the path to an item is incorrect, a question mark (?) is displayed in the Dock. Note You may not specify the path to a network share; for example, smb://serverName. Network share paths are implemented as aliases, which work differently than folder and document paths. If you specify a network share, a question mark (?) is displayed in the Dock. Once enabled, this group policy takes effect when users log out and log back in. Merge with users Dock Merge the Workgroup Dock settings with the users Dock. Once enabled, this group policy takes effect when users log out and log back in.
125
Finder Settings
Finder Settings
Use the User Configuration> Policies > Centrify Settings > Mac OS X Settings > Finder Settings group policies to configure Finder commands, preferences and views. The Configure Finder commands policy allows you to control which commands are available in the Apple menu and Finder menus for users. The Configure Finder preferences policy enables you to specify the type of Finder for the user environment. After enabling the policy, you can choose one of two types from the drop-down list: Normal Finder applies the standard Mac OS X desktop. This is the default value, and is the environment that all users will have if the policy is not enabled.
Simple Finder restricts users to applications that are in the Dock.
When Simple Finder is enabled, users cannot open applications, open, modify, or delete documents, or create folders in the Finder. They also cannot mount network drives. They can only use items that are in the Dock. Use the Dock Settings policies to configure the Dock; for example, enable Place applications in Dock and Place documents and folders in Dock to control the applications and folders that users can access. The Configure Finder views policy enables you to control the arrangement and appearance of items on the users desktop, in Finder windows, and in the top-level folder of the computer.
126
Finder Settings
The Finder Settings policies are as follows:

Use this policy Configure Finder commands To do this Specify the commands in Finder menus and the Apple menu that are available to users. Select commands from the following list: Connect to Server Select to allow users to connect to a remote server by choosing 'Connect to Server' in the Finder Go menu. Deselect to prevent users from accessing this command. Go to iDisk Select to allow users to connect to an iDisk by choosing 'Go to iDisk' in the Finder Go menu. Deselect to prevent users from accessing this command. Eject Select to allow users to eject discs (for example, CDs, DVDs, floppy disks, or FireWire drives). Deselect to prevent users from ejecting disks. Burn Disc Select to allow user on computers with relevant hardware to burn discs. Deselect to prevent users from burning disks. Go to Folder Select to allow users to open a specific folder by choosing the 'Go to Folder' command in the Finder Go menu. Deselect to prevent users from using the 'Go to Folder' command. Restart Select to allow users to restart the computer they're using, or deselect to prevent them from restarting the computer. Shut Down Select to allow users to shut down the computer they're using, or deselect to prevent them from shutting down the computer. Once enabled, this group policy takes effect when users log out and back in.
127
Finder Settings
Use this policy Configure Finder preferences
To do this Configure Finder preferences, including whether to use normal or Simple Finder, which items to show on the desktop, how a new window behaves, and whether to show filename extensions and the Empty Trash warning. Select from the following options: Finder type Select the normal Finder or Simple Finder as the user environment. The normal Finder looks and acts like the standard Mac OS X desktop. Simple Finder removes the ability to use a Finder window to access applications or modify files, limiting users' access to only what is in the Dock. In addition, users can't mount network volumes, create folders, or delete files. Show these items on the Desktop Choose whether users see icons for local hard disks, external disks, CDs (DVDs and iPods), and connected servers on the desktop. If you hide them, icons for disks and servers still appear in the top-level folder when a user clicks the Computer icon in a Finder window's toolbar. New Finder window shows Select Home to show items in the user's home folder, or select Computer to show the top-level folder, which includes local disks and mounted volumes. Always open folders in a new window Select this option to display folder contents in a separate window when a user opens a folder. Always open windows in column view Select this option to display folders in column view, which maintains a consistent view across windows. Show warning before emptying the Trash Select this option to display the normal warning when a user empties the Trash, or deselect it if you don't want users to see this message. Always show file extensions Select this option to show filename extensions (such as .txt or .jpg) that identify the file type; or deselect it to hide filename extensions. Once enabled, this group policy takes effect when users log out and back in.
128
Finder Settings
Use this policy Configure Finder views
To do this Enable this group policy to control Finder views, for example the arrangement and appearance of items on a user's desktop, in Finder windows, and in the top-level folder of the computer. The options in Desktop View allow you to adjust the size and arrangement of icons on the desktop. Use Icon Size to adjust the icon size. Use Icon Arrangement to specify how to arrange icons: To keep items aligned in rows and columns, select Snap to grid. To arrange items by criteria such as name or type (for example, all folders grouped together), select Keep arranged by .... Items in Finder windows are viewed in a list or as icons and you can control aspects of how these items look. 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 drives, mounted volumes, and removable media (such as CDs or DVDs). In Icon View, use Icon Size to adjust the size of icons. Use Icon Arrangement to specify how to arrange icons: To keep items aligned in rows and columns, select Snap to grid. To arrange items by criteria such as name or type (for example, all folders grouped together), select Keep arranged by .... In List View, set the following: Select relative dates to show an item's creation or modification date relative to today, rather than as a fixed date; for example, Today, or Yesterday, instead of 3/24/10. Select Calculate folder sizes to calculate the total size of each folder shown in a Finder window, which can take a lot of time depending on the size of the folder. In Icon Size, select Select small or big for the size of icons in list view. Once enabled, this group policy takes effect when users log out and back in.
129
Folder Redirection
Folder Redirection
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Folder Redirection group policies to redirect specified folders from a network home directory to the local machine. When you set up a network home directory, Mac OS X writes all home directory files to the network share. Some folders, such as /Library/Caches, get heavy I/O from Apple and third-party applications, which may cause performance issues. The folder redirection policies enable you to redirect specific folders, such as /Library/Caches, to the local machines, which can result in dramatic performance improvements. Folder Redirection contains two folders with identical sets of four policies: Folder redirection actions at login time applies the specified policy when the user logs in. For example, at login delete a folder in the network home directory and create a symbolic link to it on the local machine.
Folder redirection actions at logout time applies the specified policy when the user logs out. For example, at logout, delete the symbolic link on the local machine (created at login) and restore the original folder to the network home directory.
After enabling the policy, click Add, then enter the following: Path The path to the folder on the network share. You do not need to specify the actual network share location you can simply use the tilde (~) for the users home directory; for example, ~/Library/Caches specifies the /Library/Caches directory in the users network home directory.
Link The location to create or delete on the local machine. For example:
/tmp/Library/Caches
If you wish, you can use the syntax %@ to specify the logged in users name. For example:
/tmp/%@/Library/Caches
If cain is the logged in user, the folder that is created is:

/tmp/cain/Library/Caches
130
Folder Redirection
The Folder Redirection policies are as follows:

Use this policy Delete path To do this Deletes the specified directory from the network home directory. For example, to delete the /Library/Caches file from each users home directory, enter the following in the Path box:
~/Library/Caches
Typically, you enable this policy for the login time folder. Note You are not required to enter anything in the Link box for this group policy, and in fact, anything you enter in this box will be ignored. All the policies in this folder are implemented with the same UI and the other policies require the Link box so it appears for this policy as well. Once this group policy is enabled, it takes effect when users log in (enabled for login time folder) or log out (enabled for logout time folder). Delete symbolic link and restore Deletes a previously defined symbolic link on the local machine and restores the specified directory to the network home directory. Typically, you use this policy with the Rename and create symbolic link policy. For example: At login (using Rename and create symbolic link) you save ~/Library/Caches in the network home directory to a temporary folder and redirect it to a folder on the local machine, for example /tmp/user/Library/Caches. At logout, you can enable Delete symbolic link and restore to delete the symbolic link and restore the folder on the network home directory, by specifying the following: Path: ~/Library/Caches Link: /tmp/%@/Library/Caches where: %@ specifies the logged in users name on the local machine. Once this group policy is enabled, it takes effect when users log in (enabled for login time folder) or log out (enabled for logout time folder). Deletes the specified directory from the network home directory and creates a symbolic link to it on the local machine. For example, to delete the users /Library/Caches policy from the network home directory and create a link to it on the local machine, specify the following after enabling the policy: Path: ~/Library/Caches Link: /tmp/%@/Library/Caches where %@ specifies the logged in users name on the local machine. For example, if cain is the logged in user, the cache files are written to:
Delete and create symbolic link
Once this group policy is enabled, it takes effect when users log in (enabled for login time folder) or log out (enabled for logout time folder).
131
Folder Redirection
Use this policy Rename and create symbolic link
To do this Renames the specified directory in the network home directory to a temporary folder and creates a symbolic link to it on the local machine. For example, to rename the users /Library/Caches policy on the network home directory and create a link to it on the local machine, specify the following after enabling the policy for the login time folder: Path: ~/Library/Caches Link: /tmp/%@/Library/Caches where %@ specifies the logged in users name on the local machine. For example, if cain is the logged in user, the cache files are written to:
To restore the original /Library/Caches directory, use the Delete symbolic link and restore policy (enabled for the logout time folder). Once this group policy is enabled, it takes effect when users log in (enabled for login time folder) or log out (enabled for logout time folder).
132
Import Settings
Import Settings
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Import Settings group policy to import plist files to customize your preferences. Mac OS X uses plist files to store application and other preferences. The Import plist files group policy allows you to import preferences from another machine to machines in your DirectControl-managed domain. To do so you Copy the plist files you want to use to the system volume on the domain controller
Use the Import plist files group policy to import the plist files to machines in the domain.
When you import the plist files, Centrify DirectControl copies them to the appropriate directories on the local machines to implement the preferences that they control. You can gather and copy plist files from multiple machines and paste them to the sysvol directory on the domain controller, but a more structured approach is to set up a preferences template machine, that is, a machine that is set up with your desired preferences. Then you can copy the appropriate plist files to sysvol on the domain controller. Finally, you can use Import plist files to import the plist files to DirectControlmanaged machines in the domain. Mac OS X stores plist files in the /Library/Preferences directory and in the /Users/userName/Library/Preferences directory. The following table shows specifics of using this group policy.
Use this policy Import plist files To do this Specify the names of plist files to import from the system volume (SYSVOL) similar to importing plist files in Mac Workgroup Manager. By default, the system volume folder is at: \\domain\SYSVOL\domain\plist. Before enabling this policy, you should copy all the plist files to import to the system volume (sysvol) on the domain controller. To add a file, select Enabled, click Add, then type a filename. The path you type in plist file is relative to \\domain\SYSVOL\domain\plist. For example, if the domain name is ajax.org and you enter a plist file named com.apple.MCX.plist, the file that gets imported is:
\\ajax.org\sysvol\ajax.org \com.apple.MCX.plist
You can specify additional relative directories in the path, if needed. Once this group policy is enabled, it takes effect when users log out and log back in.
133
Login Settings
Login Settings
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Login Settings group policy to specify frequently used items, such as applications, folders, or server connections to automatically open when a user logs in. After enabling this policy, you can do the following: Use the Add button to specify the path to applications to open.
In the Network Home area, use the Add button to specify URLs for servers to connect to; use the check box to specify whether to automatically connect the logged in user to the specified servers. Use the other check boxes to control whether users have the ability to add or remove login items.
The following table shows specifics of using this group policy.
134
Login Settings
Only the Login items area is visible when you first open the properties page for thie group policy. Use the scroll bar to see the Network share area and other items that you can configure with this policy.
Note Use this policy Enable login items To do this Specify the names of applications, folders, and server locations to open automatically when a user logs in. Select Enable, then do any or all of the following: Login items. To add an application to open automatically, click Add, then type the path to the application; for example:
/Applications/TextEdit.app
To initially hide the application, select Hide. The application will open, but its window and menu bar remain hidden until the user activates the application (for example, by clicking the application icon in the doc). Click OK to save the item you entered. You can click Add as often as necessary to add multiple applications. You can also select an item in the window and click Edit to change it, or Remove to delete it. Network share. To add access to a network share, click Add, then type the URL in one of the following formats:
smb://server/share smb://server/hidden$ smb://server/share/subdir smb://user:password@server/share smb://user:@server/share afp://server/share nfs://server/share nfs://192.168.0.1/share
To automatically connect the user to the share with the user's login name and password, select Authenticate selected share point with users login name and password. Note If you uncheck this option, the share name must comply with RFC1738 - Uniform Resource Locators (URL), which specifies that special characters need to be encoded, for example, by using %20 instead of a space.
135
Login Settings
Use this policy Enable login items (continued)
To do this If the network share can be authenticated using Kerberos, this option can be ignored. If the network share cannot be authenticated using Kerberos, and this option is unchecked, then the user will be prompted for a username and password. If a username is specified in the URL for the network share, then checking this option will still mount the share as the login user, while unchecking this option will mount the share as the user specified in the URL. For example, if network share is smb://mount_user:password@server/share, checking the option will mount the share as login_user, while unchecking the option will mount the share as mount_user. Click OK to save the item you entered. You can click Add as often as necessary to add multiple shares. You can also select an item in the window and click Edit to change it, or Remove to delete it. Select User may add and remove additional items to allow users to add items to the list and remove items from the list. Deselect this box to prevent users from adding items or removing the items that you have specified. Note that they can remove login items that they specified on their own. Select User may press Shift to keep items from opening to allow users to stop items from opening by holding down the Shift key during login until the Finder appears on the desktop. Deselect this option to prevent users from stopping applications from opening automatically. Once enabled, this group policy takes effect when users log out and log back in.
136

Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Media Access Settings group policies to manage the access to discs and other media for Mac OS X users. These group policies enable you to control access to specific types of media, such as CDs or DVDs, but you cannot restrict access to specific discs or to specific items, such as music or movies, on a disc type users are permitted to access. These settings correspond to the Media Access preferences you can manage using the Workgroup Manager. For example:
Use this policy Permit/prohibit access: CDs and CDROMs
To do this Control whether users can access data and applications on CDs and CDROMs. The valid options are: allow to allow access to CDs and CD-ROMs without authentication. allow, require authentication to require users to provide credentials for authentication before allowing them access to CDs and CD-ROMs. deny to prevent users from accessing any data or applications on CDs and CD-ROMs. Once enabled, this group policy takes effect when users log out and log back in. Control whether users can access data and applications on DVDs. The valid options are: allow to allow access to DVDs without authentication. allow, require authentication to require users to provide credentials for authentication before allowing them access to DVDs. deny to prevent users from accessing any data or applications on DVDs. Once enabled, this group policy takes effect when users log out and log back in.
Permit/prohibit access: DVDs
137
Use this policy Permit/prohibit access: Recordable Discs
To do this Control whether users can record or access data and applications on recordable discs. The valid options are: allow to allow access to recordable discs without authentication. allow, require authentication to require users to provide credentials for authentication before allowing them access to recordable discs. deny to prevent users from accessing any data or applications on recordable discs. Allowing users access to recordable discs enables users to burn CDs and DVDs. Recordable discs can be blank or rewritable disc media. Once enabled, this group policy takes effect when users log out and log back in. Control whether users can access data and applications on internal discs. The valid options are: allow to allow read and write access to internal discs without authentication. allow, read-only to allow read-only access to the media. allow, require authentication to require users to provide credentials for authentication before allowing them access to the media. allow, require authentication, read-only to require users to provide credentials for authentication before allowing them access to internal discs, and grant read-only access to the media if authentication is successful. deny to prevent users from accessing any data or applications on internal discs. On Mac OS X 10.4, once enabled, this group policy takes effect when users log out and log back in. On Mac OS X 10.5, once enabled, this group policy takes effect when the computer is rebooted.
Permit/prohibit access: Internal Discs
138
Use this policy Permit/prohibit access: External Discs
To do this Control whether users can access data and applications on external discs. External disks include floppy disks, FireWire drives, and all other external storage devices except CDs and DVDs. The valid options are: allow to allow read and write access to external discs without authentication. allow, read-only to allow read-only access to external discs. allow, require authentication to require users to provide credentials for authentication before allowing them access to external discs. allow, require authentication, read-only to require users to provide credentials for authentication before allowing them access to external discs, and grant read-only access to the media if authentication is successful. deny to prevent users from accessing any data or applications on external discs. Once enabled, this group policy takes effect when users log out and log back in. Control whether removable media, such as CDs, DVDs, Zip disks, or FireWire drives, are automatically ejected when users log out. If you enable this group policy, CDs, DVDs, and other disk media are automatically ejected when users log out to ensure removable media is properly disconnected and put away when users end their sessions. Once enabled, this group policy takes effect when users log out and log back in.
Eject all removable media at logout
139

Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Mobility Settings group policies to manage the synchronization rules for mobile Mac OS X users. These settings correspond to the Mobility preferences you can manage using the Workgroup Manager. The group policy categories correspond to panes in the Workgroup Manager. For example:
The user interface for Mobility Settings differs significantly between different versions of Mac OS X. Therefore, DirectControl provides separate Mobility Settings policies for each version of Mac OS X that it supports. In addition, to support existing installations that configured group policies by using a previous centrifydc_mac_settings template, DirectControl provides a set of legacy mobility settings. The Use version specific settings group policy determines whether to use legacy settings or platform-specific mobility settings. By default (if you do not configure or disable this policy) DirectControl uses legacy settings.
140
If you enable this policy, you can then enable platform-specific mobility settings for each platform in your environment; see the following sections for information on each set of policies:
Use this policy Use version specific settings To do this Enable the use of version-specific settings. If you enable this policy, you can then set platform-specific mobility settings for each platform in your environment. For example, if you have only 10.5 machines, you can enable this policy then use Mac OS X 10.5 settings. If you have 10.5, 10.6, and 10.7 machines, or any two of these, enable this policy, then configure the version-specific policies as appropriate: Mac OS X 10.5 Settings Mac OS X 10.6 Settings Mac OS X 10.7 Settings When a machine joins the domain, DirectControl determines the Mac OS X version and applies the appropriate Mobility settings. If this policy is disabled or not configured, Legacy Settings are used instead of version-specific settings. Likewise, DirectControl versions prior to 4.4.2 always use Legacy Settings and ignore this policy setting. If you configured Mobility Synchronization settings with a version of DirectControl prior to 4.4.2, these settings are saved to Legacy Settings when you upgrade to the current DirectControl version. You can keep or edit these settings as you wish. Note The Legacy Settings may not match exactly the settings for each Mac OS X version; for example, some settings may be missing while others may be redundant for a particular OS version. Configure Legacy Settings.
Mobility Synchronization Legacy Settings
Mobility Synchronization Mac OS X 10.5 Configure Mac OS X 10.5 Settings. Settings Mobility Synchronization Mac OS X 10.6 Configure Mac OS X 10.6 Settings. Settings System Preferences Mac OS X 10.7 Settings Configure Mac OS X 10.7 Settings.
When the Centrify DirectControl Administrators Console is running on Windows 2000 SP4 or Windows 2003, some of the mobility synchronization policies cannot be set to disabled, including:
Notes
Skip items Sync in the background Sync at login and logout
141
This problem is corrected on Windows 2003 if Service Pack 1 or later is applied to the machine on which the Administrators Console is running.
Mobility Synchronization Legacy Settings

When you upgrade from a version of DirectControl prior to 4.4.2, your Mobility Synchronization settings are saved to Legacy Settings. You can keep or edit the individual legacy mobility group policy settings as you wish.
Note The legacy settings may not match exactly the settings for each Mac OS X version; for example, some settings may be missing while others may be redundant for a particular OS version. Use this policy Enable/disable synchronization To do this Create mobile accounts for users automatically and synchronize mobile accounts for offline use. If you enable this policy, a mobile account is created the next time the user logs into the network account. Check the Require confirmation before creating a mobile account option if you want the user to be prompted to confirm the creation of the mobile account. Check Encrypt contents with FileVault to encrypt the mobile home directory using the Mac OS X FileVault system. Note FileVault protection can only be applied when a new mobile user is created at login. FileVault protection cannot encrypt an existing mobileuser home directory. Select one of the computer master password options. The computer master password is a safety feature that allows you to unlock the FileVault disk image if the Active Directory user forgets their password: Use computer master password, if available With this option checked, the mobile account will be created and FileVault protection applied whether or not a computer master password is available. Require computer master password With this option checked, the mobile user account will only be created if a master password is available for the computer. You can create a master password by clicking: System Preferences > Security > FileVault > Set Master Password. This group policy corresponds to settings you make by opening Mobility preferences, then clicking the Synchronization pane in the Workgroup Manager. Once enabled, this group policy takes effect when users log out and log back in. Specify the folders to synchronize in the background for users with mobile accounts. You can also choose to skip synchronization for items matching the criteria you define. Group policies in this category correspond to settings you make by opening Mobility preferences, clicking Rules, then clicking the Background Sync pane in the Workgroup Manager. Settings in this category only apply to mobile accounts on Mac OS X 10.4 and later.
Synchronization Rules: Background Sync See Setting synchronization rules for background synchronization on page 143 for details on the policies in this folder.
142
Use this policy Synchronization Rules: Login & Logout Sync See Setting synchronization rules for login and logout on page 146 for details on the policies in this folder.
To do this Specify the folders to synchronize at login and logout for users with mobile accounts. You can also choose to skip synchronization for items matching the criteria you define. Group policies in this category correspond to settings you make by opening Mobility preferences, clicking Rules, then clicking the Login & Logout Sync pane in the Workgroup Manager. Settings in this category only apply to mobile accounts on Mac OS X 10.4 and later. Select whether you want to synchronize background folders manually or automatically at a specific interval. Group policies in this category correspond to settings you make by opening Mobility preferences, clicking Rules, then clicking the Options pane in the Workgroup Manager. Settings in this category only apply to mobile accounts on Mac OS X 10.4 and later.
Synchronization Rules: Options See Setting synchronization rules for manual or automatic synchronization on page 148 for details on the policies in this folder.
Setting synchronization rules for background synchronization
Use the group policies in the Synchronization Rules: Background Sync category to choose the folders that should be synchronized in the background for users with mobile accounts. You can also use the Skip these items group polices to define criteria for folders
143
that should not be synchronized in the background. These group policies only apply to mobile accounts on Mac OS X 10.4 and later.
Use this policy Enable/disable background synchronization rules To do this Enable or disable background synchronization for mobile user accounts. You can set the following options with this policy: Check Merge with users settings if you want items selected by the user for background synchronization to be added to the synchronization list. Check Synchronize users home directory if you want to synchronize the users home directory when background synchronization takes place. Check Skip preset items if you want to automatically skip synchronization for items that usually do not require synchronization. Selecting this option enables the Skip items whose full path is policy with a default list of items to skip. If you select the Skip preset items option, the Skip items whose full path is policy is configured by default to skip the following items:
~/Library ~/.Trash
Once enabled, this group policy takes effect when users log out and log back in.
144
Use this policy Adjust items that will be synchronized in the background
To do this Specify the folders to synchronize in the background for users with mobile accounts. If you enable this group policy, click Add and type a relative path to the files and folders that should be synchronized, then click OK. The path should not start with the slash (/) character. If the path you specify does not start with the relative path designation (~), the client adds ~/ to the front of the path. You can specify multiple paths by separating each path with a comma, or by clicking Add and typing a path multiple times. For example:
~/.bash_profile,~/Documents/offline
Note On Mac OS X 10.5, this policy is not enforced reliably. When the Centrify DirectControl Administrators Console is running on Windows 2000 SP4 or Windows 2003, this policy cannot be set to disabled. This problem is corrected if Service Pack 1 or later is applied to the machine on which the Administrators Console is running. This policy requires the Enable/disable background synchronization rules policy to be enabled. Once this group policy is enabled, it takes effect when users log out and log back in. Skip these items Set the criteria to identify folders that should not be synchronized in the background for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. If you enable any of these group policies, click Show, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable/disable background synchronization rules policy to be enabled. Note When the Centrify DirectControl Administrators Console is running on Windows 2000 SP4 or Windows 2003, this policy cannot be set to disabled. This problem is corrected if Service Pack 1 or later is applied to the machine on which the Administrators Console is running. Once any of there policies are enabled, they take effect when users log out and log back in.
145
Setting synchronization rules for login and logout
Use the group policies in the Synchronization Rules: Login & Logout Sync category to choose the folders that should be synchronized when users with mobile accounts login and logout. You can also use the Skip these items group polices to define criteria for folders that should not be synchronized when mobile users login and logout. These group policies only apply to mobile accounts on Mac OS X 10.4 and later.
Use this policy Enable/disable login & logout synchronization rules To do this Enable or disable synchronization at login and logout for mobile user accounts. You can set the following options with this policy: Check Merge with users settings if you want items selected by the user for synchronization at login and logout to be added to the synchronization list. You should uncheck this option if you want to prevent users from adding items to the synchronization list in their local system preferences that override items you do not want to be synchronized. Check Skip preset items if you want to automatically skip synchronization for items that usually do not require synchronization. Selecting this option enables the Skip items that start with and Skip items whose full path is policies with a default list of items to skip. If you select the Skip preset items option, the Skip items whose full path is policy is configured by default to skip the following items:
~/Library/Application Support/SyncServices ~/Library/Caches ~/Library/Logs ~/Library/Preferences/ByHost ~/Library/Printers ~/Library/Safari/Icons ~/Library/Preferences/com.apple.dock.plist ~/Library/Preferences/com.apple.iChatAgent.plist ~/Library/Preferences/com.apple.sidebarlists.plist ~/Library/Preferences/com.apple.systemuiserver.plist ~/Library/Preferences/loginwindow.plist
If you select the Skip preset items option, the Skip items that start with policy is configured by default to skip items that start with:
IMAPMac-
Once enabled, this group policy takes effect when users log out and log back in.
146
Use this policy Adjust items that will be synchronized at login and logout
To do this Specify the folders to synchronize when mobile users log in and log out. If you enable this group policy, click Show, then click Add and type a relative path to the files and folders that should be synchronized at login and logout, then click OK. The path should not start with the slash (/) character. If the path you specify does not start with the relative path designation (~), the client adds ~/ to the front of the path. You can specify multiple paths by separating each path with a comma. For example:
~/.bash_profile,~/Documents/offline
This policy requires the Enable/disable login & logout synchronization rules policy to be enabled. Note On Mac OS X 10.5, this policy is not enforced reliably. When the Centrify DirectControl Administrators Console is running on Windows 2000 SP4 or Windows 2003, this policy cannot be set to disabled. This problem is corrected if Service Pack 1 or later is applied to the machine on which the Administrators Console is running. Once this group policy is enabled, it takes effect when users log out and log back in. Skip these items Set the criteria to identify folders that should not be synchronized when mobile users log in and log out. These group policies allow you to specify a string that identifies files and folders to skip during synchronization at login and logout: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Note that this policy applies to all items in the specified directory, but not to items in subdirectories. To skip items in subdirectories, either explicitly add the subdirectories; for example:
~/Library/Caches, ~/Library/Logs
or use the next policy, Skip items whose partial path matches, which will skip items in any directory whose path includes the specified string. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. For example,
~/Library
skips items in ~/Library and in all its subdirectories; or:

~/Caches
skips items in ~/Library/Caches, ~/Users/jrich/Caches, and so on.
147
Use this policy
To do this If you enable any of these group policies, click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable/disable login & logout synchronization rules policy to be enabled. Note When the Centrify DirectControl Administrators Console is running on Windows 2000 SP4 or Windows 2003, this policy cannot be set to disabled. This problem is corrected if Service Pack 1 or later is applied to the machine on which the Administrators Console is running. Once any of these policies are enabled, they take effect when users log out and log back in.
Setting synchronization rules for manual or automatic synchronization
Use the group policy in the Synchronization Rules: Options category to specify when to synchronize folders in the background. You can choose to synchronize folders manually or automatically at a specific interval. This group policy only apply to mobile accounts on Mac OS X 10.4 and later.
Use this policy Manually/automatically synchronize background folders To do this Select whether background synchronization for mobile user accounts should be initiated manually or automatically at a set interval. If you enable this group policy, select whether synchronization should be initiated automatically or manually. If you initiate background synchronization automatically, you can also specify how frequently folders should be synchronized. You can set frequency from every 5 minutes to every 60 minutes. The default interval is 20 minutes. In setting the background synchronization interval, you should take into account the network bandwidth and the number of concurrent users the Mac OS X server supports. If you set background synchronization to occur at a short interval, such as every 5 minutes, and there are many concurrent users, you may overload the server. For example, the server may become backlogged by the too-frequent comparison of file modification dates. If you set background synchronization to occur less frequently, for example every 60 minutes, users may load older, outdated files. For example, if a user saves changes to a file and logs off before files are synchronized at the next interval, when the user loads that same file on another computer, he may get an older version of the file or no file at all. Once enabled, this group policy takes effect when users log out and log back in.
Mobility Synchronization Mac OS X 10.5 Settings

The Mac OS X 10.5 Settings allow you to configure mobility synchronization policies that apply specifically to Mac OS X 10.5 machines. Because the user interface varies between Mac OS X 10.5, 10.6, and older versions of Mac OS X, DirectControl provides separate policies for each version. See Mobility Synchronization Legacy Settings on page 142 for
148
older versions of Mac OS X and Mobility Synchronization Mac OS X 10.6 Settings on page 156 for 10.6. If your environment does not contain 10.5 machines, you can ignore these settings.
Configuring mobile account creation and options(10.5)
Use the Configure mobile account creation group policy to specify whether to create mobile accounts when users log in. You can use this policy to automatically create mobile accounts or to explicitly prevent the creation of mobile accounts. Use the Configure mobile account options group policy to specify options for mobile accounts, including File Vault settings and home folder location. The mobile account options specified by this policy apply only to new mobile users who are created during login. This policy does not affect existing mobile users.
Note Use this policy Configure mobile account creation (10.5) To do this Configure mobile account creation. You can set the following options with this policy: Check Create mobile account when user logs in to network account to create a mobile account automatically when a user logs in. A local home folder is created for the user at first login. Deselect this option to prevent creation of a mobile account. A local home folder is not created for the user who is logged in as a network user. Note If you do not enable this policy, and you allow access to the Accounts pane of System Preferences, network users can create their own mobile accounts. Check Require confirmation before creating mobile account to allow users to decide whether to enable a mobile account at login. Users see a confirmation dialog when logging in and can click one of the following: Create Now to create a local home folder and enable the mobile account. Don't Create to log in as a network user without enabling the mobile account. Cancel Login to return to the login window. Select Show Don't ask me again checkbox to provide a check box that allows users to prevent display of the mobile account creation dialog on that computer in the future. Users who select Don't ask me again and click Don't Create , are not asked to create a mobile account on that computer (unless they hold down the Option key during login to redisplay the dialog). Select one of the Create home options: Select Create home with default sync settings to initially sync local and network homes so that the network home folder replaces the local home folder. Select Create home with syncing off to create the local home folder without syncing. Once enabled, this group policy takes effect when users log out and back in.
149
Use this policy Configure mobile account options (10.5)
To do this Specify options for mobile accounts, including File Vault settings and home folder location. Note These options only apply to a new user being created at login and do not affect existing mobile users. Select Encrypt contents with Fire Vault to encrypt the contents of the home directory. Select one of the password options: Select Use master password if available The mobile account uses FileVault regardless of whether a master password has been set. However, if a user forgets their password, an administrator will be unable to unlock the account. Select Require computer master password If a master password has not been set, the user will be unable to create a mobile account. To prevent the user's local home folder from using more space than is available in the user's network home folder, select Restrict size and enter a fixed size for the home folder. Select a location for the home folder or allow users to choose, by using the pull-down menu in Home folder location. To choose a location, select one of the following: on startup volume The local home folder is created in /Users/username on the startup volume. at path specified below Specify a different volume or folder in the Path field, using the format: /Volumes/driveName/Folder for example:
/Volumes:E/Users
If you do not specify a volume, the folder is created on the startup volume. To allow users to choose a location, select one of the following. user chooses any volume | internal volume | external volume When users with mobile accounts log in and a mobile account is being created, a window appears for choosing the location of the home folder.
150
Setting account expiration rules
The group policy in this folder enables you to specify whether, and when, to delete mobile accounts and folders.
Use this policy Delete mobile accounts automatically To do this Specify whether to delete mobile accounts and their local home folders automatically after a specified period of inactivity. Typically, Mac OS X creates a local home folder on each computer on which a user enables a mobile account. If a user stops using one or more of these computers, these local home folders create clutter and unnecessarily consume disk space. If you enable this policy, a mobile account and its local home folder are deleted after the specified period of inactivity. Set the expiration to 0 to delete the mobile account and its local home folder immediately after the user logs out. Enter the following information: Time: The number of hours, days, or weeks (specified in Time Unit Period of inactivity that triggers deletion of mobile accounts and their associated local home folders. Time Unit: Select hours, days, or weeks as the type of unit for the number specified in Time. Delete only after successful sync: Select this option to wait to delete the account and folder until after the account has been synced. This policy does not delete external accounts, that is, accounts with local home folders on an external drive. Once enabled, this group policy takes effect when users log out and log back in.
Setting synchronization rules
Use the group policies in the Synchronization Rules category to specify rules for synchronizing folders for mobile users, as follows: Specify the folders to synchronize in the background.
Specify the folders to synchronize at login and logout Specify whether to synchronize background folders manually, or automatically at a specific interval.
You can also use the Skip these items group polices to define criteria for folders that should not be synchronized in the background or when mobile users login and logout.
Understanding synchronization This section explains some aspects of synchronization to keep in mind when enabling synchronization policies.
If a file in one home folder has been modified and the same file in another home folder has not, the newer file overwrites the older file. If both files have been modified since the last sync, the user is prompted to choose which file to keep.
151
Administrators can enable and configure syncing through group policy while users can configure syncing through Accounts preferences. With group policy, you can sync any folder in a user's home folder. However, a user who creates a mobile account through the Accounts System Preferences can only sync top-level folders like ~/Desktop or ~/Documents. It is not recommended to use background syncing with folders containing files accessed by multiple computers because it is easy to inadvertently load older, un-synced files. Be careful with Login and logout syncing because a user's login and logout is delayed while files are syncing. Therefore, avoid syncing a lot of files or large files at login and logout. One strategy is to sync smaller files (such as preference files) at login and logout, while syncing larger files (such as movies) in the background; or you can further reduce network traffic by choosing not to sync the movies folder at all, requiring users to access the movies folder locally.
Note If you want to sync parts of a user's ~/Library folder, you must use login and logout syncing. Syncing the ~/Library folder retains user's bookmarks and application preferences.
See the Mac OS X Server User Management documentation for more details about synchronizing mobile accounts. To specify background synchronization rules, set the following group policies, which are found in the Background Sync folder:
Setting background sync rules
Use this policy Enable background sync rules To do this Choose whether to sync folders in the background for users with mobile accounts. To sync folders in the background:
1 select Sync in the background. 2 Then enable the policy Synchronize items > Sync in the background to specify the folders to synchronize.
You can't sync ~/Library in the background. To stop mobile accounts from syncing files:
1 You must enable this policy and deselect Sync in the background. 2 You also need to set the Synchronize items > Sync in the background policy to Not Configured or Disabled.
If you do not set these polices, users' current sync settings remain in effect and users can choose their sync settings in the Accounts pane of System Preferences. Select Merge with user's settings to add synced folders to folders the user selects for syncing, If you sync the same folder in group policy as the user chooses in the Accounts pane of System Preferences, merging causes the group policy sync settings to take precedence. If you do not select Merge with user's settings, the folders you sync replace those chosen by the user. Once enabled, this group policy takes effect when users log out and back in.
152
Use this policy Skip these items
To do this Set the criteria to identify folders that should not be synchronized in the background for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. Use the Skip items whose RegEx name is policy to skip items whose name exactly matches the specified RegEx string. Use the Skip items whose RegEx path is policy to skip all items whose path matches the specified RegEx string. Enable any of these group policies, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable/disable background synchronization rules policy to be enabled. Once any of there policies are enabled, they take effect when users log out and log back in. Enable this group policy to choose folders to sync in the background. To specify a folder, click Add and enter the folder name, then click OK. Precede the folder with ~/ to specify the location of the synced folder in the user's home folder. For example, to sync the user's Documents folder, enter ~/Documents. This policy is for syncing user's data. Do not sync ~/Library, ~/Documents/Microsoft User Data, or any of their sub-folders in the background, as they cannot be synced correctly. Once enabled, this group policy takes effect when users log out and back in.
Synchronize items (folder) Sync in the background
153
Setting login and logout synchronization rules To specify synchronization rules to occur at login and logout, set the following group policies, which are found in the Login & Logout Sync folder:
Use this policy Enable login & logout sync rules To do this Choose whether to sync folders at login and logout for users with mobile accounts. Be careful with login and logout syncing because a user's login and logout is delayed while files are syncing. To sync folders at login and logout,
1 Enable this policy and select Sync at login and logout. 2 Then enable the policy Synchronize items > Sync at login and logout to specify the folders to synchronize.
To stop mobile accounts from syncing files

1 You must enable this policy and deselect Sync at login and logout. 2 You also need to set the Sync at login and logout policy to Not Configured or Disabled .
If you don't manage these policies, users' current sync settings remain in effect and users can choose their sync settings in the Accounts pane of System Preferences. To add synced folders to folders the user selects for syncing, select Merge with user's settings. If you sync the same folder in group policy as the user chooses in the Accounts pane of System Preferences, merging causes the group policy sync settings to take precedence. If you do not select Merge with user's settings, the folders you sync replace those chosen by the user. Once enabled, this group policy takes effect when users log out and back in.
154
To do this Set the criteria to identify folders that should not be synchronized at login and logout for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. Use the Skip items whose RegEx name is policy to skip items whose name exactly matches the specified RegEx string. Use the Skip items whose RegEx path is policy to skip all items whose path matches the specified RegEx string. Enable any of these group policies, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable/disable login and logout synchronization rules policy to be enabled. Once any of there policies are enabled, they take effect when users log out and log back in. Enable this group policy to choose folders to sync in the background. To specify a folder, click Add and enter the folder name, then click OK. Precede the folder with ~/ to specify the location of the synced folder in the user's home folder. For example, to sync the user's Library folder, enter ~/Library. This policy is for syncing user's preferences and settings. Do not sync folders outside ~/Library and ~/Documents/Microsoft User Data at login and logout, as they cannot be synced correctly. Once enabled, this group policy takes effect when users log out and back in.
Synchronize items (folder) Sync at login and logout
155
Setting synchronization options for manual or automatic synchronization 10.5
Use the group policy in the Synchronization Rules: Options category to specify when to synchronize folders in the background. You can choose to synchronize folders manually or automatically at a specific interval.
Use this policy Manually/automatically sync in the background To do this Select whether background synchronization for mobile user accounts should be initiated manually or automatically at a set interval. If you enable this group policy, select whether synchronization should be initiated automatically or manually. If you initiate background synchronization automatically, you can also specify how frequently folders should be synchronized. You can set frequency from every 5 minutes to every 8 hours. The default interval is 20 minutes. In setting the background synchronization interval, you should take into account the network bandwidth and the number of concurrent users the Mac OS X server supports. If you set background synchronization to occur at a short interval, such as every 5 minutes, and there are many concurrent users, you may overload the server. For example, the server may become backlogged by the too-frequent comparison of file modification dates. If you set background synchronization to occur less frequently, for example every 60 minutes, users may load older, outdated files. For example, if a user saves changes to a file and logs off before files are synchronized at the next interval, when the user loads that same file on another computer, he may get an older version of the file or no file at all. Select Show status in menu bar to display a mobile account status menu on mobile account user's menu bar. This menu allows users to do the following: View the last time they synced Manually start a sync Edit their home sync preferences Note If you do not enable the sync status menu bar, users can still manage their home sync preferences through the Accounts pane of System preferences. However, if you manage any mobility settings through group policy, users cannot change those home sync preferences. Once enabled, this group policy takes effect when users log out and log back in.

The Mac OS X 10.6 Settings allow you to configure mobility synchronization policies that apply specifically to Mac OS X 10.6 machines. Because the user interface varies between Mac OS X 10.5, 10.6, 10.7, and older versions of Mac OS X, DirectControl provides separate policies for each version. See Mobility Synchronization Legacy Settings on page 142 for older versions of Mac OS X and Mobility Synchronization Mac OS X 10.5 Settings on page 148 for 10.5, and Mobility Synchronization Mac OS X 10.7 Settings on page 165 for 10.7. If your environment does not contain 10.6 machines, you can ignore these settings.
156
Configuring mobile account creation and options (10.6)
Use the Configure mobile account creation group policy to specify whether to create mobile accounts when users log in. You can use this policy to automatically create mobile accounts or to explicitly prevent the creation of mobile accounts. Use the Configure mobile account options group policy to specify options for mobile accounts, including File Vault settings and home folder location.
Note The mobile account options specified by this policy apply only to new mobile users who are created during login. This policy does not affect existing mobile users. Use this policy Configure mobile account creation (10.6) To do this Configure mobile account creation. Check Create mobile account when user logs in to network account to create a mobile account automatically when a user logs in. A local home folder is created for the user at first login. Deselect this option to prevent creation of a mobile account. A local home folder is not created for a user who is logged in as a network user. Note If you do not enable this policy, and you allow access to the Accounts pane of System Preferences, network users can create their own mobile accounts. Check Require confirmation before creating mobile account to allow users to decide whether to enable a mobile account at login. Users see a confirmation dialog when logging in and can click one of the following: Create Now to create a local home folder and enable the mobile account. Don't Create to log in as a network user without enabling the mobile account. Cancel Login to return to the login window. Select Show Don't ask me again checkbox to provide a check box that allows users to prevent display of the mobile account creation dialog on that computer in the future. Users who select Don't ask me again and click Don't Create , are not asked to create a mobile account on that computer (unless they hold down the Option key during login to redisplay the dialog). Select one of the Create home options: Select Create home using home and default sync settings to initially sync local and network homes so that the network home folder replaces the local home folder. The default Mac OS X sync settings in the Accounts pane of System Preferences are enabled. Select Create home using local home template to create the local home folder without syncing. The default Mac OS X sync settings are enabled. Once enabled, this group policy takes effect when users log out and back in.
157
/Volumes:E/Users
158
Setting account expiration rules
Use this policy Delete mobile accounts automatically To do this Specify whether to delete mobile accounts and their local home folders automatically after a specified period of inactivity. Typically, Mac OS X creates a local home folder on each computer on which a user enables a mobile account. If a user stops using one or more of these computers, these local home folders create clutter and unnecessarily consume disk space. If you enable this policy, a mobile account and its local home folder are deleted after the specified period of inactivity. Set the expiration to 0 to delete the mobile account and its local home folder immediately after the user logs out. Enter the following information: Time: The number of hours, days, or weeks (specified in Time Unit Period of inactivity that triggers deletion of mobile accounts and their associated local home folders. Time Unit: Select hours, days, or weeks as the type of unit for the number specified in Time. Delete only after successful sync: Select this option to wait to delete the account and folder until after the account has been synced. This policy does not delete external accounts, that is, accounts with local home folders on an external drive. Once enabled, this group policy takes effect when users log out and log back in.
Setting synchronization rules (10.6)
159
See the Mac OS X Server User Management documentation for more details about synchronizing mobile accounts.
160
Setting home sync rules To specify home synchronization rules, set the following group policies, which are found in the Home Sync folder:
Use this policy Enable home sync rules (10.6) To do this Enable this policy to configure home sync rules. This policy is used for files in the users home folder (~), but not for ~/Library. or ~/Documents/Microsoft User Data. To configure home sync, enable this policy and select one or more of the following sync options: at login Sync files when a mobile user logs in. at logout Sync files when a mobile user logs out. in the background Sync files in the background at the interval specified by the Manually/automatically sync in the background policy. manually Allow users to sync manually. Deselect any of these options to prevent that type of syncing. For example, deselect manually to prevent users from syncing manually. To stop mobile accounts from syncing files entirely, you must enable this policy and deselect all options. You also need to set the Manually/automatically sync in the background policy to Not Configured or Disabled . If you don't manage these policies, users' current sync settings remain in effect and users can choose their sync settings in the Accounts pane of System Preferences. You also need to set the Synchronize items > Synchronize home sync items policy to Not Configured or Disabled. Select Merge with user's settings to add synced folders to folders the user selects for syncing, If you sync the same folder in group policy as the user chooses in the Accounts pane of System Preferences, merging causes the group policy sync settings to take precedence. If you do not select Merge with user's settings, the folders you sync replace those chosen by the user. Once enabled, this group policy takes effect when users log out and back in.
161
Use this policy Skip these items (10.6)
To do this Set the criteria to identify folders that should not be synchronized in the background for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. Use the Skip items whose RegEx name is policy to skip items whose name exactly matches the specified RegEx string. Use the Skip items whose RegEx path is policy to skip all items whose path matches the specified RegEx string. Enable any of these group policies, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable home sync rules policy to be enabled. Once any of there policies are enabled, they take effect when users log out and log back in. Enable this group policy to choose folders to sync. To specify a folder, click Add and enter the folder name, then click OK. Precede the folder with ~/ to specify the location of the synced folder in the user's home folder. For example, to sync the user's Documents folder, enter ~/Documents. This policy is for syncing user's data. Do not sync ~/Library, ~/Documents/Microsoft User Data, or any of their sub-folders in the background, as they cannot be synced correctly. Once enabled, this group policy takes effect when users log out and back in.
Synchronize items (folder) Synchronize home sync items (10.6)
162
Setting preference synchronization rules To specify synchronization rules for preference files, set the following group policies, which are found in the Preference Sync folder:
Use this policy Enable preference sync rules (10.6) To do this Configure preference sync rules. This policy configures options for syncing preference files, which are typically stored in ~/Library. To configure preference sync, enable this policy and select one or more of the following sync options: at login Sync files when a mobile user logs in. at logout Sync files when a mobile user logs out. in the background Sync files in the background at the interval specified by the Manually/automatically sync in the background policy. manually Allow users to sync manually. Deselect any of these options to prevent that type of syncing. For example, deselect manually to prevent users from syncing manually. To stop mobile accounts from syncing files entirely, you must enable this policy and deselect all options. You also need to set the Manually/automatically sync in the background policy to Not Configured or Disabled . If you don't manage these policies, users' current sync settings remain in effect and users can choose their sync settings in the Accounts pane of System Preferences. To add synced folders to folders the user selects for syncing, select Merge with user's settings. If you sync the same folder in group policy as the user chooses in the Accounts pane of System Preferences, merging causes the group policy sync settings to take precedence. If you do not select Merge with user's settings, the folders you sync replace those chosen by the user. Once enabled, this group policy takes effect when users log out and back in.
163
Use this policy Skip these items (10.6)
To do this Set the criteria to identify preference folders that should not be synchronized for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. Use the Skip items whose RegEx name is policy to skip items whose name exactly matches the specified RegEx string. Use the Skip items whose RegEx path is policy to skip all items whose path matches the specified RegEx string. Enable any of these group policies, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable preference sync rules policy to be enabled. Once any of there policies are enabled, they take effect when users log out and log back in. Enable this group policy to choose folders to sync in the users home folder. To specify a folder, click Add and enter the folder name, then click OK. Precede the folder with ~/ to specify the location of the synced folder in the user's home folder. For example, to sync the user's Library folder, enter ~/Library. This policy is for syncing user's preferences and settings. Do not sync folders outside ~/Library and ~/Documents/Microsoft User Data at login and logout, as they cannot be synced correctly. Once enabled, this group policy takes effect when users log out and back in.
Synchronize items (folder) Sync preference sync items (10.6)
164
Use this policy Manually/automatically sync in the background To do this Select whether background synchronization for mobile user accounts should be initiated manually or automatically at a set interval. If you enable this group policy, select whether synchronization should be initiated automatically or manually. If you initiate background synchronization automatically, you can also specify how frequently folders should be synchronized. You can set frequency from every 5 minutes to every 8 hours. The default interval is 20 minutes. In setting the background synchronization interval, you should take into account the network bandwidth and the number of concurrent users the Mac OS X server supports. If you set background synchronization to occur at a short interval, such as every 5 minutes, and there are many concurrent users, you may overload the server. For example, the server may become backlogged by the too-frequent comparison of file modification dates. If you set background synchronization to occur less frequently, for example every 60 minutes, users may load older, outdated files. For example, if a user saves changes to a file and logs off before files are synchronized at the next interval, when the user loads that same file on another computer, he may get an older version of the file or no file at all. Select Show status in menu bar to display a mobile account status menu on mobile account user's menu bar. This menu allows users to do the following: View the last time they synced Manually start a sync Edit their home sync preferences Note If you do not enable the sync status menu bar, users can still manage their home sync preferences through the Accounts pane of System preferences. However, if you manage any mobility settings through group policy, users cannot change those home sync preferences. Once enabled, this group policy takes effect when users log out and log back in.

The Mac OS X 10.7 Settings allow you to configure mobility synchronization policies that apply specifically to Mac OS X 10.7 machines. Because the user interface varies between Mac OS X 10.5, 10.6, 10.7, and older versions of Mac OS X, DirectControl provides separate policies for each version. See Mobility Synchronization Legacy Settings on page 142 for older versions of Mac OS X, Mobility Synchronization Mac OS X 10.5 Settings on page 148 for 10.5, and Mobility Synchronization Mac OS X 10.6 Settings on page 156 for 10.6. If your environment does not contain 10.7 machines, you can ignore these settings.
165
Configuring mobile account creation and options (10.7)
Use the Configure mobile account creation group policy to specify whether to create mobile accounts when users log in. You can use this policy to automatically create mobile accounts or to explicitly prevent the creation of mobile accounts. Use the Configure mobile account options group policy to specify options for mobile accounts, including File Vault settings and home folder location.
Note The mobile account options specified by this policy apply only to new mobile users who are created during login. This policy does not affect existing mobile users. Use this policy Configure mobile account creation (10.7) To do this Configure mobile account creation. Check Create mobile account when user logs in to network account to create a mobile account automatically when a user logs in. A local home folder is created for the user at first login. To prevent creation of a mobile account, enable the policy and deselect this option . A local home folder is not created for a user who is logged in as a network user. Note If you do not enable this policy, and you allow access to the Accounts pane of System Preferences, network users can create their own mobile accounts. Check Require confirmation before creating mobile account to allow users to decide whether to enable a mobile account at login. Users see a confirmation dialog when logging in and can click one of the following: Create Now to create a local home folder and enable the mobile account. Don't Create to log in as a network user without enabling the mobile account. Cancel Login to return to the login window. Select Show Don't ask me again checkbox to provide a check box that allows users to prevent display of the mobile account creation dialog on that computer in the future. Users who select Don't ask me again and click Don't Create , are not asked to create a mobile account on that computer (unless they hold down the Option key during login to redisplay the dialog). Select one of the Create home options: Select network home and default sync settings to initially sync local and network homes so that the network home folder replaces the local home folder. The default Mac OS X sync settings in the Accounts pane of System Preferences are enabled. Select local home template to create the local home folder without syncing. The default Mac OS X sync settings are enabled. Once enabled, this group policy takes effect when users log out and back in.
166
/Volumes:E/Users
167
Setting account expiration rules (10.7)
Use this policy Delete mobile accounts automatically (10.7) To do this Specify whether to delete mobile accounts and their local home folders automatically after a specified period of inactivity. Typically, Mac OS X creates a local home folder on each computer on which a user enables a mobile account. If a user stops using one or more of these computers, these local home folders create clutter and unnecessarily consume disk space. If you enable this policy, a mobile account and its local home folder are deleted after the specified period of inactivity. Set the expiration to 0 to delete the mobile account and its local home folder immediately after the user logs out. Enter the following information: Time: The number of hours, days, or weeks (specified in Time Unit Period of inactivity that triggers deletion of mobile accounts and their associated local home folders. Time Unit: Select hours, days, or weeks as the type of unit for the number specified in Time. Delete only after successful sync: Select this option to wait to delete the account and folder until after the account has been synced. This policy does not delete external accounts, that is, accounts with local home folders on an external drive. Once enabled, this group policy takes effect when users log out and log back in.
Setting synchronization rules (10.7)
168
See the Mac OS X Server User Management documentation for more details about synchronizing mobile accounts.
169
Setting home sync rules To specify home synchronization rules, set the following group policies, which are found in the Home Sync folder:
Use this policy Enable home sync rules To do this Enable this policy to configure home sync rules. This policy is used for files in the users home folder (~), but not for ~/Library. To configure home sync, enable this policy and select one or more of the following sync options: at login Sync files when a mobile user logs in. at logout Sync files when a mobile user logs out. in the background Sync files in the background at the interval specified by the Manually/automatically sync in the background policy. manually Allow users to sync manually. Deselect any of these options to prevent that type of syncing. For example, deselect manually to prevent users from syncing manually. To stop mobile accounts from syncing files entirely, you must enable this policy and deselect all options. You also need to set the Manually/automatically sync in the background policy to Not Configured or Disabled . If you don't manage these policies, users' current sync settings remain in effect and users can choose their sync settings in the Accounts pane of System Preferences. You also need to set the Synchronize items > Synchronize home sync items policy to Not Configured or Disabled. Select Merge with user's settings to add synced folders to folders the user selects for syncing, If you sync the same folder in group policy as the user chooses in the Accounts pane of System Preferences, merging causes the group policy sync settings to take precedence. If you do not select Merge with user's settings, the folders you sync replace those chosen by the user. Once enabled, this group policy takes effect when users log out and back in.
170
To do this Set the criteria to identify folders that should not be synchronized in the background for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. Use the Skip items whose RegEx name is policy to skip items whose name exactly matches the specified RegEx string. Use the Skip items whose RegEx path is policy to skip all items whose path matches the specified RegEx string. Enable any of these group policies, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable home sync rules policy to be enabled. Once any of there policies are enabled, they take effect when users log out and log back in. Enable this group policy to choose folders to sync. To specify a folder, click Add and enter the folder name, then click OK. Precede the folder with ~/ to specify the location of the synced folder in the user's home folder. For example, to sync the user's Documents folder, enter ~/Documents. This policy is for syncing user's data. Do not sync ~/Library, ~/Documents/Microsoft User Data, or any of their sub-folders in the background, as they cannot be synced correctly. Once enabled, this group policy takes effect when users log out and back in.
Synchronize items (folder) Synchronize home sync items (10.7)
171
Setting preference synchronization rules To specify synchronization rules for preference files, set the following group policies, which are found in the Preference Sync folder:
Use this policy Enable preference sync rules To do this Configure preference sync rules. This policy configures options for syncing preference files, which are typically stored in ~/Library. To configure preference sync, enable this policy and select one or more of the following sync options: at login Sync files when a mobile user logs in. at logout Sync files when a mobile user logs out. in the background Sync files in the background at the interval specified by the Manually/automatically sync in the background policy. manually Allow users to sync manually. Deselect any of these options to prevent that type of syncing. For example, deselect manually to prevent users from syncing manually. To stop mobile accounts from syncing files entirely, you must enable this policy and deselect all options. You also need to set the Manually/automatically sync in the background policy to Not Configured or Disabled . If you don't manage these policies, users' current sync settings remain in effect and users can choose their sync settings in the Accounts pane of System Preferences. To add synced folders to folders the user selects for syncing, select Merge with user's settings. If you sync the same folder in group policy as the user chooses in the Accounts pane of System Preferences, merging causes the group policy sync settings to take precedence. If you do not select Merge with user's settings, the folders you sync replace those chosen by the user. Once enabled, this group policy takes effect when users log out and back in.
172
To do this Set the criteria to identify preference folders that should not be synchronized for users with mobile accounts. These group policies allow you to specify a string that identifies files and folders to skip during synchronization: Use the Skip items that start with policy to skip items that start with the specified string. The string should not contain the slash (/) character. Use the Skip items that end with policy to skip items that end with the specified string. The string should not contain the slash (/) character. Use the Skip items whose name contains policy to skip items that contain the specified string. The string should not contain the slash (/) character. Use the Skip items whose name is policy to skip items that exactly match the specified string. The string should not contain the slash (/) character. Use the Skip items whose full path is policy to skip all items in the specified directory. For example, if you specify ~/Library, no items in ~/Library directory will be synchronized. Use the Skip items whose partial path matches policy to skip items with a partial path that matches the specified string. Use the Skip items whose RegEx name is policy to skip items whose name exactly matches the specified RegEx string. Use the Skip items whose RegEx path is policy to skip all items whose path matches the specified RegEx string. Enable any of these group policies, then click Add and type a string, for example Users or /Users,~/Library, then click OK. These policies require the Enable preference sync rules policy to be enabled. Once any of there policies are enabled, they take effect when users log out and log back in. Enable this group policy to choose folders to sync in the users home folder. To specify a folder, click Add and enter the folder name, then click OK.. Precede the folder with ~/ to specify the location of the synced folder in the user's home folder. For example, to sync the user's Library folder, enter ~/Library. This policy is for syncing user's preferences and settings. Do not sync folders outside ~/Library and ~/Documents/Microsoft User Data at login and logout, as they cannot be synced correctly. Once enabled, this group policy takes effect when users log out and back in.
Synchronize items (folder) Sync preference sync items (10.7)
173
Use this policy Manually/automatically sync in the background (10.7) To do this Select whether background synchronization for mobile user accounts should be initiated manually or automatically at a set interval. If you enable this group policy, select whether synchronization should be initiated automatically or manually. If you initiate background synchronization automatically, you can also specify how frequently folders should be synchronized. You can set frequency from every 5 minutes to every 8 hours. The default interval is 20 minutes. In setting the background synchronization interval, you should take into account the network bandwidth and the number of concurrent users the Mac OS X server supports. If you set background synchronization to occur at a short interval, such as every 5 minutes, and there are many concurrent users, you may overload the server. For example, the server may become backlogged by the too-frequent comparison of file modification dates. If you set background synchronization to occur less frequently, for example every 60 minutes, users may load older, outdated files. For example, if a user saves changes to a file and logs off before files are synchronized at the next interval, when the user loads that same file on another computer, he may get an older version of the file or no file at all. Select Show status in menu bar to display a mobile account status menu on mobile account user's menu bar. This menu allows users to do the following: View the last time they synced Manually start a sync Edit their home sync preferences Note If you do not enable the sync status menu bar, users can still manage their home sync preferences through the Accounts pane of System preferences. However, if you manage any mobility settings through group policy, users cannot change those home sync preferences. Once enabled, this group policy takes effect when users log out and log back in.
174
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Scripts (Login/Logout) group policies to deploy login and logout scripts that run when an Active Directory user logs on or logs out. When you use these group policies, the login and logout scripts are stored in the Active Directory domains system volume (sysvol) and transferred to the Mac OS X computer when the group policies are applied. Login and logout scripts are useful for performing common tasks such as mounting and unmounting shares. When these group policies are enabled, the first login by an AD user will restart the login script and return the user to the login window. Subsequent logins by this user or a different user occur normally and the changes generated by the script happen immediately.
Note
Following the descriptions for these policies, see Using the sample login and logout scripts on page 177 for an explanation of how to use the sample login and logout scripts shipped with Centrify DirectControl.
Use this policy Specify login script To do this Specify the name of a login script to execute when users log on. You can specify only one file as the login script. Before enabling this policy, you should create the login script and copy it to the system volume (sysvol) on the domain controller. By default, the login script is stored in the system volume (SYSVOL) on the domain controller in the directory:
\\domain\SYSVOL\domain\Scripts\scriptname
The script path you type in Login script is relative to \\domain\SYSVOL\domain\scripts\. For example, if the domain name is ajax.org and you enter a script name of mlogin.sh, the script that gets executed on the domain controller is:
You can specify additional relative directories in the path, if needed. Note Be certain authenticated users have permission to read this file so the script can run when they log in. By default, the script runs with the Active Directory users permissions. If the script contains commands that require root permission to run, select Run with root user privileges. Once this group policy is enabled, it takes effect when users log out and log back in. Note The first AD user to log in is taken back to the login screen. Subsequent logins by this user or a different user occur normally and changes generated by the script happen immediately.
175
Use this policy Specify logout script
To do this Specify the name of a logout script to execute when users log out. You can specify only one file as the logout script. Before enabling this policy, you should create the logout script and copy it to the system volume (SYSVOL) on the domain controller. By default, the logout script is stored in the system volume (SYSVOL) on the domain controller in the following directory:
\\domain\SYSVOL\domain\Scripts\scriptname
The script path you type in Logout script is relative to: \domain\SYSVOL\domain\scripts\. For example, if the domain name is ajax.org and you enter a script name of mlogout.sh, the script that gets executed on the domain controller is:
\\ajax.org\SYSVOL\ajax.org\Scripts\mlogout.sh
Note Be certain authenticated users have permission to read this file so the script can run when they log out. By default, the script runs with the Active Directory users permissions. If the script contains commands that require root permission to run, select Run with root user privileges. Once this group policy is enabled, it takes effect when users log out and log back in.
176
Use this policy Specify multiple login scripts
To do this Specify the names of one or more login scripts to execute when a user logs on. The scripts you specify run simultaneously in no particular order. Note This policy works on Mac OS X 10.5 and later. Use specify login script for previous versions of Mac OS X. This policy is also available as a computer policy. If you specify scripts using both the computer and user policies, the computer scripts are executed first. Before enabling this policy, you should create the scripts and copy them to the system volume (sysvol) on the domain controller. By default, the login scripts are stored in the system volume (SYSVOL) on the domain controller in the directory:
\\domain\SYSVOL\domain\Scripts \scriptname1 \scriptname2
...
After enabling this policy, click Add and enter the following information: Script: The name of the script and an optional path, which are relative to \\domain\SYSVOL\domain\scripts\. For example, if the domain name is ajax.org and you enter a script name of mlogin.sh, the script that gets executed on the domain controller is:
You can specify additional relative directories in the path, if needed; for example, if you type sub\mlogin.sh, the file that gets executed is:
\\ajax.org\SYSVOL\ajax.org\Scripts\sub\mlogin.sh
Parameters: An optional set of arguments to pass to the script. These arguments are interpreted the same way as in a UNIX shell; that is, space is a delimiter, and backslash is an escape character. You can also use $USER to represent the current user's name. For example:
arg1 arg2 arg3 arg1 'a r g 2' arg3 arg\' $USER.
Note Be certain authenticated users have permission to read these files so the scripts can run when they log in. Once this group policy is enabled, it takes effect when users log out and log back in.
Using the sample login and logout scripts
A sample login and logout script are installed in the same directory as the group policy templates:
C:\Program Files\Centrify\Centrify DirectControl\group policy\policy
You can edit these files and copy them to sysvol to use as your login and logout scripts. The login script creates an automount record for the user and puts an icon on the users desktop to access the mounted shared folder. The logout script un-mounts the network shared folder and removes the automount record.
177
Security Settings
Security Settings
Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > Security group policy to require the user to enter a password to unlock the computer from the Security system preference on Mac OS X computers. This group policy corresponds to the Require password option displayed on the Security pane. For example:
This group policy corresponds to this system preference
Use this policy Require a password to wake this computer from sleep or screen saver
To do this Lock the computer screen when the computer goes into sleep or screen saver mode and requires users to enter a user name and password to unlock the screen. Enabling this group policy is the same as clicking the Require a password to wake this computer from sleep or screen saver option in the Security system preference. Once this group policy is enabled, it takes effect when the machine is rebooted. Prohibit a user from unlocking the screen if a password change is required while the screen is locked. If a user logs in with a password that must be changed, and the computer goes into sleep or screen saver mode before the user updates the password, the user is locked out. Disabling this policy allows a user to specify the old password to remove the screen lock. Lock the computer screen when the smart card is removed from the reader. You must also enable the Require a password to wake this computer from sleep or screen saver group policy to require a password to unlock the screen. Note On Mac OS X 10.6, if the System Preference: Security > General > Require password [immediately] after sleep or screen saver begins is set, along with this group policy, the lock behavior will be undefined. If you set the policy, do not set the system preference. Once this group policy is enabled, it takes effect when the machine is rebooted.
Prohibit authentication with expired password
Lock Smart Card screen
178

Use the User Configuration > Policies > Centrify Settings > Mac OS X Settings > System Preference Settings group policies to specify which preferences are displayed in System Preferences for Mac OS X users. Displaying a preference does not enable a user to modify that preference. For example, some preferences, such as Startup Disk preferences, require an administrator name and password before a user can modify its settings. Displaying a preference does enable a user to view the preferences current settings. By default, no system preference panes are displayed unless explicitly enabled. The group policies in this category correspond to System Preferences you can select for display in the Workgroup Manager. For example:
The user interface for System Preferences Settings differs significantly between different versions of Mac OS X. Therefore, DirectControl provides separate System Preferences policies for each version of Mac OS X that it supports. In addition, to support existing installations that configured group policies by using a previous centrifydc_mac_settings template, DirectControl provides a set of legacy preferences settings. The Use version specific settings group policy determines whether to use legacy settings or platform-specific system preferences settings. By default (if you do not configure or disable this policy) DirectControl uses legacy settings.
179
If you enable this policy, you can then enable platform-specific system preferences settings for each platform in your environment; see the following sections for information on each set of policies:
Use this policy Use version specific settings (Preferences) To do this Enable the use of version-specific System Preferences settings. If you enable this policy, you can then set platform-specific preferences settings for each platform in your environment. For example, if you have only 10.5 machines, you can enable this policy then use Mac OS X 10.5 settings. If you have 10.5, 10.6, and 10.7 machines, or any two of these, enable this policy, then configure the version-specific policies as appropriate: Mac OS X 10.5 Settings Mac OS X 10.6 Settings Mac OS X 10.7 Settings When a machine joins the domain, DirectControl determines the Mac OS X version and applies the appropriate Preferences settings. If this policy is disabled or not configured, Legacy Settings are used instead of version-specific settings. Likewise, DirectControl versions prior to 4.4.2 always use Legacy Settings and ignore this policy setting. If you configured System Preferences settings with a version of DirectControl prior to 4.4.2, these settings are saved to Legacy Settings when you upgrade to the current DirectControl version. You can keep or edit these settings as you wish. Note The Legacy Settings may not match exactly the settings for each Mac OS X version; for example, some settings may be missing while others may be redundant for a particular OS version. Configure Legacy Settings. Configure Mac OS X 10.5 Settings. Configure Mac OS X 10.6 Settings.
System Preferences Legacy Settings System Preferences Mac OS X 10.5 Settings System Preferences Mac OS X 10.6 Settings
System Preferences Legacy Settings

When you upgrade from a version of DirectControl prior to 4.4.2, your System Preferences settings are saved to Legacy Settings. You can keep or edit the individual legacy system preferences group policy settings as you wish.
180
The legacy settings may not match exactly the settings for each Mac OS X version; for example, some settings may be missing while others may be redundant for a particular OS version.
Note Use this policy Enable System Preferences Pane: Personal Enable System Preferences Pane: Hardware Enable System Preferences Pane: Internet & Network Enable System Preferences Pane: System To do this Select the items to display in the Personal pane of System Preferences. Select the items to display in the Hardware pane of System Preferences. Select the items to display in the Internet & Network pane of System Preferences. Select the items to display in the System pane of System Preferences.
Enable System Preferences Pane: Other Select the items to display in the Other pane of System Preferences. Preferences Panes Limit items shown in System Preferences Control the items displayed in System Preferences. You must enable this group policy for any of the other group policy settings to take effect. Once this group policy is enabled, it takes effect when users log out and log back in.
Showing items in the Personal pane of System Preferences
Use the group policies in this category to choose which items to display in the Personal pane of System Preferences.
Use this policy Enable Appearance To do this Display Appearance preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Dashboard & ExposE preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Desktop & Screen Saver preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Dock preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
Enable Dashboard & Expose
Enable Desktop & Screen Saver
Enable Dock
Enable International (Language & Text) Display International preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
181
Use this policy Enable Security
To do this Display Security preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Spotlight preferences in the Personal pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
Enable Spotlight
Showing items in the Hardware System pane of Preferences
Use the group policies in this category to display items in the Hardware pane of System Preferences.
Use this policy Enable Bluetooth To do this Display Bluetooth preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display CDs & DVDs preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Displays preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Energy Saver preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Ink preferences in the Hardware pane of System Preferences. Note Ink preferences are only shown if a graphics tablet is connected to the Mac OS X computer. Once this group policy is enabled, it takes effect when users log out and log back in. Display Keyboard & Mouse preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Mouse preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Print & FAX preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
Enable CDs & DVDs
Enable Displays
Enable Energy Saver
Enable Ink
Enable Keyboard & Mouse (Keyboard)
Enable Mouse
Enable Print & FAX
182
Use this policy Enable Sound
To do this Display Sound preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Trackpad preferences in the Hardware pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
Enable Trackpad
Showing items in the Internet & Network pane of System Preferences
Use the group policies in this category to display items in the Internet & Network pane of System Preferences.
Use this policy Enable .Mac (MobileMe) To do this Display .Mac preferences in the Internet & Network pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Fibre Channel preferences in the Internet & Network pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Network preferences in the Internet & Network pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display QuickTime preferences in the Internet & Network pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Sharing preferences in the Internet & Network pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
Enable Fibre Channel
Enable Network
Enable QuickTime
Enable Sharing
183
Showing items in the System pane of System Preferences
Use the group policies in this category to display items in the System pane of System Preferences.
Use this policy Enable Accounts To do this Display Accounts preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Classic preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Date & Time preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Parental Controls preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Software Update preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Speech preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Startup Disk preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Time Machine preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in. Display Universal Access preferences in the System pane of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
Enable Classic
Enable Date & Time
Enable Parental Controls
Enable Software Update
Enable Speech
Enable Startup Disk
Enable Time Machine
Enable Universal Access
184
Showing items in the Other pane of System Preferences
Use the group policies in this category to display the items you specify in the Other pane of System Preferences.
Use this policy Other Preferences Panes To do this Display additional preferences panes of System Preferences. Once this group policy is enabled, it takes effect when users log out and log back in.
System Preferences Mac OS X 10.5 Settings

The Mac OS X 10.5 Settings allow you to configure system preferences policies that apply specifically to Mac OS X 10.5 machines. Because the user interface varies between Mac OS X 10.5, 10.6, and older versions of Mac OS X, DirectControl provides separate policies for each version. See System Preferences Legacy Settings on page 180 for older versions of Mac OS X and System Preferences Mac OS X 10.6 Settings on page 186 for 10.6. If your environment does not contain 10.5 machines, you can ignore these settings.
Use this policy Limit items shown in System Preferences Enable System Preferences panes To do this Permit items showing in the System Preferences panel. Once enabled, this group policy takes effect when users log out and log back in. Use the group policies in this folder to select items to add to the built-in System Preferences panes and to define items to add to the Other pane of System Preferences.
Enable System Preferences panes 10.5
Use Enable built-in System Preferences panes to select the items to add to the standard System Preferences panes.
185
Use Enable other System Preferences panes to add preferences for third-party applications to the Other pane of the System Preferences panel by using the
Use this policy Enable built-in System Preferences panes (10.5) To do this Select items to add to the System Preferences panel. This policy is only effective if the Limit items shown in System Preferences group policy is enabled. If the Limit items shown in System Preferences group policy is not configured or is disabled, this group policy is ignored. Once enabled, this group policy takes effect when users log out and log back in.
Enable other System Preferences panes Define a list of additional items to add to the Other pane of the System (10.5) Preferences panel. Preference pane applications are actually collections of files inside a directory (called bundles). Inside the Contents directory of every preference pane application is the info.plist file, and inside that file is the CFBundleIdentifier key that identifies the preference pane application. You need to use the value for this key when adding a preference pane application. Generally, installed third party preference panes can be found in /System/Library/PreferencePanes, /Library/PreferencePanes or ~/Library/PreferencePanes. You can find the CFBundleIdentifier key by using the defaults command. For example, to find the value for the QuickTime pane, use the following command in a terminal window:
defaults read /System/Library/PreferencePanes/QuickTime.prefPane /Contents/info CFBundleIdentifier
which returns:
com.apple.preference.quicktime
To display the QuickTime icon in the Other pane of the System Preferences Panel, enable this policy, then click Add and enter com.apple.preference.quicktime. This policy is only effective if the Limit items shown in System Preferences group policy is enabled. If the Limit items shown in System Preferences group policy is not configured or is disabled, this group policy is ignored. Once enabled, this group policy takes effect when users log out and log back in.

The Mac OS X 10.6 Settings allow you to configure system preferences policies that apply specifically to Mac OS X 10.6 machines. Because the user interface varies between different versions of Mac OS X, DirectControl provides separate policies for each version. See System Preferences Legacy Settings for older versions of Mac OS X, System Preferences Mac OS X 10.5 Settings for 10.5. and System Preferences Mac OS X 10.7 Settings for 10.7.
186
If your environment does not contain 10.6 machines, you can ignore these settings.
Use this policy Limit items shown in System Preferences (10.6) Enable System Preferences panes To do this Permit items showing in the System Preferences panel. Once enabled, this group policy takes effect when users log out and log back in. Use the group policies in this folder to select items to add to the built-in System Preferences panes and to define items to add to the Other pane of System Preferences.
187
Use Enable other System Preferences panes to add preferences for third-party applications to the Other pane of the System Preferences panel.
which returns:

The Mac OS X 10.7 Settings allow you to configure system preferences policies that apply specifically to Mac OS X 10.7 machines. Because the user interface varies between different versions of Mac OS X, DirectControl provides separate policies for each version. See System Preferences Legacy Settings for older versions of Mac OS X, System Preferences Mac OS X 10.5 Settings for 10.5 and System Preferences Mac OS X 10.6 Settings for 10.6.
188
If your environment does not contain 10.7 machines, you can ignore these settings.
Use this policy Limit items shown in System Preferences (10.7) Enable System Preferences panes To do this Permit items showing in the System Preferences panel. Once enabled, this group policy takes effect when users log out and log back in. Use the group policies in this folder to select items to add to the built-in System Preferences panes and to define items to add to the Other pane of System Preferences.
189
Use Enable other System Preferences panes to add preferences for third-party applications to the Other pane of the System Preferences.
which returns:
190
Chapter 7
Configuring a Mac OS X computer for smart card login

This chapter explains how to set up smart card login for a Mac OS X computer. The following topics are covered: Understanding smart card login
Configuring smart card login Using smart card login Troubleshooting smart card log in
Understanding smart card login

Smart cards provide an enhanced level of security authentication for logging into an Active Directory domain. To configure a smart card for use on a Mac OS X computer with Centrify DirectControl requires that you have already set up a smart card for use in a Windows domain. You do not need to add any smart card infrastructure to the Mac OS X computer, other than a smart card reader and a provisioned smart card. Setting up smart card login for Windows requires either: Microsoft enterprise root certification authority; see the Microsoft TechNet article: Install an enterprise root certification authority.
A third party certification authority see the Microsoft KB article: Guidelines for enabling smart card logon with third-party certification authorities.
If you have set up smart card login for Windows clients in a domain, you can use Centrify DirectControl to configure smart card login for Mac OS X clients joined to the same domain. If you have provisioned a smart card for a Windows user on a Windows machine, once you configure smart card support for a Mac OS X machine, you can use the same smart card to log in to a Mac OS X machine.
Configuring smart card login

Centrify DirectControl provides the following group policies and account options to configure a Mac OS X computer with smart card support: The Enable smart card support group policy configures a Mac OS X machine to enable smart card login for Active Directory users.
The Lock smart card screen group policy creates a daemon to lock the screen when the smart card is removed.
191
In a users Active Directory account properties, the Smart card is required for interactive logon option prevents a user from logging in with only a username and password. The Require smart card login policy configures a Mac OS X machine to prevent all users from logging in with only a username and password.
Verifying prerequisites for configuring smart card login

The smart card group policies require Mac OS X 10.4 or later. Before enabling smart card support, make sure you do the following: Provision a smart card with an NT principal name and PIN. Currently, Centrify DirectControl supports Common Access Card (CAC) and Personal Identify Verification (PIV) smart cards.
Verify that the Active Directory Zone users UPN matches the the UPN on the smart card. Verify that the public key infrastructure to support smart card login is operational on the Windows machine running Active Directory and Centrify DirectControl. If the user is able to log in to a Windows machine with a smart card, and you have a card reader and a fully-provisioned card for the Mac OS X machine, the user should be able to log in to the Mac OS X machine.
Enabling smart card support

Smart card support requires configuration changes to Mac OS X. Enabling the policy, Enable smart card support, makes the required changes to Mac OS X configuration files.
To configure Mac OS X to use a smart card for logging on: 1 Make a backup of the file /etc/authorization on all machines for which you are
enabling smart card login support. Enabling the group policy Enable smart card support causes edits to this file, so you should create a backup to be safe.
2 Create or edit an existing Group Policy Object linked to a site, domain, or OU that
includes Mac OS X computers.

3 In the Group Policy Object Editor, expand Computer Configuration > Centrify
Settings > Mac OS X Settings > Security, then double-click Enable smart card support.
4 Select the Enabled option and click OK.
This group policy adds smart card support to the /etc/authorization file on Mac OS X machines that are linked to the group policy object. This policy also creates a text file
192
named /etc/cacloginconfig.plist on each machine. This configuration file directs the Mac OS X smart card log-in to look for a user in Active Directory with a user principal name (UPN) that is the same as the NT Principal Name attribute in the smart card log-in certificate. The /etc/cacloginconfig configuration file for use with Centrify DirectControl and Active Directory is different from the default configuration file provided by Apple.
Note
After reboot, the machines linked to the group policy object are ready for smart card use. Complete the procedure in the next section to enable screen locking when the smart card is removed from a machine.
Enabling screen locking for smart card removal

Depending on what you consider best practices for using a smart card, you may want the screen to lock when a user removes the smart card. Enabling the Lock smart card screen policy creates a daemon that locks the screen if the user removes the smart card.
To enable screen locking when the smart card is removed from a machine: 1 Edit the Group Policy Object (GPO) linked to a site, domain, or OU that includes Mac
OS X computers, expand User Configuration > Centrify Settings > Mac OS X Settings > Security Settings, then double-click Lock Smart Card screen.
2 Select the Enabled option and click OK. 3 Expand User Configuration > Centrify Settings > Mac OS X Settings >
Security Settings, then double-click Require a password to wake this computer from sleep or screen saver to require a password to unlock the screen.
4 Select the Enabled option and click OK.
Note On Mac OS X 10.6, if the System Preference: Security > General > Require password [immediately] after sleep or screen saver begins is set, along with the Lock Smart Card screen group policy, the lock behavior will be undefined. Therefore, be certain that if you set the policy, the system preference is not set on any computers to which the GPO applies.
This group policy creates a daemon that listens for the smart card removal event and locks the screen when it occurs.
Requiring smart card login

To fully support smart card login, you can do either of the following: Configure a machine to require smart card login. You configure this option by enabling the Require smart card login group policy (Computer Configuration > Centrify Settings > Mac OS X Settings > Security > Require smart card
Chapter 7 Configuring a Mac OS X computer for smart card login
193
login.) When you enable this policy, no one can log into a machine for which this policy applies with a username and password but must insert a smart card. If you use this approach, be certain that all users have their passwords set to never expire. Otherwise, if a password expires, a user may be unable to log in with a smart card and see a potentially confusing error message about changing their password. If you use the option to require smart card login for specific users, as explained in the next bullet, you can ignore password expiration. Set an individual users account options to require login with a smart card. When you set this option, the user cannot interactively login to a machine with a username and password but must insert a smart card.
Note
To require smart-card login for a specific user: 1 Open the Centrify DirectControl Administrators Console or Active Directory Users and
Computers.
2 Select the user. For example, in the Administrators Console, open domainName >
Zones > zoneName > Users > userName.

3 Right-click the userName and select Properties. 4 Select the Account tab. 5 In Account options, scroll until Smart card is required for interactive logon is
visible, then select it.

6 Click OK.
Disabling smart card support

To disable smart card support:
1 Edit the Group Policy Object linked to a site, domain, or OU that includes Mac OS X
computers, expand Computer Configuration > Centrify Settings > Mac OS X Settings > Security, then double-click Enable smart card support.
2 Select Disabled and click OK.
When the policy takes effect, the smart card specific strings are removed from the /etc/authorization file, and the /etc/cacloginconfig.plist file is deleted.
3 Expand User Configuration > Centrify Settings > Mac OS X Settings >
Security Settings, then double-click Lock Smart Card screen.

4 Select Disabled and click OK.
194
Using smart card login
Verifying smart card configuration

After enabling smart card support, as described in Configuring smart card login, do the following to verify that a smart card is working:
1 Verify that the user is enabled for the zone the Mac OS X computer has joined.
On the Windows machine, open Activity Directory Users and Computers or the Centrify DirectControl Console and view the Centrify Profile for the user. Verify that the user has a profile in the zone to which the Mac OS X machine is joined.
2 On the Mac OS X machine, Click Utilities > Keychain Access. 3 Click Show Keychains. 4 Insert the smart card in the reader and the keychain for the smart card certificate appears
in the Keychains window, for example, CAC-4190-6145-7ACC-2122.
5 Double-click the certificate for the user in the right-hand pane, for example, test user 3. 6 Scroll to find the NT Principal name; for example:
NT Principal Name [email protected]
The NT Principal name in the certificate should match the UPN in Active Directory.
7 Insert the smart card, and enter the users PIN.

When a user inserts a smart card into the card reader attached to a Mac OS X computer that is waiting for login, the login dialog is replaced by a smart card enabled login (if the card is provisioned for an Active Directory user who is enabled for the Centrify zone to which the machine is joined). The smart card login shows the name of the user for whom the card is
195
provisioned, and provides a single text box in which the user can type the PIN associated with the card.
If the user is not enabled for the zone, or is not a valid Active Directory user at all, the smart card login dialog is replaced by the previous login screen, either a list of local users or username and password text entry fields. The user will be successfully logged in if the following conditions are met: The user enters the correct PIN for the smart card.
The card is trusted by the domain and has not been revoked. The card is checked locally first, online or offline, to ensure that the issuing certificate authority is trusted by the Mac OS X computer via keychain trusts, which are set up when the machine joins the domain, and which are periodically refreshed Checking is performed by the domain controller when online, and by the keychain service based on cached CRLs when offline. If the user is not connected to the network but has previously logged on with a smart card or in some other way Mac OS X gets the UPN from the card and looks up the user in the cached data.
If login fails, no feedback is provided to the user as to why the login is being denied as is the case when logging in with a password. Information is logged into various system log files that can help determine the reason for a denied login.
Understanding what happens after login

A user who is logged in with a smart card has access to the same Mac OS X and Centrify DirectControl features and behaviors as a user who is logged in with a username and password. For example, the users network home directory is mounted (if so configured), a mobile user is created (if enabled in Group Policy), and so on. In general the user experience is the same in both connected and disconnected modes, with the exception of single sign-on (SSO). Because Centrify DirectControl does not cache
Note
196
the smart cards PIN, SSO is only available for smart card login while connected to the domain. Of course, certain behaviors and system responses are specific to smart card login: If the user removes the smart card after login, the response of the system depends on whether the group policy Lock smart card screen is enabled in the domain. If it is, the screen locks. Otherwise, the screen does not lock and the user may continue working.
If the user inserts a smart card while the screen saver is active, the response depends on whether Lock smart card screen is enabled in the domain. If it is, the screen saver deactivates. If the policy is not enabled, the screen saver continues running until the user moves the mouse or touches a key. When the screen saver deactivates, the system response depends on the following: If Require password to wake this computer from sleep or screen saver (and the local version of this policy, if it is not overridden by group policy) is set, the user is prompted to authenticate when the screen saver is deactivated. Otherwise, if Lock smart card screen is set, and the screen saver was activated by the user removing the smart card, the user is prompted to authenticate. If neither of these policies is set, the user is not prompted to authenticate when the screen saver deactivates. If the user is prompted to authenticate when the screen saver deactivates, the type of prompt depends on whether a smart card is inserted into the reader at that moment. If there is, the user is prompted for the PIN associated with that smart card. If there is not, the user is not prompted for their password. The reason the screen saver was activated (smart card removal or idle time) has no effect on the type of prompt that is issued when the screen saver deactivates.
Do not use local users who conflict with Active Directory users
When you configure a user for a smart card be certain that the Active Directory username does not match that of a local user. In general, to avoid potential conflicts, Centrify does not recommend creating a local user with the same username as an Active Directory user, although such a configuration does not necessarily cause problems. However, configuring a smart card user with the same name as a local user is inherently unstable and can cause unpredictable results. For a standard login, a local user is always logged in instead of an Active Directory user of the same name because the local account database is checked for authentication before Active Directory. However, the authentication mechanism is different for smart card login, so the Active Directory user on the card will be authenticated instead of the local user, unless the local user has been configured explicitly for the smart card.
197
Troubleshooting smart card log in
Although the Active Directory user is logged in, some commands and applications will look up and apply information for the local user because the Mac OS X directory database is consulted before Active Directory. This means that some of the group policy settings for smart card will not be applied to the Active Directory user and the smart card will not operate properly.
How smart card log in works with fast user switching

Fast user switching enables a user to log in to a machine with a different account without logging out the first account. If a user is logged in with a smart card, fast user switching does not work. For example, with fast user switching enabled, log in to a Mac OS X machine using a smart card (sample name, scuser). Then switch to a different, non-smart card account (for example, normal1) and enter the password. The login fails for the new account and you are then prompted for the smart card PIN. If you unplug the smart card, and the group policy Lock smart card screen is not enabled in the domain, the desktop for normal1 is displayed. If this policy is enabled, the screen is locked. You can unlock the screen by logging in as the normal1 user or by plugging in the smart card.
Troubleshooting smart card log in

If you have any problems with smart card logon, Centrify DirectControl provides a command-line tool, sctool, which you can run to configure smart card logon, as well as to provide diagnostic information. See Understanding sctool on page 213 or the man page for sctool for more information.
198
Chapter 8
Troubleshooting tips
This appendix provides troubleshooting tips for administrators using Centrify DirectControl on Mac OS X computers. The following topics are covered: Using common account management commands
Enabling logging for the Centrify DirectControl Agent Enabling logging for the Mac Directory Service Using DirectControl on a dual-boot system Using adgpupdate appropriately Understanding delays when logging on the first time with a new user account Understanding delays logging on when a computer is disconnected from the network Configuring single-sign on to work with non-Mac OS X machines Restricting login using FTP Logging on using localhost Changing the password for Active Directory users Logging in if Directory Service or Security Agent crashes Disabling Apples built-in Active Directory plug-in Showing the correct status of the Centrify DirectControl plug-in Opening a support case online Collecting information for support cases
Using common account management commands

Most UNIX-based platforms store account information in the local /etc/passwd file, and use commands such as getent command to query that information. On Mac OS X computers, however, you would typically use the Directory Service application to manage local accounts and retrieve user information. For troubleshooting purposes, therefore, you should be familiar with the commands to use for retrieving information about Active Directory users and groups.
199
Enabling logging for the Centrify DirectControl Agent
The following table describes several common Directory Service Command Line (dscl) commands that you may find useful.
Use this command
dscl /Search list /Users
To do this List all of the users in the Directory Service and in Active Directory for the zone. List only the Active Directory users enabled for the zone. Display detailed information about the specified Active Directory username. List all of the groups in the Directory Service and in Active Directory for the zone. List only the Active Directory groups enabled for the zone. Directory groupname.
dscl /CentrifyDC list /Users dscl /CentrifyDC read /Users/username
dscl /Search list /Groups
dscl /CentrifyDC list /Groups
dscl /CentrifyDC read /Groups/groupname Display detailed information about the specified Active
To get detailed information for all users or groups recognized on the Mac OS X computer, you can use the following commands:
lookupd q user a name lookupd q group a name
To get detailed information for a specific user or group, you can use the following commands:
lookupd q user a name username lookupd q group a name groupname
To clear the Directory Service cache, you can use the following command:
lookupd -flushcache
To completely clear the cache of Active Directory login credentials, you should also run the Centrify DirectControl adflush command:
adflush
To retrieve Mac OS version and build information that uname run the following command:
/usr/bin/sw_vers
-a
does not provide, you can

Centrify DirectControl includes some basic diagnostic tools and a logging mechanism to help you trace the source of problems if they occur. These diagnostic tools and log files allow you to periodically check your environment and view information about Centrify DirectControl operation, your Active Directory connections, and the configuration settings for individual computers. In most cases, logging is not enabled by default for performance reasons. Once enabled, however, log files provide a detailed record of Centrify DirectControl activity and can be
200
used to analyze the behavior of adclient and communication with Active Directory to locate points of failure. To enable Centrify DirectControl logging on the Centrify DirectControl Agent:
1 Log in as or switch to the root user. 2 Run the addebug command:
/usr/share/centrifydc/bin/addebug on
Note
You must type the full path to the command because addebug is not included in the path by default.
Once you run this command, all of the Centrify DirectControl activity is written to the /var/log/centrifydc.log file. If the adclient process stops running while you have logging on, the addebug program records messages from PAM and NSS requests in the /var/centrifydc/centrify_client.log file. Therefore, you should also check that file location if you enable logging.
Note By default, Centrify DirectControl logging uses the Macintoshs logging system, which does not capture some important logging information. To guarantee that you capture all DirectControl logging information, complete the following additional steps to direct logging to a specific file.
3 Stop the syslogd service:

service com.apple.syslogd stop
4 Open the file, /etc/centrifydc/centrifydc.conf, with a text editor, find the
parameter and value, logger.destination:syslog, then change the value as follows to direct logging output to the file, /var/log/logfile.log:
logger.destination:/var/log/logfile.log
5 Restart Centrify DirectControl:

/usr/share/centrifydc/bin/centrifydc restart
Note
For more information about starting and stopping Centrify DirectControl, see the Centrify DirectControl Administrators Guide.
For performance and security reasons, you should only enable Centrify DirectControl logging when necessary, for example, when requested to do so by Centrify Technical Support, and for short periods of time to diagnose a problem. Keep in mind that sensitive information may be written to this file and you should evaluate the contents of the file before giving others access to it. When you are ready to stop logging activity, run the addebug
off
command.
Chapter 8 Troubleshooting tips
201
Enabling logging for the Mac Directory Service
Enabling logging for the Mac Directory Service

In addition to enabling logging for the Centrify DirectControl Agent, you may find it necessary to enable logging for the Directory Service. To create a log file for the Directory Service:
1 Log in as or switch to the root or admin user. 2 Run the following command:
killall USR1 DirectoryService
After running this command, you can find the resulting log file in /Library/Logs/DirectoryService. You can then provide both the Centrify DirectControl log file and the Directory Service log file to Centrify Support if you need assistance troubleshooting issues.
Using DirectControl on a dual-boot system

If you are using a dual-boot system, and the computer name is the same for each version of the operating system, the Centrify DirectControl Agent (adclient) will not launch when you reboot and switch operating systems. The problem is that each operating system sets its own password for adclient and the password does not work for the other operating system. The best way to avoid this problem is to provide a different computer name for each operating system. Because the computer names are different, the password for one operating system is not changed by the other operating system. If you want to use the same computer name for both operating systems, you can work around the problem, as follows: Leave the domain (adleave) before rebooting and switching operating systems. Rejoin the domain (adjoin) after the machine reboots with the other operating system.
Note
You may leave and join the domain after rebooting and switching the operating system. However, you will experience some delay while adclient attempts to launch and fails.
Using adgpupdate appropriately

If adgpupdate is run multiple times in succession, it is possible that not all group policies will be applied correctly. To avoid this problem, do not run adgpupdate more than once per minute.
202
Understanding delays when logging on the first time with a new user account
Understanding delays when logging on the first time with a new user account
Depending on the configuration of your Mac OS X startup services, you may find that new users are unable to log on to a computer immediately (within the first 15 to 30 seconds) after a computer is rebooted. By default, the Mac OS X login window only requires the Disks and SecurityService startup services to start successfully to prompt for the user to log in. Authenticating users to Active Directory, however, requires the additional DirectoryServices startup service to be available. Starting the DirectoryServices startup service causes a 10 to 15 second delay before the LoginWindow can successfully authenticate new Active Directory users.
Understanding delays logging on when a computer is disconnected from the network

Depending on the configuration of your Mac OS X startup services, you may find that users may be unable to log on to a computer immediately (within first 15 seconds) when a computer that is disconnected from the network is rebooted. By default, the Mac OS X login window only requires the Disks and SecurityService startup services to start successfully to prompt for the user to log in. Authenticating users to Active Directory, however, requires the additional DirectoryServices startup service to be available. When the computer is disconnected from the network, the DirectoryServices startup service will timeout before it starts successfully, causing a 10 to 15 second delay while the DirectoryServices startup service restarts, before the LoginWindow can successfully authenticate Active Directory users. To prevent this problem on Mac OS X 10.3, you can modify the configuration of the Mac OS X startup parameters for the LoginWindow in the StartupParameters.plist file as follows:
1 Open the file System > Library > StartupItems > LoginWindow >
StartupParameters.plist.
2 Change the following line:
Requires = ("Disks", "SecurityServer");
To:
Requires = ("Disks", "SecurityServer", "DirectoryServices");
3 Save your changes.
203
Configuring single-sign on to work with non-Mac OS X machines
Configuring single-sign on to work with non-Mac OS X machines

On a Mac OS X machine, the ssh client does not forward (delegate) credentials to the server by default. Therefore, when attempting to use ssh from a Mac OS X machine with Centrify DirectControl installed to a non-Mac OS X Machine with Centrify DirectControl installed, single sign-on (SSO) does not work. To fix this problem, set the configuration parameter, GSSAPIDelegateCredentials, to yes in the /etc/ssh_config file on the Mac OS X machine.
Configuring single sign-on to an SMB share on a Windows 2008 Server

In Mac OS X 10.4, 10.5, and 10.6.0 (that is, any version previous to 10.6.1) Apple supplies an older version of Samba that does not support single-sign on to an SMB share located on a Windows 2008 server. This limitation is documented in Apple bug 6745915, which has been fixed in Mac OS X 10.6.1 by updating the Samba version to one that supports Windows 2008 Server. If you have a version of Max OS X prior to 10.6.1, you may work around this issue by saving the credentials in the keychain when you are prompted for the username and password. Users will not be asked again to verify their credentials until they change their password.
Restricting login using FTP

In Active Directory, you can set properties to prevent a user from logging in to other Macintosh computers. However, this restriction will not prevent a user from logging in via FTP to Macintosh machines with Centrify DirectControl installed. It does restrict logging in with telnet, ssh, rlogin, and rsh.
Logging on using localhost

For many UNIX platforms, you can log on using localhost to refer to the local machine; for example:
root@localhost
This syntax does not work when logging on to a Macintosh computer, whether using the Macintosh UI, or remotely through ssh or FTP.
Changing the password for Active Directory users

In the Mac OS X, the passwd command authenticates the user only after you type the user password. Because of this, the passwd command does not recognize the user as an Active Directory user until after the password is entered and the password prompts defined for Active Directory users, which are typically set through group policy or by modifying the Centrify DirectControl configuration file, are not displayed. You can still use the passwd or
204
Logging in if Directory Service or Security Agent crashes
command to change the Active Directory password for a user, but you will not see any visual indication that you are modifying an Active Directory account rather than a local user account.
chpass

If the Apple Directory Service or Security agent crashes, all users may be locked out of the system. If the crash is caused by any of the Centrify DirectControl plug-ins, you can do the following to regain access to the system: Boot into single-user mode
Remove Centrify DirectControl software from the login executable path. Reboot the system and collect log files and configuration files to send to Centrify customer support.
Checking the status of Centrify DirectControl components

This section shows how to check the status of DirectControl components that may have contributed to the Directory Service or Security Agent crash. If you are already certain of the DirectControl component that may be a problem, skip this section and go to Disabling Centrify DirectControl components on a non-functioning system on page 206 to disable the problem component. To check the current status of Centrify DirectControl components:
1 Shut down the Mac OS X machine if it is on. 2 Log on to the machine in single-user mode by pressing the power key while clicking and
holding Apple-S until you see the root prompt in a terminal window.
3 Execute the following command to see if adclient will be started at boot time:
launchctl list | grep com.centrify.adclient
If the output is:

adclient will be started at boot time. empty adclient will not be started at boot time.
com.centrify.adclient
On Centrify DirectControl versions prior to 4.0, execute the following command as well:
ls -1 /Library/StartupItems | grep Centrify
If the output is: anything but empty adclient may be started at boot time. empty adclient will not be started at boot time.
4 Execute the following command to see if dsplugin will be started at boot time:
205
defaults read /Library/Preferences/DirectoryService/DirectoryService | grep Centrify
If the output is: empty, or if the output is "Centrify be loaded.
DirectControl" = Active;
the plugin will
"Centrify DirectControl" = Inactive;
dsplugin will not be loaded
5 Execute the following command to see if CentrifyPAM is enabled:

cat /etc/authorization | grep CentrifyPAM
If the output contains lines similar to the following:

<string>CentrifyPAM:setcred,privileged</string>
the CentrifyPAM module
will be loaded. If the output is empty the CentrifyPAM module will not be loaded
6 Execute the following command to see if CentrifySmartCard is enabled:

cat /etc/authorization | grep CentrifySmartCard
If the output contains lines similar to the following:

<string>CentrifySmartCard:setcred,privileged</string>
the
module will be loaded. If the output is empty the CentrifySmartCard module will not be loaded
CentrifySmartCard PAM
7 Execute the following commands to see if CentrifyDC
module is enabled for
particular services:
cat /etc/pam.d/sshd cat /etc/pam.d/sudo | grep pam_centrify | grep pam_centrify
cat /etc/pam.d/login | grep pam_centrify
If the output contains lines similar to the following: auth sufficient pam_centrifydc.so the CentrifyDC PAM module will be loaded for that service. If the output is empty the CentrifyDC PAM module will not be loaded for that service.
Disabling Centrify DirectControl components on a non-functioning system

To disable Centrify DirectControl components when you cannot log in normally:
1 Shut down the Mac OS X machine if it is on. 2 Log on to the machine in single-user mode by pressing the power key while clicking and
3 Remount the root file system in read/write mode:
mount /
4 Disable automatic startup of adclient.
When the machine is joined to a domain, adclient starts automatically when the
206
machine boots up. Then, adclient enables DSPlugin and CentrifyPAM. To prevent the plug-ins from starting you disable adlcient, as follows:
launchctl unload -w /Library/LaunchDaemons/com.centrify.adclient.plist
5 Remove the CentrifyDS plugin from Apple Directory Service by executing the following
commands:
defaults write /Library/Preferences/DirectoryService/DirectoryService "Centrify DirectControl" '<string>Inactive</string>' defaults delete /Library/Preferences/DirectoryService/SearchNodeConfig "Search Node Custom Path Array" defaults write /Library/Preferences/DirectoryService/SearchNodeConfig "Search Policy" '<integer>1</integer>'
6 Remove the CentrifyPAM plugin from the Apple Security Agent by executing the
following command:
/System/Library/CoreServices/SecurityAgentPlugins/CentrifyPAM.bundle/Contents/ Resources/config disable
7 If its enabled, remove the CentrifySmartCard plugin from the Apple Security Agent by
executing the following command:

System/Library/CoreServices/SecurityAgentPlugins /CentrifySmartCard.bundle/Contents/Resources/config disable
8 Remove pam_centrifydc.so rules from ssh, sudo, and login configuration files.
When a Mac OS X machine joins a domain, CentrifyPAM rules for using pam_centrifydc.so are added to ssh, sudo, and login configuration files. If CentrifyPAM is not working, you need to remove these rules. The easiest way to do so is to restore the backup configuration files that are created when the machine joins a domain. The backup files are named: service.pre_cdc (for example, sshd.pre_cdc):
cp -f /etc/pam.d/sshd.pre_cdc /etc/pam.d/sshd cp -f /etc/pam.d/sudo.pre_cdc /etc/pam.d/sudo cp -f /etc/pam.d/login.pre_cdc /etc/pam.d/login
9 Reboot the machine. No Centrify DirectControl code should be running at this point.
If you still cannot log in after completing the steps in this procedure, you can use target disk mode to connect to the disabled machine via a FireWire connection to another computer. Then you can transfer log and configuration files to the running computer to show to Centrify customer support. To connect using target disk mode:
1 Shut down the disabled computer and turn on a second computer. 2 Connect the two computers using a 6-pin to 6-pin FireWire cable (or use a 9-pin to 9-
pin cable if both computers have higher-speed Firewire 800 ports).

3 Start up the disabled computer while holding down the T key.
207
A disk icon for the disabled computer appears on the desktop of the second computer. You can open this icon and drag the relevant log and configuration files to the second computer.
4 Drag the icon for the disabled computer to the trash to eject it. 5 Push and hold the power button of the disabled computer for at least five seconds to force
it to shut down. Then disconnect the FireWire cable.
Creating a local admin to restore a disabled login

If you cannot log on with the original local administrator, you can create a new one.
Note
This procedure requires that you are running Mac OS X 10.5 or newer.
To create a new local administrator:

1 Log on to the machine in single-user mode by pressing the power key while clicking and
2 Remount the root file system in read/write mode:
mount /
3 Start the Apple Directory Service:

launchctl load /System/Library/LaunchDaemons/com.apple.DirectoryServices.plist
4 Create a new user named super with a password of super.

dscl . -create /Users/super dscl . -create /Users/super UserShell /bin/bash dscl . -create /Users/super RealName SUPERUSER dscl . -create /Users/super UniqueID 505 dscl . -create /Users/super PrimaryGroupID 0 dscl . -create /Users/super NFSHomeDirectory /Users/super mkdir /Users/super dscl . -passwd /Users/super super dscl . -append /Groups/admin GroupMembership super
5 Restart the machine normally (in mutli-user mode) and login with the username super
and the password super.
Reenabling Centrify DirectControl

To reenable Centrify DirectControl software:
1 Log in to the machine as an administrator in multi-user mode. 2 Leave the domain. 3 Rejoin the domain.
208
Disabling Apples built-in Active Directory plug-in
Disabling Apples built-in Active Directory plug-in

Apple provides a built-in Apple Directory plug-in that may interfere with Centrify DirectControl installation and operation. Therefore, before installing the Centrify DirectControl Agent, disable Apples built-in Active Directory plug-in. In addition, remove Active Directory from the Authentication and Contacts search paths. If this plug-in is enabled and Centrify DirectControl has been installed, disable the plug-in, then reboot the Macintosh computer for reliable DirectControl operation.
To disable the Apple Directory plug-in and remove Apple Directory from the Authentication and Contacts search paths: 1 Do one of the following, depending on the Mac OS X version you are running:
On Mac OS X 10.4, open the Directory Access utility. On Mac OS X 10.5 or later, open the Directory Utility.
2 Click the Services tab or icon and deselect Active Directory. Then click Apply. 3 On Mac OS X 10.5 or later, click the Search Policy icon. 4 Click the Authentication tab, then select Custom path in the Search box. If Active
Directory was previously enabled, Active Directory shows (in red font) in the Directory Domains box; for example:
/Active Directory/All Domains
5 Select /Active Directory/All Domains and click Remove. Then click Apply. 6 Click the Contacts tab, then select Custom path in the Search box. If Active Directory
was previously enabled, Active Directory shows (in red font) in the Directory Domains box; for example:
/Active Directory/All Domains
7 Select /Active Directory/All Domains and click Remove. Then click Apply. 8 Close the window. 9 If you have already installed the Centrify DirectControl Agent, reboot the machine.
Showing the correct status of the Centrify DirectControl plug-in

The Centrify DirectControl plug-in is automatically added to the list of Apple Directory Utility plug-ins that are used for lookup and authentication. However, if the Apple Directory Utility tool is running when you install Centrify DirectControl, or when you join or leave a domain before updating to a new version of Centrify DirectControl, it will incorrectly display the status of the plug-in. For example, it will show the status as disabled, when in fact, the plug-in is enabled.
209
Opening a support case online
Apple changed the name of the directory access tool from Apple Directory Access (Mac OS X 10.4) to Apple Directory Utility (Mac OS X 10.5). The current manual always refers to this tool as Apple Directory Utility, so if you are running Mac OS X 10.4, when you see Apple Directory Utility in the manual, it is referring to Apple Directory Access.
Note
To avoid this problem, before launching the installer, be certain that the Apple Directory Utility tool is closed. If the Directory Utility was open during installation, simply close and re-open Directory Utility, then make certain that the Centrify DirectControl plug-in is enabled. You may also restart the Centrify DirectControl plug-in from the command line, as follows:
1 Close the Directory Utility. 2 Open a terminal. 3 Enter the following command:
/usr/share/centrifydc/bin/dsconfig restart
4 Open the Directory Utility. The status of Centrify DirectControl should be enabled.
Opening a support case online

If you need assistance with troubleshooting an issue, you may need to open a case with Centrify Support. Centrify recommends you take the following steps in preparation for opening a new case:
1 Check the Centrify Support Portal on the Centrify Web site to search the Knowledge
Base to see if your problem is a known issue or something for which there is a recommended solution. Open http://www.centrify.com/support/login.asp in a Web browser. Log in using your customer account information and password. Click Find Answer and type one or more key words to describe the issue, then click Find to view potential answers to your question. For example, to search for known issues, type known issues and click Find to see articles related to the known issues in different DirectControl releases. If your issue is not covered in an existing Knowledge Base article or the Centrify documentation set, you should open a case with Centrify Support.
2 Click Log a Case to open a new case using the Centrify Support Portal.
Alternatively, you can contact Centrify Support by email or telephone, if you prefer. Worldwide contact information is available in the How to open a case and collect information for Centrify Support Knowledge Base article (KB-0301).
3 Provide as much information as possible about your case, including the operating
210
Collecting information for support cases
environment where you encountered the issue, and the version of the Centrify product you are working with, then click Submit to open the case.

To help ensure your issue gets resolved quickly and efficiently, you should take the following steps to gather information about your working environment:
1 Verify Centrify DirectControl is running on the computer where you have encountered
a problem. For example, run the following command:

ps aux | grep adclient
If the adclient process is not running, check whether the Centrify DirectControl watchdog process, cdcwatch, is running:
ps aux | grep cdcwatch
The cdcwatch process is used to restart adclient if it stops unexpectedly. The commands in the following three steps must be run as root or with the sudo command.
Note
2 Enable logging for the Centrify DirectControl Agent; for example:

sudo /usr/share/centrifydc/bin/addebug on
3 Create a log file for the Mac OS X Directory Service; for example:
sudo killall USR1 DirectoryService
4 Run the adinfo command to generate a report that describes the domain and current
environment; for example:

sudo adinfo --diag --output filename
5 Duplicate the steps that led to the problem you want to report. For example, if an Active
Directory user cant log in to a DirectControl managed system, attempt to log the user in and confirm that the attempt fails. Be sure to make note of key information such as the user name or group name being used, so that Centrify Support can identify problem accounts more quickly.
6 Verify that log file /var/log/centrifydc.log or /var/adm/syslog/centrifydc.log
exists and contains data.

Note
The commands in the following two steps must be run as root or with the sudo command.
7 Generate information about Active Directory domain connectivity and configuration files
by running the following command:

sudo adinfo --support
This command writes output to the file /tmp/adinfo_support.txt.
211
8 If there is a core dump during or related to the problem, save the core file and inform
Centrify Support that it exists. Centrify Support may ask for the file to be uploaded for their review. If the core dump is caused by a DirectControl process or command, such as adclient or adinfo, open the /etc/centrifydc/centrifydc.conf file and change the adclient.dumpcore parameter from never to always and restart the Centrify DirectControl Agent:
sudo /usr/share/centrifydc/bin/centrifydc restart
Note
For more information about starting and stopping Centrify DirectControl, see the Centrify DirectControl Administrators Guide. directory. You should be able to create an archive of the directory, if
9 If there is a cache-related issue, Centrify Support may want the contents of the
/var/centrifydc
needed.
10 If there is a DNS, LDAP, or other network issue, Centrify Support may require a
network trace. You can use Ethereal to create the network trace from Windows or UNIX. You can also use Netmon on Windows computers.
11 Create an archive (for example, a .tar or .zip file) that contains all of the log files and
diagnostic reports you have generated, and add the archive to your case or send it directly to Centrify Support.
12 Consult with Centrify Support to determine whether to turn off debug logging. If no
more information is needed, run the following command, which must be run as root or with sudo:
sudo /usr/share/centrifydc/bin/addebug off
212
Chapter 9
Using sctool
This chapter provides a complete reference to the sctool command-line tool. The sctool utility is used to enable, disable, and diagnose smart card support. It may also be used to obtain Kerberos credentials from the smart card in the reader.
Displaying usage information

You can display a summary of usage information for sctool by typing the command and the --help or -h option; for example:
sctool --help
The usage information displayed is a summary of the valid command line options and required arguments and a brief description of each option. For more complete information about sctool, you can review the information in the commands manual page. For example, to see the manual page for sctool:
man sctool
Understanding sctool
Centrify DirectControl provides a group policy, Enable smart card support, to enable smart card support on Mac OS X 10.4 and later machines. This group policy uses the sctool utility to add smart card specific strings to the /etc/authorization file and to create the /etc/cacloginconfig.plist file. In general, you can use the group policy to enable smart card support. However, the sctool utility is also available to specifically configure or diagnose smart card support on any Mac OS X machine. When you disable smart card support, with the group policy or with sctool, the smart card strings are removed from /etc/authorization, and /etc/cacloginconfig.plist is deleted. See Chapter 7, Configuring a Mac OS X computer for smart card login, for detailed information about using group policies to enable smart card login and screen locking.
Note When you enable or disable smart card support with sctool, the change is temporary, unless the group policy, Enable smart card support, is not configured. For example, if the policy is set to enable smart card support, and you disable it with sctool, at the next reboot the policy takes effect and smart card support is re-enabled. If the policy is not configured, you can control smart card support on individual machines using sctool.
213
Synopsis
sctool -e -d -s -D -S -k --enable --disable --status --dump --support --pkinit
Setting valid options

You can use the following options with this command:
Note
You may specify only one option at a time when running sctool.
To do this Enable smart card support by making necessary edits to the /etc/authorization system configuration file, and by creating the /etc/cacloginconfig.plist file. Disable smart card support by removing smart-card specific strings from /etc/authorization, and by deleting /etc/cacloginconfig.plist. Show whether smart card support is enabled or disabled. This option outputs one of these two messages: .Centrify DirectControl SmartCard support is enabled (then exits with status 0). Centrify DirectControl SmartCard support is disabled (then exits with status 1). Display information about the system setup and about any smart cards that are attached to the machine. For each card, this option lists the type of card and any summary information. It also enumerates all identities on the card and lists the following for each: Subject name UPN (if present) Whether the card is trusted Data signing success or not Signature verification Lists the same information as the --dump option and additionally lists the state of the system configuration files.
Use this option

-e, --enable
-d, --disable
-s, --status
-D, --dump
-S, --support
214
Use this option

-k, --pkinit
To do this Obtain Kerberos credentials from the smart card currently in the reader and store them in the user's cache. This option obtains a ticket granting ticket (TGT) using the public/private key pair stored on the smart card, which is intended to be used in the same manner as the kinit(1) command: to obtain or renew credentials when they are not handled automatically (such as a long login session during which the user does not lock the screen saver), or for troubleshooting. In normal usage you should never need to run sctool --pkinit. To obtain kerberos credentials, sctool must find a certificate that matches the user, is valid for smart card login, is not expired or revoked, and is trusted by the domain. There are several ways to specify how the certificate should be found (note that only one of these options is used; sctool does not try the later options if an earlier option fails to find a certificate): If a UPN is specified on the command line, the user's keychains and the smart card in the reader (if any) are searched for a valid certificate that matches that UPN. If no UPN is specified on the command line, and the CDC_SMARTCARD_TOKEN environment variable is set, the smart card named in the environment variable is searched for a valid certificate. The NT Principal Name attribute of that certificate is used as the UPN. If the USER_PRINCIPAL_NAME environment variable is set, a certificate that matches that UPN is searched for in the same manner as in the first option. If none of the above command-line options or environment variables are set, the sctool looks up the user in AD to obtain the UPN, and searches for a matching certificate in the same manner as in the first option. While sctool --pkinit can use certificates that are stored in an on-disk keychain rather than a smart card, only use with a smart card is officially supported. If no suitable certificate is found, sctool prints an error and exits with status 1. Otherwise, it checks whether the machine is operating in disconnected mode. If so, sctool immediately exits with status 2, since Kerberos tickets cannot be obtained in disconnected mode. This allows the authorization mechanism to permit smart card login in disconnected mode, while still verifying that the certificate on the smart card is valid and trusted. If the machine is connected to the domain, sctool contacts the domain controller to obtain a TGT using the associated private key. If this fails, sctool prints an error and exits with status 1. If the users password has expired, sctool may be unable to retrieve a TGT and will issue the message:
krb5_get_init_creds_pkinit failed: Password has expired
To resolve this issue, edit the users ADUC Properties page by clicking the Profile tab and checking one or both of the following options: Account option: Smart card is required for interactive login Password never expires.
Examples
Display information about the smart cards attached to the machine:
#sudo sctool -D Password:
Chapter 9 Using sctool
215
Enable smart card support:

#sudo sctool -e Password:
216
Appendix A
Installing and removing DirectControl and joining and leaving a domain

This appendix shows other methods of installing DirectControl besides the standard method using the package installer (DMG file); see Installing the Centrify DirectControl Agent on page 12. It also shows how to remove DirectControl and how to join and leave a domain. This appendix contains the following topics: Installing using the install.sh command-line program
Installing remotely using Apple Remote Desktop Removing Centrify DirectControl Joining an Active Directory domain Leaving an Active Directory domain Viewing the results from joining or leaving a domain
217
Installing using the install.sh command-line program
Installing using the install.sh command-line program

This section explains how to install using the install.sh command-line program. This method is recommended for experienced UNIX administrators who are familiar with UNIX command-line installations. Otherwise, you should install by using the graphical user interface, which is described in Installing the Centrify DirectControl Agent on page 12.
To install using the install.sh command-line program:
Note
Before launching the installer, be certain that Apple Directory Utility is closed. If it is open while running the installer, it causes the Centrify DirectControl Directory Access plug-in to show the incorrect status, that is, it shows that the plug-in is disabled when in fact it is enabled.
1 Log on with a valid user account.

Note
You are not required to log on as the root user on, but you must know the password for the Administrator account to complete the installation.
2 Mount the cdrom device using the appropriate command for the local computers
operating environment, if it is not automatically mounted.

3 Change to the appropriate directory on the CD or on the network where the Centrify
DirectControl agent package is located. For example, change to the Agent_Mac directory.
4 Run the install.sh script to start the installation of Centrify DirectControl on the local
computers operating environment. For example:

sudo ./install.sh
Before beginning the installation, the install.sh script runs the ADCheck utility, which performs a set of operating system, network, and Active Directory checks to verify that the Mac OS X computer meets the system requirements necessary to install the Centrify DirectControl Agent and join an Active Directory domain.
5 Review the results of the checks performed. If the target computer, DNS environment,
and Active Directory configuration pass all checks with no warnings or errors, you should be able to perform a successful installation and join. If you receive errors or warnings, correct them before proceeding with the installation.
6 Follow the prompts displayed to select the services you want to install and the tasks you
want to perform. For example, you can choose whether you want to join a domain or restart the local computer automatically at the conclusion of the installation. When installation is complete, see Understanding the directory structure on page 223 for a description of the directories and files installed for Centrify DirectControl.
218
Installing remotely using Apple Remote Desktop

If you have Apple Remote Desktop 3 for remote software distribution and are deploying on computers running Mac OS X 10.4 or later, you can use Apple Remote Desktop to deploy the Centrify DirectControl Agent and join remote computers to Active Directory without user interaction. With Apple Remote Desktop 3, you can add pre- and post-installation scripts with custom parameters. By adding a post-installation script to the deployment package, you can set the appropriate parameters to join a remote computer to a specific Active Directory domain. A sample post-installation script, userscript, is included with the Centrify DirectControl software package. You can modify this sample script to specify the Active Directory domain, user name and password for joining the domain, the organizational unit or container to add the computer account to, and other parameters. By default, the sample script is automatically removed from the local computer upon completion, so that any passwords defined in the file are removed from the computer.DirectControl
To remotely install the DirectControl Agent and join a computer to the domain using Apple Remote Desktop 3: 1 Verify that you have an Apple Remote Desktop 3 Admin station and one or more Apple
Remote Desktop 3 Clients, and that the operating environment on those computers is Mac OS X 10.4 or later.
2 Verify that all of the Apple Remote Desktop 3 Client computers where you want to
install Centrify DirectControl are set to Allow Remote Desktop using the Service pane in the Sharing system preference. For example:
3 Copy the Centrify DirectControl Agent package, for example centrifydc-release-
Appendix A Installing and removing DirectControl and joining and leaving a domain
219
mac10.4-i386.dmg, to the Apple Remote Desktop 3 Admin computer and verify that you
can access the disk image.

4 Remove the following files from the package because they may cause problems for a
remote installation:
CentrifyDC.pkg/Contents/Resources/display-popup.sh,
which displays a popup
window and can hang an unattended installation.
CentrifyDC.pkg/Contents/Resources/open_adjoin.sh, which attempts to join a machine to a domain by running the adjoin command. For a remote install, to automatically join a domain, you need to run a post-installation script as explained in the next step.
To remove the files, open the .dmg file; then drag the CentrifyDC.pkg file to a writable disk.
display-popup.sh
Right-click or Ctrl-click the .pkg file to open it. Expand Contents/Resources, then drag and open_adjoin.sh to the trash. Close the package.
5 Add the post-installation script for joining the domain to the Centrify DirectControl
Agent installation package. By default, the userscript included in the Centrify DirectControl package is executed, then removed as a post-installation step. You can modify this file to automatically perform any post-installation tasks needed. If you dont want to automatically join the domain when installing on remote computers, you can skip to the next step. To automatically join the domain when installing on remote computers: If you have not already done so, open the Centrify DirectControl disk image, and copy the CentrifyDC.pkg to the Desktop or another writable directory. Click Applications > Utilities > Terminal to open a new terminal window. Change to the CentrifyDC.pkg/Contents/Resources directory. For example:
cd desktop/centrifydc.pkg/contents/resources
Open the userscript file in a text editor, such as vi. For example:
vi userscript
Edit the script to perform post-installation tasks, such as joining the computer to a domain, then save the script and quit the text editor.
At a minimum, the userscript file must specify the Active Directory Administrator password and Active Directory domain to join an Active Directory domain after installing the Centrify DirectControl Agent:
#!/bin/sh adjoin --password admin_password domain
For example, to join the arcade.com domain using the user account and password for the Active Directory user leo and placing in the computer in the organizational unit mac_os,
220
the userscript might look like this:

#!/bin/sh # This file will be executed after installing CentrifyDC, # and will be deleted after execution. adjoin --user leo --password mil3s4 --container ou=mac_os
Note For complete information about adjoin command line options, see the adjoin man page or the Centrify DirectControl Administrators Guide.
6 Open Remote Desktop on the Admin Computer, then click Scanner and verify that the
Mac computers on which you plan to install Centrify DirectControl are listed and that ARD Version column displays 3.0 (or later). For example:
Check this column for the Remote Desktop version
7 Select one or more computers from the list, then click Install. For example:
Click Install
Select one or more computers from the list
8 In the Install Packages window, click + to locate the CentrifyDC.pkg in the Centrify
221
DirectControl Agent disk image. For example:
Click + to add the CebtrifyDC.pkg
9 In the Centrify DirectControl Agent disk image, select the CentrifyDC.pkg file and click
Open to add it to the Install Packages list. For example:
10 In the Install Packages window, click Install to install the listed packages, For example:
In most cases, you can use the default settings to install the Centrify DirectControl
222
Removing Centrify DirectControl
Agent. If you want to schedule the installation for another time rather than completing the installation now, click Schedule. For more information about the Apple Remote Desktop installation parameters, see Chapter 8 Administering Client Computers, in the Apple Remote Desktop Manual. If you click Install the Remote Desktop displays a progress bar and task status for each of the computers selected for the installation.
Understanding the directory structure

When you complete the installation, the local computer will be updated with the following directories and files for Centrify DirectControl:
This directory /etc/centrifydc /usr/share/centrifydc Contains The Centrify DirectControl Agent configuration file and the Kerberos configuration file. Kerberos-related files and service library files used by the Centrify DirectControl Agent to enable group policy and authentication and authorization services. Command line programs to perform Active Directory tasks, such as join the domain and change a user password. No files until you join the domain. After you join the domain, several files are created in this directory to record information about the Active Directory domain the computer is joined to, the Active Directory site the computer is part of, and other details.
/usr/sbin /usr/bin /var/centrifydc
/System/Library/Frameworks/DirectoryService.f The Centrify DirectControl Directory Service Plugin, ramework/Resources/Plugins CentrifyDC.dsplug, that enables you to join or leave the domain using the graphical user interface.
Removing Centrify DirectControl

You can remove the Centrify DirectControl Agent and related files by running the Centrify DirectControl uninstall.sh script. The uninstall.sh script is installed by default in the /usr/share/centrifydc/bin directory on each Centrify DirectControl-managed system. There is no DMG package for removing Centrify DirectControl. To remove Centrify DirectControl on a Mac OS X computer:
1 Open a Terminal window on the computer where the Centrify DirectControl Agent is
installed. For example, select Applications > Utilities > Terminal.

2 Switch to the root user or a user with superuser permissions. For example:
su Password: root_password
3 Run the uninstall.sh script. For example:
223
Joining an Active Directory domain
/bin/sh /usr/share/centrifydc/bin/uninstall.sh
The uninstall.sh script will detect whether the Centrify DirectControl Agent is currently installed on the local computer and whether the computer is currently joined to a domain. If the computer is not currently joined to a domain, the script will begin removing Centrify DirectControl files from the local computer.

This section shows how to use the Centrify ADJoin utility to join a domain. You may run the adjoin command-line utility, interactively or in a script, for each Macintosh machine you want to add to a domain in the forest. See the Centrify DirectControl Administrators Guide for details.
To start the Centrify DirectControl program for joining or leaving a domain: 1 Click Applications > Utilities > Centrify > Adjoin. Then double-click Adjoin to
open it.
2 Enter the following information. For example:

Select this option Computer name Join to this Active Directory Domain Auto Zone To do this Defaults to the machine name but you can change it if you want to use a different name for the local host in Active Directory. The name of the domain to join. If you are already joined, a name is shown. Select Auto Zone to join the machine through Auto Zone, which allows you to join a machine with little or no configuration. See Chapter 4, Connecting a Mac OS X machine to Auto Zone..
224
Select this option Join this Zone
To do this Select Join this Zone: and type a zone name to join the machine to a zone. If you have not yet created any zones, you can join the default zone, which is created automatically by DirectControl. Overwrite the information stored in Active Directory for an existing computer account. If you want to replace the information for a computer account with the same name as the local computer, check this option. Checking this option is the same as running the adjoin command with the --force option.
Overwrite existing joined computer
Centrify provides a free version of DirectControl called Centrify DirectControl Express that does not include licensed features, such as group-policy enforcement, zonebased access control, and smart card login to Active Directory. The Disable Licensed Features button turns off licensing for DirectControl on the local computer, making it an Express installation. After licensing is disabled, this button toggles to Enable Licensed Features. See the Centrify Suite Express Edition Administrators Guide for complete information on installing and configuring Centrify DirectControl Express. For a Standard Centrify DirectControl suite installation, you can ignore this button.
Note
225
To use the default settings for joining the domain, you can continue to the next step. To specify additional options, click Show advanced options to display the additional options:
Select this option Container DN
To do this Specify the distinguished name (DN) of the container or Organizational Unit in which you want to place this computer account. By default, computer accounts are created in the domains default Computers container. If you want to specify a container, check this option, then type the DN without its domain suffix. For example, if the domain suffix is acme.com and you want to place this computer in the paris.regional.sales.acme.com organizational unit, you would type:
ou=paris, ou=regional, ou=sales
Checking this option is the same as running the adjoin command with the --container option. Preferred Domain Server Specify the name of the domain controller to which you prefer to connect. You can use this option to override the automatic selection of a domain controller based on the Active Directory site information. Checking this option is the same as running the adjoin command with the --server option. Specify an alias name you want to use for this computer in Active Directory. This option creates a Kerberos service principal name for the alias and the computer may be referred to by this alias. Checking this option is the same as running the adjoin command with the --alias option.
Computer Alias Name
Do not update PAM and DirectoryService Indicate that you do not want to update the local systems PAM and configuration DirectoryService configuration. If you dont want to have the PAM files and DirectoryService configuration updated automatically, check this option. Checking this option is the same as running the adjoin command with the --noconf option.
For more information about these options, see the Centrify DirectControl Administrators Guide or the adjoin man page.
3 Click Join Domain. 4 Type the Active Directory user name and password for a user with permission to join the
226
Leaving an Active Directory domain
local computer to the Active Directory domain, then click OK.
5 Type the user name and password for the local Administrator account.

To start the Centrify DirectControl program for joining or leaving a domain:
1 Click Applications > Utilities > Centrify > Adjoin. Then double-click Adjoin to
open it.
2 Click Leave Domain.
Select Force local leave to force the local computers settings to their pre-join conditions even if the utility cannot connect to Active Directory or is not successful in deactivating the Active Directory computer account; for example, if you receive an error message, such as DNS is down after clicking Leave Domain. You must use this option
Note
227
if the Active Directory computer account has been modified or deleted so that the host computer can no longer work with it.
3 Type the Active Directory user name and password for a user with permission to remove
the local computer from the Active Directory domain, then click OK.
4 Type the user name and password for the local Administrator account.
228
Viewing the results from joining or leaving a domain
Viewing the results from joining or leaving a domain

When joining or leaving a domain, you can click Show Log to display the commands issued and any diagnostic or error messages generated from joining or leaving the domain. For example:
229
Index
A
account mapping 53 Active Directory leaving the domain 227 linking Group Policy Objects 62 ADCheck 13 adclient log file 200 adgpupdate program 67 ADM templates adding 66 administrative template installation 64, 65 introduction 60 agent installation options 12 Apple Directory Access see Directory Access Apple Directory Utility see Directory Utility Apple Remote Desktop deploying DirectControl 219 enabling access 106 enabling administrators 99 sharing preference 106 application access 115 Automount network shares 120 technical support 10 troubleshooting issues 200 updating policies manually 67 Centrify web site 10 centrify_mac_settings.adm template 60 centrify_mac_settings.xml template 60 command line programs man pages 213 computer configuration 802.1X settings 77, 114 accounts settings 81 automatic downloads 109 automatic login 101 bypass proxy settings 97 default firewall 91 display sleep mode 88 energy saver 87, 89 firewall logging 93 firewall settings 90 FTP access 105 group policy refresh 68 hard disk sleep mode 87 iChat 91 inactive periods 102 Internet sharing 94 iPhoto 91 iTunes 92 login options 81 logon banner 69 MaxPollInterval setting 68 network settings 95 network time 92 network time provider 68, 69 passive FTP mode 97 password policies 69 personal file sharing 104 policy categories 72, 74 power button sleep 87 printer sharing 106 proxy servers 97 remote desktop 106
B
Block UDP Traffic 92 Bypass proxy settings for these hosts & domains 97
C
Centrify DirectControl agent installation 13 documentation 9 enabling logging 200 files and directories 223 group policy extension 60 package location 13 removing 223
230
remote events 106 remote login 105 remote management 86, 98 restart automatically 88 searched domains 95 security settings 101 simple host names 97 sleep mode 88 software updates 107 stealth mode 93 UDP traffic 92 update server 109 virtual memory 103 waking 88 Web sharing 105 Windows sharing 105 Xgrid controllers 106 Configure Finder commands 127 Configure Finder preferences 128 Configure Finder views 129 Configure Windows NTP Client 69 conventions, documentation 8
E
Enable built-in System Preferences panes 186, 188, 190 Enable Firewall 91 Enable Firewall Logging 93 Enable iChat 91 Enable iPhoto 91 Enable iTunes Music Sharing 92 Enable login items 135 Enable Network Time 92 Enable other System Preferences panes 186, 188, 190 Enable smart card logon 102 Enable Stealth Mode 93 Enable Windows NTP Client 69 Evaluation Guide 9
F
FTP Access 105
G
group policies administrative template 60 background refresh 68 limitations 62 relation to preferences 60 updating manually 67 using default policies 68 workgroup manager 61 Group Policy Management Console 62 Group Policy Object Editor 62, 68
D
delete mobile accounts automatically 151, 159, 168 Directory Access 209 Directory Utility 209 Disable automatic login 101 Disallow all Internet Sharing 94 Dock settings adding other folders 123 animation 124 applications listed 125 documents or folders 125 hide and show 124 icon size 123 locking 124 magnification 124 merging 125 minimizing effect 124 position 124 workgroup preference 122 documentation additional 9 audience 7 conventions 8 summary of contents 7 to 8
I
installation administrative template 64, 65 command line script 13 files and directories 223
J
joining a domain 224 to 227
L
Legacy Settings (Mobility Synchronization) 142 Limit items shown in System Preferences 185, 187, 189 localhost syntax 204 Lock Smart Card screen 178 Lock the Dock 124 log files
Index
231
location 201 performance impact 201 purpose 200 Log out after number of minutes of inactivity 102 login items, enabling 135 login script 100, 175, 177 Login Settings 134 Login Window Settings 81 log-on delays 203 logout script 176
O
Open Directory, migrating from 47 to 49
P
password changes 204 pecify Login Window Profiles 79 pecify System Profiles 80 Personal File Sharing 99, 104 Personal Web Sharing 99, 105 Place applications in Dock 125 Place documents and folders in Dock 125 Printer Sharing 106 Prohibit Access to App Store 86 Prohibit authentication with expired password 178
M
Mac OS X accessing SMB shares 36 authenticated printing 39 automounting file shares 29 directory on CD 13 disconnected operation 203 files and directories 223 group policies 60, 63 local account mapping 53 log-on delays 203 password changes 204 password enforcement policies 68 system preferences 59 man pages adjoin options 221 displaying 213 source of information 10 Manually/automatically sync in the background 10.5
156
Q
Quick Start 9
R
release notes 11 Remote Apple Events 106 Remote Login 99, 105 remote management administrators group 99 Require password 102 Require smart card login 103 root user enabling logging 201, 202
S
scripts 100, 175 sctool 213 to 216 secure virtual memory 103 Set computer idle time for starting screen saver 121 Set computer sleep time 88 Set display sleep time 88 Set login window settings 81 Set machine sleep/shutdown time 89 Set machine startup time 89 single sign-on configuring 204 limitation with Windows 2008 Server 36, 204 Skip items that end with 145, 147, 153, 155, 162, 164, 171, 173 Skip items that start with 145, 147, 153, 155, 162, 164, 171, 173 Skip items whose full path is 145, 147, 153, 155, 162,
Manually/automatically sync in the background 10.6

165
Manually/automatically sync in the background 10.7

174
Map /home to /Users 76 Map zone groups to local admin group 85 media access policies 137 mobile accounts delete automatically 151, 159, 168 mobility preferences 140
N
network file sharing 29 Network Time Protocol 69
232
164, 171, 173 Skip items whose name contains 145, 147, 153, 155, 162, 164, 171, 173 Skip items whose name is 145, 147, 153, 155, 162, 164, 171, 173 Skip items whose partial path matches 145, 147, 153, 155, 162, 164, 171, 173 sleep hard disk(s) 87 smart cards configuring machines for 191 to 198 enabling 102 enabling screen lock for 178 logging in with while offline 196 software updates 109 Specify login script 175 Specify logout script 176 Specify multiple login scripts 100, 177 specify User Profiles 114 SSO configuring 204 synchronization rules 140 automatic synch 148 background 142, 143 enable/disable 142, 144 listing items 145, 147 login & logout 143, 146 options 143, 148 options 10.5 156, 165, 174 skipping preset items 146 skipping specific items 145, 147 skipping specific items 10.5 153, 155, 162 skipping specific items 10.6 164 skipping specific items 10.7 171, 173 Synchronize home sync items 162, 171 synchronize time 69 system preferences disabling Internet sharing 94 energy saving 87 inconsistencies 62 locking computer configuration locking system preferences 102 login options 81 overview 60 panes displayed 181 to 185 screen saver 121 security settings 101, 178 service sharing 104
software updates 107 updating 67
T
technical support 10 time, synchronize 69 troubleshooting agent operation 200
U
UNIX man pages 213 user configuration AppleScript allowed/denied 117 application access 115 applications allowed/denied 116 CD/CD-ROM access 137 desktop settings 121 Dock settings 122 DVD access 137 external disc access 139 internal disc access 138 login & logout synchronization 143 login script 100, 175, 177 logout script 176 media access 137 miscellaneous allowed/denied 117 mobility 140 permit/prohibit access 115 policy categories 110, 112 preferences displayed 179 recordable disc access 138 refresh interval 69 requiring passwords 178 screen saver 121 security 178 server folders allowed/denied 116 user-specific allowed/denied 118 utilities allowed/denied 116
W
Windows 2008 Server single sign-on limitation 36, 204 Windows Sharing 99, 105 workgroup preferences application access 115 Dock settings 122
Index
233
media access 137 mobility preferences 140
X
Xgrid 106
234

MacOS Admin

Uploaded by

Copyright:

Available Formats

MacOS Admin

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MacOS Admin

Uploaded by

Copyright:

Available Formats

Centrify Suite

Mac OS X Administrators Guide

Installing the Centrify DirectControl Agent for Mac OS X

Creating home directories

Working with Mac OS X

Configuring 802.1X wireless authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Understanding group policies for Mac OS X users and computers

Setting computer-based policies for Mac OS X

Setting user-based policies for Mac OS X

Configuring a Mac OS X computer for smart card login

Installing and removing DirectControl and joining and leaving a domain

Installing using the install.sh command-line program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

About this guide

Using this guide

Conventions used in this guide

In addition to these chapters, an index is provided for your reference.

Conventions used in this guide

Where to go for more information

Where to go for more information

About this guide

Installing the Centrify DirectControl Agent for Mac OS X

Installing the Centrify DirectControl Agent Logging on

Preparing for installation on Mac OS X computers

Installing the Centrify DirectControl Agent

Deciding when and how to join a domain

Installing the Centrify DirectControl Agent

Installing the Centrify DirectControl Agent

In addition, be certain that the Apple Directory Utility is closed.

4 Double-click ADCheck to open the ADCheck utility.

performs a set of operating system, network, and Active Directory checks to

Chapter 1 Installing the Centrify DirectControl Agent for Mac OS X

Installing the Centrify DirectControl Agent

begin installing the Centrify DirectControl Agent.

Installing the Centrify DirectControl Agent

You can click Show log to see the installer log.

Chapter 1 Installing the Centrify DirectControl Agent for Mac OS X

Creating home directories

Understanding home directories

Understanding home directories

Configuring a local home directory

Configuring a network home directory

2 Add the following two parameters:

3 Save and close the file.

Configuring a network home directory

Directory Users and Computers.

Chapter 2 Creating home directories

Configuring a network home directory

Configuring a portable home directory

DirectControl configuration file:

Configuring a portable home directory

Creating mobile user accounts

Chapter 2 Creating home directories

Configuring a portable home directory

permissions on page 32 for details on how to do this.

includes Mac OS X users.

Configuring a portable home directory

Chapter 2 Creating home directories

Configuring a portable home directory

Configuring login and logout synchronization rules

right-click, then click Properties.