I have downloaded MODP 2012 and installed the DaRT recovery image tool, along with the additionally required software (WADK & WSDk (Debuggers And Tools)

When I run the DaRT recovery image tool, Tell it to create X64 dart image,  select the windows 8 X64 location, and try an create a wim but I get an access denied error

Generating DaRT image
Set-DartImage
Installing optional component: 'C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-FMAPI.cab'
Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Cleaning up temporary files
Temporary folder: C:\Users\tester\AppData\Local\Temp\DaRT8_Mount_2012.11.07.10.55.16
The clean-up has successfully been completed.

Ive tried changing permissions on the the Assessment and Deployment Kit folder and its sub folders but no go. The account im using is a Admin account. Running windows 8 x64 final

Hello,

I am using MDT to deploy a Windows 10 image to a test device. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty.

Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta

I also located the log file and found this: (Wizard.log)

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property Debug is now = FALSE]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard">

Would anyone know why the Wizard.hta is not properly launching and why MDT is not completing on Windows 10? 

Thank-you,

AP

I am using MDT to deploy a Windows 10 image to a Dell latitude 5570. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty. Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta. It deletes c:\MININT folder so cannot get the BDD.log or the task sequence log.

• Deploying windows 7 works just fine.
• The version of MDT is 2013 Update 2

Just started an update of one of my deployment shares from MDT 2013 Update 1 to Update 2. It's stuck, for the last half hour at "Checking Driver Hashes"

I do have a fair amount of drivers, but is 30 minutes normal? At what point should I stop the upgrade?

Orange County District Attorney

Please see updated information a few posts down.

I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012.  I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties.  I am trying to follow the guide on the deploymentguys. I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line.  doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2" does work.  I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2"  All i get is error setting user data for interface ethernet2, the operation is not supported.

How does one get 802.1x working in WinPE 4.0?

Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:

So here's the current situation and hopefully someone has seen it before.

My boot image has the prestart command set to x:\8021x\configure8021x.cmd.  If i make a USB boot media this command will run and work with an 8021x wire plugged in.  If I PXE boot with a non8021x wire plugged in this command will run.  If I PXE Boot with an 8021x wire plugged in it does not run the command.  If the boot image gets staged from the windows software center it also will not run my command.

Does anyone know why the staged boot image and booting from PXE are not running my prestart command?  It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?

I used to have a working TS sequence that updated the BIOS of the computer

In State Restore/Custom Tasks folder I had a command running

BIOS_Update.exe -nopause -noreboot

With Start in as

z:\Applications\BIOS_Updates\%MODEL%\

This worked flawlessly in previous versions, but after Update2, it refuses to work. The log file reports

The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="14:25:46.344-120" date="06-01-2016" component="TSManager" context="" type="3" thread="4464" file="instruction.cxx:776">

Is this a known bug, or does anyone know of a workaround/fix?

Hello,

I have read a few articles on how to used USMT with encrypted C drive if it is encrypted with BitLocker.  But here is our situation:

We have McAfee encryption and we are moving to BitLocker.  Is it possible to automate USMT with McAfee in MDT 2013 Update 2 so no user input is needed when the MDT task sequence is running USMT from WinPE and is able to get the users data?

Looking forward to suggestions.

Thank you.

Ishan

Does anyone have some step by step instructions for Pre-Provisioning Bit Locker. Through task sequences, we are currently able to bit locker the computers but it's the last set of tasks.  I would like to Bit Locker the computer while no data is on the disc so it's faster and then as its imaging, the files are already encrypted.

Currently:

• Creates BIOS Password
• TPM turned on and enabled (using CCTK)
• Remove Password
• Registry changes
• Installing MBAM 2.5
• Removing Registry Entries
  
  
  Any help would be appreciated!

Thanks

Rick

Hi all,

I use a custom GPOPack for a new computer deployment, and it randomly fails with the known error:

ZTI ERROR - Non-zero return code by ZTIApplyGPOPack, rc = 1

Earlier I found this article explaining how to fix this:

https://blogs.technet.microsoft.com/matt_hinsons_manageability_blog/2016/01/29/gpo-packs-in-mdt-2013-u1-for-windows-10/

It still fails most of the times, and when it actually succeed it does not apply all settings. It is a new computer deployment and I use a virtual environment in my test phase. For testing purpose I clear disk 0 every time I test. I have recreated to GPOPack several times. I use LGPO.exe to export it as described here:

https://blogs.technet.microsoft.com/secguide/2016/01/21/lgpo-exe-local-group-policy-object-utility-v1-0/

This behavior also seem to affect other Task Sequences as well. I have a step just before applying the GPOPack, where I import some file associations (using cmd /c dism.exe /Online /Import-DefaultAppAssociations:%SCRIPTROOT%\fileassoc.xml). Naturally I have tried disabling this in my testing.

I have only this error in the BDD.log.

Does anyone experience this or know how to fix it?

We have integrated MDT 2013 Update 2 into our Config Manager 1602 environment and I discovered through testing that an MDT user driven task sequence to deploy Windows 10 will fail to join the domain unless secure boot is enabled in UEFI. All the drivers and applications install correctly.

Non-MDT task sequences do not fail in this manner, so I am guessing an MDT specific step in the process is causing this. Does anyone have any idea where this is?

We recently set up a new WDS server with MDT 2013 on Server 2012R2. Everything on WDS was configured the same way as it was on our previous WDS server running 2008R2 (which has no problems). The deployment share was setup and images were captured. In testing, everything worked fine deploying to a single computer, but when multiple computers are trying to deploy, at least half of them fail and you get:

