Jump to content


  • Windows-Noob logo

    Welcome to windows-noob.com!

    Logging in will allow you to download scripts used in the guides.

    If you came here looking for the Endpoint Manager step-by-step guides then please start here.

    Register for free and ask your questions in our forums.

    Clients failing SUP updates - error 0x80072efe

    SMSNewb
    By SMSNewb,
    Hello, I have an office where all the clients are no longer getting updates from SCCM SUP.  The office is connected via VPN back to the main office where the MP/DP are.  All clients at this office are Windows 7 Enterprise.   Looking at the WUAHandler.log, I get: OnSearchComplete - Failed to end search job. Error = 0x80072efe.    WUAHandler    9/6/2017 11:44:54 AM    2976 (0x0BA0) Scan failed with error = 0x80072efe.    WUAHandler    9/6/2017 11:44:54 AM    2976 (0x0BA0)  

    Able to PXE boot a Hyper-V VM, but not actual machines.

    RealRider
    By RealRider,
    Hi All, I installed SCCM 1706, SQL 2016, ADK for Windows 10 (version 1703), and MDT 8443 on a Server 2016 VM, and I followed this guide https://www.windows-noob.com/forums/topic/12873-how-can-i-deploy-windows-10-enterprise-x64-with-mdt-2013-update-1-integrated-with-system-center-2012-r2-sp1-configuration-manager/ because I wanted to deploy Windows 10 with SCCM.  I was able to deploy Windows 10 to a Hyper-V VM using PXE, but I couldn't make it work on an actual laptop or desktop (both HP).  

    Operations Administrator (Security Role)

    RLC-Andrew
    By RLC-Andrew,
    Did a quick search, and didn't see anything pop out at me.  I noticed today that I have "Domain Computers" in the "Operations Administrator" Security Role group inside SCCM.  I'm assuming this is a default or was done by SCCM, as I was not the one who did this. Can anyone verify if they also have the "domain\domain computers" in that group?

    Lenovo M810z - Change TPM Version to 1.2

    adurrant
    By adurrant,
    Hello, I'm having issues bitlockering M810z with SCCM, it seems to go through fine but it appears that the TPM version is set to 2.0, I saw on the latest BIOS version that there's support for 'TPM FW Switch Feature' so hoping this is what I need, I've set up SCCM to flash the BIOS for this model, but is there any BIOS settings that I can push through SCCM to ensure that the TPM module is set to 1.2? The TPM chip is set to 'Discrete' already...   BIOS I'm upgrading to is here: http

    SCCM Agent installed but not to Server

    Master-VodaWagner
    By Master-VodaWagner,
    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

    Windows 10 Fall Creators Update (RS3) coming October 17th

    anyweb
    By anyweb,
    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

    USMT Invalid Command

    Vinod7
    By Vinod7,
    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

    PXE boot fail

    Edvin
    By Edvin,
    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

Portal by DevFuse · Based on IP.Board Portal by IPS
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.