In my customsettings.ini I have configured some applications to be automatically selected (I dont want them to be mandatory) when choosing applications to install.

applications001={GUID}

applications002={GUID}

This works fine, applications are preselected and I can unselect them if I want in MDT Wizard page applications section. But the problem is that when I unlesect them they are still installed during application install phase. Why?

Is anyone else having an issue installing apps on certain platforms?

I've set certain apps to only install on windows 8 and 8.1 machines but they are not installing

Here is the output of ztiapplications for one of the applications:

as you can see there is no mention of any condition checking for Windows 8.1 (6.3) and as such the app is not installed on any of our Windows 8.1 machines.

Hey guys,

Minor annoyance our MDT based deployments of Windows 8.1/Server 2012 R2. Part of the way through the deployment its like some sort of "time out" occurs and both these OSes will "lock" the screen by switching to the sign-on view. You just type in the password and it lets you right back in but (oddly enough) this behavior doesnt happen wen deploying Windows 7/Server 2008 R2. In an ideal world I'd like the entire deployment to run without locking to the sign-on screen at any point.

Has anyone else encountered this and come up with a workaround?

I can figure this warning message out, I am currently using MDT 2013 and have seen this warning message using mdt 2012 and mdt 2012 u1. I dont receive this warning message everytime the script is run, but it usually pops-up ever 15 or 16th run attempt.

I've done some googling and have tried what other users have suggested, rebooting servers and cleaning up customsettings.ini

Nothing seems to resolve the issue. 
Have been doing my testing doing a REFRESH deployment.

I've even start drilling into the script to see where in the code that issue could be

I have read many of the threads regarding MDT and capturing/deploying multiple partitions.  However my situation seems unique compared to many that I have read.  I am running MDT 2013 w/ ADK8.1 on my WIN7server, booting computers through PXE using TFTP64 (work location OS restraints).  Everything works in regards to capturing and deploying OS's, the issue arises when a machine i'm capturing has two partitions.  I was able to capture the D: onto the C: using a previously posted task sequence command line addition with includes the command line:   %TOOLROOT%\imagex.exe /capture D: C:\DriveD.wim "Drive D"     (with minor editing for myself)

This command works successfully when placed right before the Create WIM task sequence, creating the DriveD.wim (second partition) on the C: (primary boot partition).  My issue is applying the DriveD.wim when the Task Sequence OS deployment is ran.  I've attempted running another code using the task sequence command line addition with includes the command line:    %TOOLROOT%\imagex.exe /apply "C:\DriveD.wim" "Drive D" D:            And am getting the error "Cannot find file specified..."  On boot up after restarting the computer, i have a drive C: and drive D: (format and partition task sequence is ran towards the beginning of the task sequence creating 50% of HDD space to primary boot (C:) and 100% of remaining to primary (D:)...(approximately 100GB per partition.)      I would rather not adjust the code in the actual MDT files, rather just use a command line code if possible.  Only two of the 8 computers I image have a secondary partition as part of their baseline.

Would someone please assist me with this issue?

Thank you, Evan

Hello guys！

    I have already deployed a WDS server(A) in subnet10.1.x.x (DHCP server is also in this subnet). The OS of A is windows server 2003 r2.

    Recently i got a problem when i was deploying my second WDS server(B) in subnet10.2.x.x and the OS is windows server 2008 r2 sp1. 

    when i boot client from PXE, it always chose server A as default WDS server without any options for me. I have set the option 66 67 on DHCP server and it did not work at all. I also set the value of AllowServerSelection to 1, which still did not work for the client to offer a option to choose which WDS server to boot from. 

   Does anyone here have any idea about how to choose the WDS server when booting from PXE? Thanks!

I am installing an app bundle. I launch the LiteTouch.vbs file from my deployment share to initiate the install. The App Bundle installs the app and copies a config file from a UNC share to a directory on the C: drive and desktop icons from a UNC share to the Public all users desktop. The install and both file copies complete successfully but display the following warning upon completion: 

I am using the xcopy command for the copies.

Any ideas?

I have just moved our MDT 2010 deployment share to a Windows 7 workstation with ADK and MDT 2013.  I upgraded the share and edited the boot.ini and customsettings.ini to point to the new location.  I generated new boot media and did a PXE boot.

