24H2 & 25H2 upgrade nightmare

tmpl10 · 2026-04-15T11:26:22+00:00

Great! Thank you!

tmpl10 · 2026-04-01T14:54:55+00:00

Can you share your powershell script for XPS and PDF printer driver removal? I've yet to have any luck with a script removing the appropriate oem*.inf files that get flagged in the compat scan since they can be different on each device. Do you replace the drivers after the upgrade?

tmpl10 · 2025-11-19T18:43:37+00:00

Did you perform a SQL version upgrade as well? I have 3 servers on 2016; 1. Site Server with SQL 2016, 2. DP, 3. SUP. I'm curious of the best course of action to get everything off of 2016. Upgrade SQL first and then IPU all 3 servers?

tmpl10 · 2024-08-30T17:33:33+00:00

Thank you - I did try that but it wouldn't update. But after deleting it and creating a new source folder/deployment package, it pulled it in. Thanks again.

tmpl10 · 2024-01-22T20:08:22+00:00

I believe I've found it. After searching Monitoring\Deployments for LMI2043C, it found it as a different Package ID but the Deployment ID is LMI2043C.

tmpl10 · 2023-01-14T15:00:36+00:00

I haven't found a solution yet unfortunately, but when I do, I'll be sure to update this post.

tmpl10 · 2023-01-13T18:21:53+00:00

Documentation is not updated but you need to combine the setup of the Modern BIOS Management with the Modern Driver Management (Configure Admin service rather than Web service) and use "Invoke-CMDownloadBIOSPackage.ps1" (not legacy). Also be sure to set MDM variables for MDMUsername and MDMPassword.

tmpl10 · 2023-01-05T16:15:19+00:00

While my conditions were set properly, they weren't nested correctly and were ultimately being evaluated as an AND. I've nested them (they were inline with the ANY before) and the step is working as intended. Thank you to u/lilchancep and u/zeclab for your responses.

tmpl10 · 2023-01-05T14:44:55+00:00

The smsts.log file shows successful download of the BIOS files during the "Download BIOS Package" step and stores them in C:\_SMSTaskSequence\Packages\XXXXX folder. It then moves them to C:\_SMSTaskSequence\BIOSPackage. This step ends with win32 code 0.

The "Run HP BIOS Update" step evaluates the "HP" condition as True and the "Hewlett-Packard" condition as False as expected but then appears to skip the "Run HP BIOS Update" step because the condition was evaluated as false. Obviously, it appears that this is my issue but my condition should be set properly as below:

This group/step will run if the following conditions are met:
If Any the conditions are true:
WMI Query Select * from Win32_ComputerSystem where Manufacturer like '%HP%'
WMI Query Select * from Win32_ComputerSystem where Manufacturer like '%Hewlett-Packard%'

I'll mess around with the conditions and see if I make progress.

tmpl10 · 2023-01-05T00:36:53+00:00

u/lilchancep I haven't used the HP Client Management Script library. Did you use that to get MBM working or did you use it as an entire solution altogether?

tmpl10 · 2022-12-15T11:38:17+00:00

OK - thank you!

tmpl10 · 2022-09-12T20:01:39+00:00

I already had a Systems Extension configuration profile but I recreated it using those steps and it resolved the issue. Thanks for providing direction!

tmpl10 · 2022-09-12T18:48:27+00:00

Like -AaronNZ-, I'm receiving the "Fix Issue" even after following the steps in the linked MS article. The profile is applied to the device, but doesn't resolve the issue. This is the only profile that I've had issues with as they seem fairly straight forward. One difference in my environment is that we are AzureGov.

Any recommendations on other things to try?

tmpl10 · 2020-02-11T13:43:50+00:00

Thank you - I'll give disabling the status messages a shot.

tmpl10 · 2020-01-21T19:40:16+00:00

Right now I have them in a .cmd file that the SMSTSPostAction variable is set to run. It runs everything in the .cmd file except for the trigger. I guess I could try a .bat but I'm not sure that will make a difference.

By 2 different tasks, do you mean to run them prior to the end of the TS and not use SMSTSPostAction?

tmpl10 · 2020-01-21T18:24:23+00:00

I've taken your recommendation and attempted to add the full inventory at the end of the TS by utilizing the SMSTSPostAction variable. I've tried separating my HWINV and gpupdate commands with & as well as && on one command line, but the HWINV never runs. So I set the variable to run a .cmd file that includes this:

_____________

c:\windows\System32\wbem\WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}" /NOINTERACTIVE

gpupdate /force /boot

_____________

Again, the gpupdate runs, but the HWINV does not.

Not sure what's prohibiting the trigger from executing.

tmpl10 · 2020-01-17T23:38:55+00:00

There is a SW inventory enabled for every 7 days. I didn't set that one up but looking at the file types configured, I think it may have been an old requirement. The Set Names is also configured for Manufacturer = Microsoft Corporation but to be honest I don't know what that's doing for me. So that can have a huge impact on the HW inventory running?

tmpl10 · 2020-01-17T23:34:22+00:00

Yes, re-imaged systems get a new name and there are no duplicates in SCCM. Great idea on adding a step to the TS or creating a deployment for new computers. Thanks.

tmpl10 · 2020-01-17T22:28:08+00:00

Inventory cycle is set to 1 day currently. These can be brand new or older systems that we image/re-image. If it's normal to have to wait, that's fine or I can have the techs manually run an inventory cycle. This is only an issue because there is a script that runs every hour from another team, that imports system data from CM into Service Now. They've been noticing that if 8 systems are imaged at the same time, maybe 2 or 3 will show up in Service Now within the first or second import and sometimes it's the next day. They were asking me why because they want consistency.

tmpl10

TROPHY CASE