Errata

Readiness Review assessment incorrect answer marked as correct
On the Readiness Review assessment, one of the questions marks 2 answers as incorrect where there should only be one correct answer.



The question reads:

"Your Exchange Server 2007 organization has a single site and a single server. The server's name is Canberra. This server hosts the Hub Transport, Mailbox, and Client Access server roles. You want to enable Exchange's anti-spam features on this server but cannot locate the Enable Anti-spam item in the Actions pane when the Hub Transport server is selected. Which of the following must you do prior to enabling the anti-spam features of Exchange Server 2007?"



The only correct answer should be:

"4. Run the command Set-TransportServer -Identity 'Canberra' -AntispamAgentsEnabled $true from the

Exchange Management Shell"

Readiness Review assessment answer incorrect On the Readiness Review assessment, one of the questions has all incorrect answers and the wrong answer marked as correct. The quesiton reads: "Your organization uses a unique set of backup tapes for the backup. You back up a mailbox server according to the following schedule: Monday at 2:00 AM, full backup; Tuesday to Sunday at 2:00 AM differential backup. The storage array on the mailbox server suffers a catastrophic failure on Friday morning at 2:00 AM. You replace the array. Which of the following sets of backup tapes will you need to use to restore data?" The answers read: "1. The Sunday and Thursday tape sets. 2. The Sunday, Monday, Tuesday, Wednesday, and Thursday tape sets. 3. The Sunday, Monday, Tuesday, Wednesday, Thursday, and Friday tape sets. 4. The Sunday and Friday tape sets." The answers should read: "1. The Monday and Thursday tape sets. 2. The Sunday, Monday, Tuesday, Wednesday, and Thursday tape sets. 3. The Sunday, Monday, Tuesday, Wednesday, Thursday, and Friday tape sets. 4. The Sunday and Friday tape sets." The correct answer is: 1. The Monday and Thursday tape sets.

2003 should be 2007 On page 3, the last sentence of the first paragraph references Exchange Server 2003 rather than 2007. Change: "This lesson will also touch on Exchange Administrator roles and what steps need to be taken to prepare environments that have a previous Exchange deployment for the introduction of Exchange Server 2003." To: "This lesson will also touch on Exchange Administrator roles and what steps need to be taken to prepare environments that have a previous Exchange deployment for the introduction of Exchange Server 2007."

"2003" should be "2007"
On page 22, the first sentence of the last paragraph on the page contains an incorrect version of Exchange Server.



Change:

"The first step in determining whether a computer is capable of running Exchange Server 2003 is to determine whether it meets the minimum hardware requirements."



To:

"The first step in determining whether a computer is capable of running Exchange Server 2007 is to determine whether it meets the minimum hardware requirements."

Windows Server 2003 R2 should be Windows Server 2003 On page 23, the last sentence of the fifth bullet point refers to Windows Server 2003 R2 rather than Windows Server 2003. Change: "This MMC is installed when you apply SP2 to Windows Server 2003 R2." To: "This MMC is installed when you apply SP2 to Windows Server 2003."

five should be three
On page 30, the second sentence of the third bullet point refers to five disks rather than three.



Change:

"RAID 5 requires a minimum of five disks."



To:

"RAID 5 requires a minimum of three disks."

Shell command is missing hyphen On page 132, the shell command near the bottom of the page is missing a hyphen before ResetPasswordOnNextLogon. Change: New-MailUser -Name "James R. Hamilton" -ExternalEmailAddress SMTP:james.hamilton@contoso.com -UserPrincipalName jrhamilton@tailspintoys.internal -OrganizationalUnit Users ResetPasswordOnNextLogon $true To: New-MailUser -Name "James R. Hamilton" -ExternalEmailAddress SMTP:james.hamilton@contoso.com -UserPrincipalName jrhamilton@tailspintoys.internal -OrganizationalUnit Users -ResetPasswordOnNextLogon $true

-ExternalEmail-Address should be -ExternalEmailAddress
On page 137, the first shell command on the page contains an unneccisary hyphen in -ExternalEmailAddress.



Change:

"You can use the Exchange Management Shell cmdlet New-MailContact to create a mail contact, for example, New-MailContact -Name "Michael Allen" -ExternalEmail-Address m.allen@fabricam.com -OrganizationalUnit Users."



To:

""You can use the Exchange Management Shell cmdlet New-MailContact to create a mail contact, for example, New-MailContact -Name "Michael Allen" -ExternalEmailAddress m.allen@fabricam.com -OrganizationalUnit Users."

"Display Name" needs to be removed
On page 155, the 2nd sentence in the second paragraph contains an incorrect field.



Change:

"On the Group Information page, you can optionally specify the Display Name and the Alias fields."



To:

"On the Group Information page, you can optionally change the Alias fields."

"security" should be "distribution" On page 155, the third sentence in the exam tip box at the top of the page contains an incorrect group. Change: "Be wary of answers to examination questions that suggest disabling or enabling a dynamic security group." To: "Be wary of answers to examination questions that suggest disabling or enabling a dynamic distribution group."

the word "dynamic" should be removed On page 157, the 1st sentence of the second paragraph contains an incorrect distribution group. Change: "Adding members to a dynamic distribution group is one of the tasks that you would normally do with a CLI rather than a GUI because it is repetitive and can be scripted." To: "Adding members to a distribution group is one of the tasks that you would normally do with a CLI rather than a GUI because it is repetitive and can be scripted."

"cannot" should be "can"
On page 160, the 1st and 2nd sentences of the third paragraph contain innaccurate information regarding adding/removing members from a universal security group.



Change:

"You cannot use the Exchange Management Shell or the Exchange Management Console to add members to or remove members from a universal security group. An administrator with the appropriate rights in the domain and the forest would typically use Active Directory Users and Computers to perform this task."



To:

"You can use the Exchange Management Shell or the Exchange Management Console to add members to or remove members from a universal security group. However, an administrator with the appropriate rights in the domain and the forest would typically use Active Directory Users and Computers to perform this task."

Incorrect information in parenthesis On page 168, the 3rd sentence in the third paragraph down contains incorrect information in parenthsis at the end of the sentence. Change: "On the Mailbox Information page, complete the Organizational Unit, First Name, Initials, Last Name, User Name, User Logon Name, User Logon Name (User Principal Name), User Logon Name (pre-Windows 2000), Password, and Confirm Password fields as appropriate (or leave them blank or accept the default)." To: "On the Mailbox Information page, complete the Organizational Unit, First Name, Initials, Last Name, User Name, User Logon Name, User Logon Name (User Principal Name), User Logon Name (pre-Windows 2000), Password, and Confirm Password fields as appropriate."

"Display Name" should be "DisplayName"
On page 169, the 2nd sentence of the first paragraph contains an incorrect parameter in the command to create an equipment mailbox called Projector.



Change:

"the command New-mailbox -UserPrincipalName Projector@tailspintoys.internal -database "First Storage GroupMailbox Database" -Name Projector OrganizationalUnit

Users -Display Name Projector -ResetPasswordOnNextLogon $false –Equipment creates an equipment mailbox called Projector."



To:

"the command New-mailbox -UserPrincipalName Projector@tailspintoys.internal -database "First Storage GroupMailbox Database" -Name Projector OrganizationalUnit

Users -DisplayName Projector -ResetPasswordOnNextLogon $false –Equipment creates an equipment mailbox called Projector."

"manually" should be "explicitly" On page 177, the 1st sentence of the third bullet point in Chapter Summary contains an incorrect action. Change: "Universal distribution groups have a fixed membership, and members need to be added and removed manually." To: "Universal distribution groups have a fixed membership, and members need to be added and removed explicitly."

"Active Directory" should be removed
On page 179, the first sentence of answer 1 to Case Scenario 2 contains an incorrect folder name.



Change:

"Only members of a universal security group called Researchers have access to files in an Active Directory folder called Research Reports."



To:

"Only members of a universal security group called Researchers have access to files in a folder called Research Reports."

"Get-MailPublicFolderStatistics" should be "Get-PublicFolderStatistics" On page 222, the last bullet point on the page contains an invalid command. Change: "Practice 1: Use the Get-MailPublicFolder Commands Investigate the commands based on the Get-MailPublicFolder and Get-MailPublicFolderStatistics cmdlets." To: "Practice 1: Use the Get-MailPublicFolder Commands Investigate the commands based on the Get-MailPublicFolder and Get-PublicFolderStatistics cmdlets."

the word "Organization" should be disregarded
On page 230, the second sentence in the first paragraph incorrectly uses the word "organization" after Server 2003/2000.



Change:

"You can use the same tools to move Exchange Server 2007 mailboxes to an Exchange Server 2003 organization and to an Exchange 2000 Server organization within the same forest."



To:

"You can use the same tools to move Exchange Server 2007 mailboxes to an Exchange 2003 server and to an Exchange 2000 server within the same forest."

"MailboxSizeLimitOptions" should be "PreserveMailboxSizeLimit"
On page 237, the 2nd sentence of the last paragraph on the page contains an incorrect parameter.



Change:

"If you want to use the mailbox size limit of the source mailbox instead of the size limit of the target database, you can specify the PreserveSource option for the MailboxSizeLimitOptions parameter."



To:

"If you want to use the mailbox size limit of the source mailbox instead of the size limit of the target database, you can specify the PreserveMailboxSizeLimit parameter."

parameters in Move-Mailbox command are out of order On page 237, the Move-Mailbox command under the first paragraph contains parameters that are out of order. Change: Move-Mailbox "Don Hall" -ConfigurationOnly -TargetDatabase –Server Edinburgh "First Storage GroupMailbox Database"To: Move-Mailbox "Don Hall" -ConfigurationOnly -TargetDatabase "First Storage GroupMailbox Database" –Server Edinburgh

context missing for Move-Mailbox command On page 238, the second sentence on the page is missing context information regarding use of the Move-Mailbox command. Change: "By default, the Move-Mailbox command does not delete the source mailbox." To: "When moving mailboxes between forests, the Move-Mailbox command does not delete the source mailbox by default."

incorrect description of the GlobalCatalog and SourceForestGlobalCatalog parameters
On page 241, the 2nd sentence of the third paragraph contains incorrect information regarding the GlobalCatalog and SourceForestGlobalCatalog parameters.



Change:

"The GlobalCatalog and SourceForestGlobalCatalog parameters locate the mailbox in the target and source forests."



To:

"The GlobalCatalog and SourceForestGlobalCatalog parameters specifiy the global catalogs in which to perform search operations in the target and source forests."

