We captured a .wim image using WDS but are now unable to deploy it via MDT. I get the following error:

FAILURE (5627): 193: Run DISM.exe

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Failed to save environment to (80070057)

Failed to run the action: Install Operating System.

Unknown error (Error: 000015FB; Source: Unknown)

The execution of the group (install) has failed and the execution has been aborted. An action failed.

Etc. Anyone have any idea why this is happening and what I might do to remedy it? Any and all help and suggestions are very much appreciated!

Upgraded my Test system from MDT 2013 update 1 to update 2.  Also updated to the newest ADK. Updated deployment shares and recreated boot disks. When I try an deploy windows 7 X64 task sequence (using LiteTouchPE_x86.iso) i'm getting this error:

BDD.log:

Event 41003 sent: ZTI Heartbeat: command has been running for 1 minutes (process ID 880)    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > Error: 0x800f080d    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > DISM failed. No operation was performed.     LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > For more information, review the log file.    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > The DISM log file can be found at X:\windows\Logs\DISM\dism.log    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
Return code from command = -2146498547    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
FAILURE ( 5627 ): -2146498547  0x800F080D: Run DISM.exe    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
Event 41002 sent: FAILURE ( 5627 ): -2146498547  0x800F080D: Run DISM.exe    LTIApply    1/6/2016 12:27:07 PM    0 (0x0000)
Command completed, return code = -2147467259    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG.    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
Property RetVal is now = -2147467259    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)

STMS.log:

Expand a string: WinPEandFullOS    TSManager    1/6/2016 12:07:36 PM    696 (0x02B8)
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"    TSManager    1/6/2016 12:07:36 PM    696 (0x02B8)
Process completed with exit code 5627    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
!--------------------------------------------------------------------------------------------!    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Could not find CCM install folder. Don't use ccmerrors.dll    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Set a global environment variable _SMSTSLastActionRetCode=5627    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Clear local default environment    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Let the parent group (Install) decides whether to continue execution    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Could not find CCM install folder. Don't use ccmerrors.dll    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Task Sequence Engine failed! Code: enExecutionFail    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
****************************************************************************    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Task sequence execution failed with error code 80004005    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Cleaning Up.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Removing Authenticator    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Cleaning up task sequence folder    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
SetNamedSecurityInfo() failed.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
SetObjectOwner() failed. 0x80070005.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Deleting volume ID file V:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Executing command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
==========[ TsProgressUI started in process 1452 ]==========    TsProgressUI    1/6/2016 12:27:07 PM    1568 (0x0620)
Unregistering COM classes    TsProgressUI    1/6/2016 12:27:07 PM    1568 (0x0620)
Shutdown complete.    TsProgressUI    1/6/2016 12:27:07 PM    1568 (0x0620)
Process completed with exit code 0    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Successfully unregistered TS Progress UI.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
End program:     TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Sending error status message    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)

OS seems to install, but that's it.

•  "SPxxxxx.exe is the SoftPaq to unpack
• "-pdf" is a runtime switch that overrides the build parameters
• "-f" is a runtime switch that overrides the default path set at build time
• "-s" instructs the package to unpack in silent mode, skipping the Welcome, License, and Directory screens
• "-e" instructs the package to extract only, that is, do not run the component installation program.
• -s -a -silent -reboot (Good for silent installs.)

I'm trying to accomplish having a VHDX file that has updates (and possibly applications) preinstalled that I can copy and use as the basis for new virtual machines. I'd like the VM to be sysprepped and have an answer file so that when I boot from the VHDX file, it completes the OOBE steps and joins the domain, leaving me at the domain login screen.

I have a task sequence in MDT to install the OS and updates, then sysprep and capture. This works fine. I edited the unattend.xml file for the task sequence to answer the OOBE questions and join the domain. After the capture completes, I used a script to install the WIM in a VHDX that I can use for VMs. After booting the VHDX, it didn't appear to apply the answer file. I still had the OOBE questions and it wasn't domain joined.

I tried mounting the VHDX and inserting an unattend.xml file to C:\Windows\System32\sysprep\ but that just resulted in it throwing errors and ended up in a boot loop.

Can what I'm trying to do be done? I don't want to use MDT to deploy the image, as it's easier to just script VM creation using a base VHDX. Thanks.

Chris

The company I work for has never updated BIOS regularly on any of their systems. We have systems here that are several years old still running on the first version of that model's BIOS. 

They primarily use HP equipment but I have been having hit/miss luck with BIOS updates as a task sequence. For example, we deploy the HP EliteBook 9470m and 9480m. For both models I extracted the contents of the BIOS .exe from HP and set those up as an application. Then under Custom Tasks in State Restore I created separate folders for each model using the queries. As an example: "Select * from Win32_ComputerSystem where Model like 'HP EliteBook Folio 9470m%'"

Now, for the task sequence variable itself it is set up like this:

1. If all conditions are true

2. select SMBIOSBIOSVersion from Win32_BIOS where SMBIOSBIOSVersion < "F.62 Rev.A"

3. Select * from Win32_ComputerSystem where Model like 'HP EliteBook Folio 9470m%'

The application itself is set up as pointing to and using the following switches: "hpqFlash64.exe -s -a -r" 

This seems to work fine. However, for the 9480 hpqFlash64.exe isn't used. Instead it uses HPBIOSUPDREC64.exe and I have the application set up to use the same switches. My task sequence for the 9480m fails every single time. It also doesn't matter if I use the x86 version of the installer (HPBIOSUPDREC.exe). If I run this from command line on the machine itself it installs just fine so it is only failing as a task sequence. 

Error I get is "Litetouch deployment failed, Return Code = 2147467259 0x80004005"

Any ideas?

Hi,

I am using WADK 1607 and MDT update 2. I am having issue with deployment process. I have created a simple bare metal task quence and on deployment of windows 10 1607 from baremetal task sequence edge browser automatically launches after log on. Due to this deployment get paused, as it is running from local admin account it throws a warning message that edge browser can not be open through local admin and here task sequence pauses. The task sequence continue after clicking OK button.

The machine is on Workgroup, so there is no gpo is doing the launching of edge.

The edge launches automatically at each logon. this is very basic task sequence and we did not make any customisation which launches edge.

Abhishek

We keep running into an issue with the STATERESTORE phase of some deployment operations to newer Dell laptop models.  

Once the local administrator is logged in and the STATERESTORE phase starts.  Sometimes it will just hang doing nothing, sometimes it recovers on its own and indicates an error in the summary screen, other times it errors out entirely, and sometimes it works fine.  

What seems to be happening is a race condition for the network.  When it runs into a problem there is a consistent message in the system event log at the same time the BDD.log indicates something wrong that says: 

Warning11/7/2016 2:32:08 PMe1dexpress27None"Intel(R) Ethernet Connection I219-LM
 Network link is disconnected.

Information11/7/2016 2:32:09 PMMicrosoft-Windows-UserPnp20001(7005)Driver Management concluded the process to install driver e1d65x64.inf_amd64_2305982aeee58c7f\e1d65x64.inf for Device Instance ID PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21\3&11583659&0&FE with the following status: 0x0.

Information11/7/2016 2:32:12 PMe1dexpress32None"Intel(R) Ethernet Connection I219-LM
 Network link has been established at 1Gbps full duplex.

The BDD.log file indicating an interruption shows something such as:

