anyweb

Introduction In a previous post I showed you how you can deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager. In this post I'll show you how to do the same thing with Microsoft Deployment Toolkit (MDT) 2013, except this is fully automated, all you have to provide is a server, the operating system files and change a few variables in the script. Note: As this is fully automated, and as this does install a WDS server role hosting a boot image, you should test it in a lab first and modify the script accordingly. There are many PowerShell scripts out there to create fully automated labs (hydration kits) from MDT gurus like Johan Arwidmark or Mikael Nystrom or upcoming cool dudes like Nickolaj Andersen, but this script is tailored for one thing only, deploying Windows 8.1 x64 to the Microsoft Surface Pro 3 with all drivers loaded. You may want to download it and customize it to suit your needs for other hardware because what it does is pretty cool. This script performs the following actions:- Downloads and then Installs Windows ADK 8.1 (if you have not done so already) Downloads and then Installs MDT 2013 (if you have not done so already) Downloads all required drivers for Microsoft Surface Pro 3 (see screenshot below) Adds the Windows 8.1 x64 operating system into MDT Adds the Microsoft Surface Pro 3 drivers into MDT (see screenshot below) Creates Selection Profiles for Microsoft Surface Pro 3 and WinPE x64 (see screenshot below) Creates a Deploy Windows 8.1 x64 - Surface Pro 3 task sequence Edits the Deploy Windows 8.1 x64 - Surface Pro 3 task sequence and adds an inject drivers step for Microsoft Surface Pro 3 (see screenshot below) in addition, it sets the WMI query for the Surface Pro 3 on that step (see screenshot below) Injects the Microsoft Surface Pro 3 network drivers into the LiteTouchPE_x64.wim Creates new CustomSettings.ini and BootStrap.ini files Disables the X86 boot wim (not needed for Surface Pro 3) Changes the Selection Profile for the X64 boot wim to use the WinPE x64 selection profile (see screenshot below) Installs the Windows Deployment Service role Configures the WDS role and adds the previously created LiteTouchPE_x64.wim (see screenshot below) Starts the WDS service so that you can PXE boot (UEFI network boot).All you have to do is download the script below, then place some files in the right place, PXE boot a Microsoft Surface Pro 3 and sit back and enjoy the show. So let's get on with what you need to do... Step 1. Download the script This PowerShell script will do all the hard work for you, download it and place it on your server that is designated to be the MDT 2013 server. I've tested it on Server 2012R2 only, if you run it on a different operating system and have issues then post your results below. Setup MDT 2013 for Microsoft Surface Pro 3.zip Update: I've updated the script above to include the March 2015 drivers and updates and it's available here. Step 2. Configure the variables in the script Once you have downloaded the script, you should configure the variables interspersed throughout the script, the most important of them is the $SourceFolder variable as this decides where to get the content from (if you've copied it already) and where to store it. This variable should point to a valid drive letter, the folder name will be created if it does not exist. The $FolderPath variable will be the MDT Deployment share root folder eg: E:\DeploymentShare. There are other variables to configure, scroll down through the script to find them, such as the ones below You will also want to edit the CustomSettings.ini and BootStrap.ini settings within the script to suit your own environment. Step 3. Copy the Windows 8.1 x64 operating system files Mount a Microsoft Windows 8.1 x64 Enterprise ISO and copy the contents to $SourceFolder\Operating Systems\ as shown below Step 4. Copy MDT 2013, ADK 8.1, Surface Pro 3 drivers (optional) If you've already downloaded the above files then place them in the source folder, otherwise the script will download them for you. In the screenshot below you can see I'm manually copying the offline ADK 8.1 files, you do not have to do this as the script will download the content for you if it's not found. Step 5. Copy your Applications to the respective folders (optional) If you have apps like Office 2013, copy them to their respective folders as shown below If you do add apps, then you'll also need to change the following section of CustomSettings.ini SkipApplications=YES to SkipApplications=NO Step 6. Run the script On the server that is to be your MDT server, start the script in PowerShell ISE or which method you prefer, below you can see the script in action, it has just created the selection profiles for the Surface Pro 3 After the script is complete, you are ready to test deploying a Microsoft Surface Pro 3 installation. and below you can see the E:\Source folder after the script has run, it has downloaded a bunch of stuff ! Step 7. Sit back and watch the deployment Take a properly shutdown Surface Pro 3, and power it on using the following sequence Hold the down volume key and then press the power button while continuing to hold down the volume key, it should PXE boot Press enter when prompted and then it will load the MDT LitetouchPE_X64 boot wim. before prompting you for a computername, note that it's currently set to SurfacePro3, you can change it in the UI itself or automate it via the many methods available such as those that Mikael describes here click next and off it goes, inject the Surface Pro 3 drivers (oh and of course, you've got working network in WinPE as the network drivers were added to the boot wim already) and after a wee while, it's done. Troubleshooting If the script has issues starting WDS (and you see the error below) then restart the server, as you were asked to do at the end of the script ;-). For deployment issues, you can review the logs found in the following locations depending on what part of the OSD process you are in:- In WinPE X:\windows\temp\SMSTSLOG In Windows C:\Windows\Temp\DeploymentLogs C:\MININT\SMSOSD\OSDLOGS C:\Users\Administrator\Appdata\Local\temp\SMSTSLog Summary Automating the deployment of Windows 8.1 x64 Enterprise to the Microsoft Surface Pro 3 is not only possible but relatively easy with MDT 2013 and a custom powershell script like the one above. I must also say a big thanks to Nikolaj who helped me with some issues in the script, you are awesome ! Related Reading Using PowerShell to modify settings in MDT 2013 - http://www.scconfigmgr.com/2014/08/23/using-powershell-to-modify-settings-in-mdt-2013/ Where do I find the MAC address of my Surface Pro 3 Ethernet Adapter in order to use UEFI network boot ? - http://www.niallbrady.com/2014/09/11/where-do-i-find-the-mac-address-of-my-surface-pro-ethernet-adapter-in-order-to-use-uefi-network-boot/ Why is my Surface Pro 3 not BitLockered after OSD via System Center 2012 R2 Configuration Manager ? - http://www.niallbrady.com/2014/09/18/why-is-my-surface-pro-3-not-bitlockered-after-osd-via-system-center-2012-r2-configuration-manager/ Why does my Surface Pro 3 take a very long time to UEFI Network Boot using System Center 2012 R2 Configuration Manager ? http://www.niallbrady.com/2014/09/09/why-does-my-surface-pro-3-take-a-very-long-time-to-uefi-network-boot-using-system-center-configuration-manager-2012-r2/ Surface Pro 3, Surface Pro 2, and Surface Pro firmware and driver packs http://www.microsoft.com/en-us/download/details.aspx?id=38826 Updating the UEFI firmware offline - http://blogs.technet.com/b/askpfeplat/archive/2014/10/20/how-to-update-the-surface-pro-3-firmware-offline-using-a-usb-drive.aspx Deploy Windows to Surface Pro 3 using Microsoft Deployment Toolkit

