Windows 10: Create .WIM image on MDT status goes to unresponsive state

Hi, I have a Windows 2012R2 server which has MDT installed, I'm trying to capture .wim and after few hours it goes to unresponsive state. Already verified BDD and smsts logs in Deploymentlogs$. Image doesn't capture and fails in between. How we do know if this is a Network issue or something to do with the MDT itself ? Any help would be appreciated!!

:)

 

MDT Skips .wim creation step during capture

Hi All,

As mentioned in the title;

During the MDT Capture wizard every steps works as intended (OS installation, apps, sysprep), however it skips the "Create wim" step completely and continues with a shutdown. Any idea how to fix this?

I have logs available if needed.

MDT is being done within Hyper-V.

W10 22H2.iso

 

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.

 

MDT misc

Hello All,

Another MDT question. Please help if you can, thanks in advance.

I created two custom wim images on my MDT test server.

One is for a specific laptop model and the other is a VM.

I want to copy both wim image files to my production server.

Import both OS wim files and begin to image our computers.

I tested and it seems to work.

Does anyone know of any cons to do it this way?

I feel like it would save me time, but if it would cause issues then I would capture separately.

-Thanks.

***Post moved by the moderator to the appropriate forum category.***