Can't boot after deployement with mdt

Jean mi 1 Reputation point
2022-03-14T16:54:53.183+00:00

Hello,

Since we got new laptop (dell latitude 5420) i can't deploy a master on them.

i got this error : MDT Litetouch : FAILURE (5624)

The deployement end (error after 100% of the installation) but i can't boot on it. The file are here.

I can access to the deployement if i rebuild boot partition with bcdboot and then all is ok.

Do you know why my deployement won't work without a rebuild of the boot ?
I have other model and i dont have any problem with them, it's only on dell latitude 5420.

i have add the latest driver in my deploy, tried with older bios too.... nothing works

Does it talk to someone ?

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

4 answers

Sort by: Most helpful
  1. Simon Ren-MSFT 30,756 Reputation points Microsoft Vendor
    2022-03-18T09:56:44.56+00:00

    Hi,

    Thanks very much for your information.

    Per my experience, this issue may be due to multiple hard disks.

    By default, MDT Litetouch New Computer Scenario will deploy to disk 0 (the first disk). However, for multiple disks computer, the order of the disks could change depending on the load order of the storage drivers. Depending on the timing, Disk 0 could come up first, or could come up last, there is no way to force the disk ordering. So if we want to target a specific disk we need to change MDT.

    For more information, please refer to: ZTISelectBootDisk.wsf
    Note: This is non-Microsoft link, just for your reference. Thanks for your time.

    184564-disk1.png

    184565-disk2.png

    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.
    https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html

    2 people found this answer helpful.

  2. Simon Ren-MSFT 30,756 Reputation points Microsoft Vendor
    2022-03-15T08:50:01.167+00:00

    Hi,

    Thanks for posting in Microsoft MECM Q&A forum.

    There are some other users encounter similar issue. The solution is changing the bios option from default RAID to AHCI. Please try to see if it works. Refer to below similar threads:

    Weird imaging issues with Dell Laptops using WDS / MDT
    Latitude 5520 Images Failing Immediately
    Please note: The links are not from Microsoft, just for your reference. Thanks for your time.

    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.


  3. Jean mi 1 Reputation point
    2022-03-15T09:21:38.813+00:00

    To explain a little better :

    The deployement end, 100 % complete but as i said can't boot on it (no boot device)

    I can fix it with playing with bcdboot :

    I have to copy boot file from windows/system32 and add it to my deployement with a recovery key.

    So it seems there is a problem with the boot file during the deployement...


  4. Jean mi 1 Reputation point
    2022-03-16T15:55:13.18+00:00

    Hello

    I tried to add only the network and storage driver as you said but nothing has change - still same error.

    In dism logs i have this error :
    [920.1040] [0x80070005] GetImageErrorCode:(2866): Access is denied.

    Could it come from an anti virus ?

    Also at the end of my deployment, i tried a diskpart and i had some surprise... my main disk was f: and the disk was full (only 40G/250 are suppose to be taken)...
    I really don't get how a bcdboot can fix all of that, i am really lost.

    Thanks for trying to help.

    0 comments No comments