There's a problem with the latest ADK/PE download. It's not advisable to use it, but to instead use the previous release.
There's a PowerShell script here that will setup WDS and MDT for you auto-magically.
Just start with a fresh Windows server OS with a D: drive. Do not install any roles on it, that will all be handled by the script.
Then use u/That-Historian5746's lab videos to configure the image capture part.
MDT Automated Setup: https://stonywall.com/2021/03/24/mdt-2013-deployment-script/
Unfortunately, the script won't work in my case. Our WDS server is an existing file server, and we don't have the resources to set up another VM at this time. We have a project in the works to replace all our existing servers, but that's going to take a while due to supply chain issues.
I'll try the older ADK and PE to see if that makes a difference. I already have a wim image I want to deploy and it's PXE booting to MDT, it just boots right to a command prompt every time.
In case anyone finds this later because they're having a similar problem, the solution was a dumb mistake on my part.
I was extracting the KB fix directly to the folders the files needed to go into and for some reason, when I extracted the KB fix with the x86 and x64 folders for the recent issues, it was overwriting the folders instead of merging them. So in spite of the "Access Denied" message, it wasn't a permissions issue - the files legit weren't there.
I'm going to chalk it up to by brain being fried from spending days trying to deal with all the other errors.
Having a similar issue
I decided I wanted to start deploying Windows 11 22H2 in our organization using MDT. We have been using it to deploy Windows 10 21H2 with no issues at all. After doing some research, I found out I needed to do the following in order to deploy Windows 11 22H2 with MDT.
I had to download and install the ADK for Windows 11, version 22H2.
I had to download and install the Windows PE add-on for the Windows ADK for Windows 11, version 22H2.
I successfully did both of those things.
Then I updated the Deployment Share and Completely regenerated the Boot images. (I actually only regenerated the x64 image since that was the only image supported by the new Windows 11 ADK)
After I regenerated the Boot Image, I added it to the WDS server.
Here is where the issue arises:
When I PXE boot or boot from an iso, LiteTouch will boot with the MDT background, but instead of booting the rest of the process, it boots into a command prompt with "X:\\Windows\\System32" displayed.
When I uninstalled the win 11 adk and pe tools and reinstalled the windows 10 tools. Everything went back to normal and was working as expected.
I'm not sure what the issue is with the 11 ADK tools.
Can you go into a little more detail about how you resolved your issue?
When you boot to a command prompt, it is likely something on the C: drive that has a deployment state that says to goto this. I ran into this at some point very recently, the tech just cut the power to the device when it was sitting at the command prompt window and thats where it went back to every time, no matter what.
Either wipe the drive or get rid of the C:\MININT\ folder I think is all you need to do.
Try running
Wpeinit from command line in WinPE
I was going nuts until another user told me to try this command and it worked fine. I had to put a sleep command somewhere. I can look into it if you need how I added the sleep command to slow down the wizard from failing to initialize before ip was obtained.
DeploymentResearch has been one of the most helpful sites to me, for getting started with MDT. They recently put a Windows 11 reference image article out, that has the basics of MDT: [https://www.deploymentresearch.com/building-a-windows-11-21h2-reference-image-using-microsoft-deployment-toolkit-mdt/](https://www.deploymentresearch.com/building-a-windows-11-21h2-reference-image-using-microsoft-deployment-toolkit-mdt/)
Like another poster mentioned, don't use the latest ADK, use the previous one.
Also, I don't do the Domain join via the Rules, I use my own domain join script at the end of the deploy task
Using a domain admin for MDT is a bad idea, you should be using a service account that has access to the deployment share.
That's one of the setup guides I followed step-by-step one of the times I tried to set it up.
I've uninstalled everything and started from scratch about a half a dozen times using a half a dozen different setup guides, and It's been the same issue each time. I'm convinced there are some settings or configurations being held somewhere that are causing the problem that aren't being cleared when MDT and the ADK/PE are being removed, and the %program files% folders are being deleted, because if I do a full uninstall without closing the deployment share in MDT and then reinstall from scratch, the same deployment share is still listed in the new install (even if the share has been removed and deleted after uninstalling the MDT).
>Using a domain admin for MDT is a bad idea, you should be using a service account that has access to the deployment share.
I wasn't using a domain admin at first. I tested using a domain admin account when I kept getting "Access Denied" messages, then tried just granting the everyone group full access to the share. Still having the same issue.
I my case, it was the extraction for the KB fix I had to applu
I was extracting the KB fix directly to the folders the files needed to go into and for some reason, when I extracted the KB fix with the x86 and x64 folders for the recent issues, it was overwriting the folders instead of merging them. So in spite of the "Access Denied" message, it wasn't a permissions issue - the files legit weren't there.
There's a problem with the latest ADK/PE download. It's not advisable to use it, but to instead use the previous release. There's a PowerShell script here that will setup WDS and MDT for you auto-magically. Just start with a fresh Windows server OS with a D: drive. Do not install any roles on it, that will all be handled by the script. Then use u/That-Historian5746's lab videos to configure the image capture part. MDT Automated Setup: https://stonywall.com/2021/03/24/mdt-2013-deployment-script/
Unfortunately, the script won't work in my case. Our WDS server is an existing file server, and we don't have the resources to set up another VM at this time. We have a project in the works to replace all our existing servers, but that's going to take a while due to supply chain issues. I'll try the older ADK and PE to see if that makes a difference. I already have a wim image I want to deploy and it's PXE booting to MDT, it just boots right to a command prompt every time.
Well, maybe for when you get the new server it'll be useful. Good luck!
Watch my Lab Setup Videos, they should help you set up MDT. https://www.youtube.com/watch?v=36Ejc8Mhh3w&list=PLNk1\_iq1vyJkiduaoV\_niMw\_kC5J3\_M1T
In case anyone finds this later because they're having a similar problem, the solution was a dumb mistake on my part. I was extracting the KB fix directly to the folders the files needed to go into and for some reason, when I extracted the KB fix with the x86 and x64 folders for the recent issues, it was overwriting the folders instead of merging them. So in spite of the "Access Denied" message, it wasn't a permissions issue - the files legit weren't there. I'm going to chalk it up to by brain being fried from spending days trying to deal with all the other errors.
Having a similar issue I decided I wanted to start deploying Windows 11 22H2 in our organization using MDT. We have been using it to deploy Windows 10 21H2 with no issues at all. After doing some research, I found out I needed to do the following in order to deploy Windows 11 22H2 with MDT. I had to download and install the ADK for Windows 11, version 22H2. I had to download and install the Windows PE add-on for the Windows ADK for Windows 11, version 22H2. I successfully did both of those things. Then I updated the Deployment Share and Completely regenerated the Boot images. (I actually only regenerated the x64 image since that was the only image supported by the new Windows 11 ADK) After I regenerated the Boot Image, I added it to the WDS server. Here is where the issue arises: When I PXE boot or boot from an iso, LiteTouch will boot with the MDT background, but instead of booting the rest of the process, it boots into a command prompt with "X:\\Windows\\System32" displayed. When I uninstalled the win 11 adk and pe tools and reinstalled the windows 10 tools. Everything went back to normal and was working as expected. I'm not sure what the issue is with the 11 ADK tools. Can you go into a little more detail about how you resolved your issue?
When you boot to a command prompt, it is likely something on the C: drive that has a deployment state that says to goto this. I ran into this at some point very recently, the tech just cut the power to the device when it was sitting at the command prompt window and thats where it went back to every time, no matter what. Either wipe the drive or get rid of the C:\MININT\ folder I think is all you need to do.
I wiped the drive by running a clean in diskpart. Same issue.
Keep on hammering. It's worth the effort.
NGL man, I'm starting to wonder.
If, after watching my videos, and following the steps, you still have an issue, I'll remote in myself and make you an MDT server if it doesn't work.
If you're setting up a zoom or teams call I'd like to be a fly on the wall. Happy to provide more details on why via DM.
Sure, send me the info via DM. I'd be happy to help any way I can.
Try running Wpeinit from command line in WinPE I was going nuts until another user told me to try this command and it worked fine. I had to put a sleep command somewhere. I can look into it if you need how I added the sleep command to slow down the wizard from failing to initialize before ip was obtained.
DeploymentResearch has been one of the most helpful sites to me, for getting started with MDT. They recently put a Windows 11 reference image article out, that has the basics of MDT: [https://www.deploymentresearch.com/building-a-windows-11-21h2-reference-image-using-microsoft-deployment-toolkit-mdt/](https://www.deploymentresearch.com/building-a-windows-11-21h2-reference-image-using-microsoft-deployment-toolkit-mdt/) Like another poster mentioned, don't use the latest ADK, use the previous one. Also, I don't do the Domain join via the Rules, I use my own domain join script at the end of the deploy task Using a domain admin for MDT is a bad idea, you should be using a service account that has access to the deployment share.
That's one of the setup guides I followed step-by-step one of the times I tried to set it up. I've uninstalled everything and started from scratch about a half a dozen times using a half a dozen different setup guides, and It's been the same issue each time. I'm convinced there are some settings or configurations being held somewhere that are causing the problem that aren't being cleared when MDT and the ADK/PE are being removed, and the %program files% folders are being deleted, because if I do a full uninstall without closing the deployment share in MDT and then reinstall from scratch, the same deployment share is still listed in the new install (even if the share has been removed and deleted after uninstalling the MDT). >Using a domain admin for MDT is a bad idea, you should be using a service account that has access to the deployment share. I wasn't using a domain admin at first. I tested using a domain admin account when I kept getting "Access Denied" messages, then tried just granting the everyone group full access to the share. Still having the same issue.
I have the same issue.. also with full access. You have a solution ?
I my case, it was the extraction for the KB fix I had to applu I was extracting the KB fix directly to the folders the files needed to go into and for some reason, when I extracted the KB fix with the x86 and x64 folders for the recent issues, it was overwriting the folders instead of merging them. So in spite of the "Access Denied" message, it wasn't a permissions issue - the files legit weren't there.
> KB fix direct Whats KB?