Windows

Failure 5456: Unable to determine destination disk, partition, and/or drive, see BDD Log

MDt

The BDD.log is an aggregated MDT log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file. Deployment Toolkit (MDT) provides information on current known issues, possible workarounds for those issues, and troubleshooting guidance. The MDT log file format is designed to be read by CMTrace. Use this tool whenever possible to read the log files, because it makes finding errors much easier. Kindly refer to the following guides for more information on WDS and MDT. How to setup and install WDS role, how to configure DHCP Server option 60, 66, and 67 for WDS, how to remove Windows Deployment Services role via the GUI and PowerShell, how to add boot and install images to WDS and configure Multicast transmission via the GUI and WDSUTIL, and how to deploy images to computers or virtual machines using WDS.

Lite Touch Installation (LTI): LTI is a high-volume deployment strategy for small to midsized organisations that combine the use of MDT with WDS which allows Administrators to deploy devices via network-based installation. 

The following error below will be prompted when MDT is unable to install the Windows operating system (OS) on your device due to not being able to format the drive.

Failure 5456: Unable to determine destination disk, partition, and/or drive. See BDD.LOG. LiteTouch deployment failed, return code = -2147467259 0x80004005. Failed to run the action: inject drivers

Solution: This actually depends on your environment setup. If you have a disk partitioning tool (script) integrated into your wimpe in the path below, you do not have to perform the steps below as the installation will run smoothly. In this approach, you will have to mount the wimpe file and then unmount afterward. I will be discussing these steps in the future.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us

For those that do not have a disk partitioning tool (script) capable of formatting the drive for Windows installation, kindly follow the steps below.
– Launch Deployment Workbench, and expand the deployment share
– Navigate to the Task Sequence and right-click on the properties window to open it as shown below.

TaskSeq1

Uncheck the “Disable this step” as shown below: This will activate the Formate and disk Partition (UEFI) as shown below.
– Click on Apply and OK.

Task-seq-1

Henceforth, you should be able to configure and complete your deployment without further issues. If you wish to proceed from here, kindly refer to this guide “how to deploy Windows using ADK, MDT, and WDS“.

For some related articles, please see the following guides: No bootable media found system halted: Unable to PXE boot WDS to Virtualbox, how to configure DHCP Server option 60, 66 and 67 for Windows Deployment Services, how to remove Windows Deployment Services role via the GUI and PowerShell.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x