Windows 10: Moving MDT deployment share to a new server

Hello, I'm in the process of building a new VM of Server 2022 and would like some advice on moving our deployment share MDT to the new server. I'd like to move the deployment share that resides on a separate partition on the old server and reattach to the new Windows Server 2022. The old server has both MDT and WDS installed with the DeploymentShare and the RemoteInstall folder on the same partition. Looking for some advice before diving in and ending up loosing data.Would the approach be as follows:1. Attach the partition containing the DeploymentShare and Reminst folder to the new Server

:)

 

MDT deployment stops after processing Custom Settings

Hello,

I've recently ran into an issue where when I PXE boot a VM it will load the boot image from the deployment server but stops processing after processing the Custom Settings. It's showing only the background image.

First let me say this is a home learning environment, and the issues described below only occurred after installing Cumulative Update KB5011558. I may try removing that update to see if this fixes my issue, but I'm not confident that whatever damage occurred will reverse itself.

WDS Server Manager provides the following Error and Warning EVENTS:

Error:

• The PXE server processed a request from a client of architecture x86. However, there were no boot images installed for this architecture. PXE clients of this architecture will not be able to complete the boot process successfully. To resolve this problem, add at least one boot image for this architecture.

Warnings:

• The default boot image Boot\x64\Images\LiteTouchPE_x64.wim was not found for the x64uefi architecture.
• … not found for the x64 architecture.
• … not found for the x86x64 architecture.

I opened the command prompt (F8) and getting Access Denied trying to access the Deployment share root.

The VM was created using BIOS architecture and configured for "Windows 10 and later x64".

I should note - in response to the above Error message - I have never deployed an x86 OS nor used an x86 Boot Image in my environment, nor have I ever created a VM that was not x64.

The Server is using the built in Administrator account; no other accounts exist on that system. I checked the shares, and Administrators have Full access to deployment share root.

I completely regenerated the Boot image and even added the x86 for shits and giggles. I can see the x64 boot image being loaded by the VM.

I stopped and recreated the SMB share for the Deployment Share root.

Version info:

• Windows Server 2022 Datacenter (on ESXi host)
  • MDT v8456
  • ADK/WinPE v22000
• Windows 10 Pro for Workstations v21H2 (Host for VM that's PXE booting)
  • VMware Workstation Pro 16.2.3

- - - Updated - - -

It turns out that Cumulative Update KB5011558 corrupted some of the account and NTFS permissions.
See here for the resolution that helped correct my MDT Deployment Share permissions.

[SOLVED] MDT deployment stops after processing Custom Settings - Software Deployment & Patching

I'll be sure to create a (VM) snapshot before running future updates that size...

 

MDT install application with the credentials for connecting to network shares

Hi,



Thank you for writing to Microsoft Community Forums.



I understand your query regarding Microsoft Development Kit.



However, we do have a dedicated forum for issues related to Microsoft Development Kit, let me point you in the right direction. I would suggest you to post your query in
TechNet forums, where we have support professionals with expertise on Microsoft Development
Kit to assist you with the appropriate details.



Below are few articles that might be helpful for you:

• Using the Microsoft Deployment Toolkit
  
• Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit
  
• Prepare for deployment with MDT.
  

Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Creating deployment process with WDS/MDT.

Hi, I am a Help Desk Analyst and am being challenged with learning sysAdmin tasks. I've been tasked with setting up a deployment process, and I have been trying for a few weeks now to deploy an image with WDS/MDT. I've searched the internet hard trying to figure it out but everything I try is not working so I thought I'd try a forum.

If you could please give me some direction I appreciate it a lot!

A little about my setup:

I have two servers.

Server 1 (Windows Server 2012 R2 Standard) is in charge of AD/DNS/DHCP. Server 1 is functional and I have had no issues. Example: I can manually configure a laptop and join it to my domain then log in with my AD credentials.

Server 2 (Windows Server 2019) is meant for WDS/MDT and also has a separate partition. I have completed the install and configuration of WDS/MDT and it is joined to my domain which is Server 1.

The laptops I am trying to deploy an image to are Dell Latitude E5540 and run Windows 10 Pro.

I signed up for a trial copy of Windows Enterprise so I could grab the necessary windows install/boot files from the ISO. I have used those on my Server 2 (WDS/MDT Server) to create an Install and Boot image in Windows Deployment Services because I wanted to see the laptop go through a deployment before I started to configure the image more.

The laptop I am trying to image is a Dell Latitude E5540 and has been configured BIOs to PXE boot but when I turn the laptop on it does not even attempt to PXE boot and goes straight to the normal out of the box windows setup.

I'm a bit stumped and if there is any other information can I provide or if anyone has any recommendations I would very much appreciate it!

- - - Updated - - -

Update: I was able to find out that I needed to add Option 66 and Option 67 to my DHCP settings.

I noticed my NIC was not at the top of the list in BIOS so I adjusted that and the Dell Latitude E5540 was able to hit the server. The package must have failed. I received a BSOD for Recovery "It looks like Windows didn't load correctly".

So I am making progress I think being the PXE is now working but I have to figure out where to head from here.