FAILURE ( 5624 ): 1392: Run DISM: /Apply-Image /ImageFile:\\server\customimage.wim /Index:1 /ApplyDir:C

LiteTouch deployment failed, Return Code = -2147467259 0x80004005

Of course, I searched and searched for answers and the error codes are no help. It seems the error codes indicate that the image is corrupt, yet if I deploy a single computer, it works fine, every time. The same thing happened before when we wanted to do a new server on Server 2012R2 using MDT2012 Update 1. When we put MDT 2012 Update 1 on Server 2008R2 with the exact same images, everything worked fine. Something tells me it's some sort of setting or something related to WDS and not MDT.

Any help is much appreciated.

Hi gang,

I'm running into an issue when imaging multiple computers with MDT 2012. Let me give some background info.

I have installed Windows 7 64 bit on a laptop in audit mode, made my configurations, sysprepped the machine, and captured a .wim using WDS (captured to an external hard drive). I then imported this .wim into MDT, created a Standard Client Task Sequence to deploy the image, and successfully deployed it to a machine.

My problem comes up when I initiate this task sequence on multiple computers simultaneously. If I put 6 computers side-by-side and run the task sequence at the same time, only a couple machines will actually succeed. The rest fail with the following:

FAILURE ( 5624 ): 2: Run ImageX: /apply "\\CAAPPWN40\DeploymentShare$\Operating Systems\T731 (Final) Windows 7 64 bit May 2013\T731 (Final) Windows 7 64 bit May 2013.wim"

1 C:

Litetouch deployment failed. Return Code = -2147467259 0x80004005

Failed to run the action: Install Operating System

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

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

Operating aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Install Operating System. Execution of task sequence failed.

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

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

BDD.log is saying that "The file or directory is corrupted and unreadable."

If I restart the computer, boot back into PXE, and run the task sequence again, this time on it's own (as opposed to 6 computers at once) it works fine.

Can anyone help?

I'm trying to deploy a WIM image that I created on an Optiplex 960 to a Optiplex 9010.  It goes really well until the last part of completing the setup. Then I get ""windows setup could not configure windows to run on this computer hardware" and is stuck in a reboot loop.

The image is Windows 7 Enterpise with SP1. I've added the drivers to the Out-of-Box Drivers section.  I've even tried installing Windows from the DVD, same error. Also used the latest Intel RST drivers (f6flpy-x64.zip). The only install that works is the factory one from Dell which is Windows 7 Professional and not what we want to use.  The SATA setting is the default, RAID.

<![LOG[Success! Please rerun WindowsUpdate to ensure machine is FULLY up to date.]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Begin Windows Update. Reboot=[]  Retry=[]  Count = 1]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Property MSIT_WU_Count is now = 2]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Configuring client to use WSUS server (insert our WSUS server here)]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7600.256]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Start Search...]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Scan complete, ready to install updates. Count = 0]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[This computer is up to date (Success)]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Property MSIT_WU_Count is now = ]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Restore NoAutoUpdateKey to 0]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Restore NoAutoUpdateKey to 0]LOG]!><time="12:20:58.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="12:20:58.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Unable to create WebService class]LOG]!><time="12:20:58.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="2" thread="" file="ZTIWindowsUpdate"><![LOG[Command completed, return code = -2147467259]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Property RetVal is now = -2147467259]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Running on a laptop that would image fine in the past, and I get this above error.

I've verified that the monitoring service started properly. I feel like an update to Windows Update broke this, but have zero proof.

Hi all!

I'm trying to deploy Windows 10 Enterprise using MDT 2013 SP1. During the deployment I'm trying to have Bitlocker auto-configured and enabled. However I keep getting error: FAILURE ( 6767 ): -2144272340  0x8031002C: Enable BDE Protectors.

I've searched the interwebs but every post I see is about people who are using Configuration Manager. Since I'm not, the solutions provided there don't apply to me.

My bitlocker settings:

BDEInstallSuppress=NO
BDEDriveLetter=Q:
BDEDriveSize=2000
BDEInstall=TPMKey
BDERecoveryKey=AD
BDEKeyLocation=C:\windows\BDEKey
BDEBitLockerWaitForEncryption=TRUE

I've configured AD for Bitlocker backup, and after the deployment finishes I can manually enable bitlocker and it will save the key to AD. However I'd very much like this to be automatic since I'm trying to make it ZTI as much as possible.

I have followed the steps in this article: Configuring Bitlocker for MDT except for the part where you use a script to check if the TPM chip is already enabled. The reason I'm not doing this (yet) is because for now I only have to configure Surface 3 (not pro) tablets and I know that the chip is enabled. So from the task sequence screenshot in the article, I have only got the Enable Bitlocker step.

Thanks in advance for any suggestions!

Kind regards,

Elke

Hello,

I have tried many times to capture a full uptodate installation of Windows Server 2012R2.

When doing this sysprep and capture this ends with the following:

Network connections is available (hit F8 and check ipconfig)

I have also rights to save on the capture-location.

The problem occurs on the step : Create Wim

Anybody who knows a solution for this?

Thx

Hello,

I have been trying to use USMT to capture and restore data on  Windows 7 machine.  I run the TS from withing Windows so it acts as refresh.   It is successfully copying data to the network location other than the MDT server.   I can see the .MIG file being generated.  But when the machine is reimaged and the restore user state runs it does not restore the data.  I looked at the logs and it said "No user state to restore"

When I pointed the USMT network location to backup on the MDT server itself it was able to capture and restore user state.  

I am confused why it can capture the data but not restore it.

I am running MDT 2013 update 2.

Please advice.

Thank you.

Ishan