Posts Tagged ‘OS Deployment’

How to: Directly install from a distribution point during OSD in ConfigMgr 2012 R2

During a OS deployment with ConfigMgr 2012 R2, the WIM file is downloaded locally and than installed on the C: drive of your system. The download proces for the install.wim file takes a while! This post will discribe how to configure the task sequence to directly apply the install.wim from the distribution point.

1.) Open the task sequence and select the step “Apply Operating System”. Navigate to the “Options” tab.
2.) Select “Access content directly from the distribution point” and select “Apply”
3.) Navigate to your Operating System Images and select the properties of the image
4.) Navigate to the “Data Access” tab
5.) Select “Copy the content in this package to a package share on distribution points”
6.) Select “Apply”
7.) The install.wim file will be copied to the SMSPKGE$ folder on your distribution point
8.) Right click on the image and select “Update Distribution Points”
9.) Wait until the content status is “Success”
10.) Start a deployment of a system
11.) The download step is gone now and the image will be installed directly from the distribution point

OSDC_01    OSDC_02    OSDC_03

OSDC_04    OSDC_05    OSDC_06

OSDC_07    OSDC_08    OSDC_09

OSDC_10    OSDC_11    OSDC_12

OSDC_13    OSDC_14    OSDC_15

OSDC_16    OSDC_17    OSDC_18

ConfigMgr 2012 client installation on Windows 8 returns an error 0x800b101

Last week I have been working on a Windows 8 deployment with ConfigMgr 2012. After configuring a new task sequence, I was able to deploy the first Windows 8 image to one of many virtual desktops. The deployment went fine, until the ConfigMgr client installation. Okay, so what about now. Let’s have a look in the CCMSETUP.LOG on the client. I received the following error:
“Couldn’t verify C:\WINDOWS\ccmsetup\MicrosoftPolicyPlatformSetup.msi authenticode signature. Return code 0x800b101″.

After some search on Microsoft TechNet, I found the solution for this problemn. Microsoft has released a hotfix for this error (KB2801987) . You have to request this hotfix by e-mail.

After requesting and downloading the hotfix, you have to install this hotfix on your primary site server. It wil create a new update package named “KB 2801987 – server update – P01″. If you browse to your client installation files on your primary site server, you’ll also see that the timestamp has changed. So the ConfigMgr client installation files are also updated! Make sure you update the distribution point(s) with the new version of the ConfigMgr 2012 client installation package.

Now you’re able to succesfully deploy Windows 8 with the ConfigMgr 2012 client.

WIN8_01    WIN8_02    WIN8_03

WIN8_04    WIN8_05    WIN8_06

WIN8_07    WIN8_08    WIN8_09

WIN8_10    WIN8_11    WIN8_12

WIN8_13    WIN8_14    WIN8_15

WIN8_16    WIN8_17    WIN8_18