anyweb

don't use copyprofile it causes more problems than it fixes

works fine, are you guys using copyprofile ? if so that's the cause of your issues

did you try following this guide ?

Introduction At the start of this series of step by step guides you installed System Center Configuration Manager (Current Branch), then you configured discovery methods. Next you configured boundaries to get an understanding of how automatic site assignment and content location works. After that you learned how to update ConfigMgr with new features and fixes using a new ability called Updates and Servicing and you learned how to configure ConfigMgr to use Updates and Servicing in one of these two modes: Online mode Offline mode To prepare your environment for Windows 10 servicing (this guide) you learned how to setup Software Updates using an automated method (via a PowerShell script) or manually using the ConfigMgr console. Next you used a PowerShell script to prepare some device collections, then you configured client settings for your enterprise and finally you'll deployed the ConfigMgr client agent using the software updates method which is the least intensive method of deploying the Configuration Manager client agent. As System Center Configuration Manager (current branch) is being delivered as a service now, version 1602 was made available (March 11th, 2016) and you used Updates and Servicing to do an in-place upgrade to that version as explained here. Next you learned about how to use the Upgrade task sequence to upgrade your Windows 7, Windows 8 (and 8.1) and even your Windows 10 devices to a later build of Windows 10. You then learned about the new Windows 10 servicing features which use Servicing Plans in ConfigMgr (Current Branch). In this guide you will integrate MDT 2013 update 2. MDT integration with ConfigMgr is useful as it provides additional functionality for operating system deployment scenarios such as Offline Language Package installation or User Driven Integration (UDI). Note: This guide assumes that you have not yet enabled or configured a PXE distribution point or Network Access Account, if you have, then you can skip those steps. In addition, this guide assumes you have created a DHCP scope on your Active Directory Domain Controller and activated it. Step 1. Download MDT 2013 Update 2 Download the MDT 2013 Update 2 x64 MSI from the following link. In addition to downloading MDT 2013 Update 2, you might want to download the MDT ZIP file (located in the downloads section at the end of this post) which contains pre-created folders and files for use in the Create MDT Task sequence wizard. Simply extract it to the desired sources folder on your ConfigMgr server, for example: \\<ConfigMgrServer>\sources\osd\ the folders it creates are highlighted below after extraction Step 2. Install MDT 2013 Update 2 After you've downloaded the msi, it's time to install it. On your ConfigMgr server double-click the MSI and the wizard will appear accept the EULA and click next choose where you want to install MDT, for example on D:\Program Files\Microsoft Deployment Toolkit\ select if you want to participate in the CEIP or not and then click Install and accept the UAC prompt when complete, click Finish to close the wizard Step 3. Integrate MDT 2013 Update 2 with ConfigMgr Now that you have installed MDT you should integrate it with ConfigMgr. You do this to gain access to tools and features that MDT provides from within the ConfigMgr console. In the start screen, locate the newly installed Microsoft Deployment Toolkit application group, right click Configure ConfigMgr Integration shortcut and right click, choose Run as Administrator. The wizard settings will default to Install the MDT extensions for Configuration Manager the first time you run the integration after clicking next you should see output similar to below, if not, make sure you chose Run As Administrator Note: If the ConfigMgr console was open during this process, close it and then open it again to view the MDT integration. Step 4. Add the latest Windows 10 Enterprise x64 media I'd recommend you use the latest Windows 10 Enterprise x64 media from Microsoft Volume License site (or MSDN for a lab). The latest available media is updated with February Cumulative Updates for 1511. Mount the ISO using Windows File Explorer. After mounting the ISO, copy the contents to somewhere useful like: \\<ConfigMgrServer>\\Sources\OSD\OS\OSImages\Windows10x64\1511 to add the operating system do as follows. In the ConfigMgr console, select Software Library, then Operating Systems then Operating System Images. Right click and choose Add Operating System Image. Point it to the install.wim file in the sources folder of the Windows 10 Enterprise x64 media you just added and fill in some details about the image before continuing through that wizard until completion. Note: To make the image available on the network, distribute it to your distribution points by right-clicking and choose Distribute Content. Select one or more distribution points, and continue through that wizard until completion. Step 5. Configure a Network Access Account You'll need to configure a Network Access Account to allow content to be downloaded while in WinPE. To configure the Network Access Account do as follows: In the ConfigMgr Console, Administration workspace, select Site Configuration then Sites and right click on the Primary site listed (P01). Choose Configure Site Components, then Software Distribution. then choose Specify the account that accesses network locations, choose New and enter the credentials of the account you plan on using for Network Access. Apply the changes and close the wizard. Step 6. Enable PXE support on the Distribution Point Note: These actions install Windows Deployment Services files to C:\RemoteInstall, if you want to use a custom path or different drive letter then configure WDS manually before enabling PXE. This step assumes you have already configured a DHCP scope and activated it on your Active Directory domain controller. Enabling PXE support on the distribution point configures Windows Deployment Services automatically. To do this, open the Administration workspace and select a distribution point, right click and choose Properties. Select the PXE tab and use the following settings: Enable PXE support for clients Allow this distribution point to respond to incoming PXE requests Enable Unknown Computer support Require a Password when computers use PXE <P@ssw0rd> Allow user device affinity with Automatic Approval Click Apply when done. Step 7. Create MDT boot image, MDT Toolkit and MDT settings packages In order to utilize MDT within ConfigMgr, you need to create a few MDT components namely MDT Boot image MDT Toolkit Files MDT Settings These can be created the first time you create an MDT task sequence. To do that follow this process. In the ConfigMgr console browse to Software Library, Operating Systems, right click on Task Sequences and choose Create MDT Task Sequence. Choose a Template, there are several provided in the drop down menu listed below: Client Task Sequence Client Replace Task Sequence Microsoft Deployment Custom Task Sequence Server Task Sequence User Driven Installation Replace Task Sequence choose the default option which is Client Task sequence give the MDT task sequence a suitable name enter domain join details and choose an administrator password keep the default capture settings for Specify a boot image package to use, select the second option, create a new boot image package and browse to a previously created empty folder UNC path which contains a folder matching the version of WinPE and the Architecture of the boot image you are about to create, eg: \\<ConfigMgrServer>\Sources\OSD\boot\WinPE 10 x64 Note: If you used the MDT.ZIP file mentioned in step 1, then this folder will already be present. Also to note, do not place a backslash at the end of the path as ConfigMgr will add that to the path and you won't be able to distribute the boot wim later. fill in some details about the boot image then select the x64 Architecture and scratch space on the Components screen, browse through the list of components you want added to the boot image, for example if supporting Windows PowerShell add it here. On the Customization screen you get to choose background wallpaper, prestart commands and extrafiles in addition to enabling command support (F8). To enhance the built in logging ability you'll add smsts.ini via Extrafiles. I won't go into more detail about that other than to refer you to this post where everything is explained. Below you can see the smsts.ini file that is copied to an Extrafiles\Windows folder and in the customization screen, you point to that previously created path Next you get to create the MDT Toolkit Files package, so select the Create a new Microsoft Deployment Toolkit Files package option, and point it to a previously created path such as below: \\<ConfigMgrServer>\sources\osd\MDT\MDT2013u2\Toolkit fill in details about the MDT Toolkit Files package..be descriptive as it's common to have different versions of MDT Files over time Select your previously added Operating System Image (first option) For Deployment Method you get to choose the type of task sequence interaction will be used: Perform a zero touch installation os deployment, with no user interaction Perform a user driven installation if you want your users to have choices then select the UDI option, otherwise select the Zero Touch option to remove choices from the task sequence. for Client Package, select Specify an existing ConfigMgr client package and browse to the one you wish to use. for USMT Package select the User State Migration Tool for Windows 10 package For Settings Package, you need to create a new MDT 2013 Update 2 settings package, therefore select the second option. You only have to do this once for each version of MDT you have installed. Select Create a new settings package and fill in the path to be created as shown below something like: \\<ConfigMgrServer>\sources\osd\MDT\MDT2013u2\Settings\ for Sysprep Package, set No sysprep package is required and continue through to the end of the wizard and after a while you'll get a process completed successfully message. Note: If you want to create the WinPE 10 x86 mdt boot image, repeat the above, except do not create new toolkit and settings packages, and change the architecture of the boot wim for that step. Step 8. Distribute task sequence content At this point you are nearly ready to start testing, but first you need to distribute the task sequence content to your distribution points, the easiest way to do that is to right click on the Windows 10 x64 version 1511 - Zero Touch MDT task sequence and choose Distribute Content. the Distribute content wizard appears, listing all the packages in the task sequence select one or more distribution points by clicking Add and continue through the wizard until completion Step 9. Enable PXE support for the MDT boot image Browse to Software Library, Operating Systems, Boot images and select the WinPE 10 x64 boot image. Right click and choose Properties, and select the Data Source tab. Place a checkmark in Deploy this boot image from a PXE enabled distribution point. Repeat the above for the WinPE 10 x86 boot image. Step 10 . Deploy the task sequence Browse to Software Library, Operating Systems, Task Sequences and select the Windows 10 x64 version 1511 - Zero Touch task sequence. Right click and choose Deploy and use the following settings: For collection choose the OSD_Deploy collection (created in this guide) for Deployment Settings make sure it is set to Available and deployed to Only media and PXE and continue through the rest of the wizard until completion. Note: The last task sequence deployed (last in, first out or LIFO) will have an effect on which boot image is offered to PXE clients. If you require the WinPE 10 x64 boot image to 'answer' your clients, make sure it's attached to the last task sequence deployed. Step 11. PXE boot a computer Now everything is in place for testing a deployment of Windows 10 using an MDT 2013 Update 2 integrated task sequence in Configuration Manager (current branch). Simply PXE boot a computer that is a member of the OSD Deploy collection. While PXE booting, you can verify that the WIM file it's pulling down is indeed your newly created MDT 2013 update 2 boot image by looking at the boot image package id. after is has completed PXE boot the custom wallpaper is in place and the PXE password prompt is waiting enter the PXE password and choose the appropriate task sequence and off it goes... and you can see the familiar MDT background with information about the stages of deployment and after a while, it's all done ! Summary Using MDT integrated task sequences is relatively easy once you understand what needs to be put in place beforehand. In a later post you'll see how to use some of the added functionality that MDT integrated task sequences provide within the ConfigMgr console. Related Reading Planning for PXE-Initiated Operating System Deployments in Configuration Manager - https://technet.microsoft.com/en-us/library/hh397405.aspx How to Deploy Operating Systems by Using PXE in Configuration Manager - https://technet.microsoft.com/en-us/library/gg712266.aspx How can I use the Upgrade Task Sequence in System Center Configuration Manager (current branch) ? How can I use servicing plans in System Center Configuration Manager (Current Branch) to upgrade Windows 10 devices ? Downloads You can download a Microsoft Word copy of this guide here dated 2016/04/30 Deploying Windows 10 with MDT 2013 Update 2 in System Center Configuration Manager (current branch).zip Download a copy of the MDT files and folders used in the Create MDT task sequence wizard here MDT.zip

take a look at this post i wrote, maybe you have the same problem https://www.niallbrady.com/2016/03/29/why-does-windows-10-setup-prompt-to-choose-a-language-when-deploying-language-packs-offline-using-system-center-configuration-manager/

I cannot open the smsts.log from C:\_SMSTaskSequence\logs\smstslog\ as it says its already in use. just copy it then and open the copy, attach it here

did you add any vmware network drivers to the boot image ? if not, that's why it's failing (and that would explain the network errors) by the way, HyperV doesn't have any need for drivers in the boot image.

IntroductionMicrosoft is regular as clockwork, pushing out updates to System Center Configuration Manager Technical Preview (and the Current Branch releases also) and at a very fast pace. About a month has passed since 1603 was released for Technical Preview 4. Today they released 1604 for TP4. There are two main branches of Configuration Manager releases right now, one is Current Branch (for use in Production) and the other is Technical Preview 4 (for use in your lab to review new upcoming features). Current Branch releases are released on a slower cadence, like every 6 months or so, whereas Technical Preview releases are monthly. This technical preview release contains the following updates as listed below: Windows Store for Business integration – You can now manage and deploy applications purchased through the Windows Store for Business portal for both online and offline licensed apps. You can also view a video walkthrough of this feature. Passport for Work policies – You can now deploy Passport for Work policies to domain-joined Windows 10 PCs managed by the ConfigMgr client as well as mobile devices managed by Microsoft Intune. On-premises Health Attestation Service integration – You can now configure devices that cannot connect to the cloud-based Health Attestation Service to connect with the on-premises Health Attestation Service instead. VPN for Windows 10 – You can now deploy VPN profiles with 3rd-party providers to Windows 10 devices managed with ConfigMgr client. These providers include Pulse Secure, F5 Edge, Dell SonicWall, and Checkpoint. Software Updates Compliance dashboard – You can now use this dashboard to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk. This release also includes a new feature for customers using System Center Configuration Manager integrated with Microsoft Intune to manage mobile devices: New setting for Android devices – You now have an option to configure Smart Lock setting for Android 5.X devices in order to prevent users from bypassing the lock screen. In addition, Microsoft updated the baseline version of Configuration Manager Technical Preview available on TechNet Evaluation Center. Now it is based on the Technical Preview build 1603. Baseline bits are used for new installations. Getting the 1604 UpdateIn Configuration Manager Technical Preview 4 version 1602 or later, go to the Updates and Servicing section and click on Check for Updates in the top left corner of the ribbon (this button is not present in 1511, instead restart the SMS_Executive component). You’ll see a popup confirming that it’s checking for updates. This will kick start the dmpdownloader component into action. Use CMTrace to open the dmpdownloader.log available in <ConfigMgr installation path>\Microsoft Configuration Manager\Logs. Look for User requested dmpdownloader sync in the log file to verify you clicked on Check for Updates. Once an applicable download is found you’ll see something similar to the following in the log file, the GUID will vary depending on what update package it’s referencing. Generating state message: 6 for package d7d04967-1ab4-459d-8874-8a5733dde587 Once an applicable update is found it will be downloaded and the state in the console will be listed as Downloading The dmpdownloader.log will have a line stating “download large file with BITs”. Note: In the screenshot below, you can also see that I’m using the highlight feature of CMTrace to highlight the line with Generating state message: 6, this makes it easier to find. Next all the files within the update will be extracted before downloading the redist and then making the update available in the console with a state of Available. Right click on the update and choose Install Update Pack, when the Wizard appears you can Ignore the prerequisites check and click next Review the new features listed and click next Select your client update options Accept the EULA and click through to completion Use CMTrace to check the CMUpdate.log file found in <ConfigMgr installation path>\Microsoft Configuration Manager\Logs for detailed info about the installation of the update. Note: The CMUpdate.log will take time to start logging the installation of the update, so be patient. You can also refer to the Hman.log for details of the installation. Click on Show Status to reveal the in console status of the installation, which brings you to the monitoring node where you get to click on Show Status again to reveal the Update Pack Installation Status Once installed it’s reflected in the CMUpdate.log, look for the line INFO: Successfully dropped update pack installed notification to HMan CFD box. After the update is installed, you can click on Help and you’ll see this popup informing you that a new update is available for the Configuration Manager console itself. and after a while it’s installed below you can see the Software Updates Dashboard And here’s the 3rd Party VPN ability in Company Resource Access, VPN Profiles The Windows Store for Business integration is shown below (it’s in the administration workspace, under Cloud Services Passport for Work can be found in Assets and Compliance, Company Resource Access which requires a Server 2016 domain controller if you want to use Key based authentication (there is also certificate based) Related reading Installation – How can I install System Center Configuration Manager and Endpoint Protection Technical Preview 4 https://blogs.technet.microsoft.com/configmgrteam/2016/04/22/update-1604-for-configuration-manager-technical-preview-available-now/

Today Microsoft is releasing Windows 10 Insider Preview Build 14328 for both PC and Mobile to Windows Insiders in the Fast ring. This build is just one build newer than the Mobile build released on Wednesday so there isn’t a lot new for Mobile. For PC though this is a MAJOR build, packed with lots of new features and improvements including Windows Ink, updated Start, and more! With the amount of code change in this build there are going to be some rough edges, some of which are called out in the known issues below. If any of those make you uncomfortable, you may want to consider switching to the Slow ring and waiting for a later build which has a bit more stabilization on these new features. We’re very excited for you to try them out and tell us what you think. Here’s what’s new in Build 14328 for PC Windows Ink Microsoft announced Windows Ink at Build 2016 a few weeks ago as an all-new experience coming with the Windows 10 Anniversary Update later this summer. Starting with today’s build – you can try out the new Windows Ink experience for yourself. Windows Ink puts the power of Windows in the tip of your pen, enabling you to write on your device as you do on paper, creating sticky notes, drawing on a whiteboard, and easily sharing your analog thoughts in the digital world. Windows Ink is also integrated into apps like Maps, Microsoft Edge, and Office. If you have a device with an active pen like the Surface Pro 4 or Surface Book – Windows Ink Workspace is enabled by default and accessible via the pen button in the notification area of your taskbar. You won’t see this button if your device does not have an active pen paired with it. However, for those of you who don’t have a device with an active pen but want to try out Windows Ink Workspace, you can right-click on the taskbar and choose “Show Windows Ink Workspace button”. Updated Start ExperienceWe have made improvements to the Start experience in Windows 10 which we think improves efficiency and discoverability of finding all of your apps as well as being more consistent across PC, Tablet, and Mobile. More info > https://blogs.windows.com/windowsexperience/2016/04/22/announcing-windows-10-insider-preview-build-14328-for-pc-and-mobile/

Slump in PC sales A continued slump in personal computer sales hurt the company's core Windows business. The firm's net income fell to $3.76bn (£2.6bn) in the third quarter from $4.99bn a year earlier. Its shares were down more than 4% in after hours trading. Cloud revenues rising Revenue in its cloud business, which includes Azure, rose 3.3% to $6.1bn, but operating profits at the division shrank 14%. "We would have liked to have seen 7% to 9% growth," said Dan Morgan, a portfolio manager at Synovus Trust, which holds Microsoft shares, said of cloud revenue. "We're trying to validate this story that Microsoft is truly becoming a cloud company, and they're not going to be relying on the desktop computer." Revenue at the software giant fell to $20.53bn from $21.73bn, lower than the $22.09bn analysts had expected. Continued weakness in the personal computing market hobbled demand for one-time licences for some of its products, the company said. While some analysts are hungry for more growth from Microsoft, other analysts are adopting a wait-and-see approach. "Microsoft's cloud business is gaining sales and momentum in the marketplace, so I am willing to give them the benefit of the doubt on this quarter's missed external expectations," said Matt McIllwain, a venture capitalist at Madrona Venture Group who watches Microsoft closely. read more @ BBC News > http://www.bbc.com/news/business-36108166

hi find and locate the setupact.log and attach it here, it's in the C:\$WINDOWS.~BT\Sources\Panther folder.

maybe (i havn't tried), try it.

Peter already told you, recreate the media and enter the password in the wizard.

you dont need any drivers in the build and capture image, just use virtual machines (hyperv is great no drivers needed, native in windows 8 and windows 10)

are you trying on a virtual machine or real hardware ? i'd recommend virtual machines for any build and capture, network not found always usually means that you've not added drivers for the nic in the boot image, so what hardware are you testing on ?

replace my steps in the task sequence with steps in a script should work fine.

if you are trying it on a UEFI system it won't work This setting only affects the Windows Setup process on BIOS-based computers. UEFI-based computers are not affected by these settings. use my method instead (or a variety of it)

until i write a new post for windows 10, this should help https://www.windows-noob.com/forums/topic/3251-customising-windows-7-deployments-part-4/

if you use teamviewer i'm happy to remote in and help out, let me know

hi Gerard and welcome to windows-noob !

did you see my new blog post here, as regards your current failure message i'd need to see the entire output from the script, can you post it please ? (copy/paste save as a txt file and attach)

Introduction In a previous post I showed you how you can deploy Windows 10 x64 (version 1507) to the Microsoft Surface Pro 4 using MDT 2013 Update 1. This script has been updated with the following changes: Windows 10 x64 (version 1511, updated February 2016 media) Microsoft Deployment Toolkit (MDT) 2013 Update 2 Latest available 2016 drivers for the Surface Pro 4 Windows 10 ADK (version 1511) Note: Microsoft has released two versions of Windows 10 x64 (version 1511). The first release was the original and released in November 2015, the second release was an updated release in February 2016. For this guide I've used the February 2016 release available on the Microsoft Volume License Site. The script does care which release you use, as the previous release of Windows 10 x64 version 1511 shows up as Technical Preview wheras the February release does not. Note: This is fully automated, and as this does install a Windoes Deployment Services server role hosting a boot image, you should modify the script accordingly and test it thoroughly in a lab first. This script is tailored for one thing only, deploying Windows 10 x64 to the Microsoft Surface Pro 4 with all drivers loaded and MDT 2013 Update 2 pre-configured. Download it and customize it to suit your needs for other hardware if you wish because what it does is pretty cool. This script performs the following actions:- Downloads and then Installs Windows ADK 10 (version 1511) if you have not done so already Downloads and then Installs MDT 2013 Update 2 if you have not done so already Downloads all required drivers for Microsoft Surface Pro 4 if you have not done so already Imports the Windows 10 x64 (version 1511) operating system into MDT Imports the Microsoft Surface Pro 4 drivers into MDT Creates Selection Profiles for Microsoft Surface Pro 4 and WinPE x64 Creates a Deploy Windows 10 x64 - Surface Pro 4 task sequence Edits the Deploy Windows 10 x64 - Surface Pro 4 task sequence and adds an inject drivers step for Microsoft Surface Pro 4 Sets a WMI query for hardware detection for the Surface Pro 4 on the corresponding driver step Injects the Microsoft Surface Pro 4 network drivers into the LiteTouchPE_x64.wim Creates custom CustomSettings.ini and BootStrap.ini files Disables the X86 boot wim (as it is not needed for Surface Pro 4) Changes the Selection Profile for the X64 boot wim to use the WinPE x64 selection profile Installs the Windows Deployment Service role Configures the WDS role and adds the previously created LiteTouchPE_x64.wim Starts the WDS service so that you can PXE boot (UEFI network boot). All you have to do is download the script below, modify some variables, then place certain files in the right place such as the Windows 10 x64 Enterprise (version 1511) media. Please ensure you have a working DHCP scope on your Active Directory domain controller, then PXE boot a Microsoft Surface Pro 4 and sit back and enjoy the show. Step 1. Download the script The PowerShell script will do all the hard work for you, it is in the Downloads section at the end of this guide, download it, unzip it and place it on a server (running Windows Server 2012 R2) that is designated to be the MDT 2013 server. I've tested it on Windows Server 2012R2 only, if you run it on a different operating system and have issues then please post your results below. Step 2. Configure the variables in the script Once you have downloaded and extracted the script, you need to configure certain variables interspersed throughout the script. I'll highlight the ones you need to edit. The most important of them is the $SourcePath variable (line 59) as this decides where to get the content from 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 (line 239) specifies the MDT Deployment share root folder for example E:\MDTDeploy. There are other variables to configure, for joining the Domain (lines 316-318) and then you need to configure how you actually connect to the MDT server from WinPE (lines 392-396) Step 3. Copy the Windows 10 x64 (version 1511) operating system files Mount a Microsoft Windows 10 x64 Enterprise (version 1511) ISO and copy the contents to $SourcePath\Operating System Images\ as shown below Step 4. Optionally copy MDT 2013 Update 2, ADK 10, Surface Pro 4 drivers This is an optional step. If you've already downloaded the above files then place them in the source folder, otherwise the script will download them for you. You do not have to do this as the script will download the content for you if it's not found. Step 5. Optionally copy your Applications to the respective folders This is an optional step. If you have apps like Office 365, copy them to their respective folders under Applications If you do add any applications, you'll need to edit the corresponding section within the script for the CustomSettings.ini and replace the guid for the App as shown here (line 358) Step 6. Run the script On the server that is to be your MDT server, start PowerShell ISE as Administrator. Click on the green triangle to run the script. Below you can see the script in action After the script is complete, you are ready to test deploying a Microsoft Surface Pro 4 installation. After running the script you can see that WDS is installed and that the LiteTouch_X64 boot wim is imported into WDS. After opening the Deployment Workbench, you can see the Deploy Windows 10 x64 - Surface Pro 4 task sequence is created The Surface Pro 4 drivers step is configured and the WMI query for the hardware is also added and drivers specific to the Surface Pro 4 are imported and custom selection profiles are created Step 7. Sit back and watch the deployment Take a properly shutdown Surface Pro 4, 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 computer name, note that it's currently set to SurfacePro4 in CustomSettings.ini contained within the script, If you have optional apps they'll be listed here along with the mandatory Office 365 ProPlus you can change that behavior in the UI itself (CustomSettings.ini on the Properties/Rules of the DeploymentShare) or automate it via the many methods available such as those that Mikael describes here click Next and off it goes, before installing the Applications.. and finally it's all complete ! 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 ;-). If you cannot PXE boot, because WDS is not accepting connections (revealed by the PXE Response tab in WDS properties), then look for the following error in the scripts output: setting PXE response policy... Windows Deployment Services Management Utility [Version 6.3.9600.16384] © 2013 Microsoft Corporation. All rights reserved. An error occurred while trying to execute the command. Error Code: 0x5 Error Description: Access is denied. If you see that error, then the user you are logged in as does not have sufficient permissions to configure WDS. To resolve, make sure to Delegate permission in Active Directory for the User you are running this as, and allow that user Full Control of Computer Objects in that OU. You can test whether the permission change works by issuing the following after the script is complete: WDSUTIL /Set-Server /AnswerClients:All 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\SMSTSLOGIn Windows C:\Windows\Temp\DeploymentLogs C:\MININT\SMSOSD\OSDLOGS C:\Users\Administrator\Appdata\Local\temp\SMSTSLog Summary Automating the deployment of Windows 10 x64 Enterprise to the Microsoft Surface Pro 4 is possible and script-able with PowerShell and MDT 2013 Update 2. Related Reading How can I deploy Windows 10 x64 to the Microsoft Surface Pro 4 using MDT 2013 Update 1 - https://www.windows-noob.com/forums/topic/13190-how-can-i-deploy-windows-10-x64-to-the-microsoft-surface-pro-4-using-mdt-2013-update-1/ Downloads Download the PowerShell script - Deploy Microsoft Surface Pro 4 with MDT 2013 Update 2 - April 2016.zip You can download a Microsoft Word copy of this guide here - How can I use PowerShell to deploy Windows 10 x64 to the Microsoft Surface Pro 4 using MDT 2013 Update 2.zip

looks like your errors are network related, are you doing this on a VM or ?

i'm updating it now and will post a new blog post shortly, but in the mean time look for the line that contains this string "$SourcePath\Operating Systems\$OStoDeploy" and change it to "$SourcePath\Operating System Images\$OStoDeploy" then run it again, should work and depending on the version of Windows 10 you are deploying (1507 or 1511) read the change below, the above script was only tested with Windows 10 x64 - 1507, therefore if you use Windows 10 x64 - 1511 (original november release) it would fail, the below will resolve that. # use this line for Windows 10 1507 # import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose # Use this line for Windows 10 1511 import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise Technical Preview in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose If however you are using the Windows 10 x64 - 1511 media that was updated to February 2016 (availabe on Microsofts volume license site) then use the first import statement and rem out the second, like so. # use this line for Windows 10 1507, or updated Windows 10 1511 media from Feb 2016 import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose # Use this line for original Windows 10 1511 media # import-mdttasksequence -path "DS001:\Task Sequences\$OStoDeploy" -Name "Deploy $OStoDeploy - Surface Pro 4" -Template "Client.xml" -Comments "(c) windows-noob.com" -ID "001" -Version "1.0" -OperatingSystemPath "DS001:\Operating Systems\$OSToDeploy\Windows 10 Enterprise Technical Preview in Windows 10 x64 install.wim" -FullName "windows-noob" -OrgName "windows-noob.com" -HomePage "http://www.windows-noob.com"-AdminPassword "P@ssw0rd" -Verbose

the script creates the TS.XML via MDT, you don't need to create it, you must however supply the Windows 10 media as explained in this guide.