CD-ROM: 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.
CD-ROM: 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"
Page 3: 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."
Page 22: "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."
Page 23: 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."
Page 30: 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."
Page 132: 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
Page 137: -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."
Page 155: "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."
Page 155: "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."
Page 157: 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."
Page 160: "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."
Page 168: 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."
Page 169: "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 Group\Mailbox 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 Group\Mailbox Database" -Name Projector OrganizationalUnit
Users -DisplayName Projector -ResetPasswordOnNextLogon $false –Equipment creates an equipment mailbox called Projector."
Page 177: "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."
Page 179: "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."
Page 222: "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."
Page 230: 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."
Page 237: 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 Group\Mailbox Database"
To:
Move-Mailbox "Don Hall" -ConfigurationOnly -TargetDatabase "First Storage Group\Mailbox Database" –Server Edinburgh
Page 237: "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."
Page 238: 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."
Page 241: 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."
Page 244: 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."
Page 246: "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."
Page 248: Two Policy Parameters contain incorrect hyphens
On page 248, in Table 5-3 three of the Policy Parameters contain an incorrect hyphen.
Change:
"EmailAddressPolicy-Enabled
HiddenFromAddressLists-Enabled
DeliverToMailboxAnd-Forward"
To:
"EmailAddressPolicyEnabled
HiddenFromAddressListsEnabled
DeliverToMailboxAndForward"
Page 256: 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."
Page 258: 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."
Page 262: 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 Group\Mailbox 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 Group\First Glasgow Mailbox Database" -SourceMailboxCleanupOptions DeleteSourceMailbox -IgnorePolicyMatchTo:
"If you want to move these users from the default mailbox database (First Storage Group\Mailbox 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 Group\First Glasgow Mailbox Database"Page 268: 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."
Pages 268 & 269: 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 Files\Microsoft\Exchange Server\Scripts or C:\Program Files\ Microsoft\Exchange Server\excripts)."
To:
"Exchange Server 2007 provides a set of preconfigured PowerShell scripts that are stored in the C:\Program Files\Microsoft\Exchange Server\Scripts subdirectory."
Page 269: "PSHome" should be "C:\Program Files\Microsoft\Exchange Server\Scripts"
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 Files\Microsoft\Exchange Server\Scripts subdirectory can be run directly from Exchange Management Shell without specifying a path."
Page 269: 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:\WINDOWS\system32\WindowsPowerShell\v1.0). While it is possible to point the PowerShell variable $PSHome to the location of the C:\Program Files\Microsoft\Exchange Server\Scripts subfolder, this is seldom necessary because the C:\Program Files\Microsoft\Exchange Server\Scripts subfolder is included in the system search path. To display the search path, use the $env:path command."
Page 269: "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."
Page 270: "PSHome" should be "C:\Program Files\Microsoft\Exchange Server\Scripts"
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 Files\Microsoft\Exchange Server\Scripts) as MoveDon.ps1."
To:
"Save the file in the C:\Program Files\Microsoft\Exchange Server\Scripts subdirectory as MoveDon.ps1."
Page 271: "PSHome" should be "C:\Program Files\Microsoft\Exchange Server\Scripts"
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 Files\Microsoft\Exchange Server\Scripts subdirectory as MoveAnyone.ps1."
Page 278: 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 Files\Microsoft\Exchange Server\exscripts subdirectories.
Change:
"Save the file in the PSHome subdirectory (C:\Program Files\Microsoft\Exchange Server\Scripts or C:\Program Files\Microsoft\Exchange Server\exscripts) as CreateNewUser.ps1, as shown in Figure 5-33."
To:
"Save the file in the C:\Program Files\Microsoft\Exchange Server\Scripts subdirectory as CreateNewUser.ps1, as shown in Figure 5-33."
Page 280: "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 Files\Microsoft\Exchange Server\Scripts. If your PSHome subdirectory is not at C:\Program Files\Microsoft\Exchange Server\exscripts, amend the practice accordingly."
To:
"This practice assumes that the $ExScripts variable points to the subdirectory C:\Program Files\Microsoft\Exchange Server\Scripts. If the $ExScripts variable does not points to the subdirectory C:\Program Files\Microsoft\Exchange Server\Scripts, amend the practice accordingly."
Page 284: "$Identity" should be "$Mailbox"
On page 284, answers B and D contain incorrect parameters.
Change:
B. Move-Mailbox -Identity $Identity –TargetDatabase "First Storage Group\First Glasgow Mailbox Database" -SourceMailboxCleanupOptions DeleteSourceMailbox
Param(
[string] $Identity
)
D. Param(
[string] $Identity
)
Move-Mailbox -Identity $Identity –TargetDatabase "First Storage Group\First Glasgow Mailbox Database"
To:
B. Move-Mailbox -Identity $Identity –TargetDatabase "First Storage Group\First Glasgow Mailbox Database"
Param(
[string] $Identity
)
D. Param(
[string] $Mailbox
)
Move-Mailbox -Identity $Identity –TargetDatabase "First Storage Group\First Glasgow Mailbox Database"
Page 287: 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."
Page 287: 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."
Page 288: 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."
Page 288: "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 Files\Microsoft\Exchange Server\Scripts."
To:
"The $ExScripts variable that points to C:\Program Files\Microsoft\Exchange Server\Scripts."
Page 289: "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."
Page 294: 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."
Page 294: 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"
Page 295: 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."
Page 295: 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."
Page 298: 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."
Page 299: 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."
Page 305: 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."
Page 306: 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."
Page 310: 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."
Page 320: 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."
Page 357: "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."
Page 357: "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"
Page 358: 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."
Page 360: 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 Configuration\Mailbox 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 Configuration\Mailbox 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."
Page 362: 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 Configuration\Mailbox 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 Configuration\Mailbox 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."
Page 366: 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."
Page 367: 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"
Page 368: "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."
Page 369: 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."
Page 381: "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."
Page 387: "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"
Page 387: 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"
Page 388: "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"
Page 390: "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)."
Page 392: "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."
Page 397: "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."
Page 402: "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"
Page 407: "%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?"
Page 410: "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"
Page 412: 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."
Page 415: 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."
Page 418: "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."
Page 419: "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."
Page 431: 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."
Page 435: 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:"
Page 435: 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."
Page 435: 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."
Page 435: 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."
Page 436: 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"
Page 473: 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."
Page 473: 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."
Page 476: 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 Files\Microsoft\Exchange Server\Scripts):"
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 Files\Microsoft\Exchange Server\Scripts):"
Page 478: 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."
Page 478: 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."
Page 480: "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."
Page 486: 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."
Page 499: 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.