MDT Windows 11 - Specific Vostro 5481 Problem

[Bankesy]

Good afternoon all,

 

Hoping somebody can think of something I haven't as we use MDT just fine to deploy Windows 11 but hit a specific problem on our Vostro 5481 devices.

 

Should be Windows 11 compatible as the service tags return Windows 11 drivers on the Dell website but unlike any other device we hit the 'Dirty Environment Found' error on these around about the steps when MDT is installing Windows roles and features\runtimes.

 

What could it be about these specific devices when the task sequence works perfectly on everything else?

[garethEds]

What happens if you stop the deployment during the initial MDT phase and clean the disk before starting again? 

 

I always thought the error you see is due to the machine having incomplete deployments. So - maybe the machine isn't 'clean'.

 

SHIFT + F10

Diskpart

Select Disk 0

Clean All or maybe Clean (cannot remember the correct instruction)

 

Something like that. It will clean the disk for you and return you to the command prompt. You can then start building again.

[Bankesy]

@garethedmondson

 

Thanks, unfortunately this did not resolve the issue.

 

I wonder if it could be driver related or maybe something on this model is triggering a restart when there should not be one and knocking the task sequence out.

[garethEds]

2 minutes ago, Bankesy said:

@garethedmondson

 

Thanks, unfortunately this did not resolve the issue.

 

I wonder if it could be driver related or maybe something on this model is triggering a restart when there should not be one and knocking the task sequence out.

#

In that case can you try installing a bare Windows 11 with no specific driver deployment? If that works then add an install from cloud for the drivers and it will do them during a windows update cycle.

[garethEds]

To add to this - we went driverless on some machines and let Windows Update sort it out for us. The new DeployR does this very well.

[Olliedawg]

I've had similar before & what @garethedmondson mentioned usually fixed it.

 

Out of interest try reset the BIOS to defaults & run the TS again. Have you got all the necessary WinPE Dell Drivers?

[Bankesy]

@garethedmondson @Olliedawg

 

Thanks, testing these ideas now.

 

How would I know\check regarding the WinPE Dell Drivers? I can image other Dell models just fine.

 

Just had a quick look at that DeployR as well.

[Olliedawg]

Just now, Bankesy said:

@garethedmondson @Olliedawg

 

Thanks, testing these ideas now.

 

How would I know\check regarding the WinPE Dell Drivers? I can image other Dell models just fine.

 

Just had a quick look at that DeployR as well.

 

You can get driver packs which you can inject into the WinPE via the deployment share. Sometimes required for WinPE to "see" the network card, or storage controllers etc.. 

 

Dell Command | Deploy WinPE Driver Packs | Dell UK 

 

If you don't already inject drivers into WinPE, you're probably just using the generic ones which Microsoft includes as standard.

 

At what stage in the TS do you get the error?

[Fazza]

I had an issue with Windows PE when imaging via SCCM (I was on the latest ADK) so I uninstalled the latest ADK and used the one previous to it as it still supported W11 25h2 and that seemed to resolve the issues of drivers in the Windows PE SCCM was using so maybe that might be something you need to do?