Monthly Archives: August 2014

ConfigMgr Client Log locations during OSD

Posted on by
Reply

Just a quick reference for finding the client logs during an Operating System Deployment.

As we all know ConfigMgr moves the logs during a deployment depending on the stage of deployment.

We can define 4 major stages in regard to the log file locations:

  1. System has started in WinPE, no hard drive configuration has taken place:
    “x:\windows\temp\smstslog” folder
  2. System has started in WinPE, hard drive has been partitioned and formatted:
    “x:\smstslog” folder
    “c:\_SMSTaskSequence\Logs\Smstslog” folder
  3. System has started in Windows but ConfigMgr is NOT yet installed:
    “c:\_SMSTaskSequence\Logs\Smstslog” folder
  4. System has started in Windows and ConfigMgr IS installed:
    “c:\windows\ccm\logs\Smstslog” folder

After the completion of the OSD the Task Sequence log file can be found in:

“c:\windows\ccm\logs\smsts.log

Probably you will find 2 of those, 1 with a date appended. This is because log files can’t grow unlimited!

Deploy the Windows 7 Kernel Mode Driver Framework (KMDF) with ConfigMgr 2012

Posted on by
11

So you got your brand new Dell or other manufacturer’s hardware, deploy an OS with ConfigMgr 2012 and he, no go – chrash – missing drivers etc.

Well you might need the new Kernel Mode Driver Framework 1.11 (here) or the User Mode Driver Framework 1.11 (here).

But wait, this is an Windows Update! And I am doing OSD.

To successfully add the Driver Framework use good old dism
during OSD. Of course you will build a new reference image but in the meantime you have some deployment to do.

Okay let’s start.

First extract the files out of the .msu (I am using the x64 version for this). Use WinRar or 7zip for this.

In this folder create a batch file – install.cmd – containing following code:

Dism.exe /Image:%1\ /Add-Package /PackagePath:"%~dp0Windows6.1-KB2685811-x64.cab" /NoRestart

So the content of folder will now look like this (b.t.w. we do not need the .msu in the package ;-))

Create a ConfigMgr package from these files. No program needed! Distribute the content.

Now we can apply this in our Task Sequence. It has to be done AFTER the ‘Apply Operating System’, but BEFORE the installation of the ConfigMgr client.

Add a ‘Run Command Line’ and enter following as command:

Cmd.exe /c install.cmd %OSDTargetSystemDrive%

Reference the package.

Now the KMDF will be installed during the deployment!

You can do the same steps for the UMDF.

(Re)-Creating a boot image for ConfigMgr 2012 using Windows ADK

Posted on by
Reply

When you are having problems with your boot images (corruption or just malfunctioning) there might come a time you need to (re)-create one or maybe both.

This is a very straight forward process which will be described below.

You use the Windows ADK for this process. Depending on your version of ConfigMgr this will be the 8 (http://www.microsoft.com/en-us/download/details.aspx?id=30652) or 8.1 (http://www.microsoft.com/en-us/download/details.aspx?id=39982) version.

Run the ‘Deployment and Imaging Tools Environment’ As Administrator

This will open up the environment

Depending on the architecture the command to issue will be the following:

32-bit boot-image:

COPYPE.CMD x86 C:\WINPE86\

64-bit boot-image:

COPYPE.CMD amd64 C:\WINPE64\

ARM boot-image:

COPYPE.CMD arm C:\WINPEARM\

The target folder can be a folder of choice!

This will only take a few seconds.

And there it is, your freshly created boot image!
You can find this in the C:\WINPE64\media\sources folder.

In the ConfigMgr console go-to ‘Software Library – Overview – Operating Systems – Boot Images’, right-click and select ‘Add Boot Image’

Select your new image:

Provide information:

And there it is, your boot image in ConfigMgr.

Now you can work with this image as well!
Just remember to distribute the image, and when needed to enable ‘Deploy this boot image from PXE-enabled distribution point’