multiple inaccuracies in the "Deleting source mailboxes" note box On page 244, the NOTE box for "Deleting source mailboxes" at the bottom of the page contains multple inaccuracies. Change: "NOTE Deleting source mailboxes By default, moving a mailbox does not delete the source mailbox. This gives a fallback situation should a mailbox move, particularly a bulk mailbox move, fail. The original mailboxes are still there, and you can try the move again. In general, it is a good idea to check that mailboxes have been moved successfully before deleting the source mailboxes. However, once you have checked that the move has occurred without errors, you should delete the source mailboxes. The SourceMailboxCleanupOptions parameter lets you delete a source mailbox as part of a mailbox move, but you should use this with care." To: "NOTE Deleting source mailboxes By default, moving a mailbox across forests does not delete the source mailbox. This gives a fallback situation should a mailbox move, particularly a bulk mailbox move, fail. The original mailboxes are still in the source forest, and you can try the move again. In general, it is a good idea to check that mailboxes have been moved successfully before deleting the source mailboxes. However, once you have checked that the cross-forest move has occurred without errors, you should delete the source mailboxes. The SourceMailboxCleanupOptions parameter lets you delete a source mailbox as part of a mailbox move, but you should use this with care. It is not necessary to specifiy the SourceMailboxCleanupOptions parameter when moving mailboxes within a single forest."

"MailboxSizeLimitOptions" should be "PreserveMailboxSizeLimit"
On page 246, the 2nd sentence of the first paragraph contains an incorrect parameter.



Change:

"For example, earlier in this lesson we discussed setting the MailboxSizeLimitOptions parameter to PreserveSource in a Move-Mailbox command so that the move does not fail if you are moving a mailbox that is larger than the size limit specified in the target database."



To:

"For example, earlier in this lesson we discussed specifying the PreserveMailboxSizeLimit parameter in a Move-Mailbox command so that the move does not fail if you are moving a mailbox that is larger than the size limit specified in the target database."

Two Policy Parameters contain incorrect hyphens On page 248, in Table 5-3 three of the Policy Parameters contain an incorrect hyphen. Change: "EmailAddressPolicy-EnabledHiddenFromAddressLists-EnabledDeliverToMailboxAnd-Forward"To: "EmailAddressPolicyEnabledHiddenFromAddressListsEnabledDeliverToMailboxAndForward"

Information regarding additional storage groups is incorrect
On page 256, the second sentence in the NOTE box at the bottom of the page contains incorrect information regarding additional storage groups.



Change:

"However, any additional storage group that you create will, by default, contain a mailbox database called Mailbox Database."



To:

"However, you might have created additional storage groups and placed a mailbox database called Mailbox Database in each."

information in Answers C and D of Question 1 is partially incorrect On page 258, Answers C and D incorrectly state that the "Finish" control is greyed out. Change: "C. The Finish control is grayed out, and you cannot close the Move Mailbox Wizard. At 11:30 PM, a single command is sent to Exchange Management Shell to implement all the mailbox moves. After the mailboxes have been moved, you can click Finish to close the wizard. D. The Finish control is grayed out, and you cannot close the Move Mailbox Wizard. At 11:30 PM, multiple commands are sent to Exchange Management Shell, each of which implements a mailbox move. After the mailboxes have been moved, you can click Finish to close the wizard." To: "C. You cannot close the Move Mailbox Wizard because the wizard remains on the the Move Mailbox page until the scheduled time is reached. At 11:30 PM, a single command is sent to Exchange Management Shell to implement all the mailbox moves. After the mailboxes have been moved, you can click Finish to close the wizard. D. You cannot close the Move Mailbox Wizard because the wizard remains on the the Move Mailbox page until the scheduled time is reached. At 11:30 PM, multiple commands are sent to Exchange Management Shell, each of which implements a mailbox move. After the mailboxes have been moved, you can click Finish to close the wizard."

Instructions for deleting mailboxes are not needed
On page 262, the first paragraph on the page contains instructions that are not needed within the context of the paragraph.



Change:

"If you want to move these users from the default mailbox database (First Storage GroupMailbox Database) to the database First Glasgow Mailbox Database in the same storage group, delete the mailboxes in the source database, and retain the mailbox recipient policies when you move the mailboxes, you could pipe the output of the previous command into an appropriate command based on the Move-Mailbox cmdlet as follows:"



Import-CSV "C:IdentifyUsers.csv" | ForEach-Object –Process {Get-Mailbox –Identity $_.Identity} | Move-Mailbox -TargetDatabase "First Storage GroupFirst Glasgow Mailbox Database" -SourceMailboxCleanupOptions DeleteSourceMailbox -IgnorePolicyMatchTo:

"If you want to move these users from the default mailbox database (First Storage GroupMailbox Database) to the database First Glasgow Mailbox Database in the same storage group, you could pipe the output of the previous command into an appropriate command based on the Move-Mailbox cmdlet as follows:"



Import-CSV "C:IdentifyUsers.csv" | ForEach-Object –Process {Get-Mailbox –Identity $_.Identity} | Move-Mailbox -TargetDatabase "First Storage GroupFirst Glasgow Mailbox Database"

Information regarding the PSHome variable are not needed
On pages 268 & 269, the last sentence on page 268 contains a reference to the variable PSHome that is not needed.



Change:

"Exchange Server 2007 provides a set of preconfigured PowerShell scripts that are stored in the PSHome subdirectory (typically, depending on how the server is set up, C:Program FilesMicrosoftExchange ServerScripts or C:Program Files MicrosoftExchange Serverexcripts)."



To:

"Exchange Server 2007 provides a set of preconfigured PowerShell scripts that are stored in the C:Program FilesMicrosoftExchange ServerScripts subdirectory."

the word "DOS" is not needed On page 268, the second sentence of the third paragraph on the page incorrectly uses the word DOS in reference to batch commands. Change: "Such files contain the DOS commands that otherwise you would type into the console to carry out the required operation." To: "Such files contain the commands that otherwise you would type into the console to carry out the required operation."

Information regarding the PSHome subdirectory is incorrect
On page 269, the descriptive information in the PSHome subdirectory NOTE box is incorrect.



Change:

"Note The PSHome subdirectory



“PSHome” is a generic name for this directory and does not actually appear in the directory path. The PowerShell variable PSHome can contain different values, depending on setup, and can equal, for example, “Scripts” or “exscripts.”"



To:

"Note The PSHome subdirectory



By default, the PowerShell variable $PSHome points to the Windows PowerShell directory (C:WINDOWSsystem32WindowsPowerShellv1.0). While it is possible to point the PowerShell variable $PSHome to the location of the C:Program FilesMicrosoftExchange ServerScripts subfolder, this is seldom necessary because the C:Program FilesMicrosoftExchange ServerScripts subfolder is included in the system search path. To display the search path, use the $env:path command."

"PSHome" should be "C:Program FilesMicrosoftExchange ServerScripts" On page 269, the 3rd sentence of the first paragraph on the page contains an incorrect reference to PSHome. Change: "Script files that you store in the PSHome subdirectory can be run directly from Exchange Management Shell without specifying a path." To: "Script files that you store in the C:Program FilesMicrosoftExchange ServerScripts subdirectory can be run directly from Exchange Management Shell without specifying a path."

"psi" should be "ps1" On page 269, the 4th sentence in the last paragraph on the page contains an incorrect command. Change: "If, on the other hand, you wanted to list any invalid recipients in a specific OU, you can enter the OU as a parameter, for example, CheckInvalidRecipients.psi –OrganizationalUnit Users." To: "If, on the other hand, you wanted to list any invalid recipients in a specific OU, you can enter the OU as a parameter, for example, CheckInvalidRecipients.ps1 –OrganizationalUnit Users."The 6th sentence in the last paragraph on the page contains an incorrect command. Change: "In this case, the command is CheckInvalidRecipients.psi –OrganizationalUnit –FixErrors." To: "In this case, the command is CheckInvalidRecipients.ps1 –OrganizationalUnit Users –FixErrors."

"PSHome" should be "C:Program FilesMicrosoftExchange ServerScripts"
On page 270, the first sentence of the last paragraph on the page incorrectly states that the PSHome subdirectory is the same as the Exchange Server Scripts subdirectory.



Change:

"Save the file in your PSHome subdirectory (probably C:Program FilesMicrosoftExchange ServerScripts) as MoveDon.ps1."



To:

"Save the file in the C:Program FilesMicrosoftExchange ServerScripts subdirectory as MoveDon.ps1."

"PSHome" should be "C:Program FilesMicrosoftExchange ServerScripts" On page 271, the 1st sentence of the third paragraph incorrectly states that the PSHome subdirectory is the same as the Exchange Server Scripts subdirectory. Change: "Save the file in your PSHome subdirectory as MoveAnyone.ps1." To: "Save the file in the C:Program FilesMicrosoftExchange ServerScripts subdirectory as MoveAnyone.ps1."

references to PSHome and the "exscripts" subdirectory need to be disregarded
On page 278, Step 3 contains incorrect references to the PSHome and C:Program FilesMicrosoftExchange Serverexscripts subdirectories.



Change:

"Save the file in the PSHome subdirectory (C:Program FilesMicrosoftExchange ServerScripts or C:Program FilesMicrosoftExchange Serverexscripts) as CreateNewUser.ps1, as shown in Figure 5-33."



To:

"Save the file in the C:Program FilesMicrosoftExchange ServerScripts subdirectory as CreateNewUser.ps1, as shown in Figure 5-33."

"PSHome" should be "$ExScripts" On page 280, the 3rd and 4th sentences in the first paragraph contain incorrect references to PSHome. Change: "This practice assumes that the PSHome subdirectory is at C:Program FilesMicrosoftExchange ServerScripts. If your PSHome subdirectory is not at C:Program FilesMicrosoftExchange Serverexscripts, amend the practice accordingly." To: "This practice assumes that the $ExScripts variable points to the subdirectory C:Program FilesMicrosoftExchange ServerScripts. If the $ExScripts variable does not points to the subdirectory C:Program FilesMicrosoftExchange ServerScripts, amend the practice accordingly."

"$Identity" should be "$Mailbox"
On page 284, answers B and D contain incorrect parameters.



Change:

B. Move-Mailbox -Identity $Identity –TargetDatabase "First Storage GroupFirst Glasgow Mailbox Database" -SourceMailboxCleanupOptions DeleteSourceMailbox

Param(

[string] $Identity

)

D. Param(

[string] $Identity

)

Move-Mailbox -Identity $Identity –TargetDatabase "First Storage GroupFirst Glasgow Mailbox Database"To:

B. Move-Mailbox -Identity $Identity –TargetDatabase "First Storage GroupFirst Glasgow Mailbox Database"

Param(

[string] $Identity

)

D. Param(

[string] $Mailbox

)

Move-Mailbox -Identity $Identity –TargetDatabase "First Storage GroupFirst Glasgow Mailbox Database"

Question directions regarding deleting databases are incorrect
On page 287, the second sentence of Question 3 in Case Scenario 1 contains invalid directions.



Change:

"You want to delete the mailbox in the source database after you have moved it to the target database."



To:

"You want to increase mailbox quotas after you have moved the mailbox to the target database."

Question directions regarding deleting databases are incorrect On page 287, the second sentence of Question 1 in Case Scenario 1 contains invalid directions. Change: "You want to delete the mailboxes in the source database after you have moved them to the target database." To: "You plan to apply different quotas to the mailboxes after you have moved them to the target database."

"PSHome" should be "$ExScripts"
On page 288, the 5th sentence in Question 3 of Case Scenario 2 contains an incorrect variable.



Change:

"Your PSHome subdirectory is at C:Program FilesMicrosoftExchange ServerScripts."



To:

"The $ExScripts variable that points to C:Program FilesMicrosoftExchange ServerScripts."

Question directions regarding deleting mailboxes is incorrect On page 288, the second sentence of Question 2 in Case Scenario 2 contains invalid directions. Change: "The moved mailboxes should be deleted from their source mailbox databases." To: "The moved mailboxes will be assigned increased mailbox quotas."

"target mailbox" should be "target mailbox database" On page 289, the second sentence of the second bullet point on the page contains an incorrect parameter. Change: "Expand this technique so that you can also specify the target mailbox as a parameter." To: "Expand this technique so that you can also specify the target mailbox database as a parameter."

Caption text for Figure 6-1 is incorrect
On page 294, the caption under Figure 6-1 contains incorrect information on active transport agents.



Change:

"Figure 6-1 Active transport agents and the order in which they are applied"



To:

"Figure 6-1 Active transport agents in the order of their priority."

Information regarding viewing transport agents is incorrect On page 294, the second sentence on the page contains incorrect information about viewing transport agents. Change: "You can view the transport agents in the order in which they are applied by entering the following Exchange Management Shell command: Get-TransportAgent" To: "You can view the transport agents in the order of their priority by entering the following Exchange Management Shell command: Get-TransportAgent"

Clarification needed regarding discarded spam messages
On page 295, the 7th sentence down in the first paragraph on the page requires clarification regarding discarded spam messages.



Change:

"Finally, messages that are received from SMTP servers on the blocked addresses list will always be discarded as spam, even if they also appear on the allowed addresses list."



To:

"Finally, messages that are received from SMTP servers on the blocked addresses list will always be discarded as spam, unless the SMTP servers also appear on the allowed addresses list."

Clarification needed regarding handling of e-mail from a block listed server On page 295, the 8th sentence down in the first paragraph contains incorrect information regarding SMTP server block lists. Change: "The only way to receive e-mail from an SMTP server on a block list is to remove it from the block list." To: "To receive e-mail from an SMTP server on a block list is to remove it from the block list or grant an exception by adding the SMTP server to the IP allow list."

Information regarding filtering recipients is incorrect
On page 298, the last sentence of the first paragraph contains incorrect information regarding how a server handles invalid addresses.



Change:

"If this setting is not enabled, the hub transport server will reject the invalid address."



To:

"If this setting is not enabled, the hub transport server must generate a non-delivery report for every invalid address."

Additional information needed in regards to Sender Reputation On page 299, the 1st sentence in the paragraph at the bottom of the page requires additional clarification on the Sender Reputation setting. Change: "Sender reputation is used to add SMTP servers to the IP block list for a limited duration based on the characteristics of the messages sent." To: "Sender reputation is used to add SMTP servers to the IP block list for a limited duration based on the characteristics of the sending host (open proxy) and the messages received from that host."

Explanation of setting is incorrect
On page 305, the last sentence under the bullet point "Purge message if message body deleted—transport" is incorrect.



Change:

"If you want the sanitized message forwarded to the recipient, you can enable this option."



To:

"If you do not want the sanitized message forwarded to the recipient, you can enable this option."

Shell command in Step 2 of Practice 1 is incorrect On page 306, the first sentence of Practice 1 Step 2 contains an incorrect shell command. Change: "Verify that the anti-spam server settings are enabled on the hub transport server by issuing the Exchange Management Shell Command: Set-TransportServer –Identity ‘ServerName’–Anti-SpamAgentsEnabled $true." To: "Verify that the anti-spam server settings are enabled on the hub transport server by issuing the Exchange Management Shell Command: Set-TransportServer –Identity ‘ServerName’ –AntiSpamAgentsEnabled $true."

Information incorrect regarding blocked addresses list
On page 310, the 2nd sentence in the first bullet point under the Lesson Summary contains incorrect information on the handling of messages that are on the blocked addresses list.



Change:

"Messages that are received from SMTP servers on the blocked addresses list will always be discarded as spam, even if they also appear on the allowed addresses list."



To:

"Messages that are received from SMTP servers on the blocked addresses list will be discarded as spam, unless they also appear on the allowed addresses list."

configuration is stored in Active Directory and not on an individual Hub Transport server On page 320, the 3rd sentence in the second paragraph contains incorred information regarding transport rules. Change: "Because transport rules work at the organizational level, a transport rule that you create on one hub transport server will be replicated to all other hub transport servers in the organization." To: "Because transport rules work at the organizational level, a transport rule that you create is applied via the Active Directory directory service to all other Hub Transport servers in the Exchange 2007 organization."

"all users" should be "all mailbox-enabled users"
On page 357, the 2nd sentence of the second paragraph incorrectly states that ActiveSync is enabled for all users.



Change:

"By default, Exchange ActiveSync is enabled for all users."



To:

"By default, Exchange ActiveSync is enabled for all mailbox-enabled users."

"OWA policy" should be "OWA settings" On page 357, the 2nd sentence in the seventh bullet point down at the bottom of the page incorrectly references non-existant OWA policies. Change: "Unlike the OWA policy that allows you to grant access to specific servers, this is a blanket ban or allow on all servers" To: "Unlike OWA settings that allow you to grant access to specific servers, this is a blanket ban or allow on all servers"

step missing regarding applying a policy to a user's mailbox
On page 358, the last sentence in the last paragraph on the page is missing a step to enable the ability to select a policy.



Change:

"This will open the Exchange ActiveSync Properties dialog box, shown in Figure 7-12. On the dialog box, click Browse, select a policy to apply to the user, and then click OK."



To:

"This will open the Exchange ActiveSync Properties dialog box, shown in Figure 7-12. On the dialog box, select the checkbox Apply an Exchange ActiveSync mailbox policy, then click Browse, select a policy to apply to the user, and then click OK."

additional information required for recovering a user password On page 360, the first sentence of the last paragraph on the page is missing information regarding when the "Manage Mobile Device" action is available. Change: "To recover a user password, open the Recipient ConfigurationMailbox node in Exchange Management Console, select the user’s mailbox, and then click Manage Mobile Device from the Actions pane." To: "To recover a user password, open the Recipient ConfigurationMailbox node in Exchange Management Console, select the user’s mailbox, and then click Manage Mobile Device from the Actions pane. Note that the Manage Mobile Device action is ony available for mailboxes with an established device partnership."

additional information needed for performing a remote wipe
On page 362, the 1st sentence of the second paragraph under "Configuring Remote Wipe" is missing information regarding the availability of the "Manage Mobile Device" action.



Change:

"To perform a remote wipe, select the user’s mailbox under the Recipient ConfigurationMailbox node and then click Manage Mobile Device in the Actions pane."



To:

"To perform a remote wipe, select the user’s mailbox under the Recipient ConfigurationMailbox node, and then click Manage Mobile Device from the Actions pane. As mentioned, the Manage Mobile Device action is ony available for mailboxes with an established device partnership."

HTTP missing from most commonly used mail access protocols On page 366, the 1st sentence of the second paragraph on the page is missing HTTP as a commonly used mail access protocol. Change: "IMAP4 and POP3 are the most commonly used mail access protocols." To: "Besides HTTP, IMAP4 and POP3 are the most commonly used mail access protocols on the Internet."

additional clarification needed for external calendar access
On page 367, the last bullet point on the page contains an incorrect location for a server.



Change:

"To have POP3 users access calendar data hosted on an external server, issue the command Set-PopSettings –CalenderItemRetrievalOption 2 -InternetURL https://external.calendar.url"



To:

"To have POP3 users access calendar data hosted on a server published via an external URL, issue the command Set-PopSettings –CalenderItemRetrievalOption 2 -InternetURL https://external.calendar.url"

"SetImapSettings" should be "Set-ImapSettings" On page 368, the first sentence in the Note box at the bottom of the page is missing a hyphen in the Set-ImapSettings command. Change: "In the event that you want to configure certain users to use POP3 or IMAP4 protocol settings to other users, you can specify individual settings using the Set-PopSettings or SetImapSettings command." To: "In the event that you want to configure certain users to use POP3 or IMAP4 protocol settings to other users, you can specify individual settings using the Set-PopSettings or Set-ImapSettings command."

additional clarification needed for external calendar access
On page 369, the 3rd bullet point on the page contains an incorrect location for a server.



Change:

"To have IMAP4 users access calendar data hosted on an external server, issue the command Set-ImapSettings –CalenderItemRetrievalOption 2 InternetURL https://external.calendar.url."



To:

"To have IMAP4 users access calendar data hosted on a server published via an external URL, issue the command Set-ImapSettings –CalenderItemRetrievalOption 2 InternetURL https://external.calendar.url."

"SharePoint" should be "Windows SharePoint Services" On page 381, the first sentence of the 2nd paragraph contains an incorrect name for an add-on component. Change: "As you learned in Chapter 4, “Configuring Public Folders,” the traditional functionality serviced by Exchange public folders is now better addressed through products such as SharePoint, which is included as an add-on component with Windows Server 2003 R2 and Windows Server 2008." To: "As you learned in Chapter 4, “Configuring Public Folders,” the traditional functionality serviced by Exchange public folders is now better addressed through products such as Windows SharePoint Services, which is included as an add-on component with Windows Server 2003 R2 and Windows Server 2008."

"e-mail enabled accounts" missing from descriptions
On page 387, the 4th and 7th bullet point down is missing a specific account in the description.



Change:

"All Users All mail-enabled users in the organization

Public Folders All public folders"



To:

"All Users All mailbox-enabled and e-mail-enabled accounts in the organization

Public Folders All e-mail-enabled public folders"

Description of "Default Offline Address Book" requires additional clarification On page 387, the second bullet point down requires additional clarification. Change: "Default Offline Address Book Contains all items in the default global address list but can be viewed offline" To: "Default Offline Address Book Although strictly speaking not an address list, the OAB contains all items in the default global address list for offline use"

"objects" should be "recipient objects"
On page 388, the first sentence under Figure 8-3 requires additional clarification regarding objects.



Change:

"To create an address list that shows only a subset of all objects within the Exchange organization, perform the following steps"



To:

"To create an address list that shows only a subset of all recipient objects within the Exchange organization, perform the following steps"

"1:00 am" should be "5:00 am" On page 390, the second sentence of the last paragraph on the page contains an incorrect time. Change: "The default setting is for OABs to be rebuilt at 5:00 am (the default OAB is rebuilt at 1:00 am)." To: "The default setting is for OABs to be rebuilt at 5:00 am (for example, the default OAB is rebuilt at 5:00 am)."

"New-Offline-AddressBook" should be "New-OfflineAddressBook"
On page 392, the first sentence of the 1st paragraph contains a unnecessary hyphen in a cmdlet.



Change:

"To create a new OAB using Exchange Management Shell, utilize the New-Offline-AddressBook cmdlet."



To:

"To create a new OAB using Exchange Management Shell, utilize the New-OfflineAddressBook cmdlet."

