beautypg.com

Groups and mailing lists – Google Apps Directory Sync Administration Guide User Manual

Page 30

background image

30

Release 4.0.2

queries, see “About LDAP Queries” on page 41.

WARNING:

Check to be sure that you are importing the correct number of users. If you import more

users than you have licenses in Google Apps, you may experience errors during synchronization for
exceeding your user limit.

User Profiles: If your LDAP directory server includes further information, such as addresses, phone
numbers, or contact information, you can synchronize this information into Google Apps.

You can use GADS to import the full names of your users into Google Apps. If you want to do this, find
the LDAP attributes that contain this information. User names are often stored in two attributes: one for
the first name and one for the last name. If you do not have an LDAP attribute with the appropriate
information, you can skip this step.You can synchronize this through LDAP extended attributes. For
more information, see “User Profiles” on page 101.

If you have full user profiles in your LDAP directory server and you want to synchronize this
information into Google Apps, you can import User Profiles. For more information, see “User Profiles”
on page 101.

Aliases: You can synchronize one or more attributes for aliases from your LDAP directory into Google
Apps nicknames. Use an LDAP browser to confirm the LDAP attribute (or attributes) you want to use.
Be sure that the attribute contains only an email address, and not other data such as a phone number.

Unique ID: If your users are likely to change user names, set up a Unique ID attribute beforehand so
that user information is not lost when a user changes their name. This should be a field on your LDAP
that is unique for each user, and will not change when your users change names. On Active Directory
servers, the

objectGUID

attribute is recommended.

Passwords: GADS supports a limited set of password operations. If you want GADS to handle
passwords, this requires additional preparation and planning. For more information, see “Passwords”
on page 32
.

If you have an Active Directory server, you can keep your LDAP passwords synced to Google Apps
with Google Apps Password Sync. For more information on Google Apps Password Sync, see the
Google Apps admin help center:

http://support.google.com/a/bin/answer.py?answer=2611859

Deleted and Suspended Users: By default, users not found on your LDAP directory will be deleted
from Google Apps, and suspended users will be ignored. If this is what you want GADS to do, leave
deleted and suspended users settings at the default.

You can set GADS to suspend users instead of deleting them. This allows for data recovery if users
are later recovered, and the ability to view and transfer a user’s assets.

If your Google Apps account has suspended users that you want to remove, you can instead set
GADS to delete suspended users. You cannot use this setting if you use the option, described in the
paragraph above, to suspend users instead of deleting them.

For more information on these options, see “Additional User Attributes” on page 79.

Groups and Mailing Lists

There are several ways to organize your users in Google Apps. Different lists and groups can be
synchronized into Google Apps in different ways.

Decide how you want to organize your users, and consider the following topics.