locked
MDT 2013 Update 1 Causing Issues RRS feed

  • Question

  • Updated to update 1 to prepare for WIN10.  Updated all deployment shares successfully and recreated all my ISO's.  I am able to image from USB to all desktops/laptops but no longer MS Surfaces.  Getting this error: 

    FAILURE (5615): False: Boot Drive was not found, required? Litetouch deployment failed, Return Code = -2147467259 0x80004005

    currently looking through BDD.logs to see if I get more of a clue.  This was all working before update 1.


    • Edited by rodgerkrau Wednesday, February 17, 2016 9:17 PM
    Wednesday, February 17, 2016 8:53 PM

Answers

  • Did you create all new task sequences (necessary due to updated code)? Try making a new task sequence and test using that.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    • Marked as answer by rodgerkrau Friday, February 19, 2016 9:41 PM
    Thursday, February 18, 2016 9:07 PM
  • Didnt have to create all new task sequences.. Just copied the UEFI sequence from my old TS and now everything is working!
    • Marked as answer by rodgerkrau Friday, February 19, 2016 9:41 PM
    Friday, February 19, 2016 9:40 PM

All replies

  • You should go ahead and move to Update 2 since it fixes bugs in update 1. Make sure you've updated your PE drivers with drivers meant for Windows 10 as the latest MDT uses PE 10.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, February 18, 2016 3:40 PM
  • Update 2 did not fix the issue.  only an issue with UEFI devices.

    just to note, this environment was all working before the update.  Currently deploying win8.1.  Need to start preparing for win10 so updated MDT 2013 to update 1 (also tested update 2).  Also updated ADK to the latest 10 version.  now cant deploy win8.1 to ONLY  UEFI devices.


    • Edited by rodgerkrau Thursday, February 18, 2016 8:38 PM
    Thursday, February 18, 2016 8:34 PM
  • Did you create all new task sequences (necessary due to updated code)? Try making a new task sequence and test using that.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    • Marked as answer by rodgerkrau Friday, February 19, 2016 9:41 PM
    Thursday, February 18, 2016 9:07 PM
  • Didnt have to create all new task sequences.. Just copied the UEFI sequence from my old TS and now everything is working!
    • Marked as answer by rodgerkrau Friday, February 19, 2016 9:41 PM
    Friday, February 19, 2016 9:40 PM