none
MDT 2013 can't deploy Windows 8.1 with Lite touch image

    Question

  • Hello to everyone,

    at any time when i want to deploy an Windows 8.1 OS with MDT and an Litetouch image, the service stop at point 44.

    The service throws me an Failure 5627.

    This is the the BDD. log error

    [FAILURE ( 5627 ): -1073741515  0xC0000135: Run DISM.exe]LOG]!><time="15:39:32.000+000" date="11-04-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Event 41002 sent: FAILURE ( 5627 ): -1073741515  0xC0000135: Run DISM.exe]LOG]!><time="15:39:33.000+000" date="11-04-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="15:39:33.000+000" date="11-04-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="15:39:33.000+000" date="11-04-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="15:39:34.000+000" date="11-04-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="15:39:34.000+000" date="11-04-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    and this is the smsts.log error

    [Failed to run the action: Install Operating System. 
    Unknown error (Error: 000015FB; Source: Unknown)]LOG]!><time="15:39:33.686+000" date="11-04-2013" component="TSManager" context="" type="3" thread="1788" file="instruction.cxx:3101">
    <![LOG[Sending status message . . .]LOG]!><time="15:39:33.686+000" date="11-04-2013" component="TSManager" context="" type="1" thread="1788" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="1" thread="1788" file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=5627]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="0" thread="1788" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="0" thread="1788" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="0" thread="1788" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="0" thread="1788" file="instruction.cxx:3210">
    <![LOG[The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="3" thread="1788" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015FB; Source: Unknown)]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="3" thread="1788" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="1" thread="1788" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:39:33.701+000" date="11-04-2013" component="TSManager" context="" type="1" thread="1788" file="utility.cxx:302">
    <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)]LOG]!><time="15:39:33.717+000" date="11-04-2013" component="TSManager" context="" type="0" thread="1788" file="tsmanager.cpp:767">
    <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="15:39:33.717+000" date="11-04-2013" component="TSManager" context="" type="3" thread="1788" file="tsmanager.cpp:767">
    <![LOG[****************************************************************************]LOG]!><time="15:39:33.717+000" date="11-04-2013" component="TSManager" context="" type="1" thread="1788" file="tsmanager.cpp:789">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="15:39:33.717+000" date="11-04-2013" component="TSManager" context="" type="3" thread="1788" file="tsmanager.cpp:790">

    I got the same error on MDT 2012 therefore i updated to MDT 2013.

    What i have done since this error?

    - i fully regenerate the boot images

    - i created new tasksequenzes

    - i import all the necessary driver to the deployment toolkit and the driver package section in mdt.

    nothing gives me an other error as this above.

    Can anyone give me a tip how to fix this error?

    PS:

    here are the full BDD and smsts log files

    https://dl.dropboxusercontent.com/u/2332305/Deployment_error/BDD.LOG

    https://dl.dropboxusercontent.com/u/2332305/Deployment_error/smsts.log

    PPS: if i created this Request in the wrong section please push it to the right one. 



    • Edited by Hendrik.Höcke Tuesday, November 05, 2013 11:07 AM gramma
    • Moved by arnavsharmaMVP Tuesday, November 05, 2013 11:15 AM Posted in SCCM forums
    Tuesday, November 05, 2013 11:04 AM

Answers

  • I found the solution!!!!

    When regenerating the bootimages MacAfee AntVirus Scan prevent Dism.exe to add necessary components.

    After canceling the MacAfee process the bootimages where regenerated without any warning or error.

    Windows 8.1 deployment works! 


    Thursday, November 07, 2013 4:21 PM

