You are here:   Errata
  |  Login

We are sorry...

On this page we have gathered a list of errors and their corrections that were found after the book was released. The following errata were submitted by our customers and approved as valid errors by the author(s) or editor(s).

In general, make sure you have the latest version of the book sample files.

Deployment Fundamentals - Volume 5: Building a Real-World Infrastructure with Windows Server 2012 R2, MDT 2013, and PowerShell

Kindle Page 130
The HV01 specs (2x 200GB SAS SSD and 2x 500GB SATA HD) does not match the screenshot (2x 200GB SAS SSD and 5x 500GB SATA HD)

System Center 2012 R2 Configuration Manager: Mastering the Fundamentals, 3rd Edition

In the first print (books printed prior to September, 2014): The size for the data disk (D:) used on CM02 and CM03 was not specified. 300 GB is recommended since that's the size of the Content Library on CM01, but any volume above 50 GB will do for completing the guides in the books.   Also, there was an incorrect reference to an "Office 2013" appendix which now have been removed in.

Page 27
Typo, "Server 2012 SP1 CU8" should be "SQL Server 2012 SP1 CU8"

Page 253
Instructions for adding VIAMONSTRA\JUS account to various _install groups are missing. This is addressed in books printed after September, 2014, and in the Kindle edition.

Page 279
The JAP user account should be the JUS user account (the JAP account does not exist). This is addressed in books printed after September, 2014,
and in the Kindle edition.

The Deploy a Required Application Using PowerShell - PowerShell script is missing the Start-CMContentDistribution command.

2014-07-08: Sample files updated, the Get-CMClientBusinessHours.ps1 script was missing

Page 290
Import an Application: The is missing in the book sample files, to complete the guide you need to create the WinRAR app in ConfigMgr, and export it first.

System Center 2012 Configuration Manager: Mastering the Fundamentals

Page 20
Step i. should read: "Browse to the LocalCorpAdmins group you created, add it to Restricted Groups, and click OK.

Page 86.
The "Create a WMI Filter to Exclude All Existing ConfigMgr 2012 Clients" section is unfortunately incorrect. Please use a Startup script instead, as described in this document: Addendum - Installing a Client Using a Startup script

Deployment Fundamentals - Volume 4: Deploying Windows 8 and Office 2013 Using MDT 2012 Update 1

Page 67
Typo, "File History Restore viwer" should be "File History Restore viewer".

Page 82
ApplyGPOPack=NO is missing from the CustomSettings.ini list, the sample file is correct though. Info about what ApplyGPOPack does is also missing, check the MDT Help for more information on ApplyGPOPack.

Page 166 - 169
The four Visual C++ command lines are missing the ".wsf" extension.

Deployment Fundamentals - Volume 3: Deploying Windows 7 Using System Center Configuration Manager 2007

Page 89
"Windows Server 2008 R2 Enterprise" should be "Windows 7 Enterprise"

Page 149
The path for creating the USMT 4.0 package should be \\FS01\PackageSource$\OSD\USMT\USMT 4.0.

Page 339 - 340
12 - 15: All references to the "ConfigMgr 2007 SP2" path should be "Install - ConfigMgr 2007 SP2"
15: The "Extend ConfigMgr 2007 Schema" path is named "Configure - Extend AD for ConfigMgr 2007"
17: The "SQL Server 2008 R2 Express" path is named "Install - SQL Server 2008 R2 Express"

Missing step: Copy the SCCM2007-SP2-KB977384-ENU.msi file (ConfigMgr 2007 R3 PreReq) to C:\HydrationDF3\HydrationDS\Applications\Install - ConfigMgr 2007 R3\PreReqs

Deployment Fundamentals - Volume 2: Deploying Physical and Virtual Servers Using MDT 2010 and SCVMM 2008 R2

Page 44
Step 4 is a duplicate, skip it.

Page 45
Steps 8 and 9 are duplicates, skip them.

Page 78
The command line should be: cscript.exe Configure-SNMP.wsf

Page 81
The command line for the "Configure - ViaMonstra Set DHCP Service Start Type Application" should be: cscript.exe Configure-SetDHCPAutoStart.wsf

Deployment Fundamentals - Volume 1: Migrating to Windows 7 using MDT 2010 Lite Touch and WDS

Page 91
Step 1. "Process Monitor" should be "Process Explorer"