MCTS Self-Paced Training Kit (Exam 70-236): Configuring Microsoft® Exchange Server 2007 comments and corrections part 2

This article contains comments, corrections, and information about known errors relating to the Microsoft Press book MCTS Self-Paced Training Kit (Exam 70-236): Configuring Microsoft® Exchange Server 2007, 978-0-7356-2410-8.Part 1 is available here (http://support.microsoft.com/kb/947010) .

The following topics are covered:

• Page 511: arbitrary should be unique
• Page 511: Incorrect description of agent
• Page 512: Additional information needed
• Page 512: Incorrect information regarding forked messages
• Page 514: Additional information needed for Figure 10-2
• Page 521: Incorrect information
• Page 521: Incorrect terminology
• Page 524: circular logging should be Exchange Server 2007
• Page 525: circular logging should be Exchange Server 2007
• Page 525: 5 MB should be 20 MB
• Page 526: Clarification needed
• Page 526: More specificity needed
• Page 527: circular logging should be Exchange Server 2007
• Page 527: More specificity needed
• Page 528: More specificity needed
• Page 539: circular logging should be Exchange Server 2007
• Page 542: Incorrect information given
• Page 554: MSExchange should be MSExchangeIS
• Page 556: Reference to Transport Layer Security should be removed
• Page 560: Reference to circular logging should be removed
• Page 562: circular logging should be Exchange Server 2007
• Page 563: Circular logging should be Exchange Server 2007
• Page 566: Incorrect information
• Page 567: Clarification needed
• Page 568: Clarification needed
• Page 616: Incorrect information regarding the SEND EventID
• Page 623: Reports are not written to a database file
• Page 624: Clarification needed for Forefront Server Security Administrator instructions
• Page 626: Clarification needed regarding Edge transport servers
• Page 630: Clarification needed regarding mailbox settings relevant for client access
• Page 631: Information regarding command that obtains client settings is incorrect
• Page 643: Additional information required
• Page 644: Corrections needed in Real World example
• Page 648: Microsoft provides an Exchange-aware VSS based backup solution
• Page 649: Inaccurate information regarding full backups
• Page 649: Link provided for circular logging is English only
• Page 649: Multiple inaccuracies regarding differential and incremental backups
• Page 650: "replicated database" should be "shadow copy"
• Page 650: Incorrect information regarding performing restores
• Page 651: Link for SLA additional information broken
• Page 651: Additional information regarding .edb file size
• Page 652: Clarification needed
• Page 654: OWA is not relevant to OAB
• Page 654: Multiple inaccuracies regarding OAB
• Page 656: Information incorrect on how OAB is generated
• Page 656: OWA is not relevant to OAB
• Page 657: Clarification needed
• Page 663: Size of backup incorrect
• Page 663: Note block not required
• Page 667: Incorrect information
• Page 668: Additional information needed regarding SCSI devices
• Page 668: Information regarding DPM 2007 missing
• Page 671: "All" should be "VSS"
• Page 672: Additional information needed
• Page 672: Clarification needed
• Page 672: Clarification needed
• Page 672: Incorrect information
• Page 673: CAS role missing from Practice setup
• Page 677: Microsoft provides an Exchange-aware backup solution
• Page 680: Incorrect information regarding Deleted Item Recovery
• Page 681: Clarification needed regarding Recovering Messages
• Page 681: Inaccurate information regarding hard deletions
• Page 681: Multiple inaccuracies regarding Recovering Messages
• Page 682: "Recovering Hard-Deleted Items" should be "Recovering Soft- and Hard-Deleted Items"
• Page 682: Clarification needed
• Page 682: Clarification needed for recovering hard-deleted items
• Page 682: Incorrect information regarding hard-deleted items
• Page 683: Background cleanup process runs independent of scheduled maintenance
• Page 684: Incorrect information
• Page 690: Incorrect information regarding dial tone recovery
• Page 692: NewStorageGroup should be New-StorageGroup
• Page 693: NewMailboxDatabase should be New-MailboxDatabase
• Page 694: "RSG file" should be "RSG"
• Page 695: Clarification needed regarding dial tone recoveries
• Page 696: Additional information required regarding merging databases
• Page 696: Clarification needed
• Page 696: Incorrect information regarding the Move-Mailbox cmdlet
• Page 697: Information missing regarding creating a dial tone database
• Page 698: Additional information required for clarification
• Page 702: Additional information regarding .stm files required
• Page 707: Additional information required to perform hard deletions
• Page 710: Clarification needed for recovering hard and soft-deleted items
• Page 710: Soft-deleted messages aren't in the Deleted Items folder
• Page 711: "any administrative rights" should be "any additional administrative rights"
• Page 711: "Keith" should be "Mark"
• Page 723: Clarification requred
• Page 724: "Outbox" should be "Sent Items"
• Page 725: Incorrect information about Edge Transport Servers
• Page 727: Command incomplete
• Page 727: "more complicated" should be "different"
• Page 728: Additional information needed regarding restoring mailbox servers
• Page 731: Remove "stand-alone"
• Page 731: "/m:Recover" should be "/m:RecoverServer"
• Page 732: Public folders will not replicate automatically
• Page 733: "completed" should be "removed"

Page 511: 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."

Page 511: 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."

Page 512: 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."

Page 512: 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."

Page 514: 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."

Page 521: 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. "

Page 521: 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."

Page 524: 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."

Page 525: 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."

Page 525: 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"

Page 526: 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."

Page 526: 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:"

Page 527: 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."

Page 527: 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:"

Page 528: 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:"

Page 539: 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."

Page 542: 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."

Page 554: 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."

Page 556: 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."

Page 560: 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."

Page 562: 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."

Page 563: 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."

Page 566: 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."

Page 567: 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."

Page 568: 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."

Page 616: 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."

Page 623: 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."

Page 624: 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."

Page 626: 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."

Page 630: 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."

Page 631: 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"

Page 643: 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."

Page 644: 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."

Page 648: 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."

Page 649: 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."

Page 649: 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. "

Page 649: 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."

Page 650: "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."

Page 650: 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."

Page 651: 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."

Page 651: 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."

Page 652: 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."

Page 654: 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."

Page 654: 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 Files\Microsoft\Exchange Server\ExchangeOAB. 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 Files\Microsoft\Exchange Server\ExchangeOAB. 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."

Page 656: 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."

Page 656: 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)"

Page 657: 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."

Page 663: 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."

Page 663: 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."

Page 667: 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."

Page 668: 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."

Page 668: 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."

Page 671: "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."

Page 672: 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."

Page 672: 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."

Page 672: 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."

Page 672: 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."

Page 673: 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."

Page 677: 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."

Page 680: 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."

Page 681: 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."

Page 681: 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."

Page 681: 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."

Page 682: "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"

Page 682: 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."

Page 682: 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."

Page 682: 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."

Page 683: 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."

Page 684: 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."

Page 690: 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."

Page 692: 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."

Page 693: 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."

Page 694: "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."

Page 695: 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."

Page 696: 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."

Page 696: 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:"

Page 696: 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."

Page 697: 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."

Page 698: 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."

Page 702: 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."

Page 707: 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."

Page 710: 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."

Page 710: 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."

Page 711: "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."

Page 711: "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."

Page 723: 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."

Page 724: "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."

Page 725: 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."

Page 727: 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."

Page 727: "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."

Page 728: 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."

Page 731: 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."

Page 731: "/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."

Page 732: 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."

Page 733: "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.