The system boots from the PXE boot imahe, but instead of displaying the MDT deployment wizard pages so I can choose a deployment task to run, the system just boots to a command prompt with a cursor blinking at x:\Windows\system32.

What could be causing this issue?

I am trying to create a deployment for Win 7 x64 in MDT 2012, and it is going quite well.  My problem is with the Windows Update passes -- for some reason it misses many Office and Component updates until I go to deploy.  Then it takes another hour to grab and install those.  I don't understand why it does not grab them during the TS process.

I am doing a staged capture in a VM environment, starting with a zero-touch capture that includes Office 2010 and all the updates.  This is my thin image and it takes about 5.5 hours through capture.  Then I take this thin image, add standard apps that cannot be silently installed, customize desktop options that cannot be easily automated (another huge pain, but another topic), and, I was hoping, install all the updates for Office 2010 and other non-OS components.

In the first TS, I run the updates pre-installation, use the TS step to install Office, and run them again post-installation.  It does pick up a few, but then the logs say the system is fully updated and goes on to the next step.

In the second TS, I use the post-installation update step.  One of the apps I use installs SQL components, and the TS picks up on this and installs several updates it finds.  Then it decides the machine is up to date and moves on, skipping about 40 updates as of this writing.

As a test, I inserted a reboot step between app installation and the post-install Update step, but it still ignored the Office updates.  Research on the issue turned up the idea that at some point ZTIWindowsUpdate turns on the extra updates, and also several suggestions that this is how it is supposed to work (and why the standard TS is designed this way).

I rolled my VM back to the suspended point and I'm running WU manually at the console.  I had to enable "Microsoft Update" manually, and now it is happily pulling down the updates.  I just hope there's enough smarts left in the VM to run to  the task to completion.

I'm hoping that some whiz with the process can enlighten us on how to force ZTIWindowsUpdate to search for critical updates for all Microsoft components, not just the OS ones.

UPDATE:

Digging into the code and logs, it seems that a certain condition is not occurring to trigger the Microsoft Update service; bFoundMU must be true for this to happen.  A ServiceID hard coded is not being matched--the reason escapes me.  Near as I can tell, after a magic reboot it finally finds a match for this ServiceID.  Hopefully this snippet does not get munged...

    On Error Resume Next
            Item = oFSO.GetFileVersion ( ees("%SystemRoot%\System32\WUAUENG.DLL" ) )
            oLogging.CreateEntry "Ready to Opt-In to Microsoft Update: WUA Version: " & Item , LogTypeInfo
            Set ServiceManager = nothing
            Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
        On Error Goto 0

        If ServiceManager is nothing then
            oLogging.CreateEntry "Failed to Create Object: Microsoft.Update.ServiceManager" , LogTypeWarning
        Else
            bFoundMU = False
            For each Item in ServiceManager.Services
                WScript.Echo "Registered Update Service: " & Item.ServiceID & "   " & Item.Name
                If Item.ServiceID = "7971f918-a847-4430-9279-4a52d1efe18d" then
                    bFoundMU = True
                End if
            Next

            oLogging.CreateEntry "Microsoft Update Service:  Enabled = " & bFoundMU, LogTypeInfo
            If not bFoundMU then
                On Error Resume Next
                    Err.clear
                    ServiceManager.ClientApplicationID = "My App"
                    If Err.Number <> 0 then
                        oLogging.CreateEntry "There was an error getting Windows Update to opt into Microsoft Update. Please verify you are running the latest version of Windows Update Agent." , LogTypeWarning
                    End if

The logs look virtually identical between the two runs.  This is getting way deeper than I understand the update process or about service IDs.

UPDATE 2:

Digging further, it seems that the the condition of bFoundMU has no bearing on whether or not MU is used, but possibly the existence of muauth.cab.  From the deploy log where it actually started, bFoundMU is still false, but at that point the Office updates started to come in:

<![LOG[Property MSIT_WU_Count is now = 1]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Archive NoAUtoUpdate State: Was [<empty>].]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property NoAutoUpdate_Previous is now = <empty>]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.5.7601.17514]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ Status: 3]LOG]!><time="11:05:35.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Start Search...]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
__bunch of skipped updates__
<![LOG[  SKIP  - 258b6ca1-a8ec-4dfa-b619-fb8cecac6e2e - Turkish Language Pack - Windows 7 Service Pack 1 for x64-based Systems (KB2483139) - 56 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 48f7e3b7-2c8f-4900-ae32-f3d8f29c988d - Microsoft SQL Server 2005 Express Edition Service Pack 4 (KB2463332) - 55 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - d68e0cb2-9501-405e-af9c-156f352d6735 - Security Update for Microsoft Visual C++ 2010 Redistributable Package (KB2467173) - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 719584bc-2208-4bc9-a650-d3d6347eb32e - Security Update for Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (KB2565063) - 9 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - eb7a169f-6bca-4e00-a52a-623c063c162d - Update for Office File Validation 2010 (KB2553065), 32-bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - f51a0e5b-24a9-4be1-8b36-0f22f99949e7 - Security Update for Microsoft SharePoint Workspace 2010 (KB2566445), 32-Bit Edition - 17 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 35eb79df-cb34-491c-ab0a-34b63f32b45c - Update for Microsoft Office 2010 (KB2553092), 32-Bit Edition - 9 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - a6309b2e-7ee4-4b02-8ce9-cf39796a2411 - Update for Microsoft OneNote 2010 (KB2553290) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - f5202a56-ff34-401d-a040-f97c7f70891c - Update for Microsoft Office 2010 (KB2553310) 32-Bit Edition - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 33a4aa0a-cb01-4326-85f4-4a7d33d8782b - Update for Microsoft Outlook Social Connector 2010 (KB2553406) 32-Bit Edition - 1 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - aae5e2c7-3498-4f43-af66-aec06a59713f - Microsoft Silverlight (KB2636927) - 12 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - c8077d6d-00c2-421b-89f6-30828574519a - Update for Microsoft Office 2010 (KB2767886) 32-Bit Edition - 271 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 9c5e43a3-3ae9-434d-b105-a9d7902d5f9f - Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition - 395 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - b8fcacb4-add0-4cc9-8551-675b59965798 - Update for Microsoft Office 2010 (KB2825640) 32-Bit Edition - 18 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 5923c276-0628-4ba4-be3d-e56aa029a14b - Security Update for Microsoft Office 2010 (KB2687423) 32-Bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 79b27019-3090-4309-bfdc-c8be9b21ab96 - Update for Microsoft Access 2010 (KB2553446) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">

After the subsequent reboot, bFoundMU was set to true.

Setup; Win2012R2, WDS 6.3.9600.16384, MDT 2013 (6.2.5019.0), Surface Pro 2 128GB, MS USB Ethernet adapter

Issue 1: the TFTP transfer of the PE image is Extremely slow. 10 Mbps. Have tried to adjust Maximum Block Size without any improvement.

Issue 2: When I try to deploy both Windows 8.1 and Office 2013 the TS fails. It will not (start) installing the Application - the log confirms that it starts the script, but ends up with ZTI Heartbeat forever.
If I install Windows first and after the OS installation connect to the MDT server and start a TS With just Office 2013 it works without problem.
The disturbing part here is that if I use the same TS With both OS and Office on a Hyper-V Virtual machine it works...

Have anyone seen this before?

Hi

IS any way to take the Installed Applications details of machines and copied to Network Locations through MDT TS before the OSD in new or Refresh Deployment?

Shailendra

Shailendra Dev

     Hi, I am new the MDT and have created a reference image (Win7x86), and was able to deploy and capture to a target computer. (Just stand alone for now)

     When I deploy the image, it seems to work fine, (I even figured out how to make it keep my audio drivers).

However, when the system boots, it automatically logs in as the administrator. 

    Then only way I can get around this is to run sysprep /oobe, at the command line, then the system reboots

Prompts me for a user name  and works like I expected.

    Can anyone point me in the correct direction?, Maybe I missed a step or two??

    The examples that I watched online did not show this behavior (But they were MDT 2010)

                  Thank You

                          Wolverine

Hi, I have recently ran into an issue with targeting the right disk to image my system. For the task I have, I use disk 0 to target the right drive to Partition and Format before applying everything else. We use a variety of lenovo laptops without a problem but these X200 has been a different story. Disk 0 is 1404MB and Disk 1 became the main drive. I do not have any other storage hardware other than the SATA and USB. Here is a piece of the log:

<![LOG[  Console > Microsoft DiskPart version 6.3.9600]LOG]!><time="14:13:05.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Copyright (C) 1999-2013 Microsoft Corporation.]LOG]!><time="14:13:05.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > On computer: MININT-AE7J1NB]LOG]!><time="14:13:05.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="14:13:06.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > Please wait while DiskPart scans your configuration...]LOG]!><time="14:13:06.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DiskPart has finished scanning your configuration.]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Disk ###  Status         Size     Free     Dyn  Gpt]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   --------  -------------  -------  -------  ---  ---]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Disk 0    Online         1405 MB      0 B         ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Disk 1    Online          149 GB      0 B         ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Disk 2    Online          935 MB      0 B         ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 0     C   OSDisk       NTFS   Partition   1404 MB  Healthy            ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 1     D                NTFS   Partition    149 GB  Healthy            ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console >   Volume 2     E                FAT32  Removable    934 MB  Healthy            ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[  Console > DISKPART> ]LOG]!><time="14:13:07.000+000" date="04-25-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">

