Ignite Lab 3: Exchange Server 2010

(Beta) Transport Routing

© 2009 Microsoft Corporation. All rights reserved. 0

 DISCLAIMER
© 2009 Microsoft Corporation. All rights reserved.
Microsoft®, Internet Explorer, and Windows® are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks
of their respective owners.
THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND TRAINING PURPOSES ONLY
AND ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

No part of the text or software included in this training package may be reproduced or
transmitted in any form or by any means, electronic or mechanical, including
photocopying, recording, or any information storage and retrieval system, without
permission from Microsoft®. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft,
and Microsoft cannot guarantee the accuracy of any information presented after the
date of publication. The names of actual companies and products mentioned herein
may be the trademarks of their respective owners.
To obtain authorization for uses other than those specified above, please visit the
Microsoft Copyright Permissions Web page at
http://www.microsoft.com/about/legal/permissions
This content is proprietary and confidential, and is intended only for users described in
the content provided in this document. This content and information is provided to
you under a Non-Disclosure Agreement and cannot be distributed. Copying, disclosing
all or any portion of the content and/or information included in this document is
strictly prohibited.

© 2009 Microsoft Corporation. All rights reserved. 1

Lab: Exchange Server 2010 (Beta) Transport Routing
In this lab exercise, you will simulate failures in various components of Exchange Server
2010 (Beta) transport and learn about improvements made in high availability and
manageability of transport systems.
As organizations examine their e-mail infrastructures to eliminate potential points of
failure, they look for ways to protect against data loss beyond just mailbox servers.
During periods of heavy e-mail traffic, queues of undelivered messages can build up on
transport servers. If a transport server fails with messages in its queue, data may be lost.
In the past, the only way to guard against the loss of message queues was to replicate
the queue with expensive 3rd party replication products.
Both Hub Transport and Edge Transport servers in Exchange Server 2010 (Beta) have
built-in redundancy to protect against the loss of messages in transit. A “safe copy” of
each message is retained until the message is successfully delivered to the next hop; so if
a queue fails, there is a backup copy on another transport server.
Previously this level of redundancy would have been expensive to deploy and
complicated to manage, but now it is built-in and automatic. As an added benefit, in
this new redundancy model, transport servers essentially become “stateless”, which
makes it easier to take them offline for maintenance.
Estimated time to complete this lab: 45 minutes

What You Will Learn

After completing this lab, you will be able to:
Understand new high availability features of Exchange Server 2010 (Beta)
transport.
Test and validate Shadow Messaging.
Test and validate failover/self-healing of connectors and transport services.
Test and validate the Automated Service Recovery feature.

Scenario
Northwind Traders has implemented Exchange Server 2010 (Beta). The company
classifies Exchange as a critical application, and it has business requirements for all
messaging components to be highly available. As an Exchange administrator, you have
been tasked with ensuring high availability of Exchange transport, meaning that
messages should still be delivered even in the event of a Hub Transport server failure.
The virtual environment for this lab is as follows:

© 2009 Microsoft Corporation. All rights reserved. 2

© 2009 Microsoft Corporation. All rights reserved. 3
Exercise 1: Validating message queue replication by
Shadow Messaging
In this exercise, you will simulate the loss of a Hub Transport server in a site, while
messages are queued on the Hub. The Exchange Server 2010 (Beta) Shadow Messaging
feature will detect the outage and ensure that the message is safely delivered without
any mail loss.

Tasks
1. Start virtual environment and log into server.
a. Click Start Administrative Tools, and then click Hyper-V
Manager.
b. Verify no Virtual Machines are running.

Some of the steps in this lab may not function correctly unless EX01, EX02 and EX03
Note: are started in succession, and then all Microsoft Exchange Services are verified as
started before starting the next server. For Example; start EX01, wait for it to start
completely, and then verify all services are started, and then start EX02, verify all
services are started, and then start EX03.

c. Click SetB-DC01 and then in the right pane click Start.

