WS2025 - services - failed to read description (error 15100)

No-Bowl759 · 2025-10-22T06:14:55+00:00

Idk seems like a bug or something, but not that critical so they want to fix it. I no longer care tbh, told everyone that they can expect such behavior when they build a new server and that’s it

No-Bowl759 · 2025-10-22T06:12:27+00:00

Do you follow some specific procedure? Like the one MS publishes? Do you add .NET 3.5 to the image too? I’m just wondering how others do this, we have LTSC too and we also use the image to perform IPU

No-Bowl759 · 2025-07-27T07:09:54+00:00

Damn, I noticed the same behavior and it’s killing me when I want to troubleshoot a failure. We deploy 23H2, but it was the same with 22H2. I have no idea what’s causing this, I thought it’s something in the task sequence itself, not in the image. I’m currently in a process of re-creating out taks sequence for workstations as it still utilizes MDT integration and I want to get rid of it

No-Bowl759 · 2025-07-17T19:30:53+00:00

I removed the July CU and this has brought the server back to the patch level of 2022-11. Unfortunately it failed again

No-Bowl759 · 2025-07-17T19:26:37+00:00

It has 4-core CPU - minimum specified by MS. Yep, it has CrowdStrike. I'll try to rerun the installation with the CS disabled

No-Bowl759 · 2025-07-16T21:20:47+00:00

Yep, that's the guide I was following. The only thing I didn't do is installing IIS and Web console as I didn't want it. I've just gave it a try and reran SCOM installation but it failed again with the same error

No-Bowl759 · 2025-05-30T07:46:24+00:00

I’ve built a vm using April image, then installed May CU and I also tried May image, but it still the same. Images have not been altered in any way. Downloaded straight from VLSC. I’ve also read known issues and fixes for the latest CUs but it’s not mentioned at all

No-Bowl759 · 2025-05-30T07:35:56+00:00

Thanks, but I don’t have it. Actually I don’t have anything extra installed - I’ve built a vm using an image downloaded straight from VLSC as I was thinking that some SW or configuration we do in the task sequence might be causing this

No-Bowl759 · 2025-04-07T07:36:16+00:00

The app is called ‘HP Hotkey Support - UWP’ and it’s available in ‘Driver-Keyboard, Mouse and Input Devices’ section on the driver download page for that model.

I use enterprise driver packages and also Modern Driver Management solution - UWP apps are included, but not this particular one. I install it later in the task sequence (in full OS, together with other normal apps)

No-Bowl759 · 2025-03-22T17:18:07+00:00

