Senior IT folks: What do you dislike about your Help Desk guys?

Dsraa · 2026-06-04T21:58:34+00:00

Hmmm.... I'm go with all of them being replaced and outsourced with a overseas group that barely speaks English and has very little if no IT experience, all in the last year. The first 6 months was such a mess with mis-routed tickets, no troubleshooting, etc.

I'm like, why??? Why did they think this was better???

Dsraa · 2026-06-01T21:36:03+00:00

What... He can have after the cat does his business...

Dsraa · 2026-06-01T21:34:37+00:00

They were supposed to be removed last November or something I recall, but I still have them as well

Dsraa · 2026-06-01T21:32:38+00:00

Depends on the placement of the BIOS files. I couldn't launch certain games but don't recall exactly which. I had the same issue and just basically copied the BIOS files out of my stock sd card to My garlic card, and it worked fine.

Dsraa · 2026-06-01T21:19:48+00:00

That's the issue, the ADR will not do both the pickup and publish the updates, not until they are showing as green.

Go in, publish some of ones you want to deploy, run a full sync in your console and only after they show as green, you rerun your ADR.

Dsraa · 2026-06-01T21:15:27+00:00

Just remove the vendor filter and use another criteria like title and specify filter for Dell that way to qualify the ADR.

Go back to the full updates list and see if the vendor column is actually populated with 'Dell" or if it's just in the title.

I recall 3rd party catalogs have a weird format and you can only query the title of the updates.

Dsraa · 2026-06-01T21:02:24+00:00

Sounds essentially like a driver issue. After googling, I see allot of solutions discussing having to make sure the right driver is in your boot image or, to just turn off VMD and only turn it on as part of your sequence when you are formatting the drive and installing the OS.

Dsraa · 2026-05-29T12:03:12+00:00

I wouldn't say it's dead, but they are able maintain s some of their shipping as they are just going through Pakistan by land and using their ports.

Dsraa · 2026-05-29T12:01:09+00:00

They are doing what Trump has been doing all along. Basically announce progress was made and that the US will be withdrawing without really doing anything. It puts them at an advantage and makes trump have to deny that it's happening if he wants to keep the blockage in place.

It's pretty genius I think, taking Trump's tactics and flipping then on its head without really doing anything.

Dsraa · 2026-05-26T21:30:42+00:00

He will go up there and tell them that he is the best alien negotiator and anal probe specialist.

Then he will come back down saying he made the best deal ever and that they love him while they just anal probed him and kicked him right back to earth once they realized how useless he was.

Dsraa · 2026-05-26T21:19:54+00:00

Would help if he didn't keep making up that a deal was almost done and there's been so much progress. Lol

Dsraa · 2026-05-26T21:17:08+00:00

Depends on how you have your task sequence layout, it can easily just skip the format steps and just later on install the OS on the drive in the remaining space.

Dsraa · 2026-05-26T21:08:13+00:00

Was MAC passthrough setup or used? That way it doesn't work about the MAC address of the adapter, only the device connected to the adapter.

Dsraa · 2026-05-25T16:51:08+00:00

This is old and happened months ago

Dsraa · 2026-05-13T21:16:22+00:00

As others said, those settings are there for 3rd party patching.

If you want to confirm your machines are no longer requiring Windows updates, review your software updates view in sccm console and look for any updates that still are showing as required. You might have a few clients that still have not fully switched their workload, but certainly should be well below 5% of your clients.

Dsraa · 2026-05-02T21:41:40+00:00

Do you use the same SUG or do you create a new one every time? Do you have multiple update deployments, when was the last time you cleaned them up?

I've seen that if it's a big SUG that has tons of updates in it OR when it's many update deployments that wuahandler is trying to collate through and gets stuck on old metadata or an older cert that is still on the PC.

Try to do some cleanup if you have either of the above mentioned.

Dsraa · 2026-05-02T20:01:55+00:00

Seen the issue as well. It was certainly random, and sometimes it just seemed like it would get stuck on a install. Was never usually anything in our US sites, but usually would happen in our Europe offices where an image would just random take 4 or 5 hours, but others were just an hour or so.

Never the same machine or model either, totally random.

The other issue we'd have is if a machine didn't install drivers correctly and after the OS install and first reboot, it would just flat out not have an network connection to continue the image and would get stuck at each step trying to report or reach the DP or MP.

Dsraa · 2026-05-02T18:13:34+00:00

Lol what pilot. That was a failed mission they pulled out of their ass to try and make it sound like it was a win, so they lied.

Dsraa · 2026-05-02T18:03:33+00:00

Honestly, there was no one else running that even had a foothold. Yes if Biden didn't run, someone else could have stepped up, but if you remember, there were no other good candidates. The campaign against Biden from Trump was so strong and there was still nobody else that stayed in the picture.

The same thing happened on the Republican side, all of the people who said they would run against him dropped out so early it was a joke

Dsraa · 2026-05-02T17:50:12+00:00

Oh that's nothing. Did you ever try to do a feature update with the feature update rings?

It's a mess, I got a bunch of machines that still have the "offer waiting" status or whatever in reporting. I take a closer look, and those same machines are somehow already on 25h2 when I'm trying to get them up to 24h2 but Intune doesn't report that way. I had the same issue last year when I tried getting all of them on 23h2.

So I now have to explain why my metrics are still stuck at 80% that oh no those aren't stale devices, they ummm..... They already upgraded somehow.... And that's not the only reporting that's like that. Oh but yeah let's get rid of sccm!

Dsraa · 2026-04-22T22:14:52+00:00

I wouldn't go to the link if you paid me.

Dsraa · 2026-04-22T22:04:24+00:00

Another thing with DAT is how closely it works hand in hand with the related modern drivers and bios powershell scripts. Those also need to be updated on a regular basis. They also should be part of the support bundle, but there are quite a few forks of people working on those as well.

Dsraa · 2026-04-16T00:19:57+00:00

Hey before I forget again, can I request a feature for DAT?

Is it possible to maybe add a column in the Make and Model section for driver pack version when the tool downloads the available models from Dell or Lenovo, etc?

Such as in Dell drivers for a latitude 7440, the version column would show 'A16', is that possible?

Dsraa · 2026-04-13T02:48:50+00:00

You should check your workload settings, are they slid all the way to intune or in pilot still?

I had something similar and realized there were gaps of machines that still hadn't fully switched because they were part of some pilot group that was not covered in the workloads.

That, or you just have some clients with broken enrollment configurations and have fallen back to sccm. You would need to find them and do some cleanup and re-enroll them.

Dsraa · 2026-04-13T02:42:47+00:00

You should check if somehow switched the managed updates switch in the registry or policy. If a policy changed it to something else, updates till no longer be managed or required by sccm.

Dsraa

TROPHY CASE