"DevicePassword-Expiration" should be "DevicePasswordExpiration" On page 397, the second sentence of the 3rd bullet point down contains a cmdlet with an incorrect hyphen. Change: "The Exchange Management Shell parameter for this setting when using the Set-ActiveSyncMailboxPolicy cmdlet is DevicePassword-Expiration." To: "The Exchange Management Shell parameter for this setting when using the Set-ActiveSyncMailboxPolicy cmdlet is DevicePasswordExpiration."

"Conditions" should be "Address Format"
On page 402, the caption for Figure 8-15 is incorrect.



Change:

"Figure 8-15 New E-Mail Address Policy Conditions"



To:

"Figure 8-15 New E-Mail Address Policy Address Format"

"%true" should be "$true" On page 407, Question 3 contains an incorrect parameter. Change: "What will happen if you execute the Exchange Management Shell command Set-OfflineAddressBook –Identity NewOAB –IsDefault %true using an account with the appropriate permissions?" To: "What will happen if you execute the Exchange Management Shell command Set-OfflineAddressBook –Identity NewOAB –IsDefault $true using an account with the appropriate permissions?"

"public folder" should be "public folder hierarchy"
On page 410, the 5th sentence down on the page requires additional information on type of folder.



Change:

"In the event that you want to force synchronization of all public folders on a mailbox database server, issue the following command: Update-PublicFolderHierarchy"



To:

"In the event that you want to force synchronization of the public folder hierarchy on a mailbox database server, issue the following command: Update-PublicFolderHierarchy"

Incorrect assignment of permissions On page 412, the first sentence after the 3rd bullet point contains incorrect objects and groups for permissions. Change: "Unlike administrator permissions, client permissions are assigned to mail-enabled objects, such as users and distribution groups." To: "Unlike administrator permissions, client permissions are assigned to mailbox-enabled user accounts and mai-enabled security groups."

Public folders will not replicate to all other mailbox servers
On page 415, the second bullet point down in the Lesson Summary contains incorrect information regarding replication of public folders.



Change:

"By default, a public folder will replicate to all other mailbox servers in an organization that hosts a public folder database."



To:

"By default, only the public folder hierarchy is replicated to all other mailbox servers in an organization that host a public folder database."

"password" should be "mailbox" On page 418, the third bullet point down under Chapter Summary contains a reference to an incorrect policy. Change: "Mobile devices are managed by Exchange ActiveSync password policies." To: "Mobile devices are managed by Exchange ActiveSync mailbox policies."

"mail" should be "mailbox"
On page 419, the third sentence down under Case Scenario 2 contians an incorrect account.



Change:

"Both students, teachers, and support staff have mail-enabled accounts in the Exchange organization."



To:

"Both students, teachers, and support staff have mailbox-enabled accounts in the Exchange organization."

Get-Message should be Get-Queue On page 431, the Usage column of the Get-Queue row in Table 9-1 refers to Get-Message rather than Get-Queue. Change: "Lets you view the configuration details of the queues that are present on transport servers. You can use the Get-Message cmdlet to retrieve a set of messages and then pipe the results to one of the cmdlets that modify queues and messages." To: "Lets you view the configuration details of the queues that are present on transport servers. You can use the Get-Queue cmdlet to retrieve a set of messages and then pipe the results to one of the cmdlets that modify queues and messages."

Identity should be Filter
On page 435, the third sentence of the third paragraph refers to Identity rather than Filter.



Change:

"For example, to use the Identity parameter to identify and remove all messages from don.hall@tailspintoys.internal from all queues on the default server without sending an NDR, you would enter the following command:"



To:

"For example, to use the Filter parameter to identify and remove all messages from don.hall@tailspintoys.internal from all queues on the default server without sending an NDR, you would enter the following command:"

Remove-Mailbox should be Remove-Message
On page 435, the MORE INFO box contains two references to Remove-Mailbox that should read Remove-Message.



Change:

"Remove-Mailbox cmdlet

For more information about the Remove-Message cmdlet, including syntax and filter conditions, search Exchange Server 2007 Help for “Remove-Mailbox” or access http://technet.microsoft.com/en-us/library/aa996371.aspx."



To:

"Remove-Message cmdlet

For more information about the Remove-Message cmdlet, including syntax and filter conditions, search Exchange Server 2007 Help for “Remove-Message” or access http://technet.microsoft.com/en-us/library/aa996371.aspx."

Move-Mailbox should be Remove-Message On page 435, the first sentence of the third paragraph refers to Move-Mailbox rather than Remove-Message. Change: "You can use an Identity parameter or a Filter parameter with Move-Mailbox." To: "You can use an Identity parameter or a Filter parameter with Remove-Message."

Remove-Mailbox should be Remove-Message On page 435, the first sentence refers to Remove-Mailbox rather than Remove-Message. Change: "The Remove-Mailbox cmdlet also lets you specify an Identity parameter that can optionally identify a message queue and server in addition to the message itself." To: "The Remove-Message cmdlet also lets you specify an Identity parameter that can optionally identify a message queue and server in addition to the message itself."

Missing quotation marks
On page 436, the command in the Quick Check box is missing quotation marks.



Change:

"Remove-Message –Filter {FromAddress –eq kim.akers@tailspintoys.internal} -WithNDR $False"



To:

"Remove-Message –Filter {FromAddress –eq "kim.akers@tailspintoys.internal"} -WithNDR $False"

Incorrect instructions
On page 473, the first sentence of the Filtering Event Viewer Logs section is incorrect.



Change:

"You can filter a log by clicking Filter in the View menu or by double-clicking a log and accessing the Filter tab in the log’s Properties dialog box."



To:

"You can filter a log by clicking Filter in the View menu or by right-clicking a log and selecting Properties in order to access the Filter tab in the log’s Properties dialog box."

Incorrect information regarding Windows logs On page 473, the third bullet point is incorrect. Change: "Windows PowerShell No events were recorded in this log. It is possible that Microsoft has provided this log for future use. Future releases of Exchange Server 2007 might remove the PowerShell log and use the Windows PowerShell log instead." To: "Windows PowerShell The Windows PowerShell event log records details of Windows PowerShell operations, such as starting and stopping the program "engine," starting and stopping the Windows PowerShell providers, and details about Windows PowerShell commands."

PSHome should be ExScripts On page 476, the third sentence refers to PSHome rather than ExScripts. Change: "You do this by typing the following into a text editor and saving it with a file name GetEvent.ps1 in the PSHome subdirectory (typically, C:Program FilesMicrosoftExchange ServerScripts):" To: "You do this by typing the following into a text editor and saving it with a file name GetEvent.ps1 in the ExScripts subdirectory (typically, C:Program FilesMicrosoftExchange ServerScripts):"

Incorrect information regarding frame
On page 478, the first sentence of the NOTE is incorrect.Change:

"A frame encapsulates layer 2 (network interface layer) data. Network Monitor reads and displays encapsulations that include both network interface layer data (such as Ethernet data) and higher-layer data from protocols such as Address Resolution Protocol (ARP), IP versions 4 and 6, Transmission Control Protocol (TCP), and DNS. A frame is distinct from a packet in that a packet encapsulates layer 3 (Internet layer) data. However, the terms are often used interchangeably."



To:

"A frame is a layer-2 element that encapsulates layer 3 (network layer) data. Network Monitor reads and displays encapsulations that include both data link layer elements (such as Ethernet headers and trailers) and higher-layer data from protocols such as Address Resolution Protocol (ARP), IP versions 4 and 6, Transmission Control Protocol (TCP), and DNS. A frame is distinct from a packet in that a packet encapsulates layer 3 (network layer) data."

Incorrect information regarding the use of Network Monitor On page 478, the first sentence after the bulletted list is incorrect. Change: "You might, for example, use Network Monitor to diagnose hardware and software problems when an Exchange Server 2007 server cannot communicate with other computers." To: "You might, for example, use Network Monitor to diagnose connectivity problems when an Exchange Server 2007 server cannot communicate with other computers."

"network interface–layer protocols, Internet-layer protocols" should be "data-link-layer protocols, network-layer protocols"
On page 480, the last sentence before the Examining the Network Monitor Interface section is incorrect.



Change:

"You can filter frames on the basis of source and destination addresses, network interface–layer protocols, Internet-layer protocols, transport-layer protocols, protocol properties, and pattern offset."



To:

"You can filter frames on the basis of source and destination addresses, data-link-layer protocols, network-layer protocols, transport-layer protocols, protocol properties, and pattern offset."

Incorrect information On page 486, the second sentence of the Best Practices Analyzer box is incorrect. Change: "The Best Practices Analyzer examines a single Exchange Server 2007 server, all servers in an administration group, or all servers in a deployment." To: "The Best Practices Analyzer can examine a single Exchange 2007 server, a group of selected servers, or all servers in an organization."

PSHome should be ExScripts
On page 499, the second sentence of question 6 refers to PSHome rather than ExScripts.



Change:

"You save the following code as a PowerShell script ListEvent.ps1 in the PSHome subdirectory."



To:

"You save the following code as a PowerShell script ListEvent.ps1 in the ExScripts subdirectory."

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.

Incorrect description of agent
On page 511, the NOTE is incorrect.



Change:

"An agent is an Exchange Transport component that can provide routing information."



To:

"An agent is an Exchange Transport component that extends the processing capabilities of the message transport."

arbitrary should be unique On page 511, the second sentence of the MessageID bullet point is incorrect. Change: "If the MessageID header field does not exist or is blank, an arbitrary value is assigned." To: "If the MessageID header field does not exist or is blank, a unique value is assigned to identify the message."

Incorrect information regarding forked messages
On page 512, the NOTE is incorrect.



Change:

"A forked message is a message that is transferred to one or more recipients."



To:

"A forked message is a message copy that the categorizer creates for the original message if recipients reside in separate destinations or require different message formats."

Additional information needed On page 512, the last sentence of the third sentence requires more information.Change: "This feature works only on Hub Transport servers." To: "This feature works only on Hub Transport servers, but not on Edge Transport servers because Edge Transport servers do not have access to the recipient information in Active Directory."The last sentence of the fourth paragraph contains the same error. Change: "This feature works only on Hub Transport servers." To: "This feature works only on Hub Transport servers, but not on Edge Transport servers because Edge Transport servers do not have access to the recipient information in Active Directory."

Additional information needed for Figure 10-2 On page 514, the second sentence requires more information. Change: "Figure 10-2 illustrates the command." To: "Figure 10-2 illustrates the command without the Server parameter."

Incorrect information
On page 521, the MORE INFO box is incorrect.



Change:

"More Info: Circular logging



Circular logging helps control the hard disk space that is used by the log files at the expense of overwriting older data in logs. For a concise but informative article about circular logging, access http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1171496,00.html Note that this is not a Microsoft site and that the URL might change. If you cannot access it, search for “Circular Logging” on the Internet."



To:

"Note: Circular logging



The Exchange Server 2007 product documentation incorrectly refers to the process of deleting old message tracking log files as circular logging. Circular logging is a feature of the Extensible Storage Engine (ESE) to save disk space by overwriting transaction log files after the data that the log files contain has been committed to the databases. Transaction log files have nothing to do with message tracking log files. For more information about transaction logging including a section about circular logging, see “Understanding Transaction Logging” in the Exchange Server 2007 online help at http://technet.microsoft.com/en-us/library/bb331951.aspx. "

