HOTSPOT
Your network contains an Active Directory forest named contoso.com. The forest contains two sites
named Site1 and Site2. You have an Exchange Server 2013 organization that contains two servers.
The servers are configured as shown in the following table.
An administrator creates a new Active Directory site named Site3. The administrator creates
mailboxes for the users in Site3. All of the mailboxes of the Site3 users are located on EX1. Site3
contains a domain controller named dc3.contoso.com. The Site3 users report that sometimes, when
they open Microsoft Outlook, it takes a long time to access their mailbox. You need to reduce the
amount of time it takes for the users to access their mailbox. Which command should you run? (To
answer, select the appropriate options in the dialog box in the answer area.)
Explanation:
Autodiscover Service
Microsoft Exchange 2013 includes a service named the Autodiscover service. This topic gives an
overview of the service and explains how it works, how it configures Outlook clients, and what
options there are for deploying the Autodiscover service in your messaging environment.
The Autodiscover service does the following:
Automatically configures user profile settings for clients running Microsoft Office Outlook 2007,
Outlook 2010, or Outlook 2013, as well as supported mobile phones. Phones running Windows
Mobile 6.1 or a later version are supported. If your phone isn’t a Windows Mobile phone, check your
mobile phone documentation to see if it’s supported.
Provides access to Exchange features for Outlook 2007, Outlook 2010, or Outlook 2013 clients that
are connected to your Exchange messaging environment.
Uses a user’s email address and password to provide profile settings to Outlook 2007, Outlook 2010,
or Outlook 2013 clients and supported mobile phones. If the Outlook client is joined to a domain, the
user’s domain account is used.
When you install a Client Access server in Exchange 2013, a default virtual directory named
Autodiscover is created under the default website in Internet Information Services (IIS). This virtual
directory handles Autodiscover service requests from Outlook 2007, Outlook 2010, and Outlook
2013 clients and supported mobile phones under the following circumstances:
When a user account is configured or updated
When an Outlook client periodically checks for changes to the Exchange Web Services URLs
When underlying network connection changes occur in your Exchange messaging environment
Additionally, a new Active Directory object named the service connection point (SCP) is created on
the server where you install the Client Access server.
The SCP object contains the authoritative list of Autodiscover service URLs for the forest. You can
use the SetClientAccessServer cmdlet to update the SCP object. For more information, see SetClientAccessServer.
SECTION1
Set-ClientAccessServer EX1
Use the Set-ClientAccessServer cmdlet to set properties on specified Client Access server objects.
Use the Set-ClientAccessServer cmdlet to change AutoDiscover settings.
NOT Set-ExchangeServer
Use the Set-ExchangeServer cmdlet to set Exchange attributes in Active Directory for a specified
server.
NOT Set-RPCClientAccess
Use the Set-RpcClientAccess cmdlet to manage the settings for the Exchange RPC Client Access
service that’s running on a Microsoft Exchange Server 2010 Client Access server.SECTION2
-AutoDiscoverSiteScope ‘Site1;Site3’
The AutoDiscoverSiteScope parameter specifies the site for which the Autodiscover service is
authoritative.
Clients that connect to the Autodiscover service by using the internal URL must belong to a listed
site.
NOT -AutoDiscoverServiceInternalURI
The AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover
service.
Need to specify Site3
NOT -IgnoreDefaultScope
NOT a parameter of Set-ClientAccessServer
The IgnoreDefaultScope parameter instructs the command to ignore the default recipient scope
setting for the
Exchange Management Shell session and use the entire forest as the scope.
This allows the command to access Active Directory objects that aren’t currently in the default
scope. Using the
IgnoreDefaultScope parameter introduces the following restrictions:
You can’t use the DomainController parameter. The command uses an appropriate global catalog
server automatically.
You can only use the DN for the Identity parameter. Other forms of identification, such as alias or
GUID, aren’t accepted.
You can’t use the OrganizationalUnit and Identity parameters together.
You can’t use the Credential parameter.
NOT -DomainController
The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain
controller that writes this configuration change to Active Directory.
Will not resolve the issue.
At first it seems like it should have site 2 but site 2 is on Ex2 and only site 1 and site 3 are on ex1