Errata for Self-Paced Training Kit (Exam 70-646): Windows Server® 2008 Server Administrator

"Autounattended.xml" should read "Autounattend.xml"

Note from the Author or Editor:
Change autounattended.xml to autounattend.xml

"You can use the Network Settings tab" should read "You can use the Multicast tab"

Note from the Author or Editor:
Change: You can use the Network Settings tab, shown in Figure 1-8, to You can use the Multicast Settings tab, shown in Figure 1-8,

MORE INFO VOLUME ACTIVATION MANAGEMENT TOOL The URL supplied links to a Technet article on MANAGING IMAGES http://technet.microsoft.com/en-us/library/cc770460.aspx This URL should be for an article on VAMT

Note from the Author or Editor:
Please change the URL to http://technet.microsoft.com/en-us/library/ff686876.aspx

The sentence "In addition, note that the site-local address still exists, but it is displayed as deprecated, as discussed earlier in this session" is incorrect. The addresses in Fig 2-5, to which this refers, are link-local addresses not site-local. Also, deprecated, in this instance, is in reference to the DAD state, i.e. Tentative, Preferred, Deprecated and Invalid, rather than the status of the site-local address type.

Note from the Author or Editor:
On reflection the sentence "In addition, note that the site-local address still exists, but it is displayed as deprecated, as discussed earlier in this session" at the end of page 55 isn't needed and might be confusing. Please delete this sentence.

"FIGURE 2-6 Displaying IPv6 addresses and site IDs" Screen shot shows "Scope ID" but I cannot see anywhere in the chapter that explains that Site ID is the same as Scope ID when using the netsh command.

Note from the Author or Editor:
In paragraph after Figure 2.5 on page 56, the first sentence should read "If you are administering an enterprise network with a number of sites you also need to know the site IDs (or scope IDs)."

Step 7 of Exercise gives the following command: add address "isatap" fec0:0:0:fffe:0:5efe:10.10.0.50 However, if you have set up VAN-DC1 according to the instructions in the Appendix, its IPv4 address is 10.10.0.10, so the command should be: add address "isatap" fec0:0:0:fffe:0:5efe:10.10.0.10

Note from the Author or Editor:
Change both instances of 10.10.0.50 to 10.10.0.10 on page 99

On page 164 in the last paragraph it refers to "sever Group Policy settings that enhance the management of OCSP and CRL data use. ... This is shown in Figure 3-18." Figure 3-18 on page 165 shows a screenshot of a Revocation Configuration Name and it's status. Isn't it supposed to show the Certificate Path Validations Settings group policy setting?

Note from the Author or Editor:
Page 164. Delete "This is shown in Figure 3-18" Page 165. Delete Figure 3-18 Page 166. Renumber Figure 3-19 to Figure 3-18 (callout and caption) Page 167. Renumber Figure 3-20 to Figure 3-19 (callout and caption)

The wrong command is referenced in the section on "Active Directory Domain Service Database Mounting Tool" at the top of page 623. The text identifies the data mining tool as dsadmin.exe in the first and second paragraphs. Should it not be dsamain.exe?

Note from the Author or Editor:
Change 3 instances of dsadmin.exe on page 623 to dsamain.exe

Appendix A Exercise 4 Step 3 has the instructions to set the static IP address of 10.10.0.21 to a server computer named VAN-SRV2 Appendix A Exercise 5 Step 3 has the instructions to set the static IP address of 10.10.0.21 to a client computer named VAN-CL1 The same static IP address is used twice. I foresee this causing DNS issues.

Note from the Author or Editor:
Alter Exercise 5 step 3 to Netsh interface ipv4 set address "Local Area Connection" static 10.10.0.31

Appendix A Exercise 5 Step 4 has the command to rename Windows 7 client comptuer as follows: netdom renamecomputer %computername% /newname:VAN-CL1 Appendix A Exercise 5 Step 6 has the command to join a Windows 7 client comptuer to the domain as follows: netdom join VAN-CL1 /domain:adatum Netdom is NOT included with Windows 7 by default and the command will fail. It can be added with the Remote Server Administration Tools. Really though the book should use the powershell command Add-Computer instead.

Note from the Author or Editor:
The following modifications are to be made to Exercise 5 in the Appendix: Add the following to Step 3 after the comand "netsh interface ..." netsh interface ipv4 set dnsservers "Local Area Connection" static 10.10.0.10 primary Change Step 4 to the following Hold down the Windows Key and the Break Key to open the System Properties dialog box. Click Advanced System Settings. On the Computer Name tab click Change. In the Computer Name textbox enter VAN-CL1. Click OK. Change Step 6 to the following Hold down the Windows Key and the Break Key to open the System Properties dialog box. Click Advanced System Settings. On the Computer Name tab click Change. In the Domain textbox enter ADATUM. When prompted, enter the Administrator account credentials.