Jump to content




anyweb

Using SCCM 2012 RC in a LAB - Part 15. Deploying Windows 8 Consumer Preview using Configuration Manager 2012 RC2



Recommended Posts

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary's and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies.

 

In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture process to create our Base Windows 7 X64 wim image. In Part 8 we created a USMT 4 package to migrate the users data using hardlinking and then we imported the captured image into ConfigMgr and created a Deploy Windows 7 X64 task sequence. We created a Deploy Windows 7 X64 Collection and set some User Device Affinity collection variables.

 

In Part 9 we created an Application, and created a deployment type for that application to only install if the Primary User was True for that device (User Device Affinity), we then copied our Task Sequence (duplicated it), deployed the new Task Sequence, added a computer to the new collection and then PXE booted the computer to the Deployment Menu. In Part 10 we monitored the Deployment process in a lot of detail to how UDA sent state messages and we verified that our application installed on the users Primary Device, in addition we modified our collection variables, and added a prestart command to our boot image to prompt for the SMSTSUdaUsers. In Part 11 we setup the Reporting Services Point Role and verified that reporting was working.

 

In Part 12 we demonstrated a new feature in ConfigMgr which allows us to Patch operating system WIM images using Offline Servicing. This means that you can apply Windows Updates by using Component-Based Servicing (CBS) to update the your previously captured WIM images. In Part 13 we looked at how Role Based Administration is used within ConfigMgr and we created a new custom role to allow a user (or users within a Security Group) to view Software Update Reports. This is useful because you will probably want one team to take care of configuring and deploying software updates, and to grant another (Management etc) the capability of reviewing Compliance Reports. In Part 14 we performed a side-by-side migration from Configuration Manager 2007.

 

Now we will test deploying Windows 8 Consumer Preview.

 

Note: This is a Windows 8 Consumer Preview OS being installed using a release candidate product so your results may vary and of course it's not supported by Microsoft. I'm only doing this because I want to see if it's possible to deploy Windows 8 with the current release of Configuration Manager 2012 and of course it's fun :-)

 

Windows 8 Consumer Preview System Requirements

 

 

Windows 8 Consumer Preview works great on the same hardware that powers Windows 7:


  •  
    Processor: 1 gigahertz (GHz) or faster

  •  
    RAM: 1 gigabyte (GB) (32-bit) or 2 GB (64-bit)

  •  
    Hard disk space: 16 GB (32-bit) or 20 GB (64-bit)

  •  
    Graphics card: Microsoft DirectX 9 graphics device or higher

  •  
    To use touch, you need a tablet or monitor that supports multitouch

  •  
    To access Windows Store and to download and run apps, you need an active Internet connection and a screen resolution of at least 1024 x 768

  •  
    To snap apps, you need a screen resolution of at least 1366 x 768

Step 1. Get the ISO and Extract the contents on your Configuration Manager 2012 server

 

 

Download Windows 8 Consumer Preview from here, I used the X86 ISO (Windows8-ConsumerPreview-32bit-English.iso) for my Guide.

I then Mounted that ISO in my Configuration Manager 2012 RC 2 Hyperv virtual Machine and extracted the contents to \\sccm\sources\os\Windows 8 X86 Beta

 

windows 8 extracting.png

 

Step 2. Add the Operating System Installer Image and Distribute Content

 

In the Configmgr Console, expand Software Library, Operating Systems, Operating System Installers, right click and choose Add Operating System Installer

 

add operating system installer w8.png

 

browse to the path where we extracted it in Step 1

 

w8 path.png

 

fill in some details about the image

 

w8 details.png

 

and click next through to the summary

 

summary w8.png

 

Once added, distribute the content to your DP's by right clicking the image and choose Distribute Content.

 

distribute content w8.png

 

and continue through the wizard just like you've done before with Windows 7's installer image.

 

 

Step 3. Create the Build and Capture Task Sequence

 

In task sequences, right click and choose Create Task Sequence

 

w8 create task sequence.png

 

Choose the Build and Capture a reference operating system image option

 

w8 bac.png

 

fill in the details and choose a X86 boot image as we are Build and Capturing the X86 Windows 8 image...

 

Note: if you are trying with the X64 image, then use a X64 boot image.

 

w8 bac task sequence.png

 

for the Install Windows step, select the following options, for Product key, use the key listed here otherwise the Setup Windows and Configmgr step will fail (error 31) later on in the process.

 

for network select to join a workgroup

 

w8 join workgroup.png

 