Need help!

Thanks!

Here is what I have tried. I have tried recreating the DeploymentShare. Moved my Deployment Test Share to the standard 2008 Server running MDT 2012. I have setup a Win7 x64 box as the Deployment Manager. I am still getting the following error:

Litetouch deployment failed, Return Code = -2147467259  0x80004005
Failed to run the action: Copy OEM files. 
Incorrect function, (Error: 00000001; Source: Windows)

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

Operation abourted (Error: 80004004; Source Windows)

Failed to run the last action: Copy OEM files, Execution of task sequence failed. 

Incorrect funtion. (Error: 00000001; Source: Windows)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Recreated the Image, Task Sequences, CS.ini and Boot.ini) Incorporated all OOB Drivers, Packages. Using a USB 16Gb flash drive with LiteTouchx86. 

List last time we tried to create a separate deployment share. Copy all the preexisting data from a working known good deployment share with images, task sequence, cs.ini and all image files. Still getting the same issue. 

Finally checked some of the Google, technet and forums for any assistance but non seem to do the trick. 

I'm new to the process but have been working with a fellow tech who has been working with MDT for six months and he can not find the issue either. 

Thanks for all your help up front. 

Hello Forum, I've run into a weird issue. Only one of my images will not deploy. It doesn't boot to the PXE environment, it hangs at the windows screen(see screenshot). I figured, maybe it's a driver thing, so I went to the manufacturer's site and grabbed the latest drivers as well as the Winpe drivers, still no go. Next, I deleted the deployment's boot folder contents and completely regenerated the boot files, still no go. I've also, rebuilt the wim file from scratch, still at a dead end. I'm totally baffled because only one of our models has this problem.

version: MDT 2012 6.1.2373.0

Hosted on Windows Server 2008 R2 VM

WDS: NO 

Since it's not booting to the PXE environment, it's not generating any logs files. Please Help

IT Support " Scripting Noob "

HI Guys,

I just get some problems about map a network drive with command line in MDT 2013.

The following is my test environment (in vmware workstation) .

  DC : Windows server 2008 R2  (with ADDS DNS DHCP WDS )

  MDT : Windows server 2008 R2 + MDT 2013

  Sql   : Windows server 2008 R2 + Sql express 2008

  Client: which will be pushed OS

I create a task senquence to push os to a virtual machine and it is successful when I using default disk partition step .

But I want to test with the way of diskpart command with a txt . First of all I add command line to map the Y: drive where the diskpart.txt file located (command "net use Y: \\mdt\deploymentshare$ /user:test\administrator Password"). Then Add the other command line that "diskpart /s Y:\diskpart.txt" . It failed at last .

I found that failed to map the Y: network drive . The most strange thing is that I can map successfully by manual in windows PE after pushing stoped .

Does anyone know how to map a network drive in MDT with command line ? Thanks a lot .