MMS is back ! The folks putting on the Midwest Management Summit were able to get the hotel to extend conference room discount pricing, so they are also extending the normal conference registration price until Friday, October 17th. After that, you would have to pay full price for the conference and hotel rooms. The Midwest management Summit is a 3-day conference purposely capped to just 500 attendees so that nobody gets lost in the crowd. Almost 60 Microsoft MVP’s will be presenting real-world solutions to systems management challenges with ConfigMgr, OpsMgr, SCOrch, PowerShell, and more. Hotel Rooms Discount If you are using our user group discount code, you’ll need to book the discounted hotel room rate through https://www.radissonhotels.com/en-us/hotels/radisson-blu-bloomington-mall-of-america using the promotion code ‘MNSCUG’ before Friday, October 17th. Midwest Management Summit November 10-11-12, 2014 http://mms.mnscug.org Twitter and Facebook The MMS Conference Committee Key Contacts: Nash Pherson – User Group Coordinator – nash@mnscug.org Kalsey Beach - Event Coordinator - kalsey@dogoodevents.com MMS Conference Committee - Everybody - mms@mnscug.org

what does your smsts.log file tell you when it comes to installing that driver package ?

hi you posted your questions on the end of someone elses thread, and they weren't related so I separated this, in future, please raise a new topic when posting your questions.

