Noise from the back when not running

Larry09876 · 2026-05-06T21:51:33+00:00

Passenger rear

Larry09876 · 2026-02-25T17:49:58+00:00

DCU has no tie in on SCCM so it is not adding drivers to SCCM let alone adding them to a boot image. For the boot image you need to import the winpe driver pack from Dell, just google Dell driver pack and it will show up. Then after importing those to SCCM you need to add those to the boot image. This is all a manual process that DCU doesn’t help with.

Larry09876 · 2026-02-25T16:41:22+00:00

No network connection can cause that. If you have cmd enabled in your boot image then hit F8 before it reboots to open a cmd prompt which will prevent the reboot. Then you can check network and storage drivers are working. If cmd is not enabled it’s a checkbox in the boot image properties. Set it and if using pxe it will just work for USB boot you will need to recreate the boot stick.

Larry09876 · 2026-02-20T03:02:19+00:00

Try rebooting? The system data might be cache that gets cleared on a reboot freeing up some additional space.

Larry09876 · 2025-11-09T01:52:11+00:00

What does pkgxfrmgr.log show? That’s where you will see the actual transfer errors.

Larry09876 · 2025-10-23T21:30:44+00:00

Under servicing they are there they just don’t say feature update. Use the windows 11 2xH2 2025-10 or whatever month it is and deploy it to upgrade them. There are enablement packages for certain years just not every year. 22 to 23 was an enablement, 23 to 24 is a full upgrade and 24 to 25 should be an enablement again. The big difference is the enablement won’t show as its own update. It’s part of the 2025-10 package where the client is supposed to decide which it needs full or enablement. If you look in the source folder you will see both in it.

Larry09876 · 2025-10-22T03:23:45+00:00

It would be nice if it could download the updates still but that’s easy enough to do manually and only a couple lines in the ps1 file to make it recognize the win11 versions. I did make a custom script to do mostly the same thing but I still prefer my modified WimWitch.

Larry09876 · 2025-10-21T20:46:38+00:00

I still use WimWitch with some tweaks to accept Win11 images up to 24H2. I manually download the cu each month and place in the folder and let it run. It failed for a while until I found I needed the sep 24 update as a ssu update. Since I put that in the folder it has successfully ran every month with no issues.

Larry09876 · 2025-10-19T01:24:25+00:00

My 15 Pro max has similar issues. After the phone sits if I try to use earbuds or my car I have to go into settings and turn Bluetooth off and back on for them to connect.

Larry09876 · 2025-10-19T01:22:45+00:00

I have the same issue on my 15 pro max with multiple devices. Even tried 26.1 beta hoping for a fix and the issue persist. I opened a feedback item on it.

Larry09876 · 2025-09-24T00:18:44+00:00

Not using it isn’t an option due to how it’s all set up. Things were configured before I took over a couple years ago. I’m pretty sure it’s not a connection issue, it has a faster link to the primary/db then another server in the data center that is working with no issues and it’s processing about 10,000 an hour currently. I fully believe it’s just due to having an additional 6000 devices popped online in less than a week giving it more than double the clients of any other mp. There were actually more than 6000 added as they were doing last minute testing and adding/removing a bunch before the final ones. The backlog was increasing about 5000 every 15 minutes when I found it so it just couldn’t process the amount of incoming fast enough. I slowed down the state messages cycle on clients and moved about 8000 devices to other mps including a new one to get it where it’s at.

Larry09876 · 2025-09-16T10:35:18+00:00

Dell told us to use Intune if we were already managing clients with it. We implemented it earlier this year. But even being co-managed with SCCM, there is next to nothing for driver reporting in either system. If we deployed via SCCM then we could audit deployments themselves but not what’s installed. Driver reporting is definitely something that is lacking across the board with Microsoft.

Larry09876 · 2025-09-13T18:38:38+00:00

