Hi All, I am on the Tech Preview 1708 release and there is only a single SCCM server with a remote SQL database I cannot upload the entire logs on here but I have installed clients on 90% of my companies estate but I have 3 computers that are troublesome. 1 x Windows Server 2016 and 2 x Windows 10 Enterprise The client was installed from Windows Updates, but looking in the ccmsetup.log I can see these 2 errors Failed to persist AAD on-boarding info. Error 0x87d00217

On Microsoft's blog, they announced that RS3 (Redstone 3) aka Fall Creators Update is coming October 17th 2017. "Create and play this holiday with the Windows 10 Fall Creators Update coming Oct. 17" It offers the following new features Windows Inking Windows Inking keeps getting better, letting you ink directly onto PDF’s, making it easier and faster to comment and share with others, improving on what you could do with pen and paper alone. Smart Ink applies artificial

Hello - We are using SCCM 1702 with ADK 10.0.15063.0 and MDT integrated. We are in the process of migrating Windows 7 to Windows 10 with Refresh Scenario. So using USMT to capture all files and folders (Except Windows/Program Files/ Program Files (X86). So we use a customcapure.xml. While restoring we restore only selective files so using CustomRestore.XML. The task Sequence has the Following Steps  1. Disable Bitlocker 2. Capture User Settings 3. Restart to WinPE 4. Apply OS

I'm starting to get greyhair after all my tries to fix PXE problem I have. The problem started after I removed SUP and Wsus role from the primarysite to a new site. That made the PXE boot fail for some reason. I'm running SCCM 1606 with 12 servers that have DP and PXE role. Non of them are working at the moment. The error I get is PXE-E53: No boot filename received This is what i get in the SMSPXE log RequestMPKeyInformation: Send() failed.    SMSPXE    2017-08-31 15:56:08    3216

A few weeks ago I upgraded SCCM to version 1706.  Shortly after, I decided to begin building out our environment for Windows 10 Enterprise 1703 deployment.  I upgraded our Microsoft Deployment Toolkit (MDT) version from build 2013 Update 2 to the latest version (build 8443) and Windows Assessment and Deployment Kit (ADK) from Windows 10 1607 to Windows 10 1703 in preparation.  I added a new operating system image and boot image, injected the appropriate Windows 10 NIC drivers into the boot WIM,

Installing this hotfix has been a bit problematic. All appears to go well until reaching the "Install Files" section. At that point, it fails and says to check the CMUpdate.log for details. I'll post the contents of the log file. So far, I've redownloaded and reinstalled the hotfix, disabled all antivirus applications on the server, and confirmed SQL permissions were correct. Any advice would be greatly appreciated. CMUpdate.txt

Trying to figure out if it's possible to get the Bitlocker pre-provision task sequence step to run on a wipe and reload scenario. -Going Win7 (no encryption) to Win10 (encrypted) -USMT is hardlinking inside WinPE -Old Win7 OS (other than hardlinked files) are being wiped (like normal) on "Apply operating system" step  Anyway to make this scenario work? 

Hi So I've updated the ADK on my SCCM server following this guide. "anotherSCCLWebsite"/how-to-update-windows-adk-on-a-sccm-server/ It now updated to 15063 I then fixed the Secure boot Bug as below https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/ then replicated the changes using the following powershell script. https://gallery.technet.microsoft.com/RegenerateBootImageWinPE10-f508f1e4/view/