A site dedicated to Cloud and Datacenter Management

Book Review: Microsoft System Center Configuration Manager Field Experience

Configuration Manager Field Experience CoverRecently, I finished reading the Microsoft System Center: Configuration Manager Field Experience eBook.

The chapters that I found most helpful was Chapter 6 “Operating System Deployment Tips”, hence the majority of my highlights are from this chapter.

I’ve decided to share my highlights from reading this specific publication, in case the points that I found of note/interest will be of some benefit to someone else. So, here are my highlights (by chapter). Note that not every chapter will have highlights (depending on the content and the main focus of my work).

Chapter 01: Introduction to WMI in Configuration Manager 2012

  • None


Chapter 02: Configuration Manager Custom Reporting

  • For example, you might want information about MAC addresses. Start by finding the table or view that contains this information. To do this, run the following query to get all tables and views that contain a column name like %MacAddress%: Select * from INFORMATION_SCHEMA.COLUMNS Where COLUMN_NAME like ‘%MacAddress%’
  • The configuration database contains different types of views. For example, views that start with V_GS contain current data while those that start with V_HS contain historical data.
  • An inner join returns the matching records in both tables.
  • So an inner join by design looks for matching records in both tables.


Chapter 03: Integrating SQL Server Reporting Services with Configuration Manager 2012

  • To change the URL, you must uninstall the reporting services point, change the URL, and then reinstall the reporting services point
  • The reporting services point account must have Read rights to the site database.


Chapter 04: Customizing SSRS Reports for Configuration Manager 2012

  • None


Chapter 05: Customizing Function-Based Built-In Reports

  • None


Chapter 06: Operating System Deployment Tips

  • You can test missing drivers with drvload to see if you have the correct driver to add to your boot image. Below is a quick step-by-step procedure for using drvload to verify that you have the proper driver.
    • 1. Determine the driver that is missing and download it to media.
    • 2. Insert media and change directory to the folder holding your INF files.
    • 3. Run drvload.exe NameOfYour.inf.
    • 4. Validate that you can access the disk or obtain an IP address
    • 5. Add to a boot image in Configuration Manager.
  • Best practice is to build a solid driver store that is easy for you to maintain and to know what you have in your environment. Michael Niehaus ( and Johan Arwidmark ( both have very detailed blog posts on the subject with examples of sound driver stores if you would like to find out more information.
  • It’s important to regularly check your OEM for updated drivers not only to improve device functionality but to also patch security vulnerabilities in the drivers.
  • Always build your reference image on a virtual machine in BIOS compatibility mode.
  • USB boot media must be formatted as FAT32
  • The typical disk layout for UEFI deployments looks like this:
    • Recovery (NTFS, 300 MB)
    • System (FAT32, active, 300 MB)
    • Microsoft Reserved Partition (MSR, 128 MB)
    • Operating System (NTFS, 100%)
  • By integrating MDT into Configuration Manager, you gain the ability to use the additional templates, actions, and customized boot images and to call external scripts, databases, web services, and much more to enhance and streamline your operating system deployment needs.
  • Setting OSDPreserveDriveLetter=YES will deploy the operating system to the drive from which it was captured. For instance, the install.wim is captured with the c:\ drive as the destination disk, so that would hold true with OSDPreserveDriveLetter set to true. In some cases, this setting does not produce the desired affect, but in most cases this will work fine.
  • The task sequence disables Group Policy Object (GPO) processing during the task sequence
  • By default only one rollover log is maintained and the rest of the log is purged.
  • The Configuration Manager team has provided the ability to extend logging so you can have more to work with if you are troubleshooting something or simply want to verify what happened. CCMLOGLEVEL, CCMLOGMAXHISTORY, and CCMLOGMAXSIZE all are configurable in the installation properties of the ConfigMgr Client Installation step of the task sequence. By setting these variables, you will gain more robust logging:
    • CCMLOGLEVEL=0 Turns on verbose logging.
    • CCMLOGMAXHISTORY=6 Sets the number of log files to keep.
    • CCMLOGMAXSIZE=2621440 Sets the log size to 2.5 MB.
  • Global conditions in Configuration Manager 2012 are rules that represent business or technical conditions that can be used to specify how an application is provided and deployed to client devices
  • For details about how to set up chassis-type global conditions, go to
  • Configuration Manager task sequences run under the system context in session 0, so any application that requires interaction will fail or simply sit and time out
  • MDT has a variable called SLShare that you can use in MDT Integrated task sequences to find all of the common log files and copy them up to a file share when the task sequence is complete.


Don’t forget to check out the following:

CANITPro: Did you know there is a site dedicated to Canadian IT professionals? You can win a 3D movie prize package by upgrading your IT skills with Microsoft. Check out CANITPRO At The Movies, either in English: CANITPro At The Movies or French: CANITPro At The Movies

Azure: Sign up for a FREE trial and get $200 to spend on Microsoft Azure cloud computing services. Full access, no strings.

MSDN: Ever wanted to work with the latest Microsoft technologies, without having to spend thousands of dollars? Now you can, with the MSDN subscription

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: