Jump to content


Leaderboard

  1. anyweb

    anyweb

    Root Admin


    • Points

      5

    • Content Count

      8,277


  2. Peter33

    Peter33

    Established Members


    • Points

      3

    • Content Count

      752


  3. Iroqouiz

    Iroqouiz

    Established Members


    • Points

      1

    • Content Count

      342


  4. Oilers93

    Oilers93

    Established Members


    • Points

      1

    • Content Count

      9



Popular Content

Showing content with the highest reputation since 05/04/2020 in Posts

  1. 1 point
    Hi Martinez, if you are running a Proxy server in your environment run these command on your Management Point in an admin cmd. netsh winhttp set proxy proxy.fqdn:port "<local>;*.fqdn" bitsadmin /util /setieproxy localsystem NO_PROXY bitsadmin /util /setieproxy localsystem proxy.fqdn:port "<local>;*.fqdn" iisreset I was struggeling with the same problem for a long time. The IIS server has some serious problems when the IEProxy for local system is configured with AUTODETECT. That can result in various errors in Config Manager. The settings above also fixed my installation errors for MDOP Bitlocker and Cache Server for delivery optimization. So long Peter
  2. 1 point
    Turns out no Software Update point is needed, just needed to add an Operating System Upgrade package and point it to the CORRECT folder...
  3. 1 point
    Hello Shashi, you're very welcome and stay safe yourself too. So long Peter
  4. 1 point
    I was able to Solve my authenticate issue. While running the site install Powershell script, I had to give the group names as the Pre-Windows 2000 as they differed slightly.
  5. 1 point
    Make sure you have a valid certificate bound to your IIS default site for the Distribution Point.
  6. 1 point
    yup, for anyone wondering, in part 4 of my series you'll see how to do this silently, https://www.niallbrady.com/2019/11/13/want-to-learn-about-the-new-bitlocker-management-in-microsoft-endpoint-manager-configuration-manager/
  7. 1 point
    are all packages failing to get to the dp ? or only some packages ? i'm confused about you mentioning PXe, what has that to do with packages getting to the dp, you need to fix the packages getting to the dp first and then concentrate on your other issues
  8. 1 point
    you need to provide more detail about this distribution point, was it ever working ? have you tried to reinstall the DP role on this server ? you mention 'during the reimage of the device' what do you mean by that ?
  9. 1 point
    did you look at your logs ? there are some errors in there, i've highlighted one for you
  10. 1 point
    have you seen this yet ? https://techcommunity.microsoft.com/t5/configuration-manager-blog/cloud-management-gateway-addressing-common-challenges/ba-p/1351262?utm_source=dlvr.it&utm_medium=twitter
  11. 1 point
    Have you set up boundaries and boundary groups and made sure you've added your server in the Content location box?
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...