select your Configmgr Client in the next step then next your way through on to the Capture image step, fill in your capture details

 

w8 capture details.png

 

click next through to summary

 

w8 bac ts done.png

 

Now right click the task sequence and choose Edit, Disable the Entire Capture Group (for now) and also disable the apply device drivers step.

 

w8 disable stuff.png

 

 

Step 4. Deploy the Build and Capture Task Sequence

 

Right click on the task sequence and choose Deploy,

 

deploy w8.png

 

point it to the All Systems Collection (this is a LAB so this is OK, don't deploy task sequences to All Systems in production please....)

 

deploy w8.png

 

make sure it's set to Available and enable PXE

 

available w8.png

 

click your way through to completion of the wizard..

 

w8 deploy ts done.png

 

 

 

Step 5. PXE boot a new virtual machine and start the process

 

PXE boot your Virtual Machine (create a new one in hyperV), Press F12 for Network boot then you'll see the now familiar and very nice Configuration Manager 2012 splash screen

 

w8 pxe w8.png

 

select your Build and Capture Task sequence and press enter, it starts applying the OS

 

w8 apply os.png

 

and the Operating System installation starts..notice the color scheme is slightly different to what we are used to, and I like it !

 

the os install begins.png

 

before it reboots it might be an idea to monitor the SMSTS.log file using cmtrace

 

w8 cmtrace.png

 

and after the first reboot we get our first look at Windows 8 Consumer Preview setting up :-)

 

w8 fish.png

 

and another reboot takes place..before Windows 8 finalizes settings

 

w8 finalize settings.png

 

and then Setup Windows and ConfigMgr does it's work..

 

setup windows and configmgr w8.png

 

and we are done !

 

w8 done.png

 

Conclusion: ConfigMgr rocks, and Windows 8 Consumer Preview rocks !!

 

metro.png

 

more screenshots coming soon when bandwidth allows...currently it's worse than 56k dialup !!!

  • Like 1

Share this post


Link to post
Share on other sites


Thanks for a great article! I thought it would be easy like that but sadly I recived problem during the capture.

 

Following error could be found in the smsts.log,

 

Unable to sysprep the machine, hr=d000004

Syspreping the machine failed, hr=d000004

Failed to run the action : Prpare OS. The system cannot open the file (error 00000004: Source Windows)

 

I used the key from Microsofts webpage, and the image (x64) was downloaded from their webpage.

 

Any suggestions?

 

Thanks in advance!

Share this post


Link to post
Share on other sites

disable the entire Capture group and it'll work just fine.

Share this post


Link to post
Share on other sites

disable the entire Capture group and it'll work just fine.

 

