XE4 MDT image cannot be deployed to Dell XE4 PC, but is good for Dell XE3 PC, through PXE (WDS) server.

Li, Shijun 21 Reputation points
2022-11-14T19:47:01.527+00:00
  1. We created a XE4 MDT image with MDT8456 tool. Its wim file was generated by sysprep from this XE4 PC. Its OS is Win 10 IoT enterprise LTSC 21H2. This MDT image is good for Dell XE3 PC, but cannot be deployed to Dell XE4 PC, which is very strange (see attached two pictures)
  2. When creating this XE4 MDT image in ISO file format (Offline version), it can be deployed successfully to Dell XE4 PC
    We would like to deploy this XE4 MED image through PXE (WDS) server. Please help us to solve our current issues.
    260170-rempotely-deploy-a-image-with-bootable-winpe-in-us.png

260225-rempotely-deploy-a-image-from-pxe-wds.png

System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
214 questions
Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
825 questions
0 comments
Accepted answer
  1. CherryZhang-MSFT 6,481 Reputation points
    2022-11-23T01:43:21.99+00:00

    Hi @Li, Shijun ,

    Thanks for your feedback and sharing. We're glad that the question is fixed now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly. It's appreciated that you could click "Accept Answer" to the reply.

    Problem/Symptom:
    XE4 MDT image cannot be deployed to Dell XE4 PC.

    Solution/Workaround:

    1. From the reimaged XE4 PC where the wizard.hta window was blank and was with the Drivers from Dell XE4 cab file, I updated this PC through windows update,
    2. Extract all drivers from this updated PC
    3. Using these extracted drivers to created MDT image of XE4
    4. Deploy this MDT image to XE4 PC

    Thanks again for your time! Have a nice day!

    Best regards,
    Cherry

    0 comments

6 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. CherryZhang-MSFT 6,481 Reputation points
    2022-11-18T07:26:49.4+00:00

    Hi @Li, Shijun ,

    I have done some research on your question. This may be caused by the task sequence has not been fully executed. Please check the following logs, is there any useful information?

    • BDD.log
    • SMSTS.log
    • Wizard.log

    There are three locations to locate MDT log files for troubleshooting:

    Before the Image is applied to the machine：X:\MININT\SMSOSD\OSDLOGS
    After the system drive is formatted：C:\MININT\SMSOSD\OSDLOGS
    After the deployment is successful：%WINDIR%\SMSOSD or %WINDIR%\TEMP\SMSOSD

    Looking forward to your feedback.

    Best regards,
    Cherry

  2. Li, Shijun 21 Reputation points
    2022-11-22T00:02:24.307+00:00

    Hi Cherry:

    So far the issue of The blank wizard window instead of the summary window at the end of MDT8456 image deployment is still there. Please see the attached pdf file that briefly described what I have be doing.

    262720-the-blank-wizard-window-instead-of-the-summary-win.pdf

    0 comments
  3. CherryZhang-MSFT 6,481 Reputation points
    2022-11-15T06:23:31.867+00:00

    Hi @Li, Shijun ,

    1, I have done some research on your question. Most people choose to do is add a simple delay (wscript.sleep 2500) in the Litetouch.wsf script (in the DeploymentShare Scripts folder). The value of the delay is generally 2500 (2.5 seconds), this value should work for most. You could possibly lower this, or even increase it if you still have the error. For example, 5 seconds or even 10 seconds.
    For more details, please refer to the following articles:
    MDT 2010 Deploy, DHCP Error (microsoft.com)
    https://4sysops.com/archives/resolving-a-connection-to-the-deployment-share-could-not-be-madeerrors-in-mdt/
    Note: Microsoft provides third-party contact information to help you understand the problem. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    2, The WinPE profile for the Boot.WIMs may lack the correct NIC driver for Dell XE4. Dell provides a WinPE Driver pack to customer.
    For more details, please refer to this link:
    https://serverfault.com/questions/281507/wds-error-a-connection-to-the-deployment-share-could-not-be-made
    Note: Microsoft provides third-party contact information to help you understand the problem. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    3, Furthermore, what version of the ADK and windows PE are you using? It is Recommend that grab the driver pack for the correct version of WinPE for the OS being deployed.

    4, At this stage of the error, can we get smsts.log and BDD.log by pressing F8 into the command line? If so, please check the relevant logs, if there are any useful information.

    Looking forward to your feedback.

    Best regards,
    Cherry

    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.

  4. Li, Shijun 21 Reputation points
    2022-11-17T20:43:20.203+00:00

    Hi Cherry:

    Finally, I have solved the problem by adding a second network card and booting with the UEFI PXEv4 instead of using ONBOARD NIC(IPV4). But after the deployment was done, there is a window "Wizard.hta which is empty. Usually there is a Summary window at the end of development. Could you please have ideas on this unexpected observation (Second picture)?

    Thanks for your time and help very much

    261604-image1.png
    261612-image2.png

    0 comments