Incorrect terminology On page 521, the first paragraph is incorrect. Change: "By default, the Exchange Server 2007 server uses circular logging to limit the amount of storage that message tracking log files require. The criteria for overwriting log files are based on both file size and age." To: "By default, Exchange Server 2007 deletes old message tracking log files after 30 days to limit the amount of storage that message tracking log files require. Another criteria that causes Exchange Server 2007 to delete old tracking log files is that the message tracking log directory reaches its specified maximum size."

circular logging should be Exchange Server 2007
On page 524, the last sentence of the third paragraph refers to "circular logging" rather than "Exchange Server 2007".



Change:

"After the maximum size or age limit (by default, 30 days) is reached, circular logging deletes the oldest message tracking log files."



To:

"After the maximum size or age limit (by default, 30 days) is reached, Exchange Server 2007 deletes the oldest message tracking log files."

5 MB should be 20 MB
On page 525, the first line of the third paragraph refers to 5 MB rather than 20 MB.



Change:

"To set the maximum size of individual message tracking log files to 5 MB on an"



To:

"To set the maximum size of individual message tracking log files to 20 MB on an"

circular logging should be Exchange Server 2007 On page 525, the last sentence refers to "circular logging" rather than "Exchange Server 2007". Change: "As stated previously, circular logging deletes the oldest message tracking log files when the message tracking log directory reaches its specified maximum size." To: "As stated previously, Exchange Server 2007 deletes the oldest message tracking log files when the message tracking log directory reaches its specified maximum size."

More specificity needed
On page 526, the second paragraph after the box is incorrect.Change:

"For example, to set the maximum size of the message tracking log directory to 500 MB on an Exchange Server 2007 server named Glasgow that has the Hub Transport server role installed, you would enter the following command:



Set-TransportServer Glasgow -MessageTrackingLogMaxDirectorySize 500MB



To set the maximum size of the message tracking log directory to 150 MB on an Exchange Server 2007 server named Edinburgh that has the Mailbox server role installed, you would enter the following command:"



To:

"For example, to set the maximum size of the message tracking log directory to 500 MB on an Exchange Server 2007 server named Glasgow that has the Hub Transport server role installed, you would enter the following command:



Set-TransportServer Glasgow -MessageTrackingLogMaxDirectorySize 500MB



To set the maximum size of the message tracking log directory for the Mailbox server role to 150 MB on an Exchange Server 2007 server named Edinburgh that has the Mailbox server role installed, you would enter the following command:"

Clarification needed On page 526, the second paragraph of the "Specified and Actual Maximum Message Tracking Log Directory Size" box requires more information. Change: "When the Hub Transport server role and the Mailbox server role are installed on the same server, the maximum size of the message tracking log directory is typically two times the specified value." To: "When the Hub Transport server role and the Mailbox server role are installed on the same server and use the same message tracking log directory, the maximum size of this directory is equal to the sum of the separate size limits specified for the Hub Transport server role and the Mailbox server role."

More specificity needed
On page 527, the third paragraph of the "Configuring the Maximum Age for Message Tracking Logs" section is incorrect.



Change:

"For example, to change the maximum age of a message tracking log file to 45 days on an Exchange Server 2007 server named Glasgow that has the Hub Transport server role installed, you would enter the following command:



Set-TransportServer Glasgow -MessageTrackingLogMaxAge 45.00:00:00



To change the maximum age of a message tracking log file to 20 days on an Exchange Server 2007 server named Edinburgh that has the Mailbox server role installed, you would enter the following command:"



To:

"For example, to change the maximum age of the message tracking log files for the Hub Transport server role to 45 days on an Exchange Server 2007 server named Glasgow that has the Hub Transport server role installed, you would enter the following command:



Set-TransportServer Glasgow -MessageTrackingLogMaxAge 45.00:00:00



To change the maximum age of the message tracking log files for the Mailbox server role to 20 days on an Exchange Server 2007 server named Edinburgh that has the Mailbox server role installed, you would enter the following command:"

circular logging should be Exchange Server 2007 On page 527, the second sentence of the "Configuring the Maximum Age for Message Tracking Logs" refers to circular logging rather than Exchange Server 2007. Change: "If a message tracking log file reaches its specified maximum age, circular logging deletes it." To: "If a message tracking log file reaches its specified maximum age, Exchange Server 2007 deletes it."

More specificity needed On page 528, the third paragraph of the "Configuring Message Subject Logging in Message Tracking Logs" section is incorrect. Change: "For example, to disable message subject logging on an Exchange Server 2007 server named Glasgow that has the Hub Transport server role installed, you would enter the following command: Set-TransportServer Glasgow -MessageTrackingLogSubjectLoggingEnabled $False To enable message subject logging (assuming it has previously been disabled) on an Exchange Server 2007 server named Edinburgh that has the Mailbox server role installed, you would enter the following command:" To: "For example, to disable message subject logging for the Hub Transport server role on an Exchange Server 2007 server named Glasgow that has the Hub Transport server role installed, you would enter the following command:Set-TransportServer Glasgow -MessageTrackingLogSubjectLoggingEnabled $False To enable message subject logging for the Mailbox server role (assuming it has previously been disabled) on an Exchange Server 2007 server named Edinburgh that has the Mailbox server role installed, you would enter the following command:"

circular logging should be Exchange Server 2007
On page 539, the first sentence of question 3 refers to circular logging rather than Exchange Server 2007.



Change:

"You want to guarantee that tracking log files will never be removed by circular logging on an Exchange Server 2007 server named Chicago that has both the Hub Transport server and the Mailbox server roles installed."



To:

"You want to guarantee that tracking log files will never be removed by Exchange Server 2007 on a server named Chicago that has both the Hub Transport server and the Mailbox server roles installed."

Incorrect information given On page 542, the second sentence of the second paragraph is incorrect. Change: "If you have a server with the Hub Transport server role installed that is not coping with increased load, the answer might be to install the role in a second server and configure a load balancing method, such as Domain Name System (DNS) round-robin." To: "If you have a server with the Hub Transport server role installed that is not coping with increased load, the answer might be to install the role in a second server for load balancing." The MORE INFO box is also incorrect. Change: "Round-robin For more information about using DNS round-robin for load balancing, search the Windows Server Help and Support Center for “Configuring round robin” or access http://technet.microsoft.com/de-de/windowsserver/default.aspx." To: "Load Balancing for Transport Servers For more information about load balancing transport servers, search the Exchange Server 2007 Help for “Load Balancing and Fault Tolerance for Transport Servers” or access http://technet.microsoft.com/en-us/library/bb267003.aspx."

MSExchange should be MSExchangeIS
On page 554, the first sentence after table 10-5 references MSExchange rather than MSExchangeIS.



Change:

"The MSExchange Mailbox object has other counters associated with it that test particular aspects of Exchange operation."



To:

"The MSExchangeIS Mailbox object has other counters associated with it that test particular aspects of Exchange operation."

Reference to Transport Layer Security should be removed On page 556, the second to last sentence contains a reference to Transport Layer Security that should be removed. Change: "In addition, you can determine the total number of Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connections that have been opened since the POP3 service was started." To: "In addition, you can determine the total number of Secure Sockets Layer (SSL) connections that have been opened since the POP3 service was started."

Reference to circular logging should be removed
On page 560, the last sentence before the IMPORTANT box contains a reference to circular logging.



Change:

"As with message tracking logs, Exchange Server 2007 server uses circular logging to limit the total disk space for protocol logging based on file size and file age."



To:

"As with message tracking logs, Exchange Server 2007 automatically purges old log files to limit the total disk space for protocol logging based on file size and file age."

circular logging should be Exchange Server 2007 On page 562, the last sentence of the first paragraph refers to circular logging rather than Exchange Server 2007. Change: "After the maximum size or age limit is reached, circular logging deletes the oldest protocol log files." To: "After the maximum size or age limit is reached, Exchange Server 2007 deletes the oldest protocol log files."

Circular logging should be Exchange Server 2007
On page 563, the last sentence of the third paragraph refers to circular logging rather than Exchange Server 2007.



Change:

"Circular logging deletes the oldest log files when the protocol log directory reaches its maximum specified size or when a log file reaches its maximum specified age."



To:

"Exchange Server 2007 deletes the oldest log files when the protocol log directory reaches its maximum specified size or when a log file reaches its maximum specified age."

Incorrect information On page 566, the last paragraph contains incorrect information. Change: "The Set-CASMailbox cmdlet sets Client Access–related attributes for Exchange ActiveSync, OWA, POP3, and IMAP4 for a specified mailbox on an Exchange Server 2007 server that has the Client Access role installed. The cmdlet does not support a Server parameter, and you cannot specify a remote server." To: "The Set-CASMailbox cmdlet sets Client Access–related attributes for Exchange ActiveSync, OWA, POP3, and IMAP4 for a specified mailbox. The cmdlet supports the DomainController parameter, so that you cannot specify a specific domain controller for the operation."

Clarification needed
On page 567, the first sentence after the MORE INFO box should be clarified.



Change:

"You can use PowerShell commands based on the Get-CASMailbox cmdlet to return a list of the attributes of a Microsoft Exchange Server 2007 mailbox on a server that has the Client Access server role installed."



To:

"You can use PowerShell commands based on the Get-CASMailbox cmdlet to return a list of mailbox attributes that are relevant for the Client Access server role."

Clarification needed On page 568, the first two sentences of the second paragraph should be clarified. Change: "The Set-POPSettings cmdlet enables you to specify the POP3 settings for an Exchange Server 2007 Client Access server that is running the POP3 service. The cmdlet does not support a Server parameter, and you need to run the commands on the Client Access server." To: "The Set-POPSettings cmdlet enables you to specify the POP3 settings for an individual or all Exchange Server 2007 Client Access servers that is running the POP3 service. By using the Server parameter, you can specify an individual Client Access server that you want to configure."

Incorrect information regarding the SEND EventID
On page 616, the 2nd sentence in the second paragraph contains incorrect information regarding the SEND EventID.



Change:

"Note that the SEND EventID specifies only messages sent to an external Exchange organization and does not list the user’s internal mail."



To:

"Note that the SEND EventID specifies messages transferred over a send connector and does not list the messages delivered via store driver between Hub Transport servers and Mailbox servers."

Reports are not written to a database file On page 623, the last sentence of the fourth paragraph contains incorrect information regarding reports that are written to a database file. Change: "These reports are written to a database file called the Virus Incident log and a text file called the Virus log." To: "Virus-related events are written to a database file called the Virus Incident log and a text file called the Virus log."

Clarification needed for Forefront Server Security Administrator instructions
On page 624, the first complete sentence on the page incorrectly states that if the Forefront Server Security Administrator is installed on the server it will automatically connect to that server.



Change:

"By default, if the tool is installed on an Exchange Server 2007 server, it connects to that server."



To:

"By default, if the tool is installed on an Exchange Server 2007 server, it suggests to connect to that server."

Clarification needed regarding Edge transport servers On page 626, the first sentence of the last paragraph on the page contains incorrect information regarding Edge transport servers and quarantining messages. Change: "Edge transport servers do not currently quarantine messages." To: "By default, Edge transport servers do not quarantine messages."

Clarification needed regarding mailbox settings relevant for client access
On page 630, the second to the last sentence on the page incorrectly states that client settings are stored on CAS servers.



Change:

"To list the client settings on a client access server, you would use Exchange Management Shell commands based on the Get-CASMailbox cmdlet."



To:

"To list the mailbox settings relevant for client access, you would use Exchange Management Shell commands based on the Get-CASMailbox cmdlet."

Information regarding command that obtains client settings is incorrect On page 631, the last sentence of the first paragraph incorrectly states that client settings are stored on the CAS server. Change: "For example, the following command returns the client settings for all the mailboxes on the server on which it runs that have OWA enabled" To: "For example, the following command returns the client settings for all the mailboxes that have OWA enabled"

Additional information required
On page 643, the third sentence of the 3rd paragraph is missing a type of snapshot.



Change:

"You will look at the use of the Volume Shadow Copy Service (VSS), which lets you quickly restore from a backup that was taken by using a hardware-based snapshot."



To:

"You will look at the use of the Volume Shadow Copy Service (VSS), which lets you quickly restore from a backup that was taken by using a hardware-based or software-based snapshot."

Corrections needed in Real World example On page 644, the 2nd paragraph in the Real World box contains inaccuracies. Change: "It had invested in a top-of-the-range Storage Area Network (SAN) system. The disk set was striped with parity for instant failover and then mirrored across a fiber network to a disk array in another building. All spindles were hot swappable. The loss of a disk or even an entire array was easily retrievable and would have minimal or no effect on the user experience." To: "It had invested in a top-of-the-range Storage Area Network (SAN) system. The disk set was striped with parity to sustain a disk failure without service interruption and then mirrored across a fibre channel network to a disk array in another building. All spindles were hot swappable. The loss of a disk or even an entire array was easily retrievable and would have no effect on system availability."

Microsoft provides an Exchange-aware VSS based backup solution
On page 648, the description for VSS in the second bullet point incorrectly states that Microsoft does not provide an Exchange-aware VSS based backup solution.



Change:

"VSS Exchange Server 2003 introduced support for VSS and this support is extensively enhanced in Exchange Server 2007. However, Microsoft does not provide an Exchange-aware VSS based backup solution. NTBackup does not support VSS. Third-party backup software is required to back up the Exchange database with VSS."



To:

"VSS Exchange Server 2003 introduced support for VSS and this support is extensively enhanced in Exchange Server 2007. Microsoft provides a software VSS-based backup solution for Exchange Server through Microsoft System Center Data Protection Manager (DPM) 2007, which is a separate product that provides

disk-based recovery and tape-based, long-term archival storage for a complete data protection and recovery solution. NTBackup does not support VSS. DPM 2007 or third-party backup software is required to back up the Exchange database with VSS."

Link provided for circular logging is English only
On page 649, the link provided in the 3rd sentence of the "MORE INFO Circular Logging" box is only in English and is not a Microsoft site.



Change:

"For a concise but informative article about circular logging, access http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1171496,00.html. Note that this is not a Microsoft site, and the URL might change. If you cannot access it, search for “Circular Logging” on the Internet."



To:

"Circular logging is a feature of the Extensible Storage Engine (ESE). ESE maintains maintains all Exchange Server mailbox databases and public folder databases. For more information about circular logging, see “Understanding Transaction Logging” in the Exchange Server 2007 online help at http://technet.microsoft.com/en-us/library/bb331951.aspx. "

Inaccurate information regarding full backups On page 649, the first sentence of the 1st paragraph incorrectly states that a full backup is the simplest backup. Change: "Full backup is the simplest backup and restore method because it gives you a single backup set to restore." To: "Full backup facilitates restore operations because it gives you a single backup set to restore."

Multiple inaccuracies regarding differential and incremental backups On page 649, the second paragraph on the page contains multiple inacurracies regarding differential and incremental backups. Change: "If you use differential or incremental backups, only changes are saved, the size of backup files is smaller than for a complete backup, and backup takes less time. However, these backup types require multiple backup sets to perform a full restore. If any of those backup sets are missing or not restorable, recovery can be only to the point prior to the nonrecoverable backup set." To: "If you use differential or incremental backups, only changes since the last full or incremental backup are saved, the size of backup files is smaller than for a complete backup, and backup takes less time. However, these backup types require multiple backup sets to perform a full restore. Especially regarding incremental backups, if any of those backup sets are missing or not restorable, recovery can be only to the point prior to the nonrecoverable backup set."

"replicated database" should be "shadow copy"
On page 650, the first paragraph contains multiple inaccurate references to "replicated databases" and also additional information is needed regarding backups.



Change:

"If you use VSS to create a replicated database, you can use all four backup types to back up the replicated database. Backups can be selected at the storage group level, and there can be only one backup job running against a specific storage group. If you back up a storage group from a replica, you cannot start a backup of the active storage group until the backup of the replica storage group finishes. Separate storage groups can be backed up in parallel."



To:

"If you use VSS to create a shadow copy of a storage group, you can use all four backup types to back up the shadow copy. Backups can be selected at the storage group level, and there can be only one backup job running against a specific storage group. If you back up the shadow copy of a storage group, you cannot start another backup of the same storage group until the VSS requestor signals backup success or failure to the VSS writer of Exchange Server 2007 and completes the backup process. Separate storage groups can be backed up in parallel."

Incorrect information regarding performing restores On page 650, the fourth sentence of the 3rd paragraph contains inaccurate information regarding restoring databases. Change: "In order to perform a restore, you would need the backup set from the full backup job and all the backup sets from the incremental backup jobs."To: "In order to restore the database up to the latest possible point in time, you would need the backup set from the last full backup job and all the backup sets from subsequent incremental backup jobs."

Link for SLA additional information broken
On page 651, the link to additional information regarding SLA in the "MORE INFO Service-level agreements" box is broken.



Change:

"For more information about SLAs, search for “Establishing Service Level Agreement Requirements” in Exchange Server 2007 Help or access http://technet.microsoft.com/en-us/library/bb124694.aspx."



To:

"For more information about SLAs, search for “Establishing a Service Level Agreement” in the Microsoft TechNet Library for Exchange Server or access http://technet.microsoft.com/en-us/library/bb124886.aspx."

Additional information regarding .edb file size On page 651, the third sentence in the 2nd paragraph needs additional information regarding .edb file sizes. Change: "The .edb file size is limited to 16 TB by ESE, but in practice the database size should be much smaller to satisfy SLAs for downtime—the bigger the database, the more time it takes to restore it." To: "The physical size limit for .edb files is 16 TB, but only the databases of the Enterprise Edition can grow to this size. Exchange Server 2007 Standard Edition limits the individual database size to 50 GB (RTM version) and 250 GB (SP1). In practice the database size should be much smaller to satisfy SLAs for downtime—the bigger the database, the more time it takes to restore it."

Clarification needed
On page 652, the first sentence of the last paragraph needs additional clarification.



Change:

"After transaction log files are committed, they are protected by backups."



To:

"After transaction log files are committed into the databases and backed up, they can be deleted."

Multiple inaccuracies regarding OAB
On page 654, the first paragraph on the page contains multiple inaccuracies regarding offline address books.



Change:

"The offline address book (OAB) is stored by default on a mailbox server in a folder in the file path C:Program FilesMicrosoftExchange ServerExchangeOAB. Replicas of the OAB are distributed to Microsoft Outlook clients to enable clients to look up address book requests without having to connect to an Exchange server. If an Exchange organization uses public folders to store OAB information, this information is stored in the public folder database and on mailbox and Client Access servers. In this case, the OAB is replicated as part of public folder replication and is backed up during public folder backup. If public folders are not used, OAB information is generated by the Availability and Autodiscover services. Chapter 4, “Public Folders,” discusses the generation and storage of OAB information."



To:

"The offline address book (OAB) is stored by default on a mailbox server in a folder in the file path C:Program FilesMicrosoftExchange ServerExchangeOAB. Microsoft Outlook clients download OABs to enable clients to look up address book requests without having to connect to an Exchange server. If an Exchange organization uses public folders to store OAB information, this information is stored in the public folder database on Mailbox servers. In this case, the OAB is replicated as part of public folder replication and is backed up during public folder backup. If public folders are not used, OAB information is generated by the OABGen service on a Mailbox server, distributed by the Microsoft Exchange File Distribution service (MSExchangeFDS) on CAS servers, and downloaded by Outlook 2007 clients and mobile devices from CAS servers via the OAB virtual directory. The Autodiscover service returns the correct OAB URL to the client according to the parameters of the client connection. Chapter 4, “Public Folders,” discusses the generation and storage of OAB information."

OWA is not relevant to OAB On page 654, the first sentence of the second paragraph incorrectly uses OWA in relation to OAB. Change: "If, however, you are using Web distribution, such as Outlook Web Access (OWA), you need to back up and restore the OAB file on your server." To: "If you are using the Web-based distribution method via the OAB virtual directory, you need to back up the OAB files generated by OABGen on your Mailbox server."

OWA is not relevant to OAB
On page 656, in Table 12-1 the Backup Method column for the first OAB entry includes incorrect information about OWA.



Change:

"File system backup (if used with OWA)"



To:

"File system backup (if the Web-based distribution method is used)"

Information incorrect on how OAB is generated On page 656, in Table 12-1 the second sentence in the Location column for the 2nd OAB entry is incorrect. Change: "Otherwise, OAB information is generated by the Availability and Autodiscover services." To: "Otherwise, OAB information is distributed by the Exchange File Distribution service and OAB virtual directory."

Clarification needed On page 657, the second sentence of the 4th paragraph needs clarification. Change: "You do not need to carry out any backup jobs to restore this server role, but recovery times can be improved if you carry out a file-level backup of the message tracking and protocol log files." To: "You do not need to carry out any backup jobs to restore this server role, but if you carry out a file-level backup of the message tracking and protocol log files you can restore these files to provide past information for message tracking and troubleshooting purposes."

Size of backup incorrect
On page 663, the second sentence of the 1st paragraph contains an incorrect backup size.



Change:

"If, for example, you are performing a full backup of 1,000 mailboxes, each, on average, containing 4 GB of data, you are looking at transferring 4 TB onto a disk or tape drive that has mechanical moving parts."



To:

"If, for example, you are performing a full backup of 1,000 mailboxes, each, on average, containing 4 GB of data, you are looking at transferring more than 4 TB onto a disk or tape drive that has mechanical moving parts."

Note block not required On page 663, the Note block in the third sentence of the 2nd paragraph contians inaccurate information and is not required. Change: "You can filter this log for events with ntbackup as the source, as shown in Figure 12-9. (Note that “NTBackup” is the name of the utility, while Event Viewer specifies “ntbackup” as the source.)" To: "You can filter this log for events with ntbackup as the source, as shown in Figure 12-9."