d. Once DC01 is running, click SetB-DC02 and then click Start.
e. Once DC02 is running, click SetB-EX01 and then click Start.
f. Verify that all Microsoft Exchange Services are started on EX01 and
then click SetB-EX02 and then click Start.
g. Verify that all Microsoft Exchange Services are started on EX02 and
then, click SetB-EX03 and then click Start.
h. Once EX03 is running, click SetB-Client01 and then click Start.

2. Stop all external mail delivery by stopping the SMTP smart host on DC01.
a. In Hyper-V Manager, click SetB-DC01 and then in the right pane
click Connect.

b. Click the Ctrl-Alt-Delete icon .

c. Log in as NWTraders\Administrator with the password of
pass@word1.
d. Click Start, point to Administrative Tools, and then click Services.
e. Right-click the Simple Mail Transport Protocol (SMTP) service
and then click Stop.

© 2009 Microsoft Corporation. All rights reserved. 4

 3. Create a new Send Connector, which will be associated to EX01 and EX02.
a. Log in to Ex01 as NWTraders\Administrator with a password of
pass@word1
b. Click Start, point to All Programs, click Microsoft Exchange Server
2010, and click Exchange Management Console.
c. Expand Microsoft Exchange On-Premise, expand Organization
Configuration, and then click Hub Transport.
d. Click the Send Connectors tab and then in the right pane click New
Send Connector.
e. In the Name box, type Internet Connector
f. In the Select the intended use for this Send connector drop-down,
select Internet, and then click Next.
g. On the Address space page, click Add.

h. In the Address field type *, click OK, and then click Next.
i. On the Network Settings page, click Route mail through the
following smart hosts:
j. Click Add, and then click Fully qualified domain name (FQDN).
k. In the FQDN field, enter DC01.NWTraders.com and click OK, and
then click Next.
l. On the Configure smart host authentication setting page, ensure
None is selected and then click Next.
m. On the Source Server page, click Add.
n. Click EX02, click OK, and then click Next.
o. On the New Connector page, confirm the settings and then click New.
p. On the Completion page, click Finish.

4. Log into the user mailbox on EX03 and send an e-mail to an external
address.
a. Log in to Client01 as NWTraders\Terry with a password of
pass@word1
b. Click Start and then click Microsoft Office Outlook.

© 2009 Microsoft Corporation. All rights reserved. 5

 If Outlook fails to start, verify the Microsoft Exchange services are started on EX03.
Note:

c. Click New, click the To button, select Steve Riley, click To ->, and
then click OK.
d. Enter a subject and some text in the email body and then click Send.
e. Close Outlook and then log off Client01.

5. Locate the mail that Terry sent in the Message Queue.

a. On EX01, in the Exchange Management console, click Toolbox in the
left pane.
b. In the middle pane, double-click Queue Viewer.
c. Click on the Messages tab.
d. If the message from [email protected] does not appear, then in the
right pane click Connect to Server, and then click Browse.
e. Select EX02, click OK, and then click Connect.
Examine the message in the EX02 queue.
f. Make note of the server (EX01 or EX02) where the message is currently
queued.

6. Locate the mail that Terry sent in the Shadow Redundancy Queue.
a. Click Connect to Server, click Browse, select EX03, click OK, and
then click Connect.
b. Click the Queues tab, and then click Create Filter.
c. In the first drop-down, select Delivery Type.
d. In the second drop-down, select Equals.
e. In the third drop-down, select Shadow Redundancy.
f. Click Apply Filter.
Notice the message count of 1 in the Shadow Redundancy queue.
g. Click on the Messages tab, and then click Create Filter.
h. In the first drop-down, select From Address.
i. In the second drop-down, select Equals.

© 2009 Microsoft Corporation. All rights reserved. 6

 j. In the third drop-down, type [email protected]
k. Click Apply Filter.
Notice the message in the EX03\Shadow queue. This message is in the
shadow because it has not yet left the organization.

7. Simulate the loss of a Hub Server, and of its local queue.