Microsoft Deployment Toolkit version: 6.3.8330.1000LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
ZTIUtility!GetAllFixedDrives (False)LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
New ZTIDisk : \\LT332\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
New ZTIDiskPartition : \\LT332\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\LT332\root\cimv2:Win32_LogicalDisk.DeviceID="C:"LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
New ZTIDisk : \\LT332\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
New ZTIDisk : \\LT332\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
ZTIUtility!GetAllFixedDrives =   C: LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Found existing task sequence state information in C:\_SMSTaskSequence, will continueLiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Not running within WinPE.LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
DeploymentMethod = UNCLiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Validating connection to \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Mapping server share: \\DEPLOYLH01\MDT_Production$ LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Mapped Network UNC Path Z:  = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Successfully established connection using supplied credentials.LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
DeployRoot = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Property DeployDrive is now = Z:LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
DeployDrive = Z:LiteTouch11/7/2016 2:32:07 PM0 (0x0000)
Phase = STATERESTORELiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Validating connection to \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Mapping server share: \\DEPLOYLH01\MDT_Production$ LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Successfully established connection using supplied credentials.LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Property DeployDrive is now = Z:LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
DeployDrive = Z:LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Validating connection to \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Mapping server share: \\DEPLOYLH01\MDT_Production$ LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Found Existing UNC Path Z: = \\DEPLOYLH01\MDT_Production$LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Successfully established connection using supplied credentials.LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
DeploymentType = NEWCOMPUTERLiteTouch11/7/2016 2:32:08 PM0 (0x0000)
ResourceRoot = \\DEPLOYLH01\MDT_Production$ LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Property ResourceDrive is now = Z:LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
ResourceDrive = Z:LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
SMS Task Sequencer found at \\DEPLOYLH01\MDT_Production$\Tools\X64, copying to C:\MININT\Tools\X64LiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Copying \\DEPLOYLH01\MDT_Production$\Tools\X64\CcmCore.dll to C:\MININT\Tools\X64\CcmCore.dllLiteTouch11/7/2016 2:32:08 PM0 (0x0000)
Copying \\DEPLOYLH01\MDT_Production$\Tools\X64\CcmUtilLib.dll to C:\MININT\Tools\X64\CcmUtilLib.dllLiteTouch11/7/2016 2:32:08 PM0 (0x0000)

{Ends here}

Depending on where the deployment process is at when the network disconnects, sometimes it auto-recovers, sometimes rebooting the computer will get it to pick up where it left off, and others it's just broken and easiest to start over.  

I've tried various methods of specifying the driver version for selection from the Out-of-Box Drivers with selection profiles, and gone to the extent of inserting the driver into the WIM image offline with DISM.  Regardless, the OS appears to be updating the driver behind the scenes, taking down the network, and breaking the deployment process.  

Any suggestions on how else to address this apparent network race problem, or other things to look at?

Hello, when using MDT with WDS (on the same server).

I'm able to configure the MDT multicast but when I look under Multicast Transmission in WDS it show my MDT Share.... but when I check the properties the transmission type is Auto-Cast and I can't found a way to change it.
I would like to set it to wait until X amounts of clients are connect.

Is that possible?

Thank you

I'm trying to add network drivers to my MDT "Lite Touch Windows PE (x64)" image and I keep getting errors. I have tried every driver under the sun and all of them are giving me error. 

The image will mount, try to add the first driver, unmount, then give an error. Gives me the following error:

The following driver package could not be added to the image. There were no changes Made to the image. Click Finish to close the wizard.

The request is not support

I even removed the WDS role from the server twice and tried to set it up again and it's still giving me this error. Any help would be GREATLY appreciated.

Thanks

I am looking to create a customized Windows 10 image. I have installed an MDT 2013 Update 2 server to do the install. Within my image I would like to install Office Click-to-Run 2016. I am using the following article for guidance:

https://technet.microsoft.com/en-us/library/dn314789.aspx

I am using MDT to both deploy and capture the image. When the image finishes capturing I am getting the following warning:

"Unexpected return code while re-arming Office 2016, RC = -1073425660"

Any help in determining if this is an issue and fixing it would be appreciated.

Thanks,

Mike

Solutions Architect

Hello MDT Friends,

I am building my first reference image for Server 2016 and I am running into a similar issue I faced with Windows 10. During the Windows Update step, the process is stuck on Downloading updates for hours (so far 5 hours and counting). I was able to fix this issue for Windows 10 by adding a cumulative update as a package in MDT as described in this thread:

https://social.technet.microsoft.com/Forums/en-US/9941646e-648d-49e2-97a4-088e5cc0d917/windows-10-1607-stuck-when-downloading-updates-from-wsus-in-mdt-windows-update-task-sequence?forum=win10itprosetup

