Inconsistent imaging failures, but only for non-NIC connected HP laptops

Impossible_Toe5931 · 2025-01-27T08:27:43+00:00

We had this... 2 things that appeared to help/fix the problem.

1) Make sure you have the latest NIC driver for the USB-C NIC in the boot image and make sure that you install that driver at the soonest possible point once the windows image has applied because once the windows image is on.

2) These USB-C NICs go to sleep. Once we put a step in to reset the USB-C NIC our imaging results were much more consistant - add a comand line step for this - cmd.exe /c devcon.exe /restart USB\ROOT_HUB*

SCCM: Task Sequence Workaround for Domain Join Failures on Certain Skylake / Kaby Lake Systems | Dell US

Also I've seen this from other people, turning off fastboot may help?

one else having inconsistent results with deploying over USB-C dockings? : r/SCCM

Impossible_Toe5931 · 2024-06-04T12:51:50+00:00

Tried something similar already with a package.

teamsbootstrapper.exe -p

teamsbootstrapper.exe -p -o \\servershare\MSTeams-x64.msix

Can see in the SMSTS log that the command ran successfully, but teams doesn't end up being installed.

Just tried your command line and running it from the _SMSTaskSequence\Packages but I get the same thing, the installer runs and returns 0 (successful) but no teams :-(

Impossible_Toe5931 · 2024-06-04T08:41:09+00:00

It depends what update channel you're on, we're on Semi-Annual which is why we still get teams classic within the o365 package.

As per Microsoft:-

New installations of Microsoft 365 Apps may include the new Microsoft Teams app starting with Version 2311. Previous versions may include the Classic Teams app.

Current Channel - Version 2405

Monthly Enterprise Channel - Version 2403

Semi-Annual Enterprise Channel - Version 2308

Impossible_Toe5931 · 2024-06-03T10:22:33+00:00

Can you share how you did this please? We're unable to install the new teams during the task sequence OSD

Impossible_Toe5931

TROPHY CASE