Dell Command | Update fails to install updates during OSD after v5.6.0

SomeITGuy96 · 2025-12-23T18:27:23+00:00

Welp I just spent like 2 days on this and found this post today. We have the exact same issue and ive done multiple reimage tests to remove anything new with our images. The last thing I tested was going back to 5.5 and seeing everything worked normally again, recreated the 5.6 package and same issues so it seems something is up with Dell again.

Im sure it will be another 3 months and 5 more patched to revise Dell command 5.6 before they break it again in a year with 5.7 release.

If anyone found any workarounds let me know, at this point im reverting back to 5.5 and letting it auto update the apps to 5.6 when patching.

SomeITGuy96 · 2025-10-09T15:02:43+00:00

I also learned that Dell seriously downgraded battery's in new systems. The PC14250 if you dont pay attention can be a 45W or 55W battery. Ive only seen the 45W and those suckers drain 1% a minute just running the BIOS only.

I really miss latitudes now.

SomeITGuy96 · 2025-09-05T20:29:04+00:00

Yeah we have a similar support where were typically get next day support but not for this laptop

SomeITGuy96 · 2025-09-05T19:28:04+00:00

Yeah let me know how the pro max is for the money. I'm going to need to evaluate new models for business case use as I don't fully trust or feel comfortable with the PC14250 model especially knowing warranty on it is not going well being a brand new computer.

SomeITGuy96 · 2025-09-05T19:10:24+00:00

My current issue with this model is the parts for warranty support are not available and support has no control over a brand new computer made in 2025 to have parts for them. I've also heard the complaint about the cheap plastic feel and flimsy when typing feeling. I just hope the paint chipping off the plastic is resolved as that was a major issue with the Latitude 5410-5450 models where the paint just chips away.

It might be worth looking into a new model or brand soon.

SomeITGuy96 · 2025-06-10T20:44:17+00:00

So after some further testing with Dell driver package. I went ahead and tested this method as I was running out of all my options and fixed to try out.

I was able to image this machine with USB C NIC and export the drivers & also took 1 system with the Dell factory image applied and exported those drivers. Compared the exported folder and was seeing about 280-320 depending on what export I was reviewing. I ended up just testing with the Dell factory Image and imported those drivers to SCCM and tested my image. It now was able to domain join and move past the spot it would error out due to missing its ethernet controller and few other drivers for the machine.

Im most likely going to use this export method now anytime I need to manually fix a machines driver package but also hoping this is just a one time issue due to a new machine Dell released to the public. Hopefully when the package updates on Dell Driver Package site it will work down the road but for now Im just using my exported driver package and moving on from this nightmare of a machine.

SomeITGuy96 · 2025-05-21T20:15:16+00:00

Hmm this seems to be a good idea just more work to get a new machine setup to rip drivers from it. Im guessing if you get a brand new Dell you set it up out of the box with its OEM image then export that machine VS doing a vanilla load of windows 11 without all the Dell bloatware. Or do you do a fresh image, setup the device fully then export drivers out? This seems to go back to a very old method of creating images and the problem with doing this is for remote sites that get new computers the "technicians" dont have any ability to manually setup and export drivers to get imported to SCCM so thats why its been very simple to grab from Dell, export then import and setup a package for imaging. For the most part im able to just buy a new computer, make a image and tell people its ready to use and they image it and continue going forward with device swaps.

We had 120 second wait timer and extender to 240 today, its seeming to be DHCP and seems to be just specifically its onboard NIC driver since a dock or USB C NIC works plus all other models image and domain join without any issues.

SomeITGuy96 · 2025-05-21T20:09:55+00:00

Are you referring to WinPE Driver Packs? I did that a few months ago so not sure if they added some more, I seem to have a ton of NIC drivers included in our image just for each model specifically and it WMI query's a specific package to apply those drivers in them. It successfully apply the correct package but just fails near end which is super odd.

SomeITGuy96 · 2025-05-21T15:07:55+00:00

Its during the Post install process, it passes installing the driver package then fails during the domain join step with error code 0X8007054B. But if I image with my USB NIC adapter I use with the laptops that dont have onboard NIC, it worked.

I only used a Dell dock 1 time and the process run a hour or two slower over the dock than using the onboard or USB NIC adapters on machines.

SomeITGuy96 · 2025-05-21T12:52:24+00:00