All replies

  • did you also update the litetouch image on your WDS or usb stick you use for deployment?

    Tuesday, November 05, 2013 11:21 AM
  • Not directly. i meant the AIK update do this for me.

    How can i do this manual?

    Tuesday, November 05, 2013 11:25 AM
  • Hendrik,

    Windows 8.1 requires MDT 2013 and Windows ADK 8.1, at this moment just to get a quick result to see if it resolves your error is to use a CLEAN! virtual machine (or any machine you can use that is ready) to install MDT 2013 and Windows ADK 8.1. Then open your deploymentshare (even if it is located on another computer/server/smb share) and update your deployment share, so new boot images can be created.

    Since the error you have provided in the logfiles is a DISM error, it may be related to this issue. But there is also 1 other thing you can look at, and that is the DISM.log, this is located in C:\Windows\Logs\DISM\DISM.log. There you will find a more specific error description!

    Good luck and keep us posted! :)


    If this post is helpful please click "Mark for answer", thanks! Kind regards


    Tuesday, November 05, 2013 10:00 PM
  • how do you deploy windows to your machines?

    and your talking about AIK? thats what you needed for MDT 2010 for MDT 2013 you need the ADK for windows 8.1 make sure you deinstall AIK first.

    Tuesday, November 05, 2013 11:07 PM
  • First, thanks for the replies. 

    I installed ADK 8.1 and MDT 2013 before, sorry for my misleading with AIK therefor i didn't uninstall AIK, but an uninstall doesn't fix the problem.

    So i uninstalled ADK 8.1 and MDT 2013 and reinstall both. No changes, furthermore the ADK installation is never shown in MDT 2013/Components it is always shown under the Required tab.

    When i recompose the Deploymentshare i got many errors stored in the Dism.log that i cant handle in the code Block. for example:

    2013-11-06 11:10:56, Info                  CBS    Universal Time is: 2013-11-06 10:10:56.327
    2013-11-06 11:10:56, Info                  CBS    Open of SC_BOOT_SERVICING_DONE event failed 2
    
    2013-11-06 11:10:56, Info                  CBS    Wintrust catalog support is not present; skipping synchronous catalog installation (possibly expected) [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2013-11-06 11:10:56, Info                  CBS    Failed to load catalog installation apis (possibly expected). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2013-11-06 11:10:56, Info                  CBS    Failed to find a matching version for servicing stack: C:\Users\root_vst\AppData\Local\Temp\MDTUpdate.3228\Mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-11-06 11:10:56, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    the complete log:

    https://dl.dropboxusercontent.com/u/2332305/Deployment_error/dism_old.log



    Wednesday, November 06, 2013 11:22 AM
  • Hi,

    Be sure that "Windows Automated Installation Kit" previously used for older MDT is uninstalled.

    Be sure to regenerate a new boot image with the drivers of your machines and import the new boot image into WDS.

    If I were you, I'd check the "Unattend.xml" parameters as well :

    - Edit your task sequence
    - Under OS Info tab > Edit Unattend.xml
    - Load a catalog from the DVD source of Windows for instance
    - Open Tools > Validate Answer File
    - Check any message in the bottom window
    - You should see for instance: "Setting DisableWelcomePage is deprecated in the Windows image"
    - Double click the messages and fix the errors if exist

    Hope this help,

    • Proposed as answer by AcetiK Thursday, November 07, 2013 10:33 AM
    Wednesday, November 06, 2013 2:28 PM
  • i got exactly the WelcomePage error. i fixed it but that doesn't change the deployment result.

    for now i install an complete new 2012 srv to proof if this error will also happen there.

    Thursday, November 07, 2013 10:41 AM
  • Are you confident with your Windows 8.1 source?

    How do you import your Windows 8.1, do you choose to import the full source? Or do you choose only the WIM?

    Thursday, November 07, 2013 12:31 PM
  • i imported the full set of source files.

    therefore, i use an wds bootimage version 6.1.7600 (it is the old version right?) but when i boot from an new boot image with 6.3.9600 the mdt never start. the wpeinit.log looks like this

    wpeinit.log

    Thursday, November 07, 2013 12:43 PM
  • this is the error that occures when i regenerate the bootimages

    === Making sure the deployment share has the latest x86 tools ===
    
    === Processing LiteTouchPE (x86) boot image ===
    
    Building requested boot image profile.
    Determining if any changes have been made in the boot image configuration.
    No existing boot image profile found for platform x86 so a new image will be created.
    Calculating hashes for requested content.
    Changes have been made, boot image will be updated.
    Windows PE WIM C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
    WIM file mounted.
    Set Windows PE system root.
    Set Windows PE scratch space.
    
    Tool zur Imageverwaltung f�r die Bereitstellung
    Version: 6.3.9600.16384
    
    Abbildversion: 6.3.9600.16384
    
    Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~en-US~6.3.9600.16384
    An error occurred - WinPE-HTA-Package Error: 0x80070005
    
    Fehler: 5
    
    Zugriff verweigert
    
    Die DISM-Protokolldatei befindet sich unter "C:\windows\Logs\DISM\dism.log".
    
    Exit code = 5
    
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\en-us\winpe-hta_en-us.cab, rc = 5.
    Added component winpe-hta
    
    Tool zur Imageverwaltung f�r die Bereitstellung
    Version: 6.3.9600.16384
    
    Abbildversion: 6.3.9600.16384
    
    Processing 1 of 1 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    An error occurred - WinPE-Scripting-Package Error: 0x80070005
    
    Fehler: 5
    
    Zugriff verweigert
    
    Die DISM-Protokolldatei befindet sich unter "C:\windows\Logs\DISM\dism.log".
    
    Exit code = 5
    
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-scripting.cab, rc = 5.
    Added component winpe-scripting
    
    Tool zur Imageverwaltung f�r die Bereitstellung
    Version: 6.3.9600.16384
    
    Abbildversion: 6.3.9600.16384
    
    Processing 1 of 1 - Adding package WinPE-WMI-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    An error occurred - WinPE-WMI-Package Error: 0x80070005
    
    Fehler: 5
    
    Zugriff verweigert
    
    Die DISM-Protokolldatei befindet sich unter "C:\windows\Logs\DISM\dism.log".
    
    Exit code = 5
    
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-wmi.cab, rc = 5.
    Added component winpe-wmi
    
    Tool zur Imageverwaltung f�r die Bereitstellung
    Version: 6.3.9600.16384
    
    Abbildversion: 6.3.9600.16384
    
    Processing 1 of 1 - Adding package WinPE-SecureStartup-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    An error occurred - WinPE-SecureStartup-Package Error: 0x80070005
    
    Fehler: 5
    
    Zugriff verweigert
    
    Die DISM-Protokolldatei befindet sich unter "C:\windows\Logs\DISM\dism.log".
    
    Exit code = 5
    
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-securestartup.cab, rc = 5.
    Added component winpe-securestartup
    
    Tool zur Imageverwaltung f�r die Bereitstellung
    Version: 6.3.9600.16384
    
    Abbildversion: 6.3.9600.16384
    
    Processing 1 of 1 - Adding package WinPE-FMAPI-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    An error occurred - WinPE-FMAPI-Package Error: 0x80070005
    
    Fehler: 5
    
    Zugriff verweigert
    
    Die DISM-Protokolldatei befindet sich unter "C:\windows\Logs\DISM\dism.log".
    
    Exit code = 5
    
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-fmapi.cab, rc = 5.
    Added component winpe-fmapi
    
    Tool zur Imageverwaltung f�r die Bereitstellung
    Version: 6.3.9600.16384
    
    Abbildversion: 6.3.9600.16384
    
    Processing 1 of 1 - Adding package WinPE-MDAC-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    An error occurred - WinPE-MDAC-Package Error: 0x80070005
    
    Fehler: 5
    
    Zugriff verweigert
    
    Die DISM-Protokolldatei befindet sich unter "C:\windows\Logs\DISM\dism.log".
    
    Exit code = 5
    
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kit\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-mdac.cab, rc = 5.
    Added component winpe-mdac
    Injected driver ADMtek Incorp. Net NET8511.INF 2.00.830.2000
    Stopping the PowerShell command execution.  Performing necessary cleanup activities.
    

    Thursday, November 07, 2013 1:10 PM
  • I found the solution!!!!

    When regenerating the bootimages MacAfee AntVirus Scan prevent Dism.exe to add necessary components.

    After canceling the MacAfee process the bootimages where regenerated without any warning or error.

    Windows 8.1 deployment works! 


    Thursday, November 07, 2013 4:21 PM
  • mcafee... *shiver*
    Thursday, November 07, 2013 6:18 PM
  • I ran into the same issue - here are the steps I took to correct it. This is assuming you have already installed Windows ADK and MDT 2013. Open Deployment Workbench - right click your MDT Deployment share and select Upgrade. 

    *NOTE* Check your Windows Deployment Services applet under Boot Images and look for the OS Version tab it probably reads 6.1.7600 or something to that effect. This is the PE image for Windows 7 and below. The following fix should update you to version 6.3.9600 that supports Windows 8.1 and Server 2012 R2.

    1. Right click MDT DeploymentShare and select Update - select Completely regenerate boot images.

    2. Once that completes go to Administrative Tools and open your Windows Deployment Services Applet.

    3. Click the plus button to expand your server node and then find the entry labeled Boot Images

    4. Right click your Lite Touch Windows PE image (in my case there are two x86 and x64) and select Replace Image. When the window opens it will ask you where your WinPE images are located - select the Browse button.

    5. Navigate to your deployment share drive (example E:\DeploymentShare\Boot) and select the Windows PE file. (Example - LiteTouchPE_x64.wim) Push Open.

    6. Click Next in the Wizard and wait for the progress bar complete.  When the wizard has finished updating your WinPE image you should now note the OS Version tab and it should read 6.3.9600. 

    7. Attempt to deploy Windows 8.1 to your client machine again and it should now complete normally. 

    I realize everyone's environment can differ but I hope this helps anyone else who runs into this issue.

    Tuesday, December 17, 2013 9:23 PM