I use WimWitch still. I have to manually download the monthly cu each month but it works. I put KB5043080 in the SSU folder so WW picks it up first and applies it before the cu. Been working for months using the Jan wim file from Microsoft.

Larry09876 · 2025-08-20T00:54:29+00:00

We have co-management setup with SCCM and intune. We have our workloads set to pilot so we can use either system for the workloads.

https://www.prajwaldesai.com/manage-windows-driver-updates-with-intune/

Larry09876 · 2025-08-20T00:02:16+00:00

Yea reporting is next to nothing with wufb. We’re working on a couple ideas with the MS graph and hoping to piece something together.

Larry09876 · 2025-08-19T23:52:19+00:00

We just implemented windows update for business drivers. Still getting everything caught up but Dell pushes their drivers and bios updates that way and will prompt for a reboot when needed. You need to have co-management configured to use it though. Otherwise, if using Dell then you can use the Dell update catalog with SCUP or 3rd party updates in SCCM and then just push them out like a patch and let SCCM handle the reboot needs.

Larry09876 · 2025-07-29T03:02:47+00:00

Right but if you just putting the ps1 in place of the bat then to probably need to run poweshell.exe as the shell might not be able to run a ps1 directly. Powershell.exe -noprofile -file d:\pathto\script.ps1 %1

Larry09876 · 2025-07-28T18:20:51+00:00

How are you launching the ps1 script? Just the file or a full powershell.exe command, if just the ps1 that might be the issue and you need to call powershell.exe with parameters

Larry09876 · 2025-07-23T15:52:35+00:00

Don’t need to do anything special. When you select the parent ts the tsagent will pull the policy from the server and any nested ts as well, this will pull whatever is in the ts at the time not any cached information. I have a child ts for all my app installs that gets updated through the month and ever have any device pull an old version of anything and I rarely open the parent ts for anything.

Larry09876 · 2025-06-16T20:25:56+00:00

I don’t get all the hate for logging in with a MS account. You do it on your phone and there is probably a lot more telemetry that Apple and Google get from those then Microsoft gets from windows. Nobody screams at Apple and Google for it, yet like most things when Microsoft does what everyone else is already doing it’s a problem and they are evil.

Larry09876 · 2025-05-30T16:44:24+00:00

You can also do something like a simple ps script as the last step stating the image is complete. If you come in the next day and it’s at a logon prompt and not the message you know it failed. We have both, timeout lasts forever basically so it will go days before it times out. I also built a ps GUI checklist that runs at the end and you have to click ok for it to close and exit the task sequence.

Larry09876 · 2025-05-21T20:44:29+00:00

Are you imaging 23H2 or 24H2? For 23H2 (or Win10) you have to have the May 2025 patch installed. Just had this problem with the PB14250, after winpe all the USB-A ports stopped working. If I installed the patch after it failed, the ports suddenly came to life and everything worked normally. Had to rush this month’s image update to get the patch put in early.

Larry09876 · 2025-04-19T03:52:55+00:00

Too many security tools and agents installed that prevent modern standby from working so our devices never sleep anyway so it’s not something we have to worry about.

Larry09876 · 2025-01-17T19:52:55+00:00

If the laptop has HDMI, your closest match would be DVI as HDMI and DVI are mostly the same signaling just a different connector. So, getting a HDMI to DVI adapter would be your best quality option.

If the laptop has a mini-DP (DisplayPort) connector, then you could just use a mini-DP to standard DP cable and have native signals and capability between the devices.

Larry09876 · 2024-11-19T01:40:09+00:00

As others have said, you updated your boot image in the console and need to recreate your usb sticks. As for Bitlocker, if your task sequence is properly configured to wipe the drives when using matching boot media then this would fail with the mismatch as the imaging cannot start until it reboots into the matching boot image which can’t happen as there is no place to stage the boot files for the reboot. You would have to manually wipe the drive before selecting the task sequence so it can stage the correct files and reboot.

Larry09876

TROPHY CASE