LiteTouchPE ISO after the deployment share update MDT

Cihan Akgol 1 Reputation point
2021-03-16T09:55:37.823+00:00

After updateting the Deployment share on MDT it would re-create new boot images (64 and 86) if there is a noticable difference (eg, system driver packs, etc) and then we would just import them new boot images into WDS. What about the LiteTouchPE ISO ? As noticed the system also creates them LiteTouch ISOs (64 and 86) what do we do with them? We are importing the new boot WIMs into WDS but is there any use for the LiteTouchPEs to be done. Any help would be appreciated, thanks

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).
919 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. AllenLiu-MSFT 47,316 Reputation points Microsoft Vendor
    2021-03-17T07:01:22.78+00:00

    Hi, @Cihan Akgol
    Thank you for posting in Microsoft Q&A forum.
    When we import MDT boot images into Windows Deployment Services, after update the Deployment Share, go to Windows Deployment Services, Boot Images, then go to Add Boot Image (LiteTouchPE_x64.wim) if Lite Touch Windows PE x64 is not already present in WDS:
    If Lite Touch Windows PE (x64) is already in WDS Boot Images, right click on the image and choose Replace Image (and then select the location of LiteTouchPE_x64.wim).
    For the details:
    https://www.dell.com/support/kbdoc/en-sg/000134992/importing-mdt-boot-images-into-windows-deployment-services
    (Third-party link, just for your reference)


    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.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.