Automating driver selection in MDT 2013

I have been working with MDT for a couple of months now, and I am really getting stucked on a problem. I wish to automate wich drivers to install for a spesific model.
we have mostly HP machines, but also Lenovo. I have tried to set drivergroup and %make%\%model%, but cant make it right. Is there something in the CS.ini? I have no clue anymore...
All help will be appreciated

Hi Espen,
An alternative is to use selection profiles which will target drivers with the selection profile based on the result of WMI query.
Please see the following link, which will tell you exactly what to do.
http://adminnexus.blogspot.nl/2012/08/yet-another-approach-to-driver.html
This is will work for sure, since it uses the result of a WMI query to pass or skip the "Inject Drivers" step. So if the following query, matches the result it will execute the injection of the drivers of this particular step:
SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Probook 6560b%"
So on every machine, you need to execute the following query in a command prompt:
"wmic computersystem get model" the result of this query can be used as input for the WMI - Model.
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Similar Messages

HP Client WinPE Driver Packs and MDT 2013

Just today I noticed that HP had a couple of WinPE driver Packs for download on their site for WinPE 3.0 and 4.0. I'm using MDT 2013 to deploy Win 7 x64 for now, perhaps Win 8.1 out in the future. What version of WinPE does MDT make for Boot Images? Which
driver pack would be best for MDT 2013 and Win 7 deployment? WinPE 3.0?
Orange County District Attorney

Just found my answer in a great post at
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Just in time!
Orange County District Attorney

HP EliteBook 820 G2 - Network Driver - MDT 2013

Hi We have one of the new HP EliteBook 820 G2. When trying to boot from WDS/MDT 2013 into WIN PE it is saying that it cannot connect to the deployment share. because PCI\VEN_8086&DEV_15A2&SUBSYS_225A103C&REV_03 - did not have a driver installed. I downloaded the driver pack from http://ftp.hp.com/pub/capssoftpaq/cmit/HP_Driverpack_Matrix_x64.html I imported the network drives into WDS and imported all Drivers from driverpack into MDT. However I am still getting this error. Googling the device returns no results. Can anyone advise?
Thanks

I think its the middle one. In my environment i have used a drivergroup selection type of installation that will inject the drivers using the computer csproduct name. If your environment doesn't have this then i don't know how you would make it work. In theory it should still pick up the drivers if you are using the "chaos" type of driver selection ie every model fetch the drivers from the same driver folder. Also make sure you do regenerate the WinPE image and then move it over from your deploymentshare to your WDS service. This is crucial because in most environments the location where the new PE image is created is not the same where WDS images are stored. Also remember to put the Windows Deployment Services-service down from services.msc and bring it back up before trying. Use a different file name (or a different background on the deployment as i did) to make sure that the PXE download is in fact updated. I can confirm that this driver package also works on EliteBook 840 G2 although the deployment summary gives me errors connecting to the deploymentshare due to the installation of this driver taking considerably long. I attached a screenshot of my network drivers in WinPE that do work. Importing these to the individual computer model folders below is also required in my environment. This may be different in yours.

Surface Pro Driver injection no longer working under MDT 2013

Since upgrading to MDT 2013 we are experiencing an issue with deploying Windows 8.1 to our Surface Pros. The deployment seems to be ignoring driver group settings in CS.ini and it basically injects no drivers. We are following the guide Microsoft posed here:
http://www.microsoft.com/en-us/download/details.aspx?id=38826
So I'm confused as to where we are going wrong. Here is the section in question from CS.ini:
[ByModel]
Subsection=Model-%Model%
[Model-Surface with Windows 8 Pro]
OSDComputerName=TAB%SerialNumber%
DriverGroup001="Windows 8.1 x64\Microsoft\Surface Pro"
DriverSelectionProfile=Nothing
XResolution=1920
YResolution=1080
Incidentally the computer name is getting set so i know this block is working. Any idea why the drivers would get skipped over?

I've been deploying to Surface tablets just fine and deployed to a Surface 3 just a couple days ago without any issues, but I do follow Johan's "Total control" way of managing drivers. http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
I'd recommend you go that way as well as you'll most likely have fewer issues. Depending on your situation you may also want to make use of the "ModelAliasExit" script and use Make variables or you can just follow the method above exactly as is.
If this post is helpful please vote it as Helpful or click Mark for answer.

MDT 2013 and RES Automation Manager