will try that, but then we will not be able to capture and then later deploy? :(

Share this post


Link to post
Share on other sites

not using this method as its unsupported and missing some vital files, in my guide i purposely disable the capture group, you can still capture it with imagex

Share this post


Link to post
Share on other sites

I ran into trouble with the x64 deployment. It will not join the domain after installing Windows OS. It is identical to the x86 setup, which will join the computer to the domain, so I'm not sure what the deal is.

Share this post


Link to post
Share on other sites

I was able to deploy Win 8 following this guide w/o any issues...except that upon reboot the VM tells me BOOTMGR is missing? I followed this guide step by step, although I did use 64bit version of Windows 8.

 

Any ideas on why the drive would not have been configured correctly?

Share this post


Link to post
Share on other sites

I was able to deploy Win 8 following this guide w/o any issues...except that upon reboot the VM tells me BOOTMGR is missing? I followed this guide step by step, although I did use 64bit version of Windows 8.

 

Any ideas on why the drive would not have been configured correctly?

 

Ah ha...I am actually failing out of the of the Task Sequence w/ the error code 0x80004005. I must have missed this earlier, and it rebooted before I had a chance to see it.

 

Any ideas on what could be causing this error code?

 

Also, sorry for the noob question, but how did you get cmtrace to load in the console of the image while it is deploying?

Share this post


Link to post
Share on other sites

cmtrace is in the boot image by default now, just press F8 (make sure you enable this ability in the boot image properties) and you'll get a command prompt you can then cd to x:\sms\bin\x64\cmtrace.exe and launch it from there if a x64 boot image or x:\sms\bin\i386\cmtrace.exe for x86

Share this post


Link to post
Share on other sites

cmtrace is in the boot image by default now, just press F8 (make sure you enable this ability in the boot image properties) and you'll get a command prompt you can then cd to x:\sms\bin\x64\cmtrace.exe and launch it from there if a x64 boot image or x:\sms\bin\i386\cmtrace.exe for x86

 

Sure - I had this enabled based upon your step by step guide, I was unaware of being able to launch the console using F8 - VERY NICE.

Share this post


Link to post
Share on other sites

Ah ha...I am actually failing out of the of the Task Sequence w/ the error code 0x80004005. I must have missed this earlier, and it rebooted before I had a chance to see it.

 

Any ideas on what could be causing this error code?

 

Also, sorry for the noob question, but how did you get cmtrace to load in the console of the image while it is deploying?

 

I have the exact same error after following this guide in my test environment, did you solve this problem?

Share this post


Link to post
Share on other sites

 

Sure - I had this enabled based upon your step by step guide, I was unaware of being able to launch the console using F8 - VERY NICE.

I'm having the same issue, does anyone have a resolution for this?

 

I'm getting a lot of errors about "faile to find a suitable device driver for device":

 

 

<![LOG[Processing driver match result.]LOG]!><time="10:49:58.094+300" date="01-15-2013" component="OSDDriverClient" context="" type="1" thread="1728" file="onlinedrivercatalog.cpp:372">

<![LOG[server returned a total of 0 driver definitions.]LOG]!><time="10:49:58.094+300" date="01-15-2013" component="OSDDriverClient" context="" type="1" thread="1728" file="onlinedrivercatalog.cpp:460">

<![LOG[Failed to find a suitable device driver for device 'VMBUS\{2450EE40-33BF-4FBD-892E-9FB06E9214CF}\5&296C0F0E&0&{2450EE40-33BF-4FBD-892E-9FB06E9214CF}'.]LOG]!><time="10:49:58.094+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'ACPI\PNP0B00\4&215D0F95&0'.]LOG]!><time="10:49:58.094+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'Video Controller (VGA Compatible)'.]LOG]!><time="10:49:58.110+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'ACPI\PNP0C01\1'.]LOG]!><time="10:49:58.110+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'ACPI\PNP0C02\1'.]LOG]!><time="10:49:58.110+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'ACPI\PNP0C02\2'.]LOG]!><time="10:49:58.110+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'PCI to ISA Bridge'.]LOG]!><time="10:49:58.126+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'ACPI\PNP0C04\4&215D0F95&0'.]LOG]!><time="10:49:58.126+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

<![LOG[Failed to find a suitable device driver for device 'VMBUS\{D34B2567-B9B6-42B9-8778-0A4EC0B955BF}\5&296C0F0E&0&{D34B2567-B9B6-42B9-8778-0A4EC0B955BF}'.]LOG]!><time="10:49:58.126+300" date="01-15-2013" component="OSDDriverClient" context="" type="2" thread="1728" file="driverinstaller.cpp:799">

 

The log also showed a lot of these errors at the beginning:

 

 

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:39.969+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:39.969+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

<![LOG[Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type]LOG]!><time="10:49:40.079+300" date="01-15-2013" component="ApplyOperatingSystem" context="" type="0" thread="1440" file="securityutil.cpp:796">

Share this post


Link to post
Share on other sites

are you deploying Windows 8 with the Configuration Manager 2012 SP1 ? the Sms\Mobile Client\Software Distribution registry key are safe to ignore, the failed to find suitable drivers are because you have not supplied driver packages containing drivers for the detected hardware, nothing too serious

 

is the deployment failing ?

Share this post


Link to post
Share on other sites

are you deploying Windows 8 with the Configuration Manager 2012 SP1 ? the Sms\Mobile Client\Software Distribution registry key are safe to ignore, the failed to find suitable drivers are because you have not supplied driver packages containing drivers for the detected hardware, nothing too serious

 

is the deployment failing ?

I tried the deployment without SP1, just saw it came out this morning.

 

The deployment failes with the same errors others were getting, I am actually failing out of the of the Task Sequence w/ the error code 0x80004005. I did miss your step about disabling drivers in the instructions so I need to redeploy after this. I'll also install SP1 today and give it a shot.

 

Any other suggestions?

Share this post


Link to post
Share on other sites

I work for a college and we have a windows 8 OS pre-existing in my lab. Those machines are frozen by DeepFreeze.

 

I want to deploy another windows 8 OS to the same machines which will make them dual boot.

 

We were using Ghost before and were able to do this by creating a separate partition and applying the OS to that partition.

 

We moved to SCCM infrastructure recently and when I tried to accomplish this through the task sequence, the existing image get wiped out.

 

Please help me with this.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×