Jump to content


chimmez

Windows 10 ADK & SCCM 2012 R2 SP1

Recommended Posts

Hi all,

 

I'm interested in seeing the current state of Windows 10 deployment using SCCM 2012 R2 SP1 in my lab. However, I'm running into a little bit of trouble. Firstly, I'm running SCCM 2012 R2 SP1 (ie, the latest version), which was upgraded with the Windows 8.1 ADK. Since then, I've downloaded and installed the Windows 10 ADK (https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx - right at the bottom). My first issue was that 'copype.cmd' wouldn't work, but I fixed that by manually inserting some variables into the a copied script called 'copype-test.cmd'.

 

As we all know, this creates a winpe folder wherever specified. From there, I grabbed the winpe WIM from the sources folder, and imported it into system center. This is what I assume to be WinPE10. However, although it is distributed, and then deployed from the PXE site server, clients will not boot using it. If it is the only boot.wim on the PXE server, a client will simply sit at the PXE service screen, and if it is just the last boot.wim image to be deployed from the PXE site, clients will use the old, 8.1 boot image. Furthermore, if I check the properties of the WinPE 10 boot.wim, I don't get the usual options (ie, add drivers etc) that one would usually expect from the properties dialog.

 

Have I had a brain-fade and forgotten a basic step when importing a boot image? Or, is this an issue with using the Win10 ADK (although I did read that SCCM 2012 R2 SP1 did support the new ADK...) I'm not at work for another 14 or so hours, but I can VPN in if someone has an idea of what the issue could be.

 

Thanks!

Chimmez.

Share this post


Link to post
Share on other sites

from the FAQ - http://blogs.technet.com/b/configmgrteam/archive/2015/05/19/sysctr-2012-configmgr-sp2-and-systctr-2012-r2-configmgr-sp1-faq.aspx

 

  • Which version of the Windows ADK should I use with System Center 2012 Configuration Manager SP2 or System Center 2012 R2 Configuration Manager SP1?
    • System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1 use the Windows Assessment and Deployment Kit 8.1. This version is required beginning with R2. If your sites currently run System Center 2012 Configuration Manager SP1, before you run Setup, on the site server and on each computer that runs an instance of the SMS Provider you must uninstall the Windows Assessment and Deployment Kit 8.0, and then download and install Windows Assessment and Deployment Kit 8.1.
    • For more information see Prerequisites For Deploying Operating Systems in Configuration Manager.
    • You can find the latest version of the Windows Assessment and Deployment Kit 8.1 on the Microsoft Download Center.

i'm guessing that you are testing something that is compatible with SCCM 2016 (the tp release) which does have windows 10 support baked in,

 

This Technical Preview includes support for Windows 10 with existing Configuration Manager and Endpoint Protection features as well as additional enhancements for operating system deployments, software update management, device management, and more. As a reminder, these are early pre-release builds. Many of the features and scenarios are still in development. As such, this preview is not intended for production environments, labs, nor full evaluations.

Need more information about System Center Configuration Manager and Endpoint Protection Technical Preview? See Technical Preview product documentation.

 

 

however have you tried modifying your boot wim as i describe in this old post here..

 

http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/

  • Like 1

Share this post


Link to post
Share on other sites

from the FAQ - http://blogs.technet.com/b/configmgrteam/archive/2015/05/19/sysctr-2012-configmgr-sp2-and-systctr-2012-r2-configmgr-sp1-faq.aspx

 

  • Which version of the Windows ADK should I use with System Center 2012 Configuration Manager SP2 or System Center 2012 R2 Configuration Manager SP1?
    • System Center 2012 Configuration Manager SP2 and System Center 2012 R2 Configuration Manager SP1 use the Windows Assessment and Deployment Kit 8.1. This version is required beginning with R2. If your sites currently run System Center 2012 Configuration Manager SP1, before you run Setup, on the site server and on each computer that runs an instance of the SMS Provider you must uninstall the Windows Assessment and Deployment Kit 8.0, and then download and install Windows Assessment and Deployment Kit 8.1.
    • For more information see Prerequisites For Deploying Operating Systems in Configuration Manager.
    • You can find the latest version of the Windows Assessment and Deployment Kit 8.1 on the Microsoft Download Center.

