Errata
Errata for MCTS Self-Paced Training Kit (Exam 70-640): Configuring Windows Server® 2008 Active Directory®
The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted By | Date submitted | Date corrected |
---|---|---|---|---|---|
Printed | Page 649 Incorrect guidance for restoring a DC from a snapshot |
Microsoft Press | Jul 13, 2010 | ||
Printed | Page 28 |
Steps 4 and 7 contain incorrect command switches |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 28 |
dns should be dnsserver On page 28, the command given in step 2 of exercise 2 is incorrect. Change: "netsh interface ipv4 set dns name="Local Area Connection"" To: "netsh interface ipv4 set dnsserver name="Local Area Connection"" |
Microsoft Press | May 06, 2010 | |
Printed | Page 29 |
Command incorrect On page 29, in Step 3 of Exercise 3 the command to add and configure the AD DS role is partially incorrect. Change: "dcpromo /unattend /replicaOrNewDomain:replica /replicaDomainDNSName:contoso.com /ConfirmGC:Yes /UserName:CONTOSOAdminsitrator /Password:* /safeModeAdminPassword:P@ssword" To: "dcpromo /unattend /replicaornewdomain:replica /replicaDomainDNSName:contoso.com /ConfirmGC:Yes /UserName:Administrator /userDomain:Contoso /Password:* /safeModeAdminPassword:P@ssword" |
Microsoft Press | May 06, 2010 | |
Printed | Page 90 |
Command line incorrect |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 92 |
Incorrect information regarding LDIFDE On page 92, the 4th line down in the Exam Tip box includes incorrect information about importing passwords. Change: "Neither command enables you to import a user’s password." To: "LDIFDE is the only command that enables you to import a user's password." |
Microsoft Press | May 06, 2010 | |
Printed | Page 94 |
"%username%" should be "$username$" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 94 |
Command line incorrect On page 94, the first line of the command under Step 1 is incorrectly formatted. Change: "DN,objectClass,sAMAccountName,sn,givenName,userPrincipalName" To: "DN,objectClass,sAMAccountName,givenName,sn,userPrincipalName" |
Microsoft Press | May 06, 2010 | |
Printed | Page 95 |
Three should be two |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 112 |
Command incorrect On page 112, the command under Step 7 is misspelled and will not function. Change: "set-exceutionpolicy remotesigned" To: "set-executionpolicy remotesigned" |
Microsoft Press | May 06, 2010 | |
Printed | Page 121 |
"user" missing from command |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 122 |
DSMOD should be DSQUERY |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 122 |
"%username%" should be "$username$" On page 122, the second full command and fourth full paragraph down contain an incorrect token. Change: "dsquery user "ou=People,dc=contoso,dc=com" | dsmod user -hmdir "\server01users%username%documents" –hmdrv "U:" As mentioned in Lesson 1, the special %username% token can be used to represent the sAMAccountName of user objects when using DS commands to configure the value of the -email, -hmdir, -profile, and -webpg parameters." To: "dsquery user "ou=People,dc=contoso,dc=com" | dsmod user -hmdir "\server01users$username$documents" –hmdrv "U:" As mentioned in Lesson 1, the special $username$ token can be used to represent the sAMAccountName of user objects when using DS commands to configure the value of the -email, -hmdir, -profile, and -webpg parameters." |
Microsoft Press | May 06, 2010 | |
Printed | Page 122 |
dsget example is incorrect and needs to be replaced On page 122, the dsget example at the bottom of the page is not correct and needs to be replaced. Change: "To display the pre-Windows 2000 logon names of all users in the Sydney office, use this command: dsquery user –office "Sydney" | dsget user –samid" To: "To display the pre-Windows 2000 logon names of all users whose description is "Accountant," use this command: dsquery user -desc "Accountant" | dsget user -samid" |
Microsoft Press | May 06, 2010 | |
Printed | Page 123 |
Parenthesis missing from VBScript example |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 124 |
"office" should be "physicalDeliveryOfficeName" On page 124, the last 2 VB script examples on the page are incorrect. Change: $objUser.PutEx(1, "office", 0) $objUser.SetInfo() To:$objUser.PutEx (1, "physicalDeliveryOfficeName", 0) $objUser.SetInfo()Change: objUser.PutEx 1, "office", 0 objUser.SetInfo()To: objUser.PutEx 1, "physicalDeliveryOfficeName", 0 objUser.SetInfo() |
Microsoft Press | May 06, 2010 | |
Printed | Page 127 |
Unnecessary space in script |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 127 |
Code example is missing a line of code to function correctly On page 127, the VBScript code example near the bottom of the page is missing a line of code. Change: Set objUser = GetObject("LDAP://UserDN") objUser.AccountDisabled=TRUETo: Set objUser = GetObject("LDAP://UserDN") objUser.AccountDisabled=TRUE objUser.SetInfo() |
Microsoft Press | May 06, 2010 | |
Printed | Page 133 |
Incorrect information regarding deleting and creating user accounts |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 137 |
"Chapter" should be "Lesson" On page 137, the first bullet point on the page references an incorrect location. Change: "In Chapter 2, you examined a script that can use a .csv file to create users. Modify the script to import users from your .csv file. Construct attributes such as userPrincipalName and displayName in the script, as the sample in Chapter 2 illustrated." To: "In Lesson 2, you examined a script that can use a .csv file to create users. Modify the script to import users from your .csv file. Construct attributes such as userPrincipalName and displayName in the script, as the sample in Lesson 2 illustrated." |
Microsoft Press | May 06, 2010 | |
Printed | Page 152 |
"Options" should be "Object Types" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 155 |
Sales group already exists On page 155, Exercise 1 requires that you create a group called Sales and add users to it. A group called Sales was previously created in Chapter 2 and needs to be removed in order to successfully complete this exercise. Add the following Note before the first step in Exercise 1. NOTE: If you have performed the exercises in Chapters 2 and 3 the group Sales may have already been created and the user Jeff Ford may already be added to it. To perform this exercise correctly you will need to delete the Sales group prior to performing any of the steps. |
Microsoft Press | May 06, 2010 | |
Printed | Page 156 |
"Distribution" should be "Security" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 165 |
Command in Step 4 is incomplete On page 165, the command used in Step 4 is incomplete and will not work. Change: csvde –i –f "%userprofile%importgroups.csv"To: csvde –i –f "%userprofile%documentsimportgroups.csv" |
Microsoft Press | May 06, 2010 | |
Printed | Page 174 |
"OU" should be "name" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 184 |
Group scopes incorrect On page 184, the first bullet under Chapter Summary contains incorrect Group scope names. Change: "Group scopes (global, universal, domain local, and universal) define group characteristics related to membership, replication, and availability of the group." To: "Group scopes (global, domain local, local, and universal) define group characteristics related to membership, replication, and availability of the group." |
Microsoft Press | May 06, 2010 | |
Printed | Page 198 |
Figure 5-4 is incorrect |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 198 |
Reference to Dsacls.exe should be removed On page 198, the last sentence contains an incorrect reference to Dsacls.exe. Change: "You will delegate permission to create computer objects, using the Dsacls.exe command, and you will redirect the default computer container." To: "You will delegate permission to create computer objects and you will redirect the default computer container." |
Microsoft Press | May 06, 2010 | |
Printed | Page 209 |
"Create and Manage a Custom MMC" should be "Automate Importing and Creating Computer Objects" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 214 |
"value" misplaced in code sample On page 214, the last two lines of the last code sample are incorrect. Change: objComputer.Put "property", value objComputer.SetInfoTo: objComputer.Put "property", value objComputer.SetInfo |
Microsoft Press | May 06, 2010 | |
Printed | Page 215 |
TargetOUDN should be ComputerDN and vice versa |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 239 |
"GPME" should be "GPMC" On page 239, the second sentence of the second paragraph under "Creating, Linking, and Editing GPOs" contains an incorrect acronym. Change: "To delegate permission to other groups, select the Group Policy Objects container in the GPME console tree and then click the Delegation tab in the console details pane." To: "To delegate permission to other groups, select the Group Policy Objects container in the GPMC console tree and then click the Delegation tab in the console details pane." |
Microsoft Press | May 06, 2010 | |
Printed | Page 261 |
"No Override" should be "Enforced" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 265 |
"class" should be "namespace" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 265 |
GPME should be GPMC On page 265, the first sentence of the fourth paragraph refers to GPME rather than GPMC. Change: "To create a WMI filter, right-click the WMI Filters node in the GPME and choose New." To: "To create a WMI filter, right-click the WMI Filters node in the GPMC and choose New." |
Microsoft Press | May 06, 2010 | |
Printed | Page 266 |
Incorrect result description of a setting On page 266, the first sentences in the 3rd and 4th bullet points under the heading "Enabling or Disabling GPOs and GPO Nodes" are incorrect. Change: "Computer Configuration Settings Disabled During computer policy refresh, computer configuration settings in the GPO will be applied." To: "Computer Configuration Settings Disabled During computer policy refresh, computer configuration settings in the GPO will not be applied." Change: "User Configuration Settings Disabled During user policy refresh, user configuration settings in the GPO will be applied." To: "User Configuration Settings Disabled During user policy refresh, user configuration settings in the GPO will not be applied." |
Microsoft Press | May 06, 2010 | |
Printed | Page 273 |
computer should be user |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 275 |
Additional steps needed On page 275, two steps are needed before step 21. The steps to add are: "20a. Click the Add button in the Security Filtering section 20b. Type the group name, Domain Users, and click OK." |
Microsoft Press | May 06, 2010 | |
Printed | Page 280 |
"Gpupdate.exe" should be "Ggpresult.exe" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 294 |
"Computer Configuration"" should be "Computer ConfigurationPolicies"" On page 294, step 1 at the bottom of the page contains an incorrect path. Change: "In Group Policy Management Editor, navigate to Computer ConfigurationWindows SettingsSecurity SettingsRestricted Groups." To: "In Group Policy Management Editor, navigate to Computer ConfigurationPoliciesWindows SettingsSecurity SettingsRestricted Groups." |
Microsoft Press | May 06, 2010 | |
Printed | Page 346 |
5136 should be 4662 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 364 |
"Security Settings" should be "Windows SettingsSecurity Settings" On page 364, step 6 of Exercise 1 is incorrect. Change: "Expand Computer ConfigurationPoliciesSecurity SettingsAccount Policies, and then select Password Policy." To: "Expand Computer ConfigurationPoliciesWindows SettingsSecurity SettingsAccount Policies, and then select Password Policy." |
Microsoft Press | May 06, 2010 | |
Printed | Page 365 |
"DomainAdmins" should be "Domain Admins" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 383 |
"Ddsmgmt.exe" should be "dsmgmt.exe" On page 383, the first sentence in the second paragraph includes an incorrectly spelled command. Change: "You can configure administrative role separation by using the Ddsmgmt.exe command." To: "You can configure administrative role separation by using the dsmgmt.exe command." |
Microsoft Press | May 06, 2010 | |
Printed | Page 400 |
Figure 9-3 uses an incorrect header |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 416 |
Question 5 in Quick Check needs to be removed On page 416, question 5 in the Quick Check at the bottom of the page hasn't been covered up until this point in the book. It should be removed. |
Microsoft Press | May 06, 2010 | |
Printed | Page 470 |
"performed by" missing |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 471 |
"attache" should be "attach" On page 471, the second to the last dcpromo command on the page is partially incorrect. Change: dcpromo /useexistingaccount:attache /unattend:"c: odcanswer.txt"To: dcpromo /useexistingaccount:attach /unattend:"c: odcanswer.txt" |
Microsoft Press | May 06, 2010 | |
Printed | Page 517 Paragraph 2 |
Wrong RFC specified Note from the Author or Editor: |
Brian Habel | Jun 12, 2011 | |
Printed | Page 518 |
"TCP" should be "UDP" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 522 |
"object" and "attribute" need to be reversed On page 522, the first sentence in the last paragraph is partially incorrect. Change: "Traditionally, replicas have been complete replicas, containing every object of an attribute, and replicas have been writable on all DCs." To: "Traditionally, replicas have been complete replicas, containing every attribute of an object, and replicas have been writable on all DCs." |
Microsoft Press | May 06, 2010 | |
Printed | Page 566 |
"forest" should be "domain" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 620 |
"Dsbutil.exe" should be "DSDButil.exe" On page 620, the 8th tool down in Table 13-2 is spelled incorrectly. Change: "Dsbutil.exe (installed with AD LDS and AD DS)" To: "DSDButil.exe (installed with AD LDS and AD DS)" |
Microsoft Press | May 06, 2010 | |
Printed | Page 621 |
Description of Repadmin.exe tool incorrect |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 624 |
Incorrect information regarding AD DS features On page 624, the last sentence of the last paragraph on the page incorrectly states that AD DS has four features that enable you to recover information without resorting to backups. The last bullet also needs to be removed. Change: "However, AD DS includes four features that enable you to recover information without resorting to backups:" To: "However, AD DS includes three features that enable you to recover information without resorting to backups:" Remove the following bullet point: "The backup and restore feature supported by Windows Server Backup." |
Microsoft Press | May 06, 2010 | |
Printed | Page 656 |
NTDS should be originalntds |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 656 |
Backslash needs to be removed before command
On page 656, the 5th command down under step 5 incorrectly places a backslash before the command.
Change:
cd windows |
Microsoft Press | May 06, 2010 | |
Printed | Page 672 |
resources should be utilization On page 672, the last sentence of the second paragraph of the "Working with Windows System Resource Manager" section refers to processor resources rather than processor utilization. Change: "This means that when processor resources are low, WSRM does not affect any application." To: "This means that when processor utilization is low, WSRM does not affect any application." |
Microsoft Press | May 06, 2010 | |
Printed | Page 797 |
private should be public |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 853 |
433 should be 443 On page 853, the last sentence of the second bullet point refers to the incorrect port. Change: "Because of this, all communications occur through port 433 over HTTPS." To: "Because of this, all communications occur through port 443 over HTTPS." |
Microsoft Press | May 06, 2010 | |
Printed | Page 859 |
"Token Signing Certificate" should be "Server Authentication" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 862 |
Minimize should be removed On page 862, the first sentence of step 5 of the first procedure is incorrect. Change: "Paste the certificate into the Minimize Windows Explorer folder." To: "Paste the certificate into the Windows Explorer folder." |
Microsoft Press | May 06, 2010 | |
Printed | Page 863 |
Claimapp should be claimapplication01 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 882 |
Answer marked as correct is incorrect |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 882 |
Answers marked as correct are incorrect |
Microsoft Press | May 06, 2010 | |
Printed | Page 884 |
Answer A should be correct |
Microsoft Press | May 06, 2010 | |
Printed | Page 888 |
On page 888, the answer to question 2 is incorrect |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 909 |
"forest" should be "domain" |
Microsoft Press | May 06, 2010 | |
Printed | Page 910 |
Answer C should be incorrect |
Microsoft Press | Jul 13, 2010 |