Errata

On my Kindle version the following sentence should be the "commonly used alias of ft."

instead of fl which is the alias for format list

The cmdlet used to format the output as a table is the Format-Table cmdlet, which has a commonly used alias of fl.

Note from the Author or Editor:
Current sentence: "The cmdlet used to format the output as a table is the Format-Table cmdlet, which has a commonly used alias of fl."

Please change to: "The cmdlet used to format the output as a table is the Format-Table cmdlet, which has a commonly used alias of ft."

OAB doesn't reside on the mailbox server role. It should be under CAS on page 125.

Note from the Author or Editor:
Remove the last row in Table 3-9 Network Ports for Mailbox Role:
Outlook accessing OAB 80/TCP, 443/TCP (SSL) Yes (SSL)

You are entirely missing remote powershell, running on 80/TCP, 443/TCP (SSL) for all roles.

Note from the Author or Editor:
It's correct and should be added. Please add the following line to table 3-11 on page 126 at the end:

Data Path:
Remote Powershell to Client Access Server

Required Ports:
80/TCP, 443/TCP (SSL)

Encrypted by default:
Yes

We need to add one more function, please update the following data path row in Table 3-11:
Autodiscover service, Availability
service, Outlook Web App (OWA),
Outlook
Anywhere, Exchange
ActiveSync,
Client Access server
to Client Access server for
Exchange ActiveSync and OWA

to this:
Autodiscover service, Availability
service, Outlook Web App (OWA),
Outlook
Anywhere, Exchange
ActiveSync,
Client Access server
to Client Access server for
Exchange ActiveSync and OWA, Outlook accessing Offline Address
Book (OAB)

Figure 5-1 should have a set of solid black lines and a set of dotted black lines. The printed copy only has solid black lines so you cannot distinguish between the two logical paths the diagram is trying to show you. The caption of the figure properly describes the solid and dotted lines.

Note from the Author or Editor:
This is true, Figure 5-1 needs to be changed in the following way: the arrow from "Submit from: Outbox" to "Mail Submission Service", from "Mail Submission Service" to "Store Driver" and from "Store Driver" to "Submission Queue" should be dotted.

The note says "MRM requires an Exchange Server 2010 Enterprise Client Access License (CAL) for every mailbox configured for MRM."

I believe this is only for managed 'custom' folders and managed default folders only require the Standard CAL.

See the first "Note" on this MS page.

http://technet.microsoft.com/en-us/library/ee364744.aspx

Note from the Author or Editor:
Please replace "MRM requires an Exchange Server 2010 Enterprise Client Access License (CAL) for every mailbox configured for MRM." with the following sentence:
"MRM requires an Exchange Server 2010 Enterprise Client Access License (E-CAL) for every mailbox configured for personal retention tags (in the case of retention policies) or managed custom folders (in the case of managed folders)."

The following sentence: ...run the Eseutil /r e00 /i /d command to bring it to a clean state.

Should be updated to the following:
...run the Eseutil /r e00 /i /d command. If the database is still in Dirty Shutdown state, use ESEUTIL /P <database.edb> to clean the state.

Note from the Author or Editor:
The following sentence:
...run the Eseutil /r e00 /i /d command to bring it to a clean state.

Should be updated to the following:
...run the Eseutil /r e00 /i /d command. If the database is still in Dirty Shutdown state, use ESEUTIL /P <database.edb> to clean the state.

Change the following part:
4. Run the Eseutil.exe /r E00 /a command but replace E00...

To:
4. Run the Eseutil.exe /r E00 /a /i command but replace E00...

Note from the Author or Editor:
Change the following step:
4. Run the Eseutil.exe /r E00 /a command but replace E00...

To:
4. Run the Eseutil.exe /r E00 /a /i command but replace E00...

Replace the following step:
5. When Eseutil is finished, the database is in clean shutdown state. You can now decide how to continue:

With the following:
5. When Eseutil is finished, verify the state of the database using the Eseutil.exe /mh <database.edb> command. If it is not in Clean Shutdown state, run Eseuitl.exe /p <database.edb>. Then you can decide how to continue:

The bullet point states that when deploying Exchange 2010 servers "The Active Directory forest mode must not be Windows Server 2008".

This seems to contradict the Exchange Server Supportability Matrix on Technet seen here http://technet.microsoft.com/en-us/library/ff728623%28EXCHG.141%29.aspx which indicates that Exchange 2010 RTM is supported when using both:

Windows Server 2008 forest functional level

or

Windows Server 2008 R2 forest functional level

Note from the Author or Editor:
This is a change that occurred after Exchange 2010 was released. The product group had not yet completed testing for Exchange 2003 in this configuration. Please remove this line: "The Active Directory forest mode must not be Windows Server 2008."

The table states that "If Exchange Server 2003 is still in place, the domain functional level supported cannot be higher than Windows Server 2003 until after Exchange Server 2003 has been removed from the environment"

This seems to contradict the Exchange Server Supportability Matrix on Technet seen here http://technet.microsoft.com/en-us/library/ff728623%28EXCHG.141%29.aspx which indicates that Exchange 2003 SP2 is supported when using both:

Windows Server 2008 domain functional level

or

Windows Server 2008 R2 domain functional level

Note from the Author or Editor:
This is a change that has occurred after RTM of Exchange 2010. To be accurate, please remove: "If Exchange Server 2003 is still in place, the domain functional level supported cannot be higher than Windows Server 2003 until after Exchange Server 2003 has been removed from the
environment."