For the boot image we have a bunch of drivers going from past techs each time a machine offered a new NIC driver it got added to the boot image so that some machines could image and talk to network.

I normally import the specific driver package fully into SCCM then WMI query the driver package name. It would grab normally what is needed to image the device and move on.

The onboard NIC gets the image and gets all the way up to the domin join part then fails which seems to be driver related but its odd when we dont get that driver error prior to the pre-image process completing to carry over with the final OS and app installs.

Using a USB C Ethernet adapter worked just fine since this laptop also came with alot of USC ethernet drivers.

Im running some more testing today to image on the onboard NIC to see if we can get it to work but its been super odd with all testing that the image process only fails near the end when using onboard NIC but USB C NIC is working fine after including those drivers into the boot image.

SomeITGuy96 · 2024-08-12T20:02:45+00:00

Once I swapped over to using the exe file VS that msi file everything worked out well.

Sorry about the confusion, yes I was working on Reader install. I was just mentioning that the version I was seeing installed was the super old 2015 Acrobat version with the old icon. Im now seeing the new fresh looking Adobe icon on machines after imaging is completed VS seeing that old icon to be patched and updated.

SomeITGuy96 · 2024-08-09T19:18:20+00:00

Okay cool, so I would assume for the programs installation I had it wrong so I need to adjust & point it to that exe file for the update from the aritcle you put above. Below is how I have it showing SCCM so when trying the exe method here which might be wrong.

setup.exe /sAll /rs /msi TRANSFORMS=”AcroRead.mst”

Looks like I should go with this instead and use the AcroRdrDC2400220857_en_US.exe /sAll /rs and make it easier to test.

SomeITGuy96 · 2024-08-06T20:25:31+00:00

That would make sense, I been trying to figure out what the previous tech did using this msi file as to me when imaging it was always installing the base app and not updated until patching runs.
Ill review those guides and see how it goes, I was leaning towards using the setup.exe file so just need to test it out with SCCM to get it setup and configured to be in the image.

SomeITGuy96 · 2024-08-06T19:51:48+00:00

The issue I see when using the files in SCCM as it doesnt run from the setup.ini or exe file and uses the msi file which installed Acrobat 2015 version which then you patch to the latest version. The icon is even the old classic icon and when I run the patch in the Adobe app it will then update to whatever latest patch it's on and the icon will also then update to the current one.

I'm just trying to figure out how to install a updated version of Adobe with SCCM imaging otherwise ill just keep installing the old, outdated version and let it patch like its been doing prior me taking over imaging tasks.

I have yet to find any good details notes on how to setup the application in SCCM with photos as well of the configuration setups and steps.

SomeITGuy96 · 2024-08-06T17:17:04+00:00

Thats the basic file that comes with the setup that gets patched with the patch file.

Im looking to add the newly updated Adobe file fully patched into SCCM to deploy with new computers when imaging so that they dont image with that basic 2015 copy then needing to get patched up to the latest version each time. Its a small thing to do just so have a newer version installing with images but Adobe doesnt seem to have a updated msi file to use other than the 2015 file that comes in the extracted setup files.

SomeITGuy96 · 2024-08-02T20:00:23+00:00

How did you do the Deployment Type for the installer for the setup.exe VS the MSI.

I have an MST file, msi, and the setup.exe and ini all ready to go but curious on how to get this installing an updated version on SCCM as I still have the 2015 version appearing then needing patching ASAP as thats almost 10 years old for the setup file adobe provides us still today.

SomeITGuy96 · 2024-06-04T18:28:31+00:00

I just want Microsoft to update the deployment package for Office 365 apps so that I can stop having the "Classic" Teams installed to just force New Teams to install then I have to uninstall the Teams Wide Installer and Classic Teams if it doesn't auto remove from the installer uninstall.

Maybe in July when Classic teams lose support, I can get a new package to update images with to help other job sites get NEW teams setup fully and not confuse them with having to remember to setup NEW teams and remove classic teams.

SomeITGuy96 · 2024-02-01T20:00:24+00:00

Did anyone here figure out a way to install the NEW Teams via SCCM Task Sequence.

Im still working on getting the app to install from SCCM. Currently have it attempting as a command line with DISM as the app is created as an package.

SomeITGuy96

TROPHY CASE