Jump to content




anyweb

How can I deploy Windows 8.1 using System Center 2012 R2 Configuration Manager



Recommended Posts

Introduction

 

AT the build conference in San Francisco yesterday Microsoft unveiled a preview version of Windows called Windows 8.1, and in conjunction with the recent release of System Center 2012 R2 Configuration Manager preview, we have the ability to deploy this new OS to see what's changed both in Configuration Manager and in Windows 8.1. A lot has changed with the introduction of System Center 2012 R2 Configuration Manager including a whole bunch of Operating System Deployment changes listed here and that includes support for Windows Server 2012 R2 and Windows 8.1.

 

In this guide we will use System Center 2012 R2 Configuration Manager to Deploy Windows 8.1 Preview. If you have not yet installed R2 then follow this guide.

 

Note: Prior to installing R2 I have installed both CU1 and CU2 for System Center 2012 Configuration Manager SP1, as they contain several fixes (PowerShell amongst others).

 

I'll use PowerShell wherever possible in this guide and i'd suggest you begin to do so to (if you haven't already), if you missed my introduction to PowerShell in Configuration Manager then please see this post.

 

Step 1. Get the Windows 8.1 Preview ISO and extract it

 

Download the preview version of Windows 8.1 from MSDN.com or from this link, extract the ISO and copy extracted files and folders to your sources share on your Configuration Manager server. I copied it to \\sccm\sources\os\os_media\windows 8.1 preview X86

 

media extracted to sources folder.png

 

Step 2. Add the Windows 8.1 Install.WIM file

 

We need to add our operating system image file to Configuration Manager, to do so we can use two methods, either in the console using manual steps or in using powershell.

 

Method #1 - Do it in the console

 

In the Operating System Deployment section of the Software Library workspace, select Operating System Images and right click, choose Add Operating System Image

 

Add Operating System Image.png

 

Point the wizard to the Install.WIM file in the sources folder of your extracted media files, eg: \\sccm\sources\os\os_media\windows 8.1 preview X86\sources\install.wim

 

data source.png

 

On the General screen, fill in information about the Windows 8.1 Preview image you are adding and edit the version or description info so that it clearly points out that this is the Install.WIM file that you are using (to make it clear later when adding Windows 8.1 Preview images to any Deploy Windows 8.1 task sequences).

 

General info.png

 

continue with the wizard through to completion.

 

completion.png

 

Method #2 - Do it using PowerShell

 

In a powershell console use the following (point it to your path)

New-CMoperatingSystemImage -Name "Windows 8.1 Preview" -path "\\sccm\sources\os\OS_Media\Windows 8.1 Preview  X86\sources\install.wim" -Version "X86 (Install.WIM)" -Description "This is the Install.wim file from the Windows 8.1 Preview sources folder. (c) windows-noob.com June 2013"

Step 3. Distribute content to our Distribution points

 

Now that we've added the image to Configuration Manager we need to distribute it to our distribution points otherwise our client computers cannot download it.

 

Method #1 - Do it in the console

 

Right click on the image and choose Distribute Content

 

Distribute Content.png

 

click next at the Review Selected Content screen, click on Add to add your distribution points, select the distribution points from the list available

 

add distribution points.png

 

and continue through the wizard until completion.

 

distribute content wizard completion.png

 

Method #2 - Do it using PowerShell

 

In a powershell console use the following (point it to your distribution point)

Start-CMContentDistribution –OperatingSystemImageName "Windows 8.1 Preview" –DistributionPointName "sccm.server2008r2.lab.local"

and review the distribution of the image via distmgr.log

 

review the package distribution status via distmgr log file.png

 

or via PowerShell by specifying the package ID of the Operating System Image.

Get-WmiObject –NameSpace Root\SMS\Site_P01 –Class SMS_PackageStatusRootSummarizer –Filter "PackageID='P0100067'"

review distribution status via powershell.png

 

Step 3. Create a Deploy Windows 8.1 task sequence

 

In the console right click on Task Sequences, choose Create Task sequence

 

Create Task Sequence.png

 

choose Install an existing package, (side note there is a new option since the introduction of R2, and that new option is called Install an Existing image package to a virtual hard drive, this setting is for Virtual Machine Manager use).

 

Install an existing image.png

 

fill in the task sequence information and select the X86 boot image (note that the version of the boot image is 6.3.9431.0)

 

Task Sequence Information.png

 

Select the newly added Windows 8.1 Preview image, it has two indexes Windows 8 Pro and Windows 8, enter your local administrator password, decide if you want to use BitLocker disc encryption or not, enter the Product key (otherwise you'll get prompted later on) and click next when done

 

Install windows.png

 

Note: in the screenshot above the product key is blank for security purposes, make sure to fill yours in if you do NOT want to be prompted during the task sequence deployment.

 

for configure network settings, enter a domain join account, and verify that it works before continuing

 

dom join verified.png

 

click next through the wizard until completion.

 

task sequence created.png

 

Step 4. Edit the task sequence

 

Right click on our newly created task sequence and choose Edit.

 

Locate the built in Enable BitLocker step and add the following wmi query for root\cimv2 so that it won't run on Virtual Machines otherwise the task sequence will bomb out on hyperV virtual machines...

select * from Win32_ComputerSystem where Model <> "Virtual Machine"

Enable BitLocker step.png

 

click Apply to save the changes and then click Ok.

 

Step 5. Deploy the task sequence

 

Method #1 - Do it in the console

 

Right click on the task sequence and choose Deploy

 

Deploy Task Sequence.png

 

and choose a collection, in my example i'll use the All Unknown Computers collection

 

all unknown computers.png

 

set the deployment purpose as Available (optional) and make if available to Configuration Manager Clients, Media and PXE.

 

make available.png

 

click next through the wizard until completion

 

deploy task sequence wizard complete.png

 

 

Method #2 - Do it using PowerShell

 

Use the following, replace the package ID listed below with the package ID of your Deploy Windows 8.1 Preview task sequence.

Start-CMTaskSequenceDeployment –TaskSequencePackageId "P0100068" –CollectionName "All Unknown Computers" –Comment "© windows-noob.com June 2013" –Deploypurpose "Available" –MakeAvailableTo "ClientsMediaAndPXE"

Step 6. PXE boot and a new (unknown) computer

 

PXE boot a computer (I use hyperV virtual machines with legacy nics added as the first boot device), press F12 when prompted to start the network boot process

 

PXE boot.png

 

the boot wim file will be downloaded, note that this is a new version since you already updated Windows ADK to 8.1 to support deploying Windows 8.1

 

boot wim loading.png

 

and you can clearly see that the version of WinPE has changed, with the new Fish logo, cute

 

Windows 8.1 fish.png

 

select our Deploy Windows 8.1 Preview task sequence

 

select our task sequence.png

 

and off it goes...

 

running the task sequence.png

 

the Windows 8.1 wim file get's downloaded and applied, and the computer reboots to start windows setup, we get to see the fish again (do you remember where we saw him before, it was in Windows 8 Consumer Preview here)

 

fishy.png

 

before a few more reboots to get windows ready for the next stage, installing the Configuration Manager client,

 

installing configuration manager client.png

 

before being presented with the new login screen for Windows 8.1

 

login screen for windows 8.1.png

 

so login with your testuser credentials to see the new start screen

 

start screen.png

 

and the new desktop

 

desktop.png

 

cool ! job done.

 

Summary

 

In this guide (there is an index here) you've learned how to Deploy Windows 8.1 Preview with System Center 2012 R2 Configuration Manager, you've learned the steps required to successfully deploy that image and finally you've done most of the work using PowerShell Cmdlets (where available). Congratulations !

  • Like 1

Share this post


Link to post
Share on other sites


Thanks for the guide. I have completed everything with no issues.

However now when i try to create an MDT task sequence i get a message:

 

Windows AIK must be installed on the current machine in order to select this option. Once created, the new package must be distributed to the needed distribution points manually before it can be used by the task sequence.

 

And "Create a new MDT Files Package" is disabled.

 

What am i missing?

Thank you.

Share this post


Link to post
Share on other sites

what version of MDT are you using and what version of ADK is installed (and what version of R2 ?)

Share this post


Link to post
Share on other sites

perhaps you need to be using MDT 2013 preview from here http://blogs.technet.com/b/configmgrteam/archive/2013/06/26/microsoft-deployment-toolkit-2013-preview-now-available.aspx

i havn't tried it yet though, I assume the above is for your LAB use, as you should not be installing R2 preview in production.

Share this post


Link to post
Share on other sites

Correct. Using in the lab.

I fixed this issue by installing MDT 2013 and Removing MDT extensions for SCCM and re installing MDT extensions.

 

But now i have a new problem :)

Creating UDI task sequence.

 

After MDT package step "select existing MDT package", it skips OS image, Deployment Method and Client package and goes right to USMT Package.

 

How can i set OS image and client packages?

 

Thanks.

Share this post


Link to post
Share on other sites

first things first, did you read the release notes to verify that that is not a bug ?

Share this post


Link to post
Share on other sites

I have just followed this with great interest and have deployed it as your instructions.

 

However into the installation I get this error

 

2013-10-11132206.jpg

 

and then when I click ok the PC reboots and then I get into a loop with this error

 

2013-10-11132725.jpg

 

I was using the GB version of the preview file.

Share this post


Link to post
Share on other sites

well the problem is in the pass specialize as it says so you'll need to check your unattend.xml file to see what the issue is, smsts.log should also give you some more clues.

Share this post


Link to post
Share on other sites

hello anyweb,

 

i'm nubie in sccm 2012 and i have a question for this topic..

if i wan to upgrade from windows 8 enterpise to windows 8.1 through sccm 2012

what should i do ?

or can i upgrade use this (this topic) step ?

Share this post


Link to post
Share on other sites

it's not supported to 'upgrade' the operating system, so the supported method would be to do a refresh, ie, capture user data, wipe the hdd and then install Windows 8.1 before restoring the data

Share this post


Link to post
Share on other sites

it's not supported to 'upgrade' the operating system, so the supported method would be to do a refresh, ie, capture user data, wipe the hdd and then install Windows 8.1 before restoring the data

 

what do mean capture user data ?

 

i have more than 100 users pc installed windows 8, and i want upgrade all of the pc's.

do you mean "capture user data" is backup the data, and restore it on new pc installed windows 8.1 ?

Share this post


Link to post
Share on other sites

I mean use scanstate in USMT to capture the data and then loadstate in usmt to restore it.

Share this post


Link to post
Share on other sites

One, maybe slightly odd, question I have lol...

 

When I use WinPE now (for 7 or 8 OSD), I don't get the fish :P.

I'm currently running the Boot Image V 6.3.9600.16384 (both on x86 and x64). This is a slightly later version than yours I presume. I used the ADK 8.1 from your guide to upgrade to SCCM 2012 R2 as well.

 

I was just wondering, has this since been changed again, or am I missing something?

 

Thanks,

 

Phil

Share this post


Link to post
Share on other sites

the fish was jut part of Windows 8.1 preview

Share this post


Link to post
Share on other sites

well the fish has come and gone twice with to 'public betas' of Windows 8, so it's quite likely we'll see another version of it in the future :)

