Errata
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 | Page 6 |
10 should be 5 and GB should be TB On page 6, the second and third sentences of the Exchange Server 2007 Standard Edition section contain incorrect information. Change: "This server edition supports up to 10 storage groups (with one of the storage groups, called the Recovery Storage group, reserved for database recovery operations) and a maximum of five databases per storage group. Each database is limited to a maximum size of 16 GB." To: "This server edition supports up to 5 storage groups (with one of the storage groups, called the Recovery Storage group, reserved for database recovery operations) and a maximum of five databases per storage group. Each database is limited to a maximum size of 16 TB." |
Microsoft Press | May 06, 2010 | |
Printed | Page 35 |
Imprecise information given regarding installation best practices |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 318 |
"Client" missing from cmdlet syntax On page 318, the first sentence of the last paragraph contains 3 incorrect cmdlets. Change: "In Exchange Management Shell, you can work with permissions using the Get-PublicFolderPermission, Add-PublicFolderPermission, and Remove-PublicFolderPermission cmdlets." To: "In Exchange Management Shell, you can work with permissions using the Get-PublicFolderClientPermission, Add-PublicFolderClientPermission, and Remove-PublicFolderClientPermission." |
Microsoft Press | May 06, 2010 | |
Printed | Page 319 |
"Client" missing from permission cmdlets |
Microsoft Press | Jul 13, 2010 |