Has anyone been able to deploy a Server 2016 reference image with Windows Updates from WSUS?

As a stab in the dark I am trying to get https://support.microsoft.com/en-us/kb/3192366 added as a package. So far it is the latest Cumulative Update I was able to search google for.

I am using the latest official volume license image for server 2016.

Regards,

DLofstedt

Hello,

We have a Dell T5810 Precision i am trying to deploy with MDT 2013 U2 using Total Control
I am getting a BSOD Megasas2.sys error 359 on reboot, up until that point the drive is detected, formatted, drivers deployed and OS installed (Win7 SP1).  When i check the dynamic logs, no errors are appearing there. There is no NVME drive, its just a normal Samsung SM871 and the BIOS has been set to AHCI no RAID. we have the same SSD in many other Dell products and no problems with deployment.

I have tried booting with just 32 bit drivers, just 64 bit drivers, removing the Megasas2.sys 64bit drivers from LSICorp that get thrown in the boot.wim on updating the DeploymentShare. I have also tried the latest WinPE 3.0, 5.0 and 10 Cab packs from the Dell website which has made no difference to the error being recieved.

I can build the box manual and install drivers, but that doesn't fix the issue that is presented and defeats the purpose of having MDT in the first place.

Can anyone offer any suggestions??

Our current MDT server needs to be rebuilt so to avoid any down time I have built another server to use while I redo the current one.  Everything I have read says all I have to do is a simple copy of the Deployment Shares (there are two I need to move) to the new server and do and update to get the share(s) working. (note: the servers are have different names) And in fact it does kind of work except that when you run the imaging process on the temp server it's running all the TS from the old server and picking up the drivers and OS from the old server. 

So further research shows that I need to change the server names Boot.ini and Config.ini files.  If I do it from the console snap in gives me an error. (I have tried changing it at the console and in the .ini files before hand)

 So what step am I missing?  Do I need to close the deployment share before I copy it over to the new server?

Thanks for you assistance.

Kris Da San Martino

Hello, we are migrating from Win7 x86 Ent to Win10 x64 Ent using SCCM 2012 R2 and as part of the migration we'll be performing USMT to a network store as the machines are being wiped.

All machines have a separate D: logical drive which users can store data on, hence we are including D:\* within USMT.

The D: drive can either be a separate partition on the same physical disk as C: or in some machines it as a separate physical disk.

 For the machines that have a separate physical disk for D:, I don't want to perform the USMT on the D: drive as this disk wont be wiped during the Win10 migration.

Is there any way to only include D:\*.* in the USMT if its not on a separate physical drive?

The only way I can think to do this is to have multiple USMT capture's in the Win10 OSD and to exclude the D:\*.* migration for Dell models that have separate drivers via the task sequence variable Model. An alternative might be to have a WMI query which looks for multiple drives on the machine.

Is there any way to check for this within the USMT xml files and only perform an include of d:\*.* if not on a separate physical disk?

Hi everyone, 

"First time Caller, long time listener" as it were.   I am encountering a rather odd issue with MDT 2013 update 2.  Upon domain join, regardless if it's a powershell script that I previously used, or the task sequence to recover to the domain, it breaks the autologon.  I have confirmed this, because I moved the domain join to become the very last step just before the post-apply cleanup, and moved both of those to be the last two steps in the task sequence and I encounter no issues.  

I created a new task sequence from scratch, so I have the necessary reg keys being added to ensure that MDT can do it's thing.   I also captured the image using MDT, so I don't believe my issue is with that either.  So, does anyone have any ideas on what could be happening?  Please note, this behavior does not occur with my Windows 7 images and task sequences, so I am loathe to believe that this is some GPO at work directly, but could be some behavior related to Windows 10, that I am not aware of....   Suggestions or advice would be greatly appreciated!  

Thanks, 

Allyn

I am unable to get to the task sequences when trying to deploy Windows 10 to a SP4. I get the splash screen, but then the SP reboots. Any thoughts?