Incorrect information
On page 667, the 3rd paragraph on the page contains several inacurracies regarding shadow copy backup.



Change:

"Exchange 2007 supports hardware-based snapshots using the VSS implemented in Microsoft Windows Server 2003. Typically, it takes much less time to restore a backup that was taken using a hardware-based snapshot than it does to restore from a streaming backup, making it easier to meet SLA time requirements that relate to the time that it takes to restore Exchange databases and thus helping you support larger database sizes."



To:

"Exchange 2007 supports VSS-based backups using the Volume Shadow Copy Service implemented in Microsoft Windows Server 2003. Typically, it takes much less time to restore a backup that was taken using a hardware-based clone than it does to restore from a streaming backup, making it easier to meet SLA time requirements that relate to the time that it takes to restore Exchange databases and thus helping you support larger database sizes."

Information regarding DPM 2007 missing
On page 668, the third sentence in the 2nd paragraph is missing DPM 2007.



Change:

"However, the Exchange-aware backup and restore utility (NTBackup) cannot implement VSS backups, and you need to use third-party software."



To:

"However, the Exchange-aware backup and restore utility (NTBackup) cannot implement VSS backups, and you need to use DPM 2007 or third-party software."

Additional information needed regarding SCSI devices On page 668, the second sentence in the "NOTE Logical unit number" box is out of date and needs additional information. Change: "SCSI is a parallel interface that allows up to 16 devices to be connected along a single cable." To: "Originally, SCSI was designed as a parallel interface that allows up to 16 devices to be connected along a single cable. Today, parallel SCSI is almost entirely replaced by more reliable serial attached SCSI (SAS) technology capable of handling several hundred devices per SAS controller."

"All" should be "VSS" On page 671, the third sentence in the "Local Continuous Replication and Cluster Continuous Replication" box incorrectly states that all backup types can be taken from the LCR copy locations. Change: "All backup types (full, copy, incremental, and differential) can be taken from the LCR copy locations." To: "VSS backup types (full, copy, incremental, and differential) can be taken from the LCR copy locations."

Additional information needed
On page 672, the second sentence of the 2nd paragraph needs clarification regarding which single point of falure is eliminated.



Change:

"CCR eliminates a single point of failure, has no special hardware requirements, and has no shared storage requirements."



To:

"CCR eliminates the Exchange information store as a single point of failure in the Mailbox server architecture, has no special hardware requirements, and has no shared storage requirements."

Clarification needed
On page 672, the second sentence in the 5th paragraph needs additional clarification.



Change:

"You can specify a longer backup window because the passive node has no real-time response constraints, thereby allowing for larger databases and larger mailbox sizes."



To:

"You can specify a longer backup window because the passive node does not need to maintain client connections, thereby allowing for larger databases and larger mailbox sizes."

Clarification needed On page 672, the first sentence of the 4th paragraph requires additional clarification. Change: "In addition to providing data and service availability, CCR provides for scheduled outages." To: "In addition to new high-availability architectures for Mailbox servers, CCR facilitates scheduled maintenance and helps to keep downtime at a minimum."

Incorrect information On page 672, the third sentence in the 6th paragraph contains incorrect information regarding backups. Change: "As a result, backups can be done on a weekly full cycle with a daily incremental backup strategy. This reduces the total volume of data that must be placed on the backup media." To: "As a result, streaming backups on the active node can be done on a weekly full cycle with a daily incremental backup strategy to keep the backup window small during work days. However, the recommended way to backup CCR-based Mailbox servers is to use a VSS-based solution on the passive node, such as DPM 2007. Backups on the passive node can be performed in much more frequent intervals, such as every 15 minutes an incremental backup and daily a full express backup as supported by DPM 2007."

CAS role missing from Practice setup
On page 673, the first sentence on the page is missing CAS roles.



Change:

"The Exchange Server 2007 Server on your test network has the Mailbox server and Hub Transport server roles installed."



To:

"The Exchange Server 2007 Server on your test network has the Mailbox, Hub Transport, and Client Access server roles installed."

Microsoft provides an Exchange-aware backup solution On page 677, the second sentence of the first bullet point incorrectly states that Microsoft does not provide an Exchange-aware backup solution. Change: "However, Microsoft does not provide an Exchange-aware backup solution, and you need third-party backup software to back up the Exchange database with VSS." To: "Furthermore, Microsoft provides an Exchange-aware backup solution in form of a separate product called DPM 2007 and you can also use third-party backup software to back up the Exchange database with VSS."

Incorrect information regarding Deleted Item Recovery
On page 680, in the Real World box, the second sentence of the 2nd paragraph contains inaccurate information regarding implementing the Deleted Item Recovery feature in Outlook 2003.



Change:

"The Deleted Item Recovery feature in Outlook 2007 (which can also be implemented in Outlook 2003 with a bit of registry hacking) reduces the number of restores required."To:

"The Deleted Item Recovery feature in Outlook 2007 (which is also available in Outlook 2003 and configurable through registry settings) reduces the number of restores required."

Inaccurate information regarding hard deletions
On page 681, the second sentence in the 3rd paragraph under "Recovering Messages" contains incorrect information regarding hard deleted items.



Change:

"If such a message is found, the message is hard deleted and removed from the Deleted Items folder."



To:

"If such a message is found, the message is hard deleted by removing the message reference from the MsgFolder table. At this point, the user can no longer recover the message in Outlook 2007 by using the Deleted Item Recovery feature."

Clarification needed regarding Recovering Messages On page 681, the second paragraph under "Recovering Messages" needs additional clarification regarding soft deletion. Change: "What happens if a message is soft deleted is that a flag is set on the entry for the message in the MsgFolder table to indicate that the message has been soft-deleted from its original folder. The MsgFolder table is a mapping between entries in the folder table and the messages table. Message counts for the mailbox and folder are also updated. If an item is in the Deleted Items folder, the user can easily recover it by opening that folder, right-clicking on the item, selecting Move To Folder, and moving the item back into the folder from which it was deleted." To: "What happens if a message is soft deleted is that a flag is set on the entry for the message in the MsgFolder table to hide the message from the messaging client. Soft-deleted items are not visible in Outlook folders. The MsgFolder table is a mapping between entries in the folder table and the messages table. Message counts for the mailbox and folder are also updated. As long as an item is not soft or hard deleted, the user can easily recover it by opening the Deleted Items folder, right-clicking on the item, selecting Move To Folder, and moving the item back into the folder from which it was deleted."

Multiple inaccuracies regarding Recovering Messages On page 681, the first paragraph under "Recovering Messages" contains multiple errors. Change: "Users can delete a message or other item in their own mailboxes by clicking on the item and pressing the Delete key. If a user deletes a message from the Inbox or Sent Items folder by this method, the message is stored in the Deleted Items folder. In addition, if a user accepts or declines a meeting request, the request moves from the Inbox to the Deleted Items folder. This type of deletion is known as a soft or logical deletion. Soft-deleted items are not removed from the mailbox but are instead moved to the Deleted Items folder in that mailbox." To: "Users can delete a message or other item in their own mailboxes by clicking on the item and pressing the Delete key. If a user deletes a message from the Inbox or any other server-based folder by this method, the message is actually not yet deleted but moved to the Deleted Items folder. In addition, if a user accepts or declines a meeting request, the request moves from the Inbox to the Deleted Items folder. Upon exiting, Outlook 2007 can automatically empty the Deleted Items folder according to the client configuration option "Empty the Deleted Items folder upon exiting." When Exchange Server 2007 receives the message deletion requests, it determines wether a soft or hard deletion must be performed based on criteria explained later in this section. Whenever possible, Exchange Server 2007 performs a soft deletion, also called a logical deletion to highlight the fact that the deleted items are not yet hard deleted, meaning they are not yet physically removed from the databases."

"Recovering Hard-Deleted Items" should be "Recovering Soft- and Hard-Deleted Items"
On page 682, the heading "Recovering Hard-Deleted Items" is partially incorrect as the section below it deals mostly with Soft-Deleted Items.



Change:

"Recovering Hard-Deleted Items"



To:

"Recovering Soft- and Hard-Deleted Items"

Clarification needed for recovering hard-deleted items
On page 682, the first paragraph under "Recovering Hard-Deleted Items" is unclear and confusing.



Change:

"If a user deletes a message using Shift+Delete or deletes an item in the Deleted Items folder, if a message is deleted by a system or gateway account (an account used to interface with another messaging system), if an item is deleted and the deleted item retention period is configured to be zero, or if the deleted item retention period has expired for an item in the Deleted Items folder, the item is hard deleted and is no longer in the user mailbox. This is known as a hard or physical delete."



To:

"The recoverability of a deleted message depends on the message reference in the MsgFolder table. If a user deletes a message directly from the Inbox or another mailbox folder by using Shift+Delete or deletes an item in the Deleted Items folder and no other criteria force Exchange Server 2007 to perform a hard deletion, then the message is soft-deleted and recoverable because the message reference still exists in the MsgFolder table. On the other hand, if the user forces a hard deletion by deleting the message in the Deleted Items Recovery dialog box again, or if a system or gateway account (an account used to interface with another messaging system) performs the hard deletion, or if the message reference is removed from the MsgFolder table because the deleted item retention period has expired for the item, then the item is physically removed from the database and no longer directly recoverable in Outlook 2007. Recovering hard-deleted items requires restores from backup by using the Recovery Storage Group or a separate recovery server."

Clarification needed On page 682, the first sentence of the 3rd paragraph requires additional clarification regarding which messages can be recovered. Change: "By default, in Outlook 2007 a user can recover a message (or other item) from the dumpster by using the Deleted Message Recovery feature." To: "By default, in Outlook 2007 a user can recover a soft-deleted message (or other item) from the dumpster by using the Deleted Message Recovery feature."

Incorrect information regarding hard-deleted items On page 682, the last sentence of the 2nd paragraph contains incorrect information about hard-deleted messages. Change: "Hard-deleted messages and other items are moved to the message dumpster." To: "During the next background cleanup process, the entries in the DeletedMessages table are examined and the corresponding entries in the messages table are deleted."

Background cleanup process runs independent of scheduled maintenance
On page 683, the first sentence of the 2nd paragraph incorrectly states that the background cleanup process is part of the scheduled maintenance.



Change:

"During scheduled maintenance, the background cleanup process runs once per hour by default."



To:

"Independent of scheduled maintenance, the background cleanup process runs once per hour by default."

Incorrect information On page 684, the third sentence of the 1st paragraph contains incorrect information about deleted items. Change: "If the deleted item retention period is set to 0, deleted items are removed from a mailbox immediately and are not stored in the Deleted Items folder." To: "If the deleted item retention period is set to 0, Exchange Server 2007 performs an immediate hard deletion for items as soon as they are removed from the Deleted Items folder or any other mailbox folder."

Incorrect information regarding dial tone recovery
On page 690, the first sentence of the 3rd paragraph contains incorrect information about dial tone recovery.



Change:

