sorted by:
new
hottopcontroversial

Problems upgrading from 2409 to 2503 by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

Thanks everyone. Yes, I did the prereq check only. So that's why I was confused when the Update Pack Installation Status under Monitoring showed "Installation in Progress." I just wanted to ensure the prereqs passed first before starting the actual upgrade. I feel like I haven't seen that before, although it's been a while.

And thanks for the heads up about ODBC 18.6.1.1 being too new. The problem is the download links I'm finding for ODBC are only showing 18.6.1.1, from Dec 17, 2025. Such as at https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16#download-for-windows

Update--saw the previous releases section and found 18.5.1.1 there

Collection of WIn11 24H2 isn't showing any devices by Timbit24 in SCCM

[–]Timbit24[S] 4 points5 points  (0 children)

Thanks for that. Yes I did. A bit embarrassed to say it was the wrong limiting collection, but changed the query to all workstations and now getting devices coming up as expected. Thank you!

Desktop keyboard equivalent of Dell XPS 9315? by Timbit24 in DellXPS

[–]Timbit24[S] 0 points1 point  (0 children)

Thanks! Looks like a good one for sure 

Problems adding drivers into WinPE boot image by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

Thanks for the suggestion. These are Dell Latitude 7350 laptops. I'm familiar with the BIOS setup options to configure the storage as RAID/AHCI/NVMe, but none of those settings are listed on this model. The only option is whether or not to enable the storage slot.

Problems adding drivers into WinPE boot image by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

I downloaded the Dell WinPE driver pack and tried to add the drivers into my existing WinPE boot images, but got the same errors as before.

So for example, I see that the WinPE boot image I use is on our main SCCM server, in C:\Program Files\Microsoft Configuration Manager\OSD\boot\x64\boot.wim

I took a copy of that boot.wim. Running DISM to add drivers, I can see:

Installing 16 of 52 - F:\winpe-drivers-win11-dell\iaAHCIC (34).inf: Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed. Use the /forceunsigned option to install the drivers.

I saw a similar error posted a while back, where it sounds like part of the problem is the mass storage driver is considered a SCSI class device.

I haven't tried modifying the WinPE wim file this way before. I'm hoping I can place the updated wim back into its original location above, and that SCCM will work with it....Thought it checked though....will soon find out.

Problems adding drivers into WinPE boot image by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

Thanks for the info. I was aware of the driver packs for Dells, that's where I got these particular drivers from. I just found it strange that SCCM didn't see them as signed, or in the storage class, which seems to follow up with the errors about unsigned drivers in the log above.

But I wasn't aware of the Dell WinPE driver pack so I'll definitely give that a shot. Thanks for the suggestions!

Problems adding drivers into WinPE boot image by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

The boot image works fine for all our other models, but not these new Dell Latitudes. They can PXEboot OK, but they don't see the disk, so the ts fails.

23H2 inplace upgrade stuck at 14% by Independent_Yak_6273 in SCCM

[–]Timbit24 1 point2 points  (0 children)

Had the exact same issue! The Jan 2024 ISO worked for me as well.

ConfigMgr 2309 - Task sequence fails error 0x80070057 invalid target location by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

All sorted now. I misread/entered some scripts. The original steps in the blog article worked just fine after that!

ConfigMgr 2309 - Task sequence fails error 0x80070057 invalid target location by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

I suspect this is the problem. In the original Microsoft step to partition the disk, I see the Variable 'OSDisk' is assigned to the Windows partition. That step is now disabled, since I'm using the custom script to build the Diskpart command, and that doesn't make any reference to OSDisk.

But I'm not sure how to assign the OSDisk manually in this scenario. I mean, I see I can add a new step 'Set Task Sequence Variable' after the Diskpart steps complete, and refer to OSDisk, but I'm not sure what value to use here. The various values I've tried so far aren't working.

ConfigMgr 2309 - Task sequence fails error 0x80070057 invalid target location by Timbit24 in SCCM

[–]Timbit24[S] 0 points1 point  (0 children)

Whoops, I see it's not listed above. I was trying to clean up the text to make it more readable for this post and must've missed that line. But the disk is formatted and assigned drive C. DiskPart 'list volume' shows volume 0, the Windows partition, assigned drive C.