Involvement of SMB v2/3 in Operating system deployment

Question

Hello,

I have Endpoint Manager 2006 implemented and this particular issue came up on a remote PXE enabled distribution point running on Windows Server 2019 which is a hyper V VM.

Operating system deployment failed when multiple computers (about 10) were deployed. on the distribution point CPU would immediately rise to about 90% and then reach 100%. RAM will eventually go up and up and max out as well. Then the DP hangs.
At the client end, some will move to the WIM file download stage and it will become slower and slower. other s fails to download the NBP.

However, OS deployment on single computers worked.

I confirmed the network settings, added virtual processors and RAM but it still failed.

But I found this and disabled SMB v2/3 and instantly resolved the issue. We then deployed 17 computers without any problem.

1. What is the involvement of SBM v2/3 in OS deployment file transfer?
2. Why dose it consumes distribution point resources?
3. I haven't seen anywhere recommending to disabled SMB on a PXE distribution point?

Cheers,
Kalith

Answer 1

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

Thank you very much for your feedback and sharing the workaround. We have limited information about the behind mechanism. As a support Engineer, we are also responsible for collection customer feedback of product itself and try the best to deliver it to the product team, in order to improve customer experience. At such situation, I will summarize this and try to deliver it to product team, but not guaranteed. Once there is any feedback, we will get back to you at the first time. Thank you for your kind understanding.

Best regards,
Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.