Filter
Top Products
Office 2008 Planning
44
Computer Requirements
Client Before Entourage is opened for the first time on a computer on which you intend to
use the Account Setup Assistant, specify any preferred DNS server(s) and search
domain(s) on the
TCP/IP tab under Network Preferences in Mac OS X. This is
because the combination of the two values is critical to the ability of the Account
Setup Assistant to find servers on the network. If no DNS server is specified, a server
that is assigned by DHCP will be used. The Account Setup Assistant is not always able
to locate servers automatically.
For information about how the Account Setup Assistant detects information for
automatic account configuration, see How the Account Setup Assistant works
in the
Office 2008 Planning section.
Server To auto-configure accounts, Entourage relies on the underlying DNS service that
supports your Active Directory infrastructure. The DNS server that is used by the
Macintosh clients must be able to do one of the following:
• Return a DNS resource record that identifies the Active Directory domain
controller for the domain names that the DNS server hosts.
• Resolve the domain name that the user enters for his or her Microsoft
Exchange account.
In either case, the DNS server should be able to provide name resolution for any
name in the Active Directory namespace that this server supports.
Entourage must be able to locate the global catalog server for the Active Directory
domain and then authenticate the user account information that is supplied for the
Microsoft Exchange mail account. The fundamental configuration step that makes this
possible is performed at the time that Active Directory is deployed. Deploying
Entourage requires no additional configuration of Active Directory.
Important
In anActive Directory infrastructure that is heavily secured, the Account
Setup Assistant might have difficulty locating the Active Directory
global catalog server and authenticating the user account. Examples of
heavily secured scenarios can include, using Windows IP sec policies,
internal firewalls, or proxy servers requiring authentication.
For more information about deploying Active Directory, see Windows Server 2003
Deployment Guide on the Microsoft TechNet Web site (technet.microsoft.com).