SCCM 2012 OSD Refresh Error: "FAILURE (5456): Unable to determine Destination Disk, Partition, and/or Drive."

I recently modified our SCCM (MDT Integrated) OSD task sequence so that we could also use the refresh deployment type.  One of the requirements for our refresh was that the hard drives be re-partitioned and formatted, just as they would if it were a "New Computer" deployment type.  To accomplish this, I copied the "Format Disk" group from the "New Computer Only" section of the task sequence into the "Refresh Only" section.  

When testing the refresh deployment, the process started off smoothly, but eventually the task sequence restarted the computer.  When the computer tried to boot back up, there was no OS on the drive. The only clue as to the cause was found in the bdd.log file: 

FAILURE (5456): Unable to determine Destination Disk, Partition, and/or Drive.


The task sequence attempts to back up the original drive to an image before re-installing the OS.  Since I had added the format steps under "Refresh Only" (which is above "Backup" in the task sequence), the drive was already wiped before the backup step tried to run.  In my case, I don't want a full backup of the computer anyway, so disabling the backup step resolved the issue.  If you do want a full backup before the drive is wiped, moving the "backup" step up into or above the "refresh only" group would probably solve this issue. 


Comments

  1. JohnNovember 3, 2013 at 9:53 AM

    So in your refreash scenario you format and repaprtition the OSDisk ? I'm trying to do the same thing but through MDT .... I am getting the 5456.

    Do you know what script is actually throughing the error, ZTIBackup ?

    ReplyDelete
    Replies
    1. Steve WhitcherNovember 4, 2013 at 9:22 AM

      John - Right, for a PC refresh, I want it to wipe the drive and reimage it, just as in a "New Computer" deployment scenario. The difference is that the task sequence starts from within the existing windows install, instead of booting from deployment media or PXE. While it is running in the existing windows instance, it runs USMT to back up user files and settings. Then it will reboot, wipe the drive, deploy the image, and just before the end, run USMT again to restore the user files and settings. But I do not want it to run the full backup, imaging the drive.

      Off the top of my head, I believe you're right, it was ZTIBackup throwing the error, but I'm not certain.

      Delete

Post a Comment

Popular posts from this blog

Mystery Solved: Bitlocker is enabled, but Intune shows the computer as non-compliant for Require Bitlocker

For some time, I have struggled to understand why Intune reports some computers as non-compliant with the "Require Bitlocker" setting, even though Bitlocker is enabled and working on the computer.  In my searches for an explanation, I found the same question asked by many others, but never an answer.  Until today. I accidentally stumbled across this article from Microsoft's Rob Lane , which explains how the Require Bitlocker setting is evaluated and why it might seem to incorrectly report a non-compliant state.  I encourage you to check out that article for full details.  I'll just summarize here the part that suddenly made this bitlocker compliance issue make sense to me. The "Require Bitlocker" setting in Intune relies on the Device Health Attestation (DHA) service in Windows 10 to report the state of Bitlocker encryption on the computer.  If Bitlocker protection is disabled or suspended, DHA will report that the computer is non-compliant with this ...
Read more

Windows 10 Credential Guard breaks WiFi

Recently, I ran into an issue with computers running windows 10 that would not connect to our WPA2-Enterprise encrypted wifi network.  When it failed to connect, there was no indication of why, only the message "Can't connect to this network."  The computers were able to connect to unencrypted networks and networks using a Pre-shared key for WPA encryption without issue. Checking the event logs on the RADIUS server to see why the comptuer failed to connect, there was no log entry for a connection attempt from the affected system.  The WLAN-Auto-Config log on the client listed a couple of errors, including Event ID 11006 and 12013, but other than showing that the failure reason was "Explicit EAP failure received", they didn't give much to go on: Log Name:      Microsoft-Windows-WLAN-AutoConfig/Operational Source:        Microsoft-Windows-WLAN-AutoConfig Date:          8/15/2016 1:11:20 PM Event ID:   ...
Read more

Data Sharing Service crashes on Windows Server 2016 - Event ID 7023

Image
While troubleshooting an issue recently on a Windows Server 2016 system, I noticed errors on the System event log about the Data Sharing Service crashing. The Data Sharing Service service terminated with the following error: %%3239247874 Searching online for more information about this service and why it might be failing, I came across a lot of people describing similar problems, but the only explanation and solution I found came from this December  blog post by Microsoft Japan .    Google translate did a great job making the post understandable to me, but since the information doesn't seem to have been widely publicized I thought I'd share it here to help get the word out. The Data Sharing Service fails due to a resource conflict with another service included in Server 2016, the User Access Logging Service.  Either one of these services alone will run without issue, but if one is already running and you try to start the other, it will fail. According to...
Read more