###BeginCaseStudy###
Topic 3, Contoso Ltd,
Overview General Overview Contoso. Ltd. is an international company that has 3,000 employees.
The company has sales, marketing, research, and human resource departments.
Physical Locations
Contoso has two main offices. The offices are located in New York and Chicago. Each moffice has a data center.
The New York office uses a network subnet of 10.1.0.0/16. The Chicago office uses a mnetwork subnet of
10.128.0.0/16.
The offices connect to each other by using a WAN link. Each office connects directly to the Internet.
Existing Environment
Active Directory The network contains an Active Directory forest named contoso.com. The forest mcontains a
single domain. All domain controllers run Windows Server 2012 R2. The forest mfunctional level is Windows
Server 2012 R2.
The forest contains six domain controllers configured as shown in the following table.
The forest is configured as a single Active Directory site.
Active Directory administrators manage the Active Directory schema. Exchange Server madministrators do not
have access to modify the schema.
Contoso has deployed Active Directory Rights Management Services (AD RMS).
Current Business Model
Contoso partners with a company names Fabrikam. Inc. on manufacturing initiatives. The partnership between
Contoso and Fabrikam requires that both companies share confidentialm information frequently.
Requirements
Business Goals
Contoso plans to install Exchange Server 2016 to provide messaging services for its users.
It must be as easy as possible for the users at Contoso to share free/busy information with mthe users at
Fabrikam.
As much as possible Contoso plans to minimize the costs associated with purchasing hardware and software.
Planned Changes
Contoso plans to implement the following changes before installing Exchange Server 2016:
Install hardware Network Load Balancing (NLB) in the New York and Chicago offices.
Implement Microsoft Office Online Servers in the New York and Chicago offices.
Provide Contoso users with company-approved tablets.
Planned Messaging Infrastructure
You plan to create an Exchange Server 2016 organization named Contoso. You plan to deploy seven servers
that will have Exchange Server 2016 installed. The servers will be configured as mshown in the following table.
All of the servers will be members of a database availability group (DAG) named DAG01.
Client Access Requirements
Contoso identifies the following client access requirements for the planned deployment:
Users must be able to configure their tablet to synchronize email by using Autodiscover.
Users must be able to access the Exchange Server organization by using the following names:
Mail.contoso.com
Autodiscover.contoso.com
Users must be able to access Outlook on the web internally and externally from their tablet.
Users must be able to access Office Online Server by using the URL of office-online.contoso.com.
Security Requirements
Contoso identifies the following security requirements for the planned deployment:
Exchange Server mailbox databases must be encrypted while at rest.
Users must be prevented from using Outlook on the web while they are offline.
Contoso users must be able to share Calendar details with approved external domains only.
Email messages sent to the users in the fabrikam.com SMTP domain must be encrypted automatically.
Whenever possible, client computers must be directed to the same Exchange server for log collection.
Users must be able to access their mailbox by using Exchange ActiveSync on the company approved tablets
only.
Email messages sent from the users in the human resources department of Contoso must be protected by
using AD RMS. regardless of the mail client.
Availability Requirements
Contoso identifies the following high-availability requirements for the planned deployment:
Servers must be able to complete a restart without administrative intervention.
The network load balancer must be able to probe the health of each workload.
If a data center fails, the databases in the other data center must be activated automatically.
Redundant copies of all email messages must exist in the transport pipeline before and after mdelivery.
Email messages must be made highly available by the Exchange Server organization before and after delivery.
If you manually mount the databases following the data center failure, the databases in the failed site must be
prevented from mounting automatically.
###EndCaseStudy###
You have an Exchange Server 2016 organization.
Users report that they receive an Autodiscover error when they attempt to configure a Microsoft Outlook
profile. You need to view the URLs that are returned to the users when they attempt to establish an
Autodiscover connection. Which command should you run from an Exchange server?
A.
Test-OutlookConnectivity
B.
Test-OutlookWebServices
C.
Test-WebServicesConnectivity
D.
Test-MAPIConnectivity
Interesting.. https://technet.microsoft.com/en-us/library/bb124509(v=exchg.141).aspx
says that Test-OutlookWebServices is available in Exchange Server 2010 and 2007..
“You have an Exchange Server 2016 organization”
0
0
But it still working in EMS
0
0
You can test Autodiscover internally from Outlook clients by running the Test E-Mail AutoConfiguration utility in Outlook. External Autodiscover testing can be performed using the Microsoft Remove Connectivity Analyzer (https://testconnectivity.microsoft.com). Here’s a good site explaining the different means of troubleshooting autodiscovery: http://www.mustbegeek.com/configure-autodiscover-in-exchange-2016/
0
0
Answer A is the right one!!!
https://technet.microsoft.com/de-de/library/dd638082(v=exchg.160).aspx
0
0
You are right.
0
0
Test-OutlookWebServices is for 2010 and 2007. The new command for 2016 on prem is
Test-WebServicesConnectivity -AutoDiscoverServer
https://technet.microsoft.com/en-us/library/aa998328(v=exchg.160).asp
The correct answer is C
2
0
Lacey, Test-WebServicesConnectivity doesn´t return the autodiscover URL (“You need to view the URLs that are returned to the users when they attempt to establish an Autodiscover connection”).
The correct answer is A: Test-OutlookConnectivity
0
0
What king of command do you enter with Test-OutlookConnectivity to have the URLs returned please?
0
0
You are wrong. “Test-WebServicesConnectivity | fl *” return autodiscover url in verbose cmdlet property.
“Test-OutlookWebServices” is not used in Exchange 2013 and later. Technet topic was removed from english verison
https://technet.microsoft.com/en-us/library/c41152b0-b304-4b13-b8ea-a24e2c2c3ea8(EXCHG.160).aspx
but it is still presented in regional sites such as
https://technet.microsoft.com/ru-ru/library/c41152b0-b304-4b13-b8ea-a24e2c2c3ea8(EXCHG.160).aspx
2
0
i verified this also, looks like in 2016 its been phased into Test-WebServicesConnectivity… cannot find a 2016 technet for Test-OutlookWebServices
0
0
That’s right, I think
0
0
https://technet.microsoft.com/en-us/library/dd638082(v=exchg.160).aspx
0
0
Test-OutlookConnectivity -ProbeIdentity “OutlookRpcCTPProbe” -MailboxID johnd@contoso.com
0
0
I’m a bit puzzled by this one, Outlook 2016 doesn’t use RPC anymore does it? In 2016 isn’t it using MAPI over HTTP? I ran your command in an exchange 2016 environment and it said “Sequence contains no elements”.
If I replace OutlookRpcCTPProbe with OutlookMapiHttpSefTestProbe then it works. I ran it with fl * but I can’t see any autodiscover url being returned.
I have ran Test-WebSerivcesConnectivity | fl * and it did return the Autodiscover url! This is the correct answer guys.
0
0
There is not much documentation available for Exchange 2016 for Test-OutlookWebServices. Moreover this cmdlet is not mentioned in the list of commands for Exchange 2013/2016, So I consider it as legacy.
Test-WebServicesConnectivity is the right answer.
0
0
More, part of that new 104Q 70-345 dumps FYI:
https://drive.google.com/open?id=0B-ob6L_QjGLpck5vRk5XUVFQb00
Best Regards!
1
0