anyweb

I assume they went this path because it's a natural progression from the Intune console extensions we had with CM12, and this method also allows telemetry transfer to Microsoft so that they can improve the product going forward. As regards the 1602 option i've added a clarification of same, when i posted this article there were no updates available for Configuration Manager Current Branch.

also you have %OSDSystemLocale% and OSDInputLocale are swapped (in the wrong place) see below

well that's your error it can't find the powershell plugin (ConfigurationManager.psd1), so where is ConfigMgr installed on this computer ?

can you show me a screenshot of the error

boot the sp4 into windows, run a full windows update on it, then shutdown windows. Try pxe booting again, does it work ?

are you sure you are shutting down the computer and not just powering off. ? can you video the PXE boot process that you see or does it completely ignore PXE boot and just boot straight into the os ?

check the UEFI bios settings so that the boot order is boot to nic before USB, pres Volume UP and then Power to enter the bios.

what do you see when you PXE boot ? can you video it ?

yes all is ok, go ahead and start installing

double check that your task sequence is using WinPE 10, because when i PXE boot my Windows 10 task sequence with a Windows 10 ADK boot image I see this (on CM12R2SP1CU1), maybe you forgot to update your boot images to your dp's after installing ADK 10 ?

what boot image is attached to this task sequence ?

this is a duplicate, see my reply to the original post here https://www.windows-noob.com/forums/topic/13851-at-my-witsdeploying-windows-10-on-surface-pro-4/?view=getnewpost