Hi,
In one of the first step of MDT I'm using a simple script that asks for the country code (e.g. NL), which I would like to store in an environment variable, which I can later on read into RES Automation Manager. But it seems that after MDT is finished and
Windows starts up, the environment variable is gone. Are there any other ways to accomplish this? I'm using it to install language specific applications from RES AM, after MDT is finished. The Windows language settings itself I set with the
CustomSettings.ini, that is based on the same simple script
[Settings]
Priority=ByCountry, CountryAbbr,Model,Default
Properties=CountryAbbr, CountryOU,CustomProperty
[ByCountry]
UserExit=ZTIGetCountry.vbs
CountryAbbr=#GetCountryCode()#
[NL]
CountryOU=NL
CountryOrRegion=31
InputLocale=0409:00020409
KeyboardLocale=nl-US
UserLocale=nl-NL
UILanguage=nl-NL
TimeZoneName=W. Europe Standard Time
ZTIGetCountryCode.vbs
Function UserExit(sType, sWhen, sDetail, bSkip)
oLogging.CreateEntry "entered UserExit ", LogTypeInfo
UserExit = Success
End Function
Function GetCountryCode()
Set objShell = CreateObject("WScript.Shell")
Set objEnv = objShell.Environment("SYSTEM")
GetCountryCode = InputBox("Fill in Country Code (NL DE DA FR PT); If default, use None")
objEnv("MDT_Language") = GetCountryCode
Set objShell = Nothing
Set objEnv = Nothing
End Function
Any idea what I can do else??
Thanks,
Mario

Hi, this looks quite similar to my blog post I did some time ago:
MDT 2012 LTI Deployment, Regional and Locale settings based on #chars of Hostname
The trick in your specific case is to either, not reboot your machine, or to set the installation of RES Automation Manager right after the reboot.
Basically MDT clean's up it's act after it is finished. This also means the environment variables which are stored in a .dat file in the C:\MININT folder are removed after MDT has finished.
So either you need to find a way to perform your RES AM job, during the MDT task sequence, or set or dump the environment variables to a file are temporarily variable which RES AM can use.
Here are some articles that will help you get further:
MDT and RES Automation Manager – Let’s come together (in Sweet Harmony)
Creating custom variables in MDT 2013
Finding All References to MDT Variables in a Deployment Share: VariableDocumentor
v1.0
Dumping Task Sequence Variables
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Synaptics Pointting device Driver installs on an Desktop machine while deploying Windows 7X64 using MDT 2013 Update 1

I am deploying Windows 7X64 on Dell OptiPlex 990 and other desktops. Deployment goes fine but the Synaptics pointing device driver gets installed after the deployment is complete. Also after applying operating system I get a prompt to Run the Synaptics Pointing
Driver setup twice. If I don't click yes to install the TS wont proceed. Its gets worse when I uninstall the Synaptics Device Driver from Appwiz.Cpl and reboot the machine the Keyboard fails with the error Code:29. Above is the screenshot of what I get after
Applying Operating System step. Thanks in Advance.

I have also encountered this in MDT 2013 Lite Touch deployments for Windows 8.1 and I am researching it.
I noted that the Synaptics driver was installed for "SmBus" in Device Manager for a motherboard with an Intel 7 Cxxx Series chipset (Dell Optiplex desktop). The HardwareID's are all PCI\VEN8086...
We use %Model% in our task sequence and have a folder for each model such as "Optiplex 7010" in Out-of-Box Drivers.

MDT 2013 + create 5 recommended UEFI/GPT drive partitions

Hi
My end goal is to deploy a custom x86 image to a UEFI device (tablet) using a USB stick. It is likely that my .wim file will be >4GB, but for now, I'm just trying to get the process working with a standard OEM <4GB .wim file.
As per this post, I have performed steps under sections 5.1, 5.2 and 5.3 MANUALLY, by booting the tablet using a WINPE 5.0 USB and running
1) diskpart /s E:\CreatePartitions.txt
and
2) E:\ApplyImage E:\Images\ThinImage.wim
Q: Above worked perfectly and it's exactly what I'm looking for. How do I incorporate 1) + 2) into MDT, or do I simply attempt to replicate the code from 1) + 2) under "Format and Partition Disk" under PreInstall\New
Computer only step?
Any advice or pointers would be really appreciated.
Many thanks in advance.