The problem I am about to describe doesn't exist with MDT 2010 update 1, MDT 2012, or MDT 2012 update 1 when using the either WAIK or ADK.  I have not attempted to reproduce this problem with older versions of MDT or pre-release versions of MDT 2013.  The problem definitely exists with MDT 2013 RTM.

This is the same problem as Inconsistent DISM.EXE error when applying unattend.xml during LTI deployment - Possible bug!, but this is more concise and provides details on how to reproduce the problem. 

Status as of 2014-03-30 (Previous workaround deemed unusable - core bug still present)

Keith Garner determined that DISM.EXE was failing while processing the <offlineServicing> section in the unattend.xml file.  Removing this section resolves the issue, but this section is needed to inject drivers into the image during WinPE and is needed  The presence of this section didn't cause any problems with previous releases of MDT/ADK - it is likely an interoperability bug within the DISM.EXE tool.  See replies below for details.

Confirmed the problem applies to deploying Windows 8.1 as well.

Problem:

When deploying Windows 7 Pro x64 w/SP1 and enabling/disabling features using unattend.xml, deployment often (almost 100% of the time) fails with this dialog:

Steps to reproduce ("bare-metal"):

1. Create a new, clean virtual machine (I used VMware Workstation)
2. Boot the VM with the Windows 7 x64 Pro w/SP1 Volume Licensing DVD
3. Install Windows with default options, OOBE choices:
   • User name = Tony
   • Computer name = Tony-PC
   • Password = tony
   • Windows Update = recommend settings
   • Time zone = Eastern
   • Location  = Work network
4. Install VMware Tools and reboot
5. Configure Internet Explorer using express settings
6. Configure Windows Update to get updates for other Microsoft products
7. Apply all available Windows Updates*
8. Install ADK for Windows 8.1 (http://www.microsoft.com/en-us/download/details.aspx?id=39982)
   • Installs .NET Framework 4.5 automatically
   • Accept all default installation choices
9. Install MDT 2013 x64 (http://www.microsoft.com/en-us/download/details.aspx?id=40796)
   • Accept all default installation choices
10. Apply all available Windows Updates again*

*When installing Windows Updates:

• Select all important updates, except Internet Explorer 11
• Select all optional updates, except Bing Bar, Bing Desktop, Security Essentials, and Silverlight.

Launch MDT Workbench:

1. Create a new deployment share
   • Accept all defaults:  C:\DeploymentShare, DeploymentShare$, etc.
2. Import Operating System:
   • Full set of source files
   • Source Directory = CD drive containing the Windows 7 x64 Pro w/SP1 Volume Licensing DVD.
   • Accept remaining defaults
3. Create a new task sequence:
   • ID = Test
   • Name = Test
   • Template = Standard Client Task Sequence
   • OS = Windows 7 Professional
   • Key = Do not specify at this time
   • Settings:
     • Full name = Tony
     • Organization = Tony
     • IE Home Page = about:blank
   • Admin password = tony
4. Update Deployment Share, and completely regenerate the boot images.

From another new, clean virtual machine:

1. Boot from the "C:\DeploymentShare\Boot\LiteTouchPE_x64.iso" file from MDT computer.
2. Run the Deployment Wizard, and enter credentials (tony, tony, . )
3. Launch the created Task Sequence (accept defaults, click keep clicking ‘next’):
   • Computer name = autogenerated
   • Join a workgroup = WORKGROUP
   • Do not move user data and settings
   • Do not restore user data  and settings
   • Locale and time = accept defaults
   • Do not capture an image

At this point, the deployment will succeed every time.

Now, edit the task sequence and edit the unattend.xml:

1. Add the Foundation Package to the answer file
2. Edit the foundation Package:
   • Disable MediaPlayback > MediaCenter
3. Save file and close task sequence.

Deploy the task sequence again using the directions above (for each attempt, I used a new, unused VM), and it will fail nearly every time!

Notes:

• Enabling/Disabling features via unattended.xml is a supported and documented process.
• I suspect a bug with DISM.EXE v6.3 while operating on Windows 6.1 images.
• I realize that adding"Install Roles and Features" and/or "Uninstall Roles and Features" task sequence items may be a workaround for this problem (I haven't tried it), but it is not asolution to the problem.