OSDeploy
W11 24H2 seems to hang for more than an hour around the start of the specialize phase when HPCMSLDriverPackLatest is used
Tested on Elitebook G7 and G8. I'm not familiar enough with OSDcloud to figure out exactly why, sorry. I don't see this issue when using the same parameters on W11 23H2. It's also not an issue when only HPIADrivers = [bool]$True is used. screenshot from setupact.log from unattendgc folder with the timings:
timing from powershell events:
Please post this in the OSD Repo for better exposure https://github.com/OSDeploy/OSD
I ran into similar issues, but they were not directly connected to this variable in my testing.
I haven't had time to get go back and dig in. Can you @ChrisBhub download the latest 24H2 ISO from MS that includes the latest monthly CUs, and then run it again using that media and see if that resolves it? If this is a MS Media issue, won't be much I can do.
I'll try to test this week with HPCMSLDriverPackLatest on in combination with a recent 24H2 iso/wim, and let you know. In the meantime, I've switched already to use recent media, because of slow or not working updates when using the default 24H2 download. (wufb, set via Intune). Recent builds seems to fix that. And instead of using HPCMSLDriverPackLatest during OSDCloud, I run an app during Autopilot executing HPIA to update the drivers.
@ChrisBhub - did you create a Win32 app and put in the ESP or you are executing a simple PS script during device setup? Do you the similar command like we do in OSDCloud: "Invoke-HPIA -Category Drivers -Action Install -NoninteractiveMode -ReportsFolder C:\OSDCloud\HP\HPIA -HPIAInstallPath C:\OSDCloud\HP\HPIA\Bin"?
@gwblok I had time to run two tests last week with HPCMSLDriverPackLatest = [bool]$True, with the december build of W11 24H2. There was indeed no hanging/delay anymore, so it seems you're right about the MS Media issue. The tests were over wifi, once on the guest at work, once at home. In the setupcomplete.log I see that it applies the wifi profile, after that it tries to run "Defender Update Stack Function", but the remote name could not be resolved: 'google.com'. Then it tries to run HPIA for Drivers, but again the remote name could not be resolved: 'hpia.hpcloud.hp.com" At first sight but without being sure, I suspect that it tries too fast before the network connection is up, 2 seconds after the start of the setupcomplete.log @AkosBakos Related to the other way of running HPIA during provisioning, I've created a Win32 app to put hpia 5.3.0 on disk, where it stays, and then another one (with dependency) to run it. It runs during device ESP indeed, but the old fashioned way with exe: C:\programdata\HPIA\HPIAinstall\HPImageAssistant.exe /Operation:Analyze /Category:Drivers /Selection:All /Action:Install /AutoCleanup /UWP:No /Noninteractive /ReportFolder:C:\programdata\hpia\HPIAReport /Softpaqdownloadfolder:C:\programdata\hpia\HPIASoftpaqs"
@ChrisBhub I am testing your way too. Like Nickolaj does: https://msendpointmgr.com/2020/09/10/automatically-install-the-latest-hp-drivers-during-autopilot-provisioning/
I am not happy with the HPIA integration into OSDCloud. I am using different OOBE and SetupComplete scripts --> so the combination is a bit tricky.
@MichaelEscamilla never had too many issues with the HPIA side in OSDCloud. Check out his fantastic blog post: https://michaeltheadmin.com/2024/11/29/osdcloud-with-hp-functions-hpia-part-4/#invoke-hpia
@AkosBakos What issues have you had with the way OSDCloud runs HPIA? We can probably make changes, but I haven't heard anything negative yet. Are you looking for additional controls around categories? Just give me your wish list
I am not happy with the HPIA integration into OSDCloud. I am using different OOBE and SetupComplete scripts --> so the combination is a bit tricky
@AkosBakos why haven't you mentioned this sooner? What's the issue?
I've just got a requirement from a HP customer, who wanted to implement HPIA during OSDCloud. Until now, the driver update from the Microsoft store was good enough for other customers.
So far, I've been pretty content with the HPIA methods built into OSDCloud that get called during Setup Complete. Eventually I'd like to add a timeout, but that's about it
I haven't been able to lock down what the issue with specialize phase is, but it's unrelated to HPIA (which is called later in the process). I think this is just yet another 24H2 bug, as it all works as expected on 23H2. I need to test with an updated 24H2 wim that I pull on my flash drive to see if that resolves the issue.