Microsoft® Exchange Server 2007 Administrator's Pocket Consultant

Errata for Microsoft® Exchange Server 2007 Administrator's Pocket Consultant




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 On page 35, the Tip may give an incorrect impression on the suitability of installing Exchange Server 2007 on a domain controller.Change:"Tip: To reduce network traffic between Exchange servers, domain controllers, and global catalog servers, you'll typically want to deploy the Mailbox, Client Access, Hub Transport and Unified Messaging roles on a computer acting as a domain controller with a global catalog. This is not a requirement, but it is a recommended best practice for most Exchange server implementations." To:"Tip: To reduce network traffic between Exchange servers, domain controllers, and global catalog servers, you may want to deploy the Mailbox, Client Access, Hub Transport and Unified Messaging roles on a computer acting as a domain controller with a global catalog. This is not a recommended best practice, but it is a supported configuration."

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 On page 319, in samples 14-9, 14-10 and 14-11 the permission cmdlets are all missing the word "Client" in their syntax. Every instance of the following cmdlets should be changed: "Get-PublicFolderPermission" "Add-PublicFolderPermission" "Remove-PublicFolderPermission" To: "Get-PublicFolderClientPermission" "Add-PublicFolderClientPermission" "Remove-PublicFolderClientPermission" Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.

Microsoft Press  Jul 13, 2010