Windows 10: MDT Server - Wrong server shown in client boot up

Microsoft MDT server.All of a sudden, some classes of laptops were failing with invalid task sequence when applying the OS image and Applications.After various attempts, I figured I'd recreate the Deployment share, - closed old, build new one..Now authentication fails because cannot connect to a server which doesn't exist.I've right clicked on the deployment share properties and verified the path is correct and as well in the bootstrap.iniFor some reason the laptops are getting the wrong server's name.In the attached, it's \\ny-mdt-01\whatever, whereas in reality it's \\ny-mdt\whatever.How

:)

 

WDS\MDT Server killing network deploying images

OK, heres the setup. I have a server with the WDS role for pxe booting a litetouch image from MDT on the same server. DHCP server is on a different subnet. I can push out one image and notice with network analyzer I have random jumps to anywhere from
800 m\s response time to 4 k response time. If I push out two images at once then it kills network and all servers and clients lose connection. Server is virtual. There is no multicasting on network. 10 gig backbone on network. It should be able to handle
the traffic easily it just seems like something is happening to that traffic when it hits the switch I just cant tell what is causing it.

 

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 2022

2. Install WDS on the new server and point the installation to the existing E:\RemoteInstall folder

3. Install MDT and attach the existing DeploymentShare.

or is it best to take the following approach with a less likely chance of overwriting data.

1. Create a new partition with the same share name on the new server.

2. Install WDS pointing the Reminst folder to the new partiton

3. Install MDT to the new partition.

4. Copy the data from the \OldServer\Reminst folder to \NewServer\Reminst folder.

5. Copy the data from the \OldServer\DeploymentShare folder to \NewServer\Deploymentshare folder.

 

MDT Multicast

Hello Everyone,

I am new to MDT multicast and was hoping someone can answer my question, I set my MDT server up for multicast and it goes all the way to 99% and I watch it in the WDS console under my deployment share, I can see three clients and when they reach 99% and
I hit refresh the clients disappear which i think means it reached 100% but then on the client side its rolls back to installing operating system and starts the percent count again. Is multicast on MDT work different, does it first download the image to one
computer and once downloaded it distributes that one image to all others . I found an article below that explains how it should work but I am not sure if I am understanding it correctly.

Here is the overall process:

• ClientA starts a multicast session to download Win7SP1x86.wim from the MDT/WDS Server.
• When the broadcast session of Win7SP1x86.wim reaches 25%, ClientB joins the session in progress. ClientB knows that it missed the first ¼ of the Win7SP1x86.wim file, so it starts writing 25% into its local copy of Win7SP1x86.wim.
• When the multicast session reaches 100% of Win7SP1x86.wim, ClientA is done and drops off. However, ClientB is still missing the first ¼ of the file, and stays on the multicast chanel as it restarts (rolls back) to zero.
• Eventually the multicast session of Win7SP1x86.wim reaches the 25% mark where ClientB first joined. ClientB now has 100% of the file and drops off. No clients are connected, and the server stops broadcasting.