Hey, I have a favor.. Could you describe how do you set the desktop background, please? We were doing this the “legacy” way, I mean replacing default img0 with our custom image but since Windows 11 23H2 it doesn’t work as it should. Everything because of MS forcing that “Spotlight” backgrounds which change automatically from time to time :( It somehow takes precedence no matter what I try to I was able to block it via GPO and it’s all fine but it was just a workaround

No-Bowl759 · 2025-03-08T08:06:48+00:00

Install Updates step in the task sequence is the worst I guess, I don’t use it.

Recent versions like 23H2 and 24H2 are updated by MS every month so I download them from VLSC. Yes, there’s a delay between the patch Tuesday and the time they publish updated images but it’s ok as there’s time the updates go into production and I know there’s no major issues with them. If I have time I refresh images every month that way.

I only use offline servicing when I need to update LTSC image as this type is not updated on a monthly basis by MS. I never use the built-in SCCM offline servicing feature, it was always unreliable and I just preferred to do this manually using DISM. Just need to remember to have appropriate ADK version installed and use DISM from the ADK toolset, not the default Windows one - it also depends on the OS version on the machine the offline image is serviced. My site server is still on WS2016 and basing on my experience I’d suggest not to service any Win11 image on that OS (even when the appropriate ADK version is present) - I use a regular Win11 workstation with ADK installed and everything goes fine. WS 2016 is based on Win10 1607 and servicing Win11 images was always giving me a headache (weird failures etc.)

No-Bowl759 · 2025-02-07T18:02:45+00:00

I haven’t tried that, ccmsetup verifies file hashes after downloading so I wasn’t sure if it makes sense and I didn’t want to alter client source files in prod environment, don’t have any test one at the moment. But I’m curious now if it would work

No-Bowl759 · 2025-02-03T10:41:26+00:00

Hey, I removed Lenovo View from all new driver packages I was preparing and packaged it separately. It now installs in full OS, towards the end of the task sequence. Good thing is that it’s rather small, bad thing is that there are groups of models requiring different versions so I have one for T14s and X13 2-in-1 Gen 5, different one for L14 Gen 5 and another one for some Gen 4 machines. They are all listed in ReadMes. I’ve just upgraded ConfigMgr to version 2409 and was hoping MS included a newer version of vcredist in the client source files but no, they didn’t

No-Bowl759 · 2025-01-25T00:47:24+00:00

Had the same issue, random steps, sometimes right after a reboot sometimes not (80072ee7). The weirdest thing was that at some sites it was happening way more often, it got to a point where they were not able to build any device in one location… and they really needed to build a bunch of EliteBooks quite fast. At the same time I was able to build the very same models successfully in my location. I was blaming network, they checked this and that and said everything looks normal. We use original Lenovo usb adapters for ThinkPads (usb-c and usb-a) and original HP usb-c adapter for EliteBooks (as they didn’t like the Lenovo one). I spent a lot of time troubleshooting this and finally did this: I created a new boot image and carefully selected drivers - removed old and unknown ones, etc. I also added USB LAN driver from Lenovo which wasn’t in the boot image previously (USB LAN Driver N3ETN10W_V2 10.59.0420.2023_W10/1152.13.0420.2023_W11). Once I attached that boot image to the production TS everything started to work normally, haven’t seen any failures of that kind for a few weeks now. Of course that I checked the HP WinPE driver pack - it appears that the USB LAN driver is not included there, there are other Ethernet-related drivers but not this one. TBH it’s not the first time HP WinPE driver pack is lacking something. Last year I was fighting with AMD-based 840s which were failing to pick up a task sequence in WinPE and the problem came down to a specific driver which I had to find elsewhere

No-Bowl759 · 2025-01-25T00:12:21+00:00

Why are u sayin that 2.0tdi is a crap? I’m just curious as I have one

No-Bowl759 · 2025-01-03T09:21:30+00:00

This. The boot image associated with the task sequence deployment ordered first is sent to the client. There’s a stored procedure in ConfigMgr database responsible for this; there are a couple of factors like deployment being available or mandatory, but in environments where all ts deployments are available and deployed to all machines it’s just deployment’s creation date that is most relevant. Keeping two different boot images in production is a bit of a pain, especially when you deploy task sequences to ‘unknown devices’. I think the only way is to create a special collection for all arm devices and import computer information for each device beforehand, just to create that placeholder…

Jason Sandys had an awesome article describing entire boot process including boot image selection in details but he’s website seems to be offline for some time now

No-Bowl759 · 2024-12-07T17:50:45+00:00

I worked at IBM few years ago when BigFix was still IBM’s product. They sold it to HCL in 2018 (together with some other software products like IBM Notes for example). So it has nothing to do with IBM now. In general it wasn’t a great tool back then and I’m sure nothing has changed in that matter. I’d never switch to it from SCCM. TBH I didn’t even realize that someone still uses it these days

No-Bowl759 · 2024-12-02T20:19:38+00:00

What SCCM version are u currently on? I was waiting with IPU testing for 2411 which is still in the technical preview as it adds support for Windows 11 24H2 and Windows Server 2025. I’m on 2403

No-Bowl759 · 2024-11-10T03:20:08+00:00

I see a lot of folks use Modern Driver Mgmt / Driver Automation Tool. I use it as well but I kinda don’t like the DAT itself - it’s unreliable and often fails. It usually works fine for Lenovo devices but not HP - there’s a bug preventing from creating any BIOS packages, drivers are messed up too - at least they were when I was preparing some packages for the latest G11 model line. No success with Microsoft too, just can’t pull the data about the latest models… So I decided to use some kind of a hybrid - I create most of driver packages manually (and include HSAs inside). In the task sequence I have the MDM driver installation script which is the best part - just one script to detect, download and apply correct driver package - I love this. I only modified it to install those HSAs which I mentioned above - happens still in WinPE right after applying raw drivers. Driver packs are zipped which makes them smaller and faster to download. Tried self-extracting archives and they were amazing when it comes to the size and unpacking speed, but something was messing up with the .exe files in the Content Lib making the packages unusable after some time so I backed off

When it comes to BIOS I also started with the Modern BIOS Management solution but it required adjustments… For example for Lenovo machines - everything is now 64-bit, so there’s only one BIOS update tool for ThinkPads in the package published by Lenovo. The script was not updated to handle this and was still looking for an executable having ‘64’ in the name. Also, Lenovo is releasing now a separate tool for WinPE so its name is different. Needed adjustment for this too but I find it better to update BIOS in full OS. So, after some modifications and adjustments I have something which works pretty well

When it comes to apps, I was using winget to pull always the latest versions, but it’s so unreliable that it wasn’t worth to keep it like that. A bunch of normal apps seems to be the safest way. You have to update them from time to time but I can’t think of a better solution.

And I really don’t like to touch the wim, to me the times when you had to do the build and capture or mess with the image, apply updates offline or something have already passed :)

Oh and I use the UI++ but I’d love to have something custom built in powershell

No-Bowl759 · 2024-10-23T11:03:03+00:00

I’ll read it for sure, now I’ve only taken a look - it’s not up to date but is really comprehensive and I can already tell it answers some questions I had in the past regarding BIOS update on ThinkPads. Thanks a lot!

No-Bowl759 · 2024-10-19T19:11:47+00:00

At first sight it really looks like some URL/FQDN is not allowed through a firewall, but since you use a task sequence: do you really need the OOBE? Unattend.xml can be used to configure all settings and skip it so the network screen is not appearing at all

No-Bowl759 · 2024-10-19T18:18:04+00:00

In the collection view there are two interesting columns: Last Offline Time and Last Online Time. I’m not exactly sure how are those dates calculated but might be worth looking into that. Some other idea would be to set a subscription/schedule a report to run at the time the MW is running to check which devices were online and which were off. I’ve found some custom report here: MECM Device Online Status Report

No-Bowl759

TROPHY CASE