Notifications mail server, Sample scenario, Further steps – Google Apps Directory Sync Administration Guide User Manual
Page 39

Getting Started
39
Step Five: Prepare Your Servers for Synchronization
Be sure that your servers and network are prepared for GADS.
Notifications Mail Server
GADS is designed to be used for scheduled synchronization without supervision, once synchronization
rules are set up. Because of this, you will need a mail server that can relay reports from GADS.
Collect the following information:
•
The addresses that should receive notifications.
•
The address the notifications should come from.
•
The SMTP relay host IP address or domain name.
•
The username and password for connecting to the SMTP relay host (if needed).
Sample Scenario
MobiStep’s Google Apps administrator decides to use OAuth, and collects a Google Apps administrator
username and password to configure this.
The administrator also contacts MobiStep’s mail administrator to set up notifications. The existing
MobiStep mail server has a rule to block all relay attempts, so the mail administrator sets up an exception
so that the machine running Directory Sync can relay mail through that server to send out notifications.
The server doesn’t use SMTP authentication, so no username or password are required. The MobiStep
administrator decides that the notifications should come from the address
so that notifications can be filtered separately into a label.
Further Steps
Further steps are discussed in later chapters:
14. Install Directory Sync. This step is covered in “Installation” on page 45.
15. Configure Directory Sync. This step is covered in “Configuration” on page 49.
16. Simulate Synchronization. This step is covered in “Sync” on page 131.
17. Revise Configuration. This step is covered in “Configuration” on page 49.
18. Preview Synchronization. This step is covered in “Command Line Synchronization” on page 135.
19. Manual Synchronization. This step is covered in “Command Line Synchronization” on page 135.
20. Scheduled Synchronization. This step is covered in “Scheduling Synchronization” on page 137.
21. Monitoring. This step is covered in “Monitoring” on page 139.