"Dial tone recovery is a procedure in which you delete an existing database or storage group and then restore it from backup."



To:

"Dial tone recovery is a procedure in which you delete the files of a corrupted database or storage group so that Exchange Server can reinitialize new and empty database files, and then you restore the data from backup by using a recovery storage group."

NewStorageGroup should be New-StorageGroup On page 692, the first sentence after Figure 12-27 refers to NewStorageGroup rather than New-StorageGroup. Change: "To create an RSG by using Exchange Management Shell, you use the NewStorageGroup cmdlet with the Recovery parameter." To: "To create an RSG by using Exchange Management Shell, you use the New-StorageGroup cmdlet with the Recovery parameter."

NewMailboxDatabase should be New-MailboxDatabase
On page 693, the second sentence after Figure 12-28 refers to NewMailboxDatabase rather than New-MailboxDatabase.



Change:

"To do this, you use a command based on the NewMailboxDatabase cmdlet with the MailboxDatabaseToRecover parameter."



To:

"To do this, you use a command based on the New-MailboxDatabase cmdlet with the MailboxDatabaseToRecover parameter."

"RSG file" should be "RSG" On page 694, the first sentence on the page incorrectly states that an RSG is a file when it is a storage group. Change: "Typically when you add a recovery database to an RSG file, restores are allowed by default." To: "Typically when you add a recovery database to an RSG, restores are allowed by default."

Clarification needed regarding dial tone recoveries
On page 695, the first paragraph on the page contains several inaccuracies.



Change:

"To perform a dial tone recovery on an Exchange 2007 mailbox server with a failed database, you should first move any uncorrupted files in the original database to a temporary location in case they are required for further recovery operations. You then mount an empty database that has the same name as the failed database on the Exchange 2007 server on which the database failed. You are warned that you are about to create an empty database."



To:

"To perform a dial tone recovery on an Exchange 2007 mailbox server with a failed database, you should first move all files from the original database and transaction log folders to a temporary location in case they are required for further recovery operations. You then mount the affected database so that Exchange Server 2007 can generate and intialize new database files. The newly intialized database is an empty database, but it has the same name as the original database and all configuration settings are retained. You are warned that you are about to create an empty database."

Clarification needed
On page 696, the 3rd paragraph requires additional clarification on restoring mailbox databases.



Change:

"You can now restore your original mailbox database from backup to the original mailbox server. Before you mount the recovery database to the RSG, copy any log files from the failed database to the RSG so that they can be played against the restored database. You can merge the databases and then use a command similar to the one you used previously to point users to their restored mailboxes on the original server, such as the following:"



To:

"You can now restore your original mailbox database from backup to the original mailbox server. Before you mount the recovered database in the original storage group, copy any log files from the failed database to the storage group so that they can be played against the restored database. Once the database is restored, you can use a command similar to the one you used previously to point users to their restored mailboxes on the original server, such as the following:"

Additional information required regarding merging databases On page 696, the 4th paragraph on the page requires additional information on merging databases. Change: "Merging the databases gives users access to messages that were placed in the dial tone database while it was in production. The merge process extracts messages from the dial tone database and places them in the recovered database. You can then remove the RSG." To: "The remaining task is to merge the databases in order to give the users access to messages that were placed in the dial tone database while it was in production. This requires you to create an RSG on the original server by using the Database Recovery Management tool and moving the dial-tone database from the second server into the RSG on the original server. After mounting the dial-tone database in the RSG on the original server, you can start the merge process to extract messages from the dial tone database and place them in the recovered database. You can then remove the RSGs on both servers."

Incorrect information regarding the Move-Mailbox cmdlet On page 696, the first sentence on the page incorrectly states that the Move-Mailbox cmdlet transfers database configuration information. Change: "You can use a command based on the Get-MailboxStatistics cmdlet to obtain configuration information for a specified mailbox database on the original server and pipe the output into a command based on the Move-Mailbox cmdlet with the ConfigurationOnly parameter to transfer database configuration information to the alternative server and thus point all the users to their new mailboxes on that server." To: "You can use a command based on the Get-MailboxStatistics cmdlet to obtain configuration information for a specified mailbox database on the original server and pipe the output into a command based on the Move-Mailbox cmdlet with the ConfigurationOnly parameter to to change the home server information in the user accounts in Active Directory and thus point all the users to their new mailboxes on that server."

Information missing regarding creating a dial tone database
On page 697, the third full sentence on the page is missing vital information regarding creating a dial tone database.



Change:

"You first need to select or create the storage group in which you will place the database in and then create the database, restore it from backup, and swap and merge the databases."



To:

"You first need to select or create the storage group in which you will place the dial-tone database in and then create the database, restore the original database in the RSG from backup, and swap and merge the databases."

Additional information required for clarification On page 698, the fourth sentence on the page is missing information on the type of backup. Change: "The database continues in use, and committed transaction logs are not truncated until the next backup." To: "The database continues in use, and committed transaction logs are not truncated until the next full or incremental backup."

Additional information regarding .stm files required
On page 702, the first sentence in the NOTE box contains incorrect information about how Eseutil handles .stm files.



Change:

"Eseutil does not support streaming (.stm) files in Exchange 2007 databases."



To:

"Exchange 2007 databases do not use streaming (.stm) files."

Additional information required to perform hard deletions On page 707, the first Step 4 on the page requires additional instructions on how to perform a hard delete. Change: "Hard delete (Shift+Delete) one or more messages." To: "Hard delete one or more messages by using the key combination Shift+Delete, confirming the deletion by clicking Yes in the Microsoft Outlook dialog box, and then selecting Recover Deleted Items on the Tools menu and deleting the messages in the Recover Deleted Items dialog box as well."

Clarification needed for recovering hard and soft-deleted items
On page 710, the first sentence in the first bullet point under Lesson Summary requires additional clarification.



Change:

"Users can recover soft-deleted items from the Deleted Items folder. In Outlook 2007, users can recover hard-deleted items from the message dumpster by using Deleted Item Recovery."



To:

"Users can usually recover deleted items from the Deleted Items folder. In Outlook 2007, users can also recover soft-deleted items from the message dumpster, such as after emptying the Deleted Items folder, by using Deleted Item Recovery feature."

Soft-deleted messages aren't in the Deleted Items folder On page 710, the second bullet point under Lesson Summary incorrectly states that soft-deleted messages are in the Deleted Items folder. Change: "You can configure the message retention and mailbox retention periods. These determine how long a soft-deleted item stays in the Deleted Items folder and how long a deleted mailbox stays in the mailbox dumpster." To: "You can configure the message retention and mailbox retention periods. These determine how long a soft-deleted item remains in the mailbox database and how long a deleted mailbox stays in the mailbox dumpster."

"any administrative rights" should be "any additional administrative rights"
On page 711, the first sentence of Question 1 requires clarification on administrative rights.



Change:

"You are an Exchange recipient administrator for Contoso, Ltd. You do not have any administrative rights on the contoso.com domain."



To:

"You are an Exchange recipient administrator for Contoso, Ltd. You do not have any additional administrative rights on the contoso.com domain."

"Keith" should be "Mark" On page 711, Answers C and D incorrectly use the name Keith instead of Mark which was used in the original question. Change: "C. Create a mailbox-enabled account for Keith Harrington. D. Restore Keith Harrington’s mailbox from backup." To: "C. Create a mailbox-enabled account for Mark Harrington. D. Restore Mark Harrington’s mailbox from backup."

Clarification requred
On page 723, the second sentence on the page requires additional information.



Change:

"Most organizations will not apply customizations to their Client Access server."



To:

"With the exception of SSL certificates, most organizations will not apply customizations to their Client Access server."

"Outbox" should be "Sent Items" On page 724, the third sentence of the 2nd paragraph uses an incorrect Mailbox folder. Change: "Generally, it is simpler to look in an Outbox for a copy of a sent message or to ask the sender to retransmit it." To: "Generally, it is simpler to look in the Sent Items folder for a copy of a sent message or to ask the sender to retransmit it."

Incorrect information about Edge Transport Servers
On page 725, the third sentence of the 1st paragraph contains incorrect information regarding Edge Transport servers and replication.



Change:

"Edge Transport servers are not joined to the domain but replicate Active Directory information using the EdgeSync process and store it within Active Directory Application Mode (ADAM), a local directory service."



To:

"Edge Transport servers are not joined to the domain. Hub Transport servers replicate the relevant Active Directory information to the Edge Transport servers by using the Microsoft Exchange EdgeSync service. On Edge Transport servers the information is stored within Active Directory Application Mode (ADAM), a local directory service."

"more complicated" should be "different"
On page 727, the last sentence on the page contains information that requires clarification.



Change:

"Recovering a clustered mailbox server is a more complicated process than recovering a mailbox server that does not use cluster continuous replication or a single copy cluster configuration."



To:

"Recovering a clustered mailbox server is a different process than recovering a mailbox server that does not use cluster continuous replication or a single copy cluster configuration."

Command incomplete On page 727, the second sentence of Step 3 contains an invalid command. Change: "Remember that you cannot use the /RecoverServer option with this specific Exchange Server 2007 role." To: "Remember that you cannot use the /m:RecoverServer option with this specific Exchange Server 2007 role."

Additional information needed regarding restoring mailbox servers On page 728, the third sentence of the 2nd paragraph requires additional clarification. Change: "If you are restoring a mailbox server that uses single copy cluster, the storage groups and mailbox databases will already be present on the shared storage device." To: "If you are restoring a mailbox server that uses single copy cluster, the storage groups and mailbox databases will already be present on the shared storage device. However, if the mailbox server failed because of an issue related to the shared storage hardware or firmware, you will now have to restore the data from backup, which is not necessary in case of a single storage failure in a CCR configuration."

Remove "stand-alone"
On page 731, the first sentence in Question 5 incorrectly states that Hub-Transport servers can be stand-alone servers.



Change:

"The hard disk drives on a stand-alone server assigned the Hub Transport server role fail completely."



To:

"The hard disk drives on a server assigned the Hub Transport server role fail completely."

"/m:Recover" should be "/m:RecoverServer" On page 731, the first sentence of Question 4 contains an invalid command. Change: "4. You are preparing to run setup with the /m:Recover option to recover a Client Access server that was destroyed in a server room fire." To: "4. You are preparing to run setup with the /m:RecoverServer option to recover a Client Access server that was destroyed in a server room fire."

Public folders will not replicate automatically
On page 732, the third sentence in the 3rd paragraph contains incorrect information regarding automatic replication of public folders.



Change:

"LCR also cannot be used with public folder databases, though this is less of a problem as public folders will replicate automatically to any other public folder database in the organization and the feature is deprecated in Exchange Server 2007."



To:

"LCR also cannot be used with public folder databases, though this is less of a problem as public folders can be replicated to any other public folder database in the organization and the feature is deprecated in Exchange Server 2007."

"completed" should be "removed" On page 733, the second sentence of the Disable-StorageGroupCopy description is incorrect. Change: "Once the command completes, the storage group and database copy configuration are completed." To: "Once the command completes, the storage group and database copy configuration are removed." 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.