a. In Queue Viewer, click Connect to Server, click Browse, select the
server where the message does not currently reside (not the server you
noted above).
b. Click OK, and then click Connect.
c. To simulate outage, pause the Virtual Machine where the message is
currently queued (the server that you noted above).
i. To pause the virtual server, in the Hyper-V Manager select the
virtual machine and then in the right pane click Pause.
d. Switch to EX01.
e. Start Exchange Management Shell.
f. At the PS Prompt, type the following command and then press
Enter:
get-TransportConfig | FL Shadow*

By default, Exchange sends a Heartbeat to the target server every 5 minutes.

Note: After 3 failures of the Heartbeat, the message is re-delivered to another available
hub server. For this lab, the Shadow Redundancy Heartbeat settings have been
modified using the Set-TransportConfig cmdlet to speed up this process.
ShadowHeartbeatRetryCount was set from 3 to 1
ShadowHeartbeatTimeoutInterval was set from 5 minutes to 2 minutes

g. Close the Exchange Management Shell

Within two minutes, EX03 will detect that the Hub server is unavailable and will re-submit
Note: the messages from the Shadow Redundancy queue, to the other Hub Server.

h. Switch to the Queue Viewer on EX01. Verify the message has been
queued on the Hub Transport server that is available.

8. Start the SMTP service on DC01 to allow the Hub Server to submit its
message to the simulated Internet Smart Host.
a. Switch to DC01.

© 2009 Microsoft Corporation. All rights reserved. 7

 b. In Services, right-click the Simple Mail Transport Protocol
(SMTP) service and then click Start.
c. Close Services and then log off DC01.

9. Monitor the message delivery to the Internet Smarthost and the

subsequent removal of the message from the Shadow Redundancy Queue.
a. On EX01, in the Queue Viewer, monitor the queue on the Hub
Transport server that is still running in the Redmond site. After a few
minutes you will notice that the queue has been cleared and the
message has been sent to the smarthost.
b. In the Queue Viewer, click Connect to Server, click Browse, select
EX03, click OK, and then click Connect.
c. Click the Queues tab, and then click Create Filter.
d. Click the red X to the right of the third drop down to clear the current
filter if any.
e. In the first drop-down, select Delivery Type.
f. In the second drop-down, select Equals.
g. In the third drop-down, select Shadow Redundancy.
h. Click Apply Filter.
i. Notice that the Shadow Redundancy queue has been automatically
cleared and that there are no messages from [email protected].
j. Close the Queue Viewer and then close the Exchange Management
Console.
k. Switch to Hyper-V Manager and Resume the paused server.

© 2009 Microsoft Corporation. All rights reserved. 8

Exercise 2: Testing and validating Automated Service
Recovery
The purpose of this exercise is to demonstrate some of the Automated Service Recovery
features of Exchange Server 2010 (Beta). In this exercise, you will simulate a corruption
of the Exchange mail queue database, from which Exchange will automatically recover.

Tasks
1. On EX01, click Start, point to Administrative Tools, and then click Services.
2. Right-click the Microsoft Exchange Transport service and then click Stop.
3. Click Start, click Computer and navigate to
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\queue

4. Double click the mail.que file.

5. Click Select a program from a list of installed programs and then click OK.
6. Click Notepad and then click OK.
7. Type the word BREAK anywhere in the mail.que file, click File, and then click
Save.

8. Close Notepad.
9. Return to Services , right-click the Microsoft Exchange Transport service,
and then click Start.

10. In the Services warning dialog box, Click OK on the warning about the
transport service starting and stopping.

11. Attempt to start the Microsoft Exchange Transport service again.

12. Return to the queue directory.
Notice how the mail.que file has been recreated and that the old corrupted
mail.que file has been moved to the Queue.old folder.

13. Return to Services, right-click the Microsoft Exchange Transport service and
then click Stop.

14. Return to the queue folder and open the mail.que file using notepad.
Notice how the corruption has been automatically removed from the newly
created mail.que file.

15. Close Notepad.

© 2009 Microsoft Corporation. All rights reserved. 9

 16. Return to Services, right-click the Microsoft Exchange Transport service and
then click Start.

17. Close any open windows and log off all Virtual Machines.

© 2009 Microsoft Corporation. All rights reserved. 10