User Guide

16 Chapter 1 Deploying iPhone and iPod touch
Preparing Access to Network Services and Enterprise Data
iPhone OS 3.0 software enables secure push email, push contacts, and push calendar
with your existing Microsoft Exchange Server 2003 or 2007 solution, as well as Global
Address Lookup, Remote Wipe, and device passcode policy enforcement. It also allows
users to securely connect to company resources via WPA Enterprise and WPA2
Enterprise wireless networks using 802.1X wireless authentication and/or via VPN using
PPTP, LT2P over IPSec, or Cisco IPSec protocols.
If your company doesn’t use Microsoft Exchange, your users can still use iPhone or
iPod touch to wirelessly sync email with most standard POP or IMAP-based servers and
services. And they can use iTunes to sync calendar events and contacts from Mac OS X
iCal and Address Book or Microsoft Outlook on a Windows PC. For wireless access to
calendars and directories, CalDAV and LDAP are supported.
As you determine which network services you want users to access, refer to the
information in the following sections.
Microsoft Exchange
iPhone communicates directly with your Microsoft Exchange Server via Microsoft
Exchange ActiveSync (EAS). Exchange ActiveSync maintains a connection between the
Exchange Server and iPhone so that when a new email message or meeting invitation
arrives iPhone is instantly updated. iPod touch doesn’t have a cellular connection, so it
receives push notifications only when it’s active and connected to a Wi-Fi network.
If your company currently supports Exchange ActiveSync on Exchange Server 2003 or
Exchange Server 2007, you already have the necessary services in place. For Exchange
Server 2007, make sure the Client Access Role is installed. For Exchange Server 2003,
make sure you’ve enabled Outlook Mobile Access (OMA).
If you have an Exchange Server but your company is new to Exchange ActiveSync,
review the information in the following sections.
Network Configuration
 Make sure port 443 is open on the firewall. If your company uses Outlook Web
Access, port 443 is most likely already open.
 Verify that a server certificate is installed on the front-end Exchange server and turn
on basic authentication only, in the Authentication Method properties, to require an
SSL connection to the Microsoft Server ActiveSync directory of your IIS.
 If you’re using a Microsoft Internet Security and Acceleration (ISA) Server, verify that a
server certificate is installed and update the public DNS to properly resolve incoming
connections.