How can I deploy Windows 10 Enterprise using System Center 2012 R2 Configuration Manager ?

[anyweb]

Update: Since Windows 10 was released in July, I've produced a new guide which replaces this one, you can read it here.

 

 

 

Note: This post was done using a technical preview version of Windows 10 and due to that fact, Configuration Manager 2012 R2 does not currently support this (or any) version of Windows 10. As a result, this is not supported by Microsoft. I'm only doing this because I want to see if it's possible to deploy Windows 10 with the current release of Configuration Manager, which at the time of writing (Oct 1st, 2014) is 2012 R2 CU3.

 

Please also read the Support statement from Microsoft about Windows 10 here of which I'm copying the relevant bits below:

 

• The next version of System Center Configuration Manager will deliver full support for client deployment, upgrade, and management of Windows 10 and associated updates.
• System Center 2012 R2 Configuration Manager or SP1 - we will provide an update to support Windows 10 deployment, upgrade and management with existing ConfigMgr features.
• System Center Configuration Manager 2007 (SP2, R2, and R3) – we will provide an update to support the management only of Windows 10
• Microsoft Deployment Toolkit (MDT) will be updated with support for Windows 10.

 

Step 1. Download the ISO and Extract the contents

Download Windows 10 Technical Preview Enterprise edition from here, I used the X64 Enterprise ISO (9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US.ISO) for my Guide.

I then Mounted that ISO in my Configuration Manager 2012 R2 Hyperv virtual Machine and extracted the contents to \\server\sources\os\os_media\Windows10x64

 

 

you might also want to download the technical preview guide from here.

 

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

 

 

browse to the path where we extracted it in Step 1



fill in some details about the image



and click next through to the summary



Step 3. Distribute the image to your distribution points

 

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



and continue through the wizard

 

 

and continue through to completion

 

Step 4. Create the Build and Capture Task Sequence

In task sequences, right click and choose Create Task Sequence



Choose the Build and Capture a reference operating system image option



fill in the details and choose a X64 boot image



Next, edit the Install Windows step, select any OS other than Windows 10 (which won't show up anyway, we'll add it later), in this screenshot I selected Windows 8.1 Enterprise.

 

Note: We will edit this step later.

for network select to join your domain and enter the credentials required



select your Configmgr Client in the next step then next your way through on to the Capture image step (if you get any capture wim filename error, ignore it), fill in your capture details, click next through to summary



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

 

Note: if you are deploying to real hardware, you should be using Apply Driver Package steps however check this post from Johan on the subject.

 

And edit the Apply Operating System Image step, so that it points to our Windows 10 installer instead of a previously captured Windows 8.1 image as shown below

 

 

Edit the Apply Windows Settings step, for Product key, use the key contained in the media's sources folder, in a file called PID.TXT file, otherwise the Setup Windows and Configmgr step will fail (error 31) later on in the process.

 

Step 5. Deploy the Task Sequence

Right click on the task sequence and choose Deploy,



point it to the All Unknown Computers Collection, choose an Available (optional) purpose, and continue through the wizard until completion.



Step 6. 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



select your Deploy Windows 10 Enterprise Task sequence and press enter, it starts applying the OS

 

I'm monitoring the installation using cmtrace...

 

once the operating system image files are copied down, the Operating System installation starts..and the os installation begins

 

 

 

followed by a reboot

 

and after the first reboot we get our first look at Windows 10 Technical Preview setting itself up, it looks a lot like Windows 8.1 :-)

 

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



and we are done ! or are we

 

 

yes, we are done !

 

 

 

 

 

Summary

 

It just goes to show, that with a little effort, you can deploy Windows 10 Enterprise edition using System Center 2012 R2 Configuration Manager. Awesome.

[Peter van der Woude]

Works like a charm! Also, I did the same by simply using the install.wim and that also works like a charm!

[netrrhexis]

Deployment works for me until configuring devices. As soon as that finishes I get the dreaded "Specialize" pass error. I am get this with Installation Source or Install.wim methods. I am not using a unattend.xml just CM TS.

[anyweb]

that's odd, did you follow my instructions exactly ? what is inside your unattend.xml found in C:\Windows\Panther\Unattend?

[thadkew]

That works perfectly.
Don't know what I would do without you, Niall. Thanks so much.

 

[ashr1uk]

Hi everyone

I'm new to this forum and am looking forward in participating.

 

I signed up today as I wish to know if anyone knows when

 

SCCM 2012 R2 Endpoint protection will be available to Windows 10? I have installed Windows 10 via sccm 2012 R2 and all is well. The client has been installed, and I can easily push out software to the windows 10 machines.

The only thing I cant do (automatically or manually) is to install FEP 2010. Any ideas anyone?

 

The other issue I had, before I gave up was trying to capture an image from a freshly built Windows 10 laptop. The laptop constantly failed at the SYSPREP stage.

 

Are these errors due to SCCM 2012 R2 not yet being compatible with Windows 10?

 

Thanks for your help guys.

[anyweb]

as Windows 10 is not finished yet, there is no SCEP version for it yet, it does however have Windows Defender included. I would expect to see support for Windows 10 being improved once SP2 for SCCM 2012 R2 ships. As regards sysprep it works for me, have you seen this

[anyweb]

actually, you are in luck (if using Intune standalone), see here

 

Ability to manage Windows Defender on Windows 10 PCs running Windows 10 Technical Preview without need for separate Microsoft Intune Endpoint Protection agent to be installed

 

via > http://blogs.technet.com/b/microsoftintune/archive/2015/04/17/new-intune-features-coming-over-the-next-week-for-android-and-more.aspx

[CraigSCCM]

smsts-20150521-115237.log

 

I built a Windows 10 Image, went to capture it using Sys Prep, but it failed i don't now why

 

It;s exactly the same way i did all the windows 7 & 8.1 builds

 

The SMSTS log display a tonne of errors

 

Sys Prep did not complete successfully Error 80004005

 

Exiting error code 16389

 

SMSTS Log attached

 

Any help would be greatly appreciated

 

Thank you

[achint]

The new driver with windows 10 version(see driver inf section heading below) is not compatible with SCCM 2012 SP2 and so all these windows 10 drivers are failing to imported to sccm driver catalog. See the DriverCatalog.log.

 

SCCM Version: SCCM 2012 R2 SP1 (5.0.8239.1000)

ADK Version : ADK for Windows 10 (10.0.10114)

OS version: Windows Server 2012 (6.2.9200)

 

Driver INF Section

 

[Manufacturer]

%Intel% = Intel, NTamd64.10.0, NTamd64.10.0.1

DriverCatalog.log

<![LOG[CreateFromINF("\\W12SCCM12R2.jigsaw.com\shared\Achint\Windows10-x64", "E1C65x64.inf")]LOG]!><time="13:03:07.897-330" date="05-26-2015" component="DriverCatalog" context="" type="1" thread="1328" file="osddrivercatalog.cpp:919">

<![LOG[initializing driver digest from '\\W12SCCM12R2.jigsaw.com\shared\Achint\Windows10-x64\E1C65x64.inf']LOG]!><time="13:03:10.462-330" date="05-26-2015" component="DriverCatalog" context="" type="1" thread="1328" file="osddriverdigest.cpp:2835">

<![LOG[\\W12SCCM12R2.jigsaw.com\shared\Achint\Windows10-x64\E1C65x64.inf is not applicable to any supported platforms.]LOG]!><time="13:03:11.210-330" date="05-26-2015" component="DriverCatalog" context="" type="3" thread="1328" file="osddriverdigest.cpp:3039">

<![LOG[Driver is not applicable to any supported platforms. Code 0x80070661]LOG]!><time="13:03:11.210-330" date="05-26-2015" component="DriverCatalog" context="" type="3" thread="1328" file="osddrivercatalog.cpp:844">

[Peter33]

Edit the inf file and delete everything in the section [ControlFlags]. See if that helps and will let you Import the drivers.

[anyweb]

i'd like to see what the inf file looks like can you attach it

[Robbie Wallis]

Mine seems to fail installing the configmgr client?

<![LOG[installing file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' with options '/quiet /norestart'.]LOG]!><time="22:28:46.399-60" date="08-01-2015" component="ccmsetup" context="" type="1" thread="2868" file="manifest.cpp:2189">
<![LOG[File 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' returned failure exit code 775. Fail the installation.]LOG]!><time="22:28:48.728-60" date="08-01-2015" component="ccmsetup" context="" type="3" thread="2868" file="manifest.cpp:2239">
<![LOG[installFromManifest failed 0x80070307]LOG]!><time="22:28:48.728-60" date="08-01-2015" component="ccmsetup" context="" type="3" thread="2868" file="ccmsetup.cpp:7202">
<![LOG[A Fallback Status Point has not been specified. Message with STATEID='311' will not be sent.]LOG]!><time="22:28:48.728-60" date="08-01-2015" component="ccmsetup" context="" type="1" thread="2868" file="ccmsetup.cpp:9767">

[anyweb]

you can include this in your Setup Windows and ConfigMgr step

 

/skipprereq:windowsupdateagent30-x64.exe

[carsontl]

Hi Niall, in your instructions here you state

 

 

 

Edit the Apply Windows Settings step, for Product key, use the key contained in the media's sources folder, in a file called PID.TXT file, otherwise the Setup Windows and Configmgr step will fail (error 31) later on in the process.

 

Does this still apply to the official windows 10 enterprise release? I searched the entire cd and did not find a PID.txt.

I did get a new key to use from MS Partner and I put that into the "apply windows settings" but i'm still getting the error 31 during Setup Windows and Configmgr.

 

Thanks for any help,

 

Tom

[anyweb]

no this does not, these instructions were only for the preview release that was released back in October 2014,

to deploy Windows 10 today you don't need the PID for the enterprise version, it will activate using KMS, unless of course you want to use the MAK key.

[kirbyrutt]

Hi Getting the same issues when importing new drivers for the Dell E7450 from the Dell .Cab file, Same error "Driver is not applicable to any supported platforms."

[anyweb]

have you applied CU1 yet ? it fixes the import of Windows 10 drivers problem.

 

http://www.niallbrady.com/2015/08/05/cumulative-update-1-for-configmgr-2012-sp2-and-configmgr-2012-r2-sp1-is-now-available/

[jrgonzalez_nyc]

Thanks Niall for always keeping us up to date. I usually come here first for all my SCCM issues.

 

Do you know if we will still need Johans workaround as well, ( http://deploymentresearch.com/Research/Post/443/Beyond-unsupported-Deploying-Windows-10-preview-including-drivers-with-ConfigMgr-2012-R2 )

in order to get drivers to deploy during OSD? Or will the CU1 patch take care of this as well?

 

Best Regards,

 

Joe

[anyweb]

you only need Johan's workaround if still using SCCM 2012 R2 (not upgraded to SP1 CU1).

[mmenzie]

now that Windows 10 Enterprise is released in full will you be updating this articles step by step OP with updated information?? I am looking to test this out with the fully released version and using a KMS key

[anyweb]

already done, and here it is

 

• CM12 in a Lab - How can I deploy Windows 10 Enterprise x64 with MDT 2013 Update 1 integrated with System Center 2012 R2 SP1 Configuration Manager ?
• CM12 in a Lab - How can I upgrade to System Center 2012 R2 SP1 with MDT 2013 update 1 integrated ?

[proweb01]

Windows 10/SCCM are working great and I'm glad that Microsoft built SCEP into Defender, but the UI is extremely limiting. We can no longer allow the clients to do simple things that we've been able to before, such as restrict the CPU usage that a scan uses. http://www.proweb-solutions.net/blog/sccm-2012-r2-sp1-windows-defender-explained/

[jkrato]

Deployment works for me until configuring devices. As soon as that finishes I get the dreaded "Specialize" pass error. I am get this with Installation Source or Install.wim methods. I am not using a unattend.xml just CM TS.

I got the same thing from a captured wim I was trying to deploy. I found this fix.

 

http://heresjaken.com/the-computer-restarted-unexpectedly-or-encountered-an-unexpected-error-during-installation-of-windows/

 

Basically changing a registry entry "HKLocalmachine/SYSTEM/SETUP/STATUS/ChildCompletion" from 1 to 3.

Don't know what caused it but once I change the entry it finally stops restarting and starts up windows.

However, it isn't working like it should. Nothing happens when you click the start button. Cant use the search bar either....

 

Any thoughts?

[Rajasekarg]

Is MDT 2013 Integration is mandate for Win 10 OSD ?? Or this ll work independent like Win 8.1 deployment.