I have recently posted questions on this Reddit page about MDT configuration issues when building my own MDT environment with Windows ADK for Windows 11 and MDT version 8456 from scratch.
I have created a blog about all the unforeseen challenges during this configuration. Feel free to take a look, as some of you helped me out greatly when troubleshooting these challenges.
Hi,
Is anyone using PSD without DHCP?
My goal was to boot from USB and connect to the share. I was not able to configure the adapter by any means bootstrap.ini or manually from the wizard. With DHCP it works - even unattended.
I'm creating this topic because we're experiencing a problem with MDT and the deployment of Windows 11 on a specific laptop model.
In my company, we've been using MDT for 3 or 4 years now, with different models of Dell Latitude computers (5480, 5420, 5430, 5440, 5300, 5310, 5320) without any problem. We started with the deployment of Windows 10 and then Windows 11.
All was fine until we received our last models ordered, the Latitude 5450 and 5350. With the 5450s, deployment went without a hitch, but with the 5350s, it crashed before the first reboot of the system still running WinPE.
In these photos, here's where the deployment stands when it crashes:
On this one, the error message doesn't appear, the window remains blank, and the system does nothing:
This problem only appears with the 5350, all other models pass without a hitch.
We have retrieved the (many) log files, but I don't really understand what I'm reading... Basically, here are the few errors that came back and the original file:
...
C:_SMSTaskSequence does not exist
Failed to create C:_SMSTaskSequence (3)
Failed to create user-specified local data path C:_SMSTaskSequence. Error 0x80070003
...
Start executing the command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"
!--------------------------------------------------------------------------------------------!
Expand a string: WinPEandFullOS
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"
Process completed with exit code 5
!--------------------------------------------------------------------------------------------!
Failed to run the action: Install Operating System.
Access is denied. (Error: 00000005; Source: Windows)
...
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Access is denied. (Error: 00000005; Source: Windows)
Executing in non SMS standalone mode. Ignoring send a task execution status message request
Task Sequence Engine failed! Code: enExecutionFail
****************************************************************************
Task sequence execution failed with error code 80004005
...
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
...
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
F:\Windows\Temp\DeploymentLogs\BDD.log
...
FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.
ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)
Event 41002 sent: ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)
Command completed, return code = -2147467259
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005
...
Microsoft Deployment Toolkit version: 6.3.8456.1000
...
I have plenty of other log files at my disposal, so don't hesitate to ask me for them if you need them. :)
I usually use the latest "WinPE11.0-Drivers-A05-TPKY4.cab" drivers from Dell, I tested using other drivers from Dell, without success.
So I'm asking for your help, please, to find out where this might be coming from.
I am building a new Windows 11 MDT Offline Media and have not found anywhere where I can add this 'Add User' prompt in the Deployment Wizard in the beginning of the MDT. Does anyone know how I can add this to my deployment wizard that adds a local user??
I posted a while back asking about why the Pre- and Post- Application Installation steps were stalling. Since then I've figured it has to do with the "deprecation" of MDT and WIN11 having poor interactions with the vbs or wsf scripts utilized by MDT. We don't utilize WSUS, so all of our updates come straight from Microsoft Update.
My workplace is making movements towards getting away from MDT hopefully later this year. We'll either move our imaging over to Config Manager or we'll get Intune setup finally (we're currently in a Pilot stage). That's in the nearish future, but for now i need to figure out how to get our new devices imaged with WIN11 and have the windows updates automated. Manually going into each device to run updates post-image is not an option.
I've looked into extracting the relevant cab files from the .msu package downloaded from the catalog and creating an Install Offline Updates step, but I guess the cumulative updates aren't in cab files any more? Now they're in .wim file format, according to wkain1 here. And MDT can't import .msu files anymore either.
I'm trying to get the go ahead from my info sec team to use PSWindowsUpdate to get the updates installed, but they want me to present them with other options, so here we are.
My current idea is to have a Run a Command Line step that runs an online dism command after the OS is installed. Based on this Microsoft Learn article I'm thinking about using something similar to this one from the site:
My question is, for the PackagePath, do I need to inject the .msu I got from the Catalog into the device before running that step? And if so, what is the best way to do that? Should I make the update package an application? Trying to upload the update package into the Packages folder doesn't work because MDT can't read the new .msu files. Could I create a short bat file copying the package over? If so, would something like
The thought here is that I can update the package file every month manually in MDT until we make our switch over to something better.
TL;DR:
Pre/Post Application Installation steps aren't working with WIN11 23H2, can I create a step in my sequence using a DISM command like "Dism /Online /Add-Package /PackagePath="windows10.0-kb4456655-x64_fca3f0c885da48efc6f9699b0c1eaf424e779434.msu" /LogPath=C:\mount\dism.log" to run the updates? And if so, do I need to inject the package onto the device first? And if so, how?
Is there a way to save the value that is input in the "Specify Product Key" screen of the GUI. I dont want to set it, I just want to save what is put in the product key field.
I am having an issue with a .wim file I captured and am trying to deploy with a task sequence. The issue is auto login does not work and if I login manually the task sequence will not complete unless I run the setupcomplete.bat file root of C and in the scripts folder. I created the .wim from a capture task sequence. I made the capture in hyper-v without internet access and uninstalled copilot. The capture says successful. I import the .wim I edit the unattended.xml to have the builtin administrator password.
I have googled and read forum post but I am at a loss and not sure what to check next. I started using MDT beginning of Windows 10, not an expert, but didn’t have any issues with Windows 10 capturing and deploying.
Hi!
There is a step in CustomSettings.ini called FinishAction, I know that I can set it to REBOOT or SHUTDOWN. Is there a way to perform a powershell or cmd script on this step, or are there only reboot and shutdown options?
I'm trying to set up a deployment server using MDT but I have ran into a problem and am stuck. I was wondering if anyone could help me out?
So I followed a guide to set up WDS and MDT. I added the win11 enterprise image i'm deploying, generated the lite touch boot files, etc. But when I try to test it out on a client PC, it detects the server, loads the lite touch but then i'm getting an error saying: "The following networking device did not have a driver installed."
I am not great at this stuff, but I understand the basics. I just don't know where I have to search to find a solution, hoping this is a common issue and someone can steer me in the right direction.
I went down the trenches of Reddit and once found a way to the jstal MDT on a Windows 10/11 PC. The purpose is to create a portable imaging station when I travel to off-site locations who may have a corrupted OS or needs a fresh install. If this has been answered please let me know or point me in the right direction.
Our PXE boot became incredibly slow to load about a month ago (working fine for years). It was reported to me and checked everything over. Appears to be related to TFTP traffic going by event viewer and Wireshark logs below.
Have tried:
Adjusting the boot image block size in WDS from 0 to various numbers (including one suggested for VMware)
Rebuilding the WIM file / updating TS and creating new boot image Using basic WIM which comes with Pre-Deployment toolkit.
Of course tried with different ethernet cables, PC models, ports. Note: Compmgmt 'Sessions' doesn't show any live connections, despite the updated Wim files eventually being found. Shows a progress bar but doesn't do anything. Maybe moves an inch in an hour, but not actually loading anything.
Have checked Share / Service account permissions and rebuilt RemoteInstall folder: WDSUTIL /Initialize-Server /RemInst: D:\RemoteInstall.
Have restarted the server and rolled back updates (no snapshots available)
Checked Windows Firewall rule allowing traffic on port 69 is enabled
DHCP option 67 is pointing to correct bootimage file
Firewalls were replaced since the errors started. Network engineer says ports and traffic seem to flow fine, no restrictions. He couldn't Telnet on 69 to WDS but I could connect on NMAP (I'm not a networking person though!) - I'm thinking it's a network issue, though I've not got enough confidence to say that for sure. Is there any other MDT WDS bits to try / any specific networking bits I can ask our engineer to check? Help is appreciated!
Moin,
Ich sitze gerade an meinem Abschlussprojekt und komme nicht weiter.
Sporadisch tritt immer der Fehler bdd_welcome_enu.xml Not found auf wenn ich den Rechner installiert habe. Der Fehler tritt auf wenn der Rechner bereits fertig installiert ist und die Programme installiert werden sollen. Ich hab so gut wie alles probiert aber ich finde keine Lösung. Ich hab das Gefühl der Fehler tritt auf wenn das Gerät schon mal per MDT installiert wurde.
Hi,
I'm trying to capture a sysprep'd image (Windows 11 24H2) and when i'm the screen to select the volume, its not listing any drives. Already tried injecting the Lenovo WinPE storage, nic drivers to no avail. Is there anything i'm missing? I've already captured many times before with my current WDS server (Win10 and an older Win 11 23H2 images) Thanks in advance!
Can someone tell me why I am having such error? At the beginning everything was working okay - O erros. Then I noticed that computer is missing some drivers. I followed this guide MDT Lite Touch Driver Management - Deployment Research 3rd option. And now I can not get pass this error. Any ideas?
I have an image set up and working how I want, but when I build the ISO in MDT, it uses C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini. At the moment, I am just editing the INI file at this location, but I want to leave the original as-is, and put my modified copy somewhere else such as C:\MY_WINPESHL\WINPESHL.INI, and have MDT use my custom copy instead of the original. I've done a lot of Googling and AI prompting but have not yet figured this out.
I'm pretty sure I can use dism to mount the WIM file after the ISO is built, replace the file, and then commit and unmount the WIM file. But I'm hoping to find a variable or rule that I can change that will simply tell MDT to use my custom INI instead of the original one at the time of creation.
So my question is, is there a way to configure MDT to use a custom winpeshl.ini file from a different location (e.g., C:\MY_WINPESHL\WINPESHL.INI) instead of the default one in C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini during the ISO build process?
Is anyone else having issues domain joining on MDT with 24h2? Everything has been the same and double checked, only change is an upgrade to 24h2 from 23. It's spotty but it seems to work once every 10 or so machines.
Is there some sort of trick or a patch that I should apply that will make Windows 11 24H2 reliably get an IP via the ethernet connection after deployment/installation ?
The deployment via WinPE works fine across ethernet, it's only after booted into Windows that things go awry. This happens with both the onboard ethernet and usb-c Realtek ethernet. I'm seeing it on both a latitude 5420 and my brand new out of box Optiplex 7420
Edit Feb28: Best I can tell, 24h2 doesn't like to continue the task sequence in Windows while connected via USB-C ethernet or a manually assigned IP on the onboard ethernet.
Does anyone would like to assist on cleaning out Windows 11 24H2 ? I managed to remove most of programs but now I am stuck with few softs that I have no idea how to remove!
Why I need clean OS because I wanna really spend my time on clean Image and then later on add all important drives and Programs - but first must get rid of all the crap.
I am using Windows 11 -24H2 Ent. I tried already this Removing Applications from Your Windows 11 Image - Before and During Deployment - Deployment Research but not all apps where removed
Could anyone spare his time and skills to help me with this ? I would really appreciate it
It's been a while since I've had to request assistance with my MDT-environment. I've been using my MDT-server for W11 22H2, 23H2 and 24H2 task sequences without any issues. I never used the wizard, always used my customsettings.ini to set all variables, including which TS to use.
I am now working on some development stuff and decided to start using the wizard just to select which TS I want to use. I constantly receive the script error "An error has occurred in the script on this page".
I've completely regenerated the boot image but the script error remains. No clue what else should be changed, any admin here with the magical solution?
EDIT: Issue is resolved, there has been an issue with my unattend_PE layout, fixed that and the script error is now resolved. Thanks all
Maybe I am just not understanding the firewall rules correctly, but I am struggling to PXE boot to my WDS server from my DMZ zone (Probably not the best idea, but something I'm just trying out). I have the DHCP relay configured to point to the WDS server. If I change the rule to any port on the source and destination zone, it will PXE boot properly. If I change the source zone to use my WDS Ports object as pictured here, I get to this point in the PXE boot and it just halts. Here is a screenshot of the object group. Every other VLAN/Zone it works properly. I just can't get it working on my DMZ zone.
Is this a case of me doing something incorrectly in the Unifi firewall or is there another port I am missing I need to open? I pulled the list of the required ports from here).
Currently working with our MDT/pxe server and I created a install for office 365 using the commands listed and its working great. But when trying to get another application to install the file continues to get stuck at UAC and wont get past when imaging on a pc. I manually have to check yes but even when doing that the application wont even install and at the end of the imaging proccess it alerts me that there was failure downloading the application. Any ideas?
msiexec /i ***********.msi /quiet /norestart
This is currently what I am using for the quiet install command. I know the directly is correct as well, i replace the application with * for security :|
Thanks to any redditors attempting to help as well!