which version of ADK are you using ? to deploy Windows 10 you should be using SCCM 2012 R2 SP1 with ADK 10 at a minimum (i'd recommend you upgrade to SCCM Current Branch version 1602), based on these lines i'm guessing you are still on ADK 8 or the boot image is WinPE 5 <![LOG[OS Version is 6.2]LOG]!><time="16:26:58.904+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="installimage.cpp:962"> <![LOG[successfully loaded a source BCD boot system]LOG]!><time="16:26:58.904+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="bootsystem.cpp:1196"> <![LOG[setupNewOS: Loaded source boot system from target volume "C:\"]LOG]!><time="16:26:58.904+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="installimage.cpp:1037"> <![LOG[!sBootDevicePath.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootvolume.cpp,34)]LOG]!><time="16:26:59.295+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="bootvolume.cpp:34"> <![LOG[system partition not set]LOG]!><time="16:26:59.295+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="3" thread="308" file="bootvolume.cpp:34"> <![LOG[unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:26:59.295+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="3" thread="308" file="bootvolume.cpp:62"> <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:26:59.295+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="commandline.cpp:229"> <![LOG[set command line: "bcdboot.exe" C:\Windows /l en-US]LOG]!><time="16:26:59.295+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="commandline.cpp:732"> <![LOG[Executing command line: "bcdboot.exe" C:\Windows /l en-US]LOG]!><time="16:26:59.295+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="commandline.cpp:828"> <![LOG[Process completed with exit code 15299]LOG]!><time="16:26:59.311+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="commandline.cpp:1124"> <![LOG[uExitCode == 0, HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bcdbooter.cpp,88)]LOG]!><time="16:26:59.311+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="bcdbooter.cpp:88"> <![LOG[bcdboot failed! bcdboot.exe C:\Windows /l en-US failed (15299) stdout: Failure when attempting to copy boot files. stderr: ]LOG]!><time="16:26:59.311+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="3" thread="308" file="bcdbooter.cpp:88"> <![LOG[TS::Boot::BcdBooter::InstallBootFilesAndConfigBCD (sTargetSystemRoot, this->defaultLanguage, sBootVolume), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1089)]LOG]!><time="16:26:59.311+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="installimage.cpp:1089"> <![LOG[unloading offline SOFTWARE registry hive]LOG]!><time="16:26:59.311+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="offlineregistry.cpp:299"> <![LOG[unloading offline SYSTEM registry hive]LOG]!><time="16:26:59.373+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="offlineregistry.cpp:313"> <![LOG[setupNewOs(&pBootSystem), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1850)]LOG]!><time="16:26:59.389+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="installimage.cpp:1850"> <![LOG[Configure(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,2028)]LOG]!><time="16:26:59.389+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="installimage.cpp:2028"> <![LOG[installation of image 1 in package 500000C3 failed to complete.. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:26:59.389+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="3" thread="308" file="installimage.cpp:2039"> <![LOG[installer.install(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,2094)]LOG]!><time="16:26:59.389+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="installimage.cpp:2094"> <![LOG[Closing image file C:\_SMSTaskSequence\Packages\500000C3\2016.3.8MSwin10x64.wim]LOG]!><time="16:26:59.389+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="wimfile.cpp:466"> <![LOG[ReleaseSource() for C:\_SMSTaskSequence\Packages\500000C3.]LOG]!><time="16:26:59.404+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="resolvesource.cpp:3873"> <![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\500000C3 before releasing]LOG]!><time="16:26:59.404+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="resolvesource.cpp:3883"> <![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\500000C3]LOG]!><time="16:26:59.404+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="1" thread="308" file="resolvesource.cpp:3921"> <![LOG[installImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,509)]LOG]!><time="16:26:59.404+360" date="03-11-2016" component="ApplyOperatingSystem" context="" type="0" thread="308" file="applyos.cpp:509"> <![LOG[Process completed with exit code 2147500037]

hi Ben there are issues with this in 1511 but 1602 is out now and hopefully resolves those issues, have you updated yet ?

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 (coming in a later 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). This new version (version 1602) will will show up in your console like in the below screenshot. This update includes the following improvements: Client Online Status: You can now view the online status of devices in Assets and Compliance. New icons indicate the status of a device as online or offline. Support for SQL Server AlwaysOn Availability Groups: Configuration Manager now supports using SQL Server AlwaysOn Availability Groups to host the site database. Windows 10 Device Health Attestation Reporting: You can now view the status of Windows 10 Device Health Attestation in the Configuration Manager console to ensure that the client computers have a trustworthy BIOS, TPM, and boot software. Office 365 Update Management: You can now natively manage Office 365 desktop client updates using the Configuration Manager Software Update Management (SUM) workflow. You can manage Office 365 desktop client updates just like you manage any other Microsoft Update. New Antimalware Policy Settings: New antimalware settings that can now be configured include protection against potentially unwanted applications, user control of automatic sample submission, and scanning of network drives during a full scan. This update also includes new features for customers using System Center Configuration Manager integrated with Microsoft Intune. Some of the features that you can expect to see are: Conditional Access for PCs Managed by Configuration Manager: You can now use conditional access capabilities to help secure access to Office 365 and other services on PCs managed with Configuration Manager agent. Conditions that can be used to control access include: Workplace Join, BitLocker, Antimalware, and Software Updates. Windows 10 Conditional Access Enhancements: For Windows 10 devices that are managed through the Intune MDM channel, you can now set and deploy an updated Compliance Policy that includes additional compliance checks and integration with Health Attestation Service. Microsoft Edge Configuration Settings: You can now set and deploy Microsoft Edge settings on Windows 10 devices. Windows 10 Team Support: You can now set and deploy Windows 10 Team configuration settings. Apple Volume Purchase Program (VPP) Support: You can now manage and deploy applications purchased through the Apple Volume Purchase Program for Business portal. iOS App Configuration: You can now create and deploy iOS app configuration policies to dynamically change settings such as server name or port for iOS applications that support these configurations. iOS Activation Lock Management: New capabilities include enabling iOS Activation Lock management, querying for the status, retrieving bypass codes, and performing an Activation Lock bypass on corporate-owned iOS devices. Kiosk Mode for Samsung KNOX Devices: Kiosk mode allows you to lock a managed mobile device to only allow certain apps and features. User Acceptance of Terms and Conditions: You can now see which users have or have not accepted the deployed terms and conditions. And there is more! To view the full list of new features in this update and to learn more about the new functionality, see What’s new in version 1602 of Configuration Manager on TechNet. Note: As the update is rolled out globally in the coming weeks, it will be automatically downloaded and you will be notified when it is ready to install from the “Updates and Servicing” node in your Configuration Manager console. If you can’t wait to try these new features, the attached PowerShell script can be used to ensure that you are in the first wave of customers getting the update. By running this script on your central administration site or standalone primary site, you will see the update available in your console right away. EnableUpdateRing PowerShell Script (Right click and Save As to download. Rename the .txt extension to .ps1 after downloading) After downloading the script start it by specifying the servername of the server you want to upgrade eg: .\EnableUpdateRing.ps1 CM01.windowsnoob.lab.local as shown here: after doing that you may have to restart the SMS Executive service to see the update show up in the console. Once the update shows up and has finished downloading, right click it and choose Install Update Pack or if you want to verify the prerequisites are in place click on Run prerequisite check. When the wizard appears, go ahead and click next and you’ll get a list of available features included in this Update Pack, if you don’t want to enable a specific feature, deselect it, you can always enable it later. Then select your chosen Client Upgrade Options Accept the EULA review the summary and press Next for all the good things to begin installing When the completion screen appears you can close that wizard and open the CMUpdate.log in CMTrace for info on the upgrade. The upgrade will take time, so be patient, it takes time ! How do you get status about the upgrade ?To get status of the upgrade select the Monitoring node and click on Site Servicing Status. To the right you’ll see information about that installation progress. You can then right click on the Update Package Name and choose Show Status to get more info. as you can see below The best method is of course to review the CMUpdate.log file and look for the following line: INFO: Successfully dropped update pack installed notification to HMan CFD box Once it’s installed after you click around in the console you’ll get a popup showing you that a new version of the console is available. Click OK to install it. After it’s installed, start the new console and review the version info, and it isas follows:- Console Version: 5.0.8355.1000 Site Version: 5.00.8355.1000 What about enabling features after the install ?After everything is installed, if you need to enable features that you didn’t enable during the install select the Administration workspace and the Updates and Servicing node, select Features and right click on the feature you didn’t enable, select the feature you want to enable, right click and choose Turn On. You cannot multi select. Review the Feature popup and click Yes. via > https://www.niallbrady.com/2016/03/11/now-available-update-1602-for-system-center-configuration-manager/ Related reading https://blogs.technet.microsoft.com/configurationmgr/2016/05/04/walking-through-an-upgrade-from-microsoft-configmgr-1511-to-configmgr-1602/

did you even look ? https://www.windows-noob.com/forums/forum/113-scom-2012/

the Surface Pro line of products are UEFI only

did you guys update the console when prompted ?

and are you sure that the computer is in the collection during deployment ?

hi folks, for those of you using OSD in System Center Configuration Manager, please take the time to read and then vote for this. I'd be very grateful ! https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/12874281-allow-us-to-disable-hide-or-edit-the-confirm-tha

what collection is this computer in when it's being deployed ?

thanks ! this is not the technical preview guide, for that see the guides below: Installation - How can I install System Center Configuration Manager and Endpoint Protection Technical Preview 4 Update 1601 now available in System Center Configuration Manager Technical Preview - https://www.niallbra...hnical-preview/ Spot the difference, maintenance windows versus service windows, Microsoft is listening and fixing ! https://www.niallbrady.com/2016/01/27/spot-the-difference-maintenance-windows-versus-service-windows-microsoft-is-listening-and-fixing/ System Center Configuration Manager Technical Preview 1602 is now available ! https://www.niallbra...-now-available/ but as regards boundaries and discovery please review these posts Configuring Discovery - How can I configure discovery for System Center Configuration Manager (Current Branch) Configuring Boundaries - How can I configure boundaries in System Center Configuration Manager (Current Branch) lastly for an index of System Center Configuration Manager Current Branch guides, see this link

did you have cmtrace open with a log file and was cmtrace opened from the source ? if so that's the cause solution, copy cmtrace elsewhere, run it from there and start the upgrade again... if not the above, then please post the file copy errors you are seeing.

this one > Note: if you are using a previously captured Windows 8 WIM file which has more than one image index, make sure to select the image index that contains the Operating System otherwise you will not be given any UEFI options in the task sequence. i'll make it more obvious..

what does the ccmsetup.log file reveal ?