Recovery images, that's a different story.
First option is to increase the size of the System partition to the desired size:
BdeDriveSize=5000
Otherwise, the best solution I've seen is to build the standard MDT partition configuration using the default MDT "Format and Partition" step. and *THEN* shrink the partition to the desired size. Yes Shrink.
The other option is to increase the size of partition 1 from
See Mike's post on WimBoot for the example script LTIApplyWim.wsf script that shows how shrinking works.
http://blogs.technet.com/b/mniehaus/archive/2014/04/13/experimenting-with-wimboot-using-mdt-2013.aspx
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Error While Using MDT 2013 to Refresh Windows XP to Windows 8.1 during Computer backup to network

Hi,
I am getting below error in Deployment Summary while Computer backup to network during Refresh from XP to 8.1 through MDT 2013.
1. I followed URL-
http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx to use USMT for the UserProfile through MDT 2013.
2. For User profile I am using Hardlink USMT through MDT Wizard, that is working fine.
3. My Deployment Share rule is below..
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\MDT2013\share$
BackupDir=%OSDComputerName%
BackupFile=%OSDComputerName%.wim
BackupDrive=ALL
4. ZTIBAckup Logs below..
2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context=""
type="1" thread="" file="ZTIBackup">
<![LOG[OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Search for Drive: OriginalPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Found Drive: C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDisk is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Checking to see if we can store the backup locally]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive C: 3231300]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive D: 272600]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive X: 2489]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store path = C:\StateStore]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Total used space: 3506389]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Available space at C:\StateStore: 22368244]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Backup can use local path]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property USMTLocal is now = True]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to:
\\MDT2013\DeploymentShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\MDT2013\share$\TEST8\TEST8.wim" "001CDrive" /flags EnterpriseN]LOG]!><time="13:16:21.000+000"
date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Command has been started (process ID 1248)]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1248)]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Version: 6.3.9600.16411]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Files/folders excluded from image capture by default:]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~bt]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~ls]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \winpepge.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Windows\CSC]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycled]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycler]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$Recycle.Bin\*]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \System Volume Information]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \swapfile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \pagefile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \hiberfil.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Turning on VERIFY option for network share]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Scanning files and directories...]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   0% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   1% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   2% ] Capturing progress: 11:04 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   3% ] Capturing progress: 9:12 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   4% ] Capturing progress: 7:58 mins remaining ]LOG]!><time="13:16:50.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   5% ] Capturing progress: 7:20 mins remaining ]LOG]!><time="13:16:55.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   6% ] Capturing progress: 7:59 mins remaining ]LOG]!><time="13:17:07.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   7% ] Capturing progress: 8:23 mins remaining ]LOG]!><time="13:17:13.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   8% ] Capturing progress: 8:20 mins remaining ]LOG]!><time="13:17:17.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   9% ] Capturing progress: 8:33 mins remaining ]LOG]!><time="13:17:26.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 11% ] Capturing progress: 8:21 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 13% ] Capturing progress: 7:37 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ RETRY ] Restoring C:\WIMA8B0.tmp again (Error = 1392)]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > Error imaging drive [C:\]]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > The file exists. ]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Return code from command = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Error creating an image of drive C:, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
<![LOG[ZTIBackup COMPLETED. Return Value = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
5. Computer Backup Dir is accessbaile and permission is ok.
Any idea to resolve this issue
Shailendra Dev

After changing the BackupDrive=D: , I am able to take backup of D drive only , but I want to take all the local drives backup before installing windows 8.1
please suggest .
Shailendra Dev

MDT 2013 - Create New User

Hello,
I've recently setup MDT 2013 to deploy some customized images that we deploy to student laptops, that were sysprep-ed and captured with ImageX. I've uploaded the custom image WIM files to MDT, and setup a task sequence. Almost everything works,
thanks to Microsoft documentation and searches of this forum for various questions I've had, however I'm stuck on two items:
1.) MDT forces an administrator account to be created during the process. That's not such a huge issue, but I'd like to disable the administrator account at the end of the task sequence. I'm not sure where/what to add to do this.
2.) We would like the machine, after imaging, to deploy the generic Windows Welcome, as if it had just been purchased from the OEM. This way when the student receives the imaged laptop, they can create their own personal account. These laptops are
not bound to AD. Right now, when the task sequence finishes the systems are logged in as an administrator. Again, I'm not sure what code to add to the task sequence (and where) to accomplish this.
Any information or links on what I'm looking for would be greatly appreciated. I'm sure that both these items are possible, but I'm not using the proper terminology on my searches to find the information I'm looking for. Thanks!