Share this post


Link to post
Share on other sites

I have a related question maybe you can help me with.

 

We deployed 2012 SCCM R2 and successfully deployed a 8.1 image. All was great and wonderful. We made some changes ot the base image and the task sequence and kicked off another PXE boot on the same box. It took the image went all the way through and when I logged on... no applications. I mean NONE. Nothing on the start screen, nothing when you searched. Incidentally, the machine logins with domain credentials as well.

 

I mucked around with the image, reverted back to one with no patches, no .NET 3.5. No good. Ok, back to the original OS image and task sequence. Same result.

 

This baffles me. We did make changes to the SCCM server (we WERE in the middle of migrating from SCCM 2007) but the Windows 7 SP1 images we are making still work fine and and deploy applications.

 

I'm going to pull a new OS image (in case it got corrupted somehow) and build a new task sequence but the originals are untouched (i made copy of the task sequence before I modified it and the image is till there untouched on the server) so I am quite confused about what could cause this.

 

Thanks for any help!

 

 

Share this post


Link to post
Share on other sites

I've a similiar problem like above this post.

 

Installation of Windows 8.1 Pro works well. But Configuration Manager Client and the follwing software gets not installed. Domain integration worked well.

After Login the prepartion of Win8.1 goes on:

47772,024windows81propreviewtortmalmostr

 

How to integrate this step into the TaskSequence? I don't want that the users have to wait after TaskSequence has finished.

 

What are the problems of this two problems?

Share this post


Link to post
Share on other sites

I have just followed this with great interest and have deployed it as your instructions.

 

However into the installation I get this error

 

 

 

and then when I click ok the PC reboots and then I get into a loop with this error

 

 

 

I was using the GB version of the preview file.

 

I'm running into the same issue as edie. The trick is, I'm not using an unattend.xml, just the task sequence. SMSTS.log isn't any help, either, since it ends showing no errors. I tried creating an unattend.xml and editing out the Windows Shell entry from the specialize pass, but the same error shows up. Any leads?

Share this post


Link to post
Share on other sites

My OSD of windows 8.1 failed. But I can't seem to find out why. I have copied the smsts.log from the client after partitioning and copying files from X:\smstslog\smsts.log. Only thing that has an other colour (Yellow) in the log is "Client agent branding title is empty. Ignoring. TSPxe 5-3-2014 15:55:00 1248 (0x04E0)"

Further I can't see any errors.

smsts.log

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

×