Forum Discussion

edd080's avatar
edd080
Brass Contributor
Sep 05, 2024

SCCM 2403 KB29166583 Hotfix

Hello to all after installing the KB29166583 hotfix I am having issues imaging any device through OSD; the device is able to pxe boot and I also arrive up to the point where i can select an image to install however when choosing any image I get the below error:

 

And the following is the smstslog :

The adk is also updated to version 10.1.26100.1 which is the latest version available.

Is anyone having these problems? Anything I can try to maybe be able to get the deployments up and running again?

I am at a loss.

Thank you for any help.

  • edd080's avatar
    edd080
    Brass Contributor

    It seems that an update has been posted in the Reddit thread:

    "Edit6: The temporary fix is to revert the LocationMgr.dll file in the management point installation folder(s). Either from an backup or receiving the file from Microsoft. They are working on an re-release of the patch. The registry keys are still in place at the moment but I think they are not required. With the next update they will anyway be removed if the MP role re installs."

     

    I backed up the original dll file and replaced with a backed up one a few days before this update was released, I am seeing far less connections to the SQL server, seems to have stabilized, but as always this is not the official fix so there is always some risk, however so far so good. Console is responsive and imaging is back up and running.

  • edd080's avatar
    edd080
    Brass Contributor
    So I had some time to test out the recent update and installed it on my sccm test server, it seems that this one so far is stable; I encountered no issues, osd imaging works fine, console remained stable and had no freezing issues.
    • Shogo's avatar
      Shogo
      Copper Contributor

      The fix does not seems to work, did not for us, and not for the person in the link above:

      Edit5: Microsoft confirmed the workaround is not working. Reinstalling the MP role does not resolve the issue either. Let´s see for further steps during the weekend. Restoring the server from backup from before the upgrade was mentioned, but this is our last option to consider. We delay this until after the weekend.

      The only thing so far is to restart the sms agent host service on all MPs at an interval before to many connections build up and the system halt.

      • edd080's avatar
        edd080
        Brass Contributor

        Shogo 

        Yep just seeing the updated thread, thank you; and yes the console does not even load for me; seeing the multiple (thousands) connections to the sql server by simply doing a netstat -an command.

         

        The fix was good while it lasted.

         

        Have to wait for MS to get this fixed anyway I suppose.

  • Michael-CM's avatar
    Michael-CM
    Iron Contributor
    Its a further bad sign for the former best and innovative MS Onpremise Product. First no more innovations and then updates with no quality check at all, which are destroying Prod Environments.
    Sorry MS (and the product team) im always fair but you have to correct your course or send a clear message to your customers that you have given up the product already.
  • Shogo's avatar
    Shogo
    Copper Contributor

    For now we have activated a script that is scheduled to run every 10th minute, restarts the sms agent host service on each MP if connections is over 10000 to avoid system halt, i have to evaluate if this limit is enough, we have two MPs so then it can be a total of max 20000 connections.

     

    EDIT: Sep 06 2024
    After some days with the above workaround, the services on MPs did restart between every 30-120 minutes, causing some disturbance.
    We have now changed to the "replace with old dll"-workaround, and it seems fine, at least after one day, still no official fix from Microsoft.

    • edd080's avatar
      edd080
      Brass Contributor
      Thank you 👍🏻 will certainly keep your script handy in case this dll workaround does not work.
  • edd080's avatar
    edd080
    Brass Contributor
    We are moving on to the second week and I still am not seeing any official fix for this issue, did you get any feedback yet?
    • StarFox64's avatar
      StarFox64
      Brass Contributor
      New hotfix is in the console. Who's gonna be the guinea pig though?
      • edd080's avatar
        edd080
        Brass Contributor
        Lol I have a test sccm server but i will be able to try this update next week and see how it goes.
  • Mike_Snodgrass's avatar
    Mike_Snodgrass
    Copper Contributor

    edd080 

    I opened a ticket with MS and this fixed it for us:

     

    add the below reg keys on all the Management Points and restart (SMS Agent Host on the MPs ) after adding them.

     

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\MP

     

    disableExtendedValidations = 1 (REG_DWORD)

    disableRequestValidations =1 (REG_DWORD)

    • edd080's avatar
      edd080
      Brass Contributor

      In my initial posts i posted a link to Reddit showing this exact workaround, it worked, then stopped working after some hours. The sql connections started to pile up between the management point and sql server up to a point that not even the sccm console was responsive .
      I applied the dll fix, and it is now working once again, the sql connections decreased considerably.
      The same Reddit thread i linked also confirms that the registry workaround does not work anymore. So you might want to monitor the server from time to time.

      • Mike_Snodgrass's avatar
        Mike_Snodgrass
        Copper Contributor

        edd080 

         

        Yep, spoke too soon. Sporadic imaging issues. Asking Microsoft about the DLL recommendation.

         

        Thanks 

  • AndyDotPhillips's avatar
    AndyDotPhillips
    Copper Contributor
    CPU usage has increased 25% over the past 4 days after applying this hotfix. After reboot, CPU back to pre-update levels. Single VM serves a low number of clients (<100) probably saved me.
    • edd080's avatar
      edd080
      Brass Contributor
      did you apply any workaround? registry fix or the dll replacement? our server is still fine up till now.
  • edd080's avatar
    edd080
    Brass Contributor

    Has anyone got any feedback about this?

    Nearly a week has passed and it seems that there is no official fix from MS for this, yet.

    • StarFox64's avatar
      StarFox64
      Brass Contributor

      edd080 so far only got the regkey suggestion. Still waiting on support to get back to me with the locationmgr.dll to try. 7 days with an unusable sccm environment. My team is not happy.

      • edd080's avatar
        edd080
        Brass Contributor
        What a total mess. Thanks for taking time to reply. 👍🏻
  • Br3akTheRules's avatar
    Br3akTheRules
    Copper Contributor

    edd080 

     

    Hi guys,

     

    I just did the 2403 and the Hotfix update on our SCCM last Friday, and from that moment on, our PXE has not worked anymore.

    Looked into the SMSPXE.log and here it is:

     

    What do you recommend me to do at this point? Is already 15.10.2024 and there is no fix from Microsoft.

     

    Thanks in advance!

     

    Edit:
    Forgot to mention my local problem.

     

    The issue for me is that when trying to deploy from an HP laptop using F12 (network boot order) + Choosing PXE over IPv4, it just does not find the server, it gets me back to the HP Menu to choose another option.

    Tried everything that I had in mind, resetting Bios to default and remaking the settings, restarting the VM 2 times, and no difference. (it just won't see the PXE

     

    • StarFox64's avatar
      StarFox64
      Brass Contributor
      Was pxe working with this model before? Do you have this models ethernet driver in the boot image? Is pxe working with other models?
      • Br3akTheRules's avatar
        Br3akTheRules
        Copper Contributor

        StarFox64 

         

        Hi @StarFox64,

        I tried so far with 2 models:
        HP ZBook Fury G7 17 (Drivers included in the SCCM) - which failed this morning;
        HP ProBook 455 G7 / 450 G9 (both failed, with the drivers included in the Task seq.)

        All the laptops were working before the update. (and in general when it was not working, indeed, it was due to lack of drivers or something in the task seq.)
        But now, it just gets stuck here:

         

         

         

Share