| 1. | What protocol does the Active Directory plug-in use to retrieve directory data from an Active Directory server? |
| 2. | If an attribute is not specified, what Active Directory attribute does the Active Directory plug-in use to create the user ID? |
| 3. | If you do not configure the Active Directory plug-in other than binding to an Active Directory server, where is the user's home folder stored? |
| 4. | When binding to an Active Directory server, what information does the Active Directory plug-in require? |
| 5. | What are the server configuration options for implementing Managed Client for X (MCX) support for Active Directory users? |
| 6. | What is the possible danger of making changes to the schema of an Active Directory server? |
| 7. | What is an advantage to using an Open Directory server to supplement an Active Directory server? |
| 8. | If an Open Directory server is used to supplement an Active Directory server instead of modifying the Active Directory schema, can Workgroup Manager manage user account preferences? |
| 1. | LDAP |
| 2. | The Active Directory plug-in bases the user ID on the user account's globally unique ID (GUID). |
| 3. | A home folder for the user is created locally in /Users. |
| 4. | The Active Directory plug-in needs the Active Directory domain and a computer ID. It also requires the name and password of a domain administrator account on the server. |
| 5. | Modify the Active Directory schema or use an ancillary Open Directory server to store the MCX data for Active Directory users. |
| 6. | Erroneous schema changes on an Active Directory server are very difficult to correct. Great care should be taken when you make schema changes. |
| 7. | An Open Directory server can supplement an Active Directory server, providing Mac OS X computers with Mac OS Xspecific records, such as MCX records. |
| 8. | No. In order to allow user preferences to be managed, the Active Directory schema must be modified to allow user records to store managed user preferences. |