I question the usage of MDT in this scenario. I also question your premise that your users should go into OOBE Setup.
MDT is designed to assist IT departments in getting windows up on machines in a End to End scenario.
MDT prompts which Task Sequence, Language/Locale/TImezone, Applications, drivers, and User Data Migration Status. Once the TAsk Sequence has started, MDT should be as automated as possible. No prompts, no user interaction.
What you are asking for is the opposite, you want user interaction during deployment, and rather than customizing each deployment, the image is pre-configured. (Unless you have different *types* of machines that require driver loading via MDT).
IN your case I would recommend just slapping an install.Wim up on a WDS server, and custom crafting an unattend.xml file to prompt each user for user accounts. (as long as you don't have to worry about drivers).
The other solution is to prompt the user for their new user account from the MDT wizard, and slam that into the machine during the task sequence (and removal of the Administrator account with net user administrator /active:no )
I actually created a powershell script to accomplish this:
http://keithga.wordpress.com/2013/09/24/microsoft-account-automation-in-windows-8/
This alternative solution is MDT 400 level work. Scripting required. :^(
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Error when deploying LiteTouch image using MDT 2013 Media Flashdrive

Please help! I have created a media flash drive (drive capacity: 64Gb) to deploy LiteTouch x86 and x64 images (Win7 and Win8, 8.1) to PCs but getting error for the 3rd time. I am using the following tools in my environment: i am using MDT 2013 on a Windows
2k8 WDS server. PXE boot works fine deploying images but i keep getting this error after creating the Media flash drive). I first got the same failure with 14 errors but recreated the media on the WorkBench using a different selection profile but now i am
getting this error: (by the way where is the BDD.LOG?)
"Deployment Summary
During the deployment process, 8 errors and 0 warnings were reported.
Details...
Failure ( 5456): Unable to determine destination disk, partition, and/or drive. See BDD.LOG for more information.
Litetouch deployment failed, return code = -2147467259 0x80004005
Failed to run the action: inject drivers.
Unknown error (error: 00001550; source: unknown)
The execution of the group (preinstall) has failed and the execution has been aborted. An acton failed.
Operation aborted (error: 80004004; xource: 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

I am planning to build a WDS with Win2k12 and MDT2013 and perhaps will be lucky to create a successful media. I created one with my WDS Win2k8 it works on a HP laptop but failed on other machines like Dell...
Did you get driver injection in configuration WDS and MDT?
Considering if the incompatible drivers cause your issue.
If you can post back the MDT log during the deployment on DELL computers, it would be helpful for us to determine your issue.
Kate Li
TechNet Community Support

MDT 2013 - Litetouch deployment failed, Return Code = -2147467259 0x80004005

I'm attempting to deploy an image that I have recently captured with MDT. I was able to capture the image without any problems and after capturing, it booted up properly. But now when I go to deploy the image using a Standard Task Sequence it
errors out. It does boot into WinPE and gets to the installing operating system portion then spits out the following 8 errors:
(5624):2: Run ImageX: /apply "\\PDC31089\DeploymentShare$\Operating Systems\Win7_BUP_1-31-14\Win7_BUP_1-31-14.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.
Operation 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 0x80004005After I receive the error messages if I attempt to restart the computer and allow it to boot up it just comes up with:"An operating system wasn't found. Try disconnecting any drives that don't contain an operating system"
I have tried the following to resolve this issue:
Create a new deployment share with only network drivers added and the one .WIM that was captured with MDT as well as one Task sequence.
Update to MDT 2013
Update Deployment share and completely regenerate Boot images
Tried starting deployment from within Windows by mapping the drive and executing litetouch.vbs
Also tried starting deployment using USB boot disk
I'm running out of ideas and seem to keep getting the same 8 error messages. It's very aggravating and am hoping that someone can point me in the right direction.
I've included some log files on Skydrive at: https://skydrive.live.com/redir?resid=6375A8F9E8089918%21105

I came across this post recently. I am having the same string of errors suddenly when I try to deploy any image from my MDT 2013 server now. Previous images now fail to install soon after the Inject Drivers task sequence at the Install Operating System sequence.
Each time I try to deploy an image(have tried several each with different task sequences), I get the same 7 errors.
The errors produced are:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Incorrect Function (Error: 00000001; Source: Windows)
The execution of the group (Install) has failed and the execution has been
aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task
sequence failed.
Incorrect Function
(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
My HD size is 146GB with about 71GB being free.
The BDD.log file is too large to post here apparently. Here are the
last bits of it.
<![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart"
context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014"
component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Search for Drive: TargetPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014"
component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found Drive: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Property OSDisk is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Target Drive Letter Found: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Found OS Drive: C 0]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[New ZTIDiskPartition : \\MININT-I3DUVLI\root\cimv2:Win32_LogicalDisk.DeviceID="C:" \\MININT-I3DUVLI\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="11:36:58.000+000"
date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Check Disk [0] <> [0] OK to skip.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[####### NOTE: If this is one of the last lines in your BDD.log file, check C: for the most up to date bdd.log!!!]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart"
context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
<![LOG[Event 41001 sent: ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread=""
file="ZTIDiskpart">

MDT 2013 Keyboard and mouse not working

I am imaging some older model Acers (Veriton N281G) via USB bootable drive and MDT 2013. In this model in particular; the keyboard and mouse does not work once the Wizard box pops up. The BIOS does indeed recognize it and I'm able to select the
USB bootable drive, but unable to move the mouse or use the keyboard once the wizard appears. All other models including HP and Lenovo work without any issues.
I've tried different keyboards/mice including PS2 and 2 different KVM's. I have a separate folder in the Out-of-Box Drivers folder for this particular model and I've imported numerous usb drivers as well as taken them all out and tried without success.
I've tried LiteTouchPE_x64 and x86.
Any suggestions? Unfortunately, we have many of these Acers in our Exam rooms with Windows XP and I'm needing to upgrade them ASAP. If it were up to me, I would just replace them all...

Very weird, I can't tell if this is a PC problem or a driver issue, and if a driver issue, which driver. Which USB controller? which keyboard?
You don't mention which WinPE version you are using. I would move between the WAIK 3.1 and ADK 8.1 to see which one works/does not work.
Additionally, I would try booting directly from a Windows 7 or Windows 8.1 install disk (Make USB bootable, and copy the install *.iso contents to the drive).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

For %TaskSequenceID% no longer working in MDT 2013.

I've used the blogs by Michael Niehaus to get MDT 2010 and MDT 2012 LTI deployment wizard application selection profiles working.
I'm now running MDT 2013 and when following the instructions here:
http://blogs.technet.com/b/mniehaus/archive/2012/09/04/revisiting-lti-deployment-wizard-application-selection-profiles.aspx, the MDT Wizard Displays the error: "No task sequences are available (TaskSequences.xml does not exist, is empty, or is inaccessible)."

Updating the deployment share seems to have resolved the issue.

Unable to capture images since upgrade to MDT 2013

I recently updated MDT 2012 to MDT 2013 to enable support for Windows 8.1. Under MDT 2012 I was able to both capture and deploy images without an issue. Since upgrading to MDT 2013 I've had nothing but grief. When I launch my Sysprep and Capture task I am
returned with the following error:
Error creating an image of drive D:, rc=2ZTI ERROR -Non-zero return code by ZTIBackup, rc=2Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM.
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The execution of the group (Capture Image) has failed and the execution has been aborted.
An action failed.
Operation aborted (Error: 80004004; Source Windows)
Failed to run the last action Create WIM. Execution of task sequence failed.
The system cannot find the file specified. (Error 00000002; 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
Once the machine boots up again I check the BDD log located in C:\Windows\Temp\DeploymentLogs and notice the following error:
<![LOG[ Console > Error opening file [\\rmh-vm-mdt2012\DeploymentShare$\Captures\WINDOWS.8.1.REF.wim].]LOG]!><time="10:23:55.000+000" date="02-06-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > Access is denied. ]LOG]!><time="10:23:55.000+000" date="02-06-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
My issue appears to be a permissions problem. For troubleshooting purposes I've given Everyone full access to \DeploymentShare$ however the problem continues to persist.
I'm not sure where to go from here. Hoping someone can help.
Thanks.

Additionally, ensure that the share itself is marked R/W access.
As a test, boot to WinPE and try to create a file, any file on the share.
However, Lordy86 may have the correct solution :^).
Keith Garner - keithga.wordpress.com

MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
to:
1-sysprep and capture using MDT 2013
2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

Hi altimav8,
Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The related guide:
Surface Pro - Enterprise Deployment Quick Start Guide
http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
Thanks for your understanding and support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Automating driver selection in MDT 2013

Similar Messages

Maybe you are looking for