i'm guessing that you are testing something that is compatible with SCCM 2016 (the tp release) which does have windows 10 support baked in,

 

 

however have you tried modifying your boot wim as i describe in this old post here..

 

http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/

 

 

 

Thanks for the link, I'll give it a shot now!

 

As far as where I found that R2 SP1 supported the Windows 10 ADK, I swear that it was posed on technet under which ADK is required, something like "A minimum of the Windows 8.1 ADK, and the Windows 10 ADK is now supported", however I can't find it now. Furthermore, this photo (http://i2.wp.com/ano...-R2-SP1-SP2.jpg) shows that the 10 ADK is at least going to be supported.

No big deal anyway, just keen to try some new System Center stuff!

Thanks again.

Share this post


Link to post
Share on other sites

Just a quick update - by following the steps that you provided in the link above (http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/) I was able to get SCCM 2012 R2 SP1 to PXE boot using the Windows 10 ADK and the new version of WinPE.

 

All that I did was use the 10 ADK toolkit environment, and, modify the targets for the packages to:

 

dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab"
dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WDS-Tools.cab"
dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-HTA.cab"
dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-MDAC.cab"
dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-NetFx.cab"
dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\winpe-securestartup.cab"
dism.exe /image:c:\WinPEMount\x64 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab"
Strangely this has also dramatically increased the speed in which OS WIMs images are downloaded from my SCCM server - it now maxes the server's upload (1 gigabit/sec), whereas with the previous boot images that I've created, it was generally capped to 100 megabits/sec, which has been an annoying problem on our production SCCM server since the R2 update (ie, it was really quick in SCCM 2012, R2 up to and including CU3 seemed to slow OSD down considerably).
Thanks for your help!
  • Like 1

Share this post


Link to post
Share on other sites

 

As far as where I found that R2 SP1 supported the Windows 10 ADK, I swear that it was posed on technet under which ADK is required, something like "A minimum of the Windows 8.1 ADK, and the Windows 10 ADK is now supported", however I can't find it now. Furthermore, this photo (http://i2.wp.com/ano...-R2-SP1-SP2.jpg) shows that the 10 ADK is at least going to be supported.

 

 

 

Configuration Manager SP2 uses the Windows Assessment and Deployment Kit (Windows ADK) to deploy an operating system. Before you run setup, you must download and install the Windows ADK on the site server and the provider computer. Whilst the prerequisite for setup is still the Windows 8.1 ADK, Configuration Manager now supports the Windows 10 ADK also.

https://technet.microsoft.com/library/mt131422.aspx#BKMK_OSD

 

I'm in the same boat. (installed with 8.1 ADK). Anyone got a supported process for upgrading, or is the manual hacks above what is required?

Share this post


Link to post
Share on other sites

Hello,

 

I found two articles that discuss the migration path.

 

1) http://blogs.msdn.com/b/beanexpert/archive/2015/08/05/how-to-switch-to-windows-10-adk-on-configmgr-2012-r2-sp1.aspx

2) http://blogs.technet.com/b/brandonlinton/archive/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager.aspx

 

Both appear very similar, but option #1 had less manual things to do. I went ahead and did it and so far everything appears to work.

Share this post


Link to post
Share on other sites

Hi boys,

 

I'm about to loose my head in concern of the 1Gbps speed of the OSD in SCCM 2012 R2 (SP1 CU2), I have read all the related topics on how to boost the connection and still cannot get the desired speed.. I did what Chimmez posted and it did not work..

 

From layer 1 to 7 I'm plugged and set to 1 Gbps, I'm testing in a lab environnement with VMs, could it be the boot image that makes the difference with the speed at the end or is it a setting in vmware ... ?

 

Thank you for the help,

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...