Browsing: Windows PE

Allmost every time I get a call from a customer, or want to answer a question in the TechNet Forums about OS Deployment, I always start by asking for logfiles. There are MANY log files when it comes to ConfigMgr 2012 R2, and most of them are normally located in the same folder every time you need them. But when you are troubleshooting OS Deployment using, one of the most common log files you almost always want to check, is the SMSTS.log. And this log file is moving around depending on the phase of the deployment process. There are plenty of blogs…

This morning, one of my customers called me and told me that they bought some new Lenovo laptops (Lenovo ThinkPad S540), but they was unable start OS Deployment using SCCM/PXE. Normally when I see this behaivor, it’s caused by a missing driver in the boot image, so I told them to verify that the driver was loaded correct. Here is a guide to verify the network driver in a SCCM Boot Image: https://www.ronnipedersen.com/2009/04/importing-network-drivers-into-the-windows-pe-boot-image/ But the driver was loaded correct, so I requested the SMSTS.log and found another common issue. The SMSTS.log file can be found here: https://www.ronnipedersen.com/2014/08/sccm-2012-r2-smsts-log-located/ In the SMSTS.log…

The IBM Deployment Pack for Microsoft System Center Configuration Manager 2007 (SCCM) is used to configure IBM hardware components prior to deploying Windows using Microsoft SCCM. This kit extends Configuration Manager 2007 by providing a convenient integrated user interface that will be familiar to SCCM administrators. The Deployment Pack completes the end-to-end deployment scenario in environments where IBM-specific configuration steps are required including RAID, IMM, RSA2, BMC, and BIOS/UEFI. Key features include: IBM-specific drivers, agents, and firmware Scriptable hardware configuration tools for the Windows Preinstallation Environment (WinPE) Sample configuration files and scripts, including sample Sysprep and Unatted.txt files Download here.

A lot of questions that often pops up in various newsgroups and on the Microsoft TechNet forums are related to importing drivers in the Windows PE boot image. This article will walk you through this process step-by-step. This guide assumes that the following steps have been completed: The PXE Service Point are installed and configured. Command line support have been enabled for both the x86 and x64 boot image. The boot image is distributed to the PXE Service Point and a Distribution Point. A Task Sequence has been created and is advertised to the client. Identifying that a driver is…