Microsoft® Exchange Server 2010 Best Practices

Errata for Microsoft® Exchange Server 2010 Best Practices




The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed, PDF, Safari Books Online
Page xxvii
1st paragraph

Domain on the Middle Tier should be Directory on the Middle Tier

Joel Stidley  Jul 06, 2010  Nov 01, 2010
Printed, PDF
Page xxvi
Under Chapter 15 heading

Erick should be Erik

Joel Stidley  Jul 06, 2010  Nov 01, 2010
Printed, PDF
Page xxxi
Acknowledgements, 2nd paragraph

Name of Stanley is not correct: Change Stanley Riemer to Stanley Reimer.

Note from the Author or Editor:
On 2nd paragraph, change Stanley Riemer to Stanley Reimer.

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Oct 17, 2010  Nov 01, 2010
Printed, PDF
Page 24
9th bullet point in Table 1-4

The bullet "RBAC management has been improved." is duplicate with "Manage RBAC Roles Groups and User Roles (covdered in more detail in Chapter 16)." Remove "RBAC management has been improved."

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Aug 14, 2010  Nov 01, 2010
Printed, PDF
Page 24
Table 1-4

"Manage RBAC Roles Groups and User Roles (covered in more detail in Chapter 16)." should say: "Manage RBAC Role Groups and User Roles (covered in more detail in Chapter 16)."

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Aug 14, 2010  Nov 01, 2010
Printed, PDF, Safari Books Online, Other Digital Version
Page 37
above figure 1-14

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."

Warren Bierley  Jun 05, 2011 
Printed, PDF, Safari Books Online
Page 85
4th parapraph

"Putting these roles between a firewall could cause..." Should be "Putting a firewall between these roles could cause..."

John Carpenter  Aug 25, 2010  Nov 01, 2010
PDF, Other Digital Version
Page 111
2nd Paragraph, About Digital Certificates

The version I am reading, which I believe is up to date, reads as follows, "The public key is used to encrypt data for you and is required by everybody that wants to security communicate with you." I believe it should read as, "The public key is used to encrypt data for you and is required by everybody that wants to securely communicate with you." Great book! Thanks, Chris

Note from the Author or Editor:
The original sentence: "The public key is used to encrypt data for you and is required by everybody that wants to security communicate with you." should read as: "The public key is used to encrypt data for you and is required by everybody that wants to securely communicate with you."

Christopher Meehan  May 16, 2011 
Printed, PDF
Page 123
bottom

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)

Kevin Bird  Oct 11, 2010  Apr 08, 2011
Printed
Page 123-127
all pages in range

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

Kevin Bird  Oct 11, 2010  Apr 08, 2011
Printed, PDF
Page 125
Table 3-11, row 3

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)

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Nov 04, 2010  Apr 08, 2011
Printed, PDF, Safari Books Online
Page 126
Bottom of page (table 3-12) and top of page (table 3-11)

Please move the following line from table 3-12 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

Anonymous  Apr 21, 2011 
Printed, PDF, Safari Books Online, Other Digital Version
Page 151
1st paragraph under "Internet Calendar Sharing"

The second to last sentence in this paragraph should say "Public URLs, on the other hand are, can be searchable on the Internet." Currently instead of saying 'URLs' it says 'certificates'.

Note from the Author or Editor:
This sentence should read: "Public URLs, on the other hand, can be logically deduced and then viewed by others over the Internet."

Brian Day  Jul 21, 2010  Nov 01, 2010
Printed
Page 204
Figure 5-1

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.

Brian Day  Jul 21, 2010 
Printed, PDF, Safari Books Online, Other Digital Version
Page 206
1st paragraph, line 3

"and content conversation" should read... "and content conversion"

Brian Day  Jul 21, 2010  Nov 01, 2010
Printed, PDF, Safari Books Online, Other Digital Version
Page 261
last paragraph

Each database is represented by a single instance of the ESE instance and shares a single set of transaction log files. It should read: Each database is represented by an instance of ESE and a separate set of transaction log files.

Note from the Author or Editor:
This reflowed text to the next page, but not page 263.

Joel Stidley  Jul 06, 2010  Nov 01, 2010
Printed, PDF, Safari Books Online, Other Digital Version
Page 292
Last paragraph, item #1.

The sentence that currently starts with... "If there is a replica available in that public folder," Should probably say... "If there is a replica available in that public folder database,"

Note from the Author or Editor:
This should read: If there is a replica available for that public folder, Exchange Server directs the client to this database for the public folder contents.

Brian Day  Jul 21, 2010  Apr 08, 2011
Printed, PDF
Page 349
The "Note" above Retention Tags and Retention Policies

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)."

Brian Day  Jul 22, 2010  Apr 08, 2011
Printed, PDF
Page 361
The end of the MRM section.

You may want to mention users with MRM policies on their mailbox cannot have an Archives mailbox created, nor can users already having an Archive mailbox have MRM policies applied to them.

Note from the Author or Editor:
Please add the following as "Note" to page 349: "Users with MRM policies on their mailbox cannot have an Archives mailbox created, nor can users already having an Archive mailbox have MRM policies applied to them."

Brian Day  Jul 22, 2010  Apr 08, 2011
Printed, PDF, Safari Books Online, Other Digital Version
Page 374
Paragraph 1, Line 6

"...and by default a newly created discovery mail has no...." should say "...and by default a newly created discovery mailbox has no..."

Brian Day  Jul 22, 2010  Apr 08, 2011
Printed, PDF
Page 382
Last line, continues onto 383.

"Office 2003 Standard and Office 2007 Professional can access RMS-protected content only; they cannot access RMS-protect content." Should that last half say.. "; they cannot protect content with RMS."

Note from the Author or Editor:
Correct the sentence "Office 2003 Standard and Office 2007 Professional can access RMS-protected content only; they cannot access RMS-protect content." to the following sentence: "Office 2003 Standard and Office 2007 Professional can access RMS-protected content only; they cannot RMS-protect content."

Brian Day  Jul 22, 2010  Apr 08, 2011
Printed, PDF, Safari Books Online
Page 493
1st Paragraph

Suspend-MailboxDatabasaeCopy should be Suspend-MailboxDatabaseCopy

Note from the Author or Editor:
The first list item should be Suspend-MailboxDatabaseCopy

Jonathan Black  Sep 21, 2010  Apr 08, 2011
Printed, PDF
Page 557
First sentence

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.

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Nov 03, 2010  Apr 08, 2011
Printed
Page 563
Immediately following the two bullet points

To create and mount a recovery storage group... should be To create and mount a recovery database...

Note from the Author or Editor:
Replace "To create and mount a recovery storage group..." with "To create and mount a recovery database..."

John Carpenter  Sep 26, 2010  Apr 08, 2011
Printed
Page 563
Above figure 12-16

"DisplayName" within command should be followed by a comma rather than a period.

Note from the Author or Editor:
Replace "Get-MailboxStatistics –Database <recovery database> |ft DisplayName. MailboxGuid, ItemCount" with "Get-MailboxStatistics –Database <recovery database> |ft DisplayName, MailboxGuid, ItemCount"

John Carpenter  Sep 26, 2010  Apr 08, 2011
Printed, PDF
Page 572
Step No. 4

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...

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Nov 03, 2010  Apr 08, 2011
Printed, PDF
Page 572
Step 5

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:

Siegfried Jagott
Siegfried Jagott
O'Reilly Author 
Nov 03, 2010  Apr 08, 2011
Printed, PDF
Page 632
Table 14.7

The heading is Exchange Server 2003 Feature however it should read Exchange Server 2007 Feature as this table is about Exchange 2007.

Joel Stidley
O'Reilly Author 
Jul 06, 2010  Apr 08, 2011
Printed, PDF, Safari Books Online, Other Digital Version
Page 641
3rd bullet point in the "Deploying Exchange Server 2010 Computers" section

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."

Gary Smith  Aug 19, 2010  Apr 08, 2011
Printed, PDF, Safari Books Online, Other Digital Version
Page 685
Table 15-1

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."

Gary Smith  Aug 19, 2010  Apr 08, 2011