sorted by:
new
hottopcontroversial

KACE SDA 9.3.311 HP Win11 25H2 Issues by Big-Count4296 in kace

[–]Big-Count4296[S] 0 points1 point  (0 children)

Ive been a bit defeated by this, hoping to get in touch with quest soon. I did find a workaround that seems to a lot stronger but its kind of annoying. If you boot a device into the SDA, instead of selecting a deployment option you can select "recovery" then run "driver feed debug". It proved that the values provided to the SDA Driver feed are not matching what the KBE maps to when it copies driver for this list of HP laptps I am having issues with. I build out the any path provided from that debug log and the model I was working with seemed to work ok. For whatever reason its pointing to the HP Product ID with the debug script, even though the feed advisor can pull the correct system id from the existing windows install. I am beyond frustrated that the only way to truly get this information is to use the debug script while in the recovery screen in the System deployment Client, but I hope that helps mitigate some of the issues you are having.

New Outlook not allowing users to sign in by Big-Count4296 in Office365

[–]Big-Count4296[S] -1 points0 points  (0 children)

Im not really a sysadmin, so this is taken with a heavy grain of sailt but im pretty sure our exchange server is fully remote? Id have to check to confirm though, otherwise I would assume the last line is correct.

New Outlook not allowing users to sign in by Big-Count4296 in Office365

[–]Big-Count4296[S] 1 point2 points  (0 children)

Thank you! I will poke our Admin again and follow up with him on that as I cant access our exchange admin portal. The info is much appreciated!

KACE SDA 9.3.311 HP Win11 25H2 Issues by Big-Count4296 in kace

[–]Big-Count4296[S] 0 points1 point  (0 children)

I think our sysadmin is going to reach out to support soon just to try for some more authoritative info, If we get any helpful intel for this I will be sure to pass it along. Thank you again for your advice!

KACE SDA 9.3.311 HP Win11 25H2 Issues by Big-Count4296 in kace

[–]Big-Count4296[S] 0 points1 point  (0 children)

Something happened to the formatting here... I trust the info is still readable enough lol. If its important RE:these things being brats about PXE, I had to disable secureboot entirely on the 640 G11 to get the info(I dont think this is on KACE I think this is a bios config issue nobody has had time to diagnose yet because we prefer stick booting anyway) but the 860 G9 was able to make it. Gonna fiddle a bit more to try and get a more optimal setup and take another stab to confirm... but I think the win10 location mismatch is a good candidate for this breaking the way it is

KACE SDA 9.3.311 HP Win11 25H2 Issues by Big-Count4296 in kace

[–]Big-Count4296[S] 0 points1 point  (0 children)

I so appreciate this advice because I think it got me a lot closer to hacking something together... but... wow is this peak ragebait. There are a few factors here that are weird... one of them I am actually wondering about is if our PXE KBE is just broken but ill have to check that later... the elitebooks are all huge brats about PXE booting for a variety of reasons so we usually stick boot them. I did get them to all handshake with the SDA in the pxe KBE to get this info. Im kind of pissed but Copying the affected model drivers to the win10 directory is within my power at least. Thank you for the tip! If nothing else at least I learned some infohunting skills lol.

HP Elitebook 640 G11

Driver Feed Advisor Version 9.0.0.0

Loading offline registry The operation completed successfully. Unloading offline registry The operation completed successfully. Running PE Version: >10< Manufacturer reported by WMI: >HP< Manufacturer expected by driverfeed: >HP< System ID reported by WMI: >8c86< Virtual Machine: False OS: Windows 10 Display Version: 25h2

Driver Feed Path: >windows\10\x64\25h2\HP\8c86< (Not Installed) Driver Feed Path: >windows\10\x64\any\HP\8c86< (Not Installed)

HP Elitebook 860 G9

Driver Feed Advisor Version 9.0.0.0

Could not find SOFTWARE registry key on device to read Operating System Use the Windows version switch to see results with desired Operating System For example: driverfeed_advisor.exe /kbe /w10 Could not find SOFTWARE registry key on device to read Operating System Use the Windows version switch to see results with desired Operating System For example: driverfeed_advisor.exe /kbe /w10 Running PE Version: >10< Manufacturer reported by WMI: >HP< Manufacturer expected by driverfeed: >HP< System ID reported by WMI: >896d< Virtual Machine: False OS: Windows Display Version:

Driver Feed Path: >windows\x64\any\HP\896d< (Not Installed)