have you verified the contents of the unattend.xml file before and after setup windows and configmgr step ?

test the package by running it in a cmd prompt as system with psexec, this will show you the problem

looks like you've no ip address or network issues, did you add any drivers for your network card/hardware and did you look at the log you posted ?

I'm happy to help you succeed in your goal, if you want me to guide you to getting things right then I will help you no problem at all, good luck

I'm very happy to say that I was once again awarded as an Enterprise Client Management MVP this year, that's 5 years in a row. I received the actual award today and here it is, the packaging and look is much nicer than previous years ! thanks a million Microsoft for giving me the honor of having this award for another year (my fifth !) and thanks to my family for supporting me with all this, and thanks to all of the loyal members of windows-noob.com and niallbrady.com !! cheers niall

ok I made two downloads available, one for SP1 and one for R2, which one did you use ?

a few pointers for you, firstly, I assume it's because you are Swedish, but it would be better to change learnmesccm to TeachMeSCCM, as that would make more sense as in Gramattically "I teach, you learn." and secondly, I had a brief look at your website and it's confusing the way it's laid out, hard to find any 'workflows' and when you do find them, they don't really make much sense, sorry not trying to bash you but rather to guide you to make it more user friendly cheers niall

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

they are all together, in the All Software Updates node, follow the guides above and you'll be more clued in to the overall picture there is one thing you must know though, the guides I write show you ONE way of doing things, Configuration Manager 2012 is very flexible so you can do things whichever way works best for your company cheers niall

why not just follow these ? using System Center 2012 Configuration Manager - Part 9. Deploying Monthly Updates using System Center 2012 Configuration Manager - Part 10. Monitoring our Monthly Updates Automatic Deployment Rule

do you have MDT integrated with Configuration Manager ? if not you need to

because it's a lab, and it's purpose is to show you how to set one up, if you want a remote SUP then that is not an issue, simply create it that way.

well if it's failing at the client installation, what does the ccmsetup.log tell you ?

have you tried to click ok and select an action from the drop down menu,

you do NOT need an Intune account to deploy the Surface Pro 3 with CM12 R2, see my guides here. CM12 in a Lab - Why is my Surface Pro 3 not BitLockered after OSD via System Center 2012 R2 Configuration Manager ? CM12 in a Lab - Where do I find the MAC address of my Surface Pro 3 Ethernet Adapter in order to use UEFI network boot ? CM12 in a Lab - How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using System Center 2012 R2 Configuration Manager ? CM12 in a Lab - Why does my Surface Pro 3 take a very long time to UEFI Network Boot using System Center 2012 R2 Configuration Manager ?

good post, would be nice if you updated it with screenshots as we love screenshots here :-)

can you clarify exactly what your issue is here ? show me a screenshot of the problem...the drive label is set in the format steps... are you using any variables in there (osdisk)

I haven't tested it with Windows 10 yet but you can be sure I'll modify it to work with Windows 10 once Windows 10 hit's RTM and it's supported in Configuration Manager 2012

yup look at this post http://www.niallbrady.com/2011/08/31/missing-nic-driver-in-winpe-boot-image-no-problem/

welcome to the forums ! :-) here's a guide to help with Migrations, and it now works from CM12 > CM12 which should solve your issue http://www.windows-noob.com/forums/index.php?/topic/4926-using-sccm-2012-rc-in-a-lab-part-14-performing-a-side-by-side-migration-from-configuration-manager-2007/

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.