MDT 2013 - Different settings per task sequence

Hi,
I'm trying to create different settings for different TaskSequenceIDs. For one TS I wanted to join the pc to a workgroup and do SkipApplications=YES and for the other TS I wanted to join a domain and do SkipApplications=NO. But I can't get it to work for
some strange reason.
I've tried and tested this solution https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content but it doesn't work.
I tried this too : http://www.the-d-spot.org/wordpress/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/ but it doesn't work.
Perhaps MDT 2013 acts different then 2012 and 2010???? It would be nice if you could help me out on this one. :-)
Paul

@fapw, we use the database for a few years now and we're quite familiar with it. But we're going to install MDT for a client and they don't have SQL and they don't want to have it installed on one of their servers. So that's why I'm playing with the customsettings.ini.
The first I made was for a plain and simple capture, then I added Make&Model and I'm making it more and more complex. The idea is to have a final customsettings.ini that imitates - or gets as close as possible to - what we have already accomplished with
the database.
In the meantime I've read that the skip-panels-stuff is something that stands above everything and thus it's not possible to control that using properties, like f.ex. MACaddress. Well, that's alright then.
But I've got GOOD news for you all : selecting values for variables based on TaskSequenceID DOES WORK in MDT 2013 and ADK 8.1. This is what I did :
https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content
So I've downloaded the vbs, created an "external" tasksequenceid.ini which is read at the beginning of my Task Sequence and booted up the pc. When you select the tasksequence of your choice the parameters get filled in correctly ! OSDComputername
was the variable that I used to show me if the other tasksequenceid.ini file was read or not. If yes, the computername would have to be my value, if not it would be MININT-randomnumber.
Only downside of this fantastic wizard is that going back to change one of your options is not possible anymore. The moment a variable has a value, it doesn't change anymore! That particular behaviour was messing up my tests yesterday.

Similar Messages

MDT 2012 - Settings Per Task Sequence

I recently converted to MDT 2012 after running MDT 2010 for awhile (which has been great). Johan had written up an article (http://www.deployvista.com/Home/tabid/36/EntryID/139/language/en-US/Default.aspx)
that allows you to do settings per task sequence without the use of a database which was amazing for our environment. After switching to 2012 this no longer works. Is there something I'm missing or what do I need to change to make this work?
Thanks!
Joe

DeployWiz_SelectTS.vbs
' // Copyright (c) Microsoft Corporation. All rights reserved.
' // Microsoft Deployment Toolkit Solution Accelerator
' // File:      DeployWiz_Initialization.vbs
' // Version:   6.0.2223.0
' // Purpose:   Main Client Deployment Wizard Initialization routines
Option Explicit
' Image List
Dim g_AllOperatingSystems
Function AllOperatingSystems
   Dim oOSes
   If isempty(g_AllOperatingSystems) then
       set oOSes = new ConfigFile
       oOSes.sFileType = "OperatingSystems"
       oOSes.bMustSucceed = false
       set g_AllOperatingSystems = oOSes.FindAllItems
   End if
   set AllOperatingSystems = g_AllOperatingSystems
End function
Function InitializeTSList
   Dim oItem, sXPathOld
   If oEnvironment.Item("TaskSequenceID") <> "" and oProperties("TSGuid") = "" then
       sXPathOld = oTaskSequences.xPathFilter
       for each oItem in oTaskSequences.oControlFile.SelectNodes( "/*/*[ID = '" & oEnvironment.Item("TaskSequenceID")&"']")
           oLogging.CreateEntry "TSGuid changed via TaskSequenceID = " & oEnvironment.Item("TaskSequenceID"), LogTypeInfo
           oEnvironment.Item("TSGuid") = oItem.Attributes.getNamedItem("guid").value
           exit for
       next
       oTaskSequences.xPathFilter = sXPathOld
   End if
   TSListBox.InnerHTML = oTaskSequences.GetHTMLEx ( "Radio", "TSGuid" )
   PopulateElements
   TSItemChange
End function
Function TSItemChange
   Dim oInput
   ButtonNext.Disabled = TRUE
   for each oInput in document.getElementsByName("TSGuid")
       If oInput.Checked then
           oLogging.CreateEntry "Found CHecked Item: " & oInput.Value, LogTypeVerbose
           ButtonNext.Disabled = FALSE
           exit function
       End if
   next
End function
' Validate task sequence List
Function ValidateTSList
   Dim oTaskList
   Dim oTS
   Dim oItem
   Dim oOSItem
   Dim sID
   Dim bFound
   Dim sTemplate
   Dim sCmd
   Set Oshell = createObject("Wscript.shell")
   set oTS = new ConfigFile
   oTS.sFileType = "TaskSequences"
   SaveAllDataElements
   If Property("TSGuid") = "" then
       oLogging.CreateEntry "No valid TSGuid found in the environment.", LogTypeWarning
       ValidateTSList = false
   End if
   oLogging.CreateEntry "TSGuid Found: " & Property("TSGuid"), LogTypeVerbose
   sID = ""
   sTemplate = ""
   If oTS.FindAllItems.Exists(Property("TSGuid")) then
       sID = oUtility.SelectSingleNodeString(oTS.FindAllItems.Item(Property("TSGuid")),"./ID")
       sTemplate = oUtility.SelectSingleNodeString(oTS.FindAllItems.Item(Property("TSGuid")),"./TaskSequenceTemplate")
   End if
   oEnvironment.item("TaskSequenceID") = sID
   TestAndLog sID <> "", "Verify Task Sequence ID: " & sID
   Set oTaskList = oUtility.LoadConfigFileSafe( sID & "\TS.XML" )
   If not FindTaskSequenceStep( "//step[@type='BDD_InstallOS']", "" ) then
       oLogging.CreateEntry "Task Sequence does not contain an OS and does not contain a LTIApply.wsf step, possibly a Custom Step or a Client Replace.", LogTypeInfo
       oProperties.Item("OSGUID")=""
       If not (oTaskList.SelectSingleNode("//group[@name='State Restore']") is nothing) then
           oProperties("DeploymentType") = "StateRestore"
       ElseIf sTemplate <> "ClientReplace.xml" and oTaskList.SelectSingleNode("//step[@name='Capture User State']") is nothing then
           oProperties("DeploymentType")="CUSTOM"
       Else
           oProperties("DeploymentType")="REPLACE"
           RMPropIfFound("ImageIndex")
           RMPropIfFound("ImageSize")
           RMPRopIfFound("ImageFlags")
           RMPropIfFound("ImageBuild")
           RMPropIfFound("InstallFromPath")
           RMPropIfFound("ImageMemory")
           oEnvironment.Item("ImageProcessor")=Ucase(oEnvironment.Item("Architecture"))
       End if
   Elseif oEnvironment.Item("OSVERSION")="WinPE" Then
       oProperties("DeploymentType")="NEWCOMPUTER"
   Else
       oLogging.CreateEntry "Task Sequence contains a LTIApply.wsf step, and is not running within WinPE.", LogTypeInfo
       oProperties("DeploymentType") = "REFRESH"
       oEnvironment.Item("DeployTemplate")=Ucase(Left(sTemplate,Instr(sTemplate,".")-1))
   End if
   oLogging.CreateEntry "DeploymentType = " & oProperties("DeploymentType"), LogTypeInfo
   set oTaskList = nothing
   set oTS = nothing
   ' Set the related properties
   oEnvironment.Item("ImageProcessor") = ""
   oEnvironment.Item("OSGUID")=""
   oUtility.SetTaskSequenceProperties sID
   If Left(Property("ImageBuild"), 1) < "6" then
       RMPropIfFound("LanguagePacks")
       RMPropIfFound("UserLocaleAndLang")
       RMPropIfFound("KeyboardLocale")
       RMPropIfFound("UserLocale")
       RMPropIfFound("UILanguage")
       RMPropIfFound("BdePin")
       RMPropIfFound("BdeModeSelect1")
       RMPropIfFound("BdeModeSelect2")
       RMPropIfFound("OSDBitLockerStartupKeyDrive")
       RMPropIfFound("WaitForEncryption")
       RMPropIfFound("BdeInstall")
       RMPropIfFound("OSDBitLockerWaitForEncryption")
       RMPropIfFound("BdeRecoveryKey")
       RMPropIfFound("BdeInstallSuppress")
   End If
   If oEnvironment.Item("OSGUID") <> "" and oEnvironment.Item("ImageProcessor") = "" then
       ' There was an OSGUID defined within the TS.xml file, however the GUID was not found
       ' within the OperatingSystems.xml file. Which is a dependency error. Block the wizard.
       ValidateTSList = False
       ButtonNext.Disabled = True
       Bad_OSGUID.style.display = "inline"
   Else
       ValidateTSList = True
       ButtonNext.Disabled = False
       Bad_OSGUID.style.display = "none"
   ENd if
   sCmd = "wscript.exe """ & oUtility.ScriptDir & "\ZTIGather.wsf"""
   oItem = oSHell.Run(sCmd, , true)
End Function

MDT 2013: Wizard Pages by Task Sequence

Hi,
I believe what I am trying to do is not possible from previous readings on this forum, BUT then I see something in my MDT 2013 OSD wizard that seems to indicate there might be a way to get it done. So here goes.
For my own demos, I am trying to develop a deployment share that is much like Johan Arwidmark's hydration kit. Some machines, like a domain controller or a SQL cluster are all well-defined: computer names, IP addresses, etc. are fixed and can be set
in customsettings.ini or in the Task Sequence with variables. However, I would also like the ability to have to deploy a "generic" machine where I can select roles, applications, etc.
This would require having different wizard pages shown for different task sequences. From what I've read, this may not be possible without developing a custom wizard (and that might be too much effort). However, I currently have two task sequences and depending
on which one I select, I see a different number of steps to complete? See screenshots. I don't know what I have currently configured that makes it like that.
(when I select "Domain Controller 01" task sequence) (Task sequence ID "DC01")
(when I select the "generic" task sequence)
Below is my customsettings.ini [the only rules file I have].
[Settings]
Priority=TaskSequence,Default
[Default]
_SMSTSORGNAME=Demo Deployment
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
AdminPassword=P@ssw0rd!
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
EventService=http://192.168.232.1:9800
SkipUserData=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipFinalSummary=NO
FinishAction=SHUTDOWN
SkipLocaleSelection=YES
HideShell=YES
[DC01]
_SMSTSORGNAME=DC01 Deployment
SkipComputerName=YES
OSDComputerName=DC01
SkipDomainMembership=YES
JoinWorkgroup=DEMO
SkipRoles=YES
I would expect the settings for task sequence "DC01" to be applied after I select that task sequence in the wizard. That doesn't seem to work. The first task in the sequence is a "Gather" task that gathers local data and processes customsettings.ini.
I understand I can't override most settings from [Default] because they would have already been processed but as you can see, that's not what I am actually trying.
I am not opposed to having multiple rules files if that would work. However, it seems like that doesn't make much difference when it comes to actually seeing different wizard steps active. I've tried adding a second customsettings_dc01.ini file and having
a Gather step that specifically references that file in the "Initialize" group.
I've considered some alternatives to making it work this way, such as having multiple deployment shares and "linking" them (although I haven't done this before) so I wouldn't have to copy all the applications.
I would also set the computer name and all in the task sequence using variables, but that still doesn't address the problem.
Any insight is appreciated,
SA.

SpeedBird186 - There are several assumptions going on here.
1. by default MDT processes the CS.ini file *before* the wizard, and *after* the Task sequence has started. If you want CS.ini file to be processed just *after* you select your TS in the wizard, use Johan's trick above.
2. There are about 20 different wizard pages, and they don't appear in *all* scenarios. the wizard framework will attempt to do an intelligent job of filtering out pages that are not relevant to the scenario at hand. For example, in the graphic above, you
can see that the OS roles and Features page will appear/disappear. This can happen for example if the task sequence you selected earlier does or does *not* have a "OS Roles and Featrues" step in the Task sequence.
3. For me, the easiest way to process roles would be to create some new "Applications" and to put them in a folder.
Keith Garner - keithga.wordpress.com

MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

Hi There,
The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
The test machine I have been using is the Surface pro 2.
The interesting part is after a failure is if I start the process over again , boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
been edited to search and apply ther split .swm files. This works well.
After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt do anything.
I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
Thank You in advance!

Hi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

MDT 2013 - Install Application in Task Sequence Stuck

I am running an application installation within my task sequence during my deployment. One of the applications prompts a user response to click yes to continue. Otherwise the task is stuck at that step. It appears to be stuck during my Java 7U51
installation running this command. It works on several machines but I get this once in a while on a few workstations when trying to deploy. any ideas?
About to run command: \\xxxxxxxxxxxxxxxxxxx\xxxxxxxxxx\Tools\X64\bddrun.exe jre-7u51-windows-i586.exe /s /v"/norestart /AUTOUPDATE=0 JAVAUPDATE=0 JU=O"

first try to install java with
MDT if any one you are using and then
run the programyou want to post an example
here
http://mdtguy.wordpress.com/2014/02/17/installing-the-latest-java-re-msi-with-mdt-2013/
Freelance-IT http://www.freelance-it.com.mx

Different settings per podcast

Hi!
Is it possible to set different settings per podcast.
E.g.
* I want to keep all episodes from my favourite
weekly radio show.
* I only want to keep *the latest* podcast of the CNN news
update.
IS Apple reading this group?? Tjis would be a really helpful setting in iTunes ;-)!!

Apple does not read this group, at least not publicly. What you'd want to do is submit a feature request. Unfortunately, this has gotten somewhat hard to do; the page that used to let you do it is now exclusively for music store requests. You can try submitting it there (http://www.apple.com/feedback/itunes.html), but there's no proof that they pay any attention to feature requests there.

How can I specify different settings in CustomSettings.ini based on the OS that is being deployed?

I originally thought this could be achieved using "OSVersion" or "OSCurrentVersion" but (unless I'm mistaken) those variables are in fact tied to the OS from witch you actually launch the MDT Wizard right? i.e. say I run MDT from within
Windows PE to deploy Windows 8. The "OSVersion" and "OSCurrentVersion" will contain values for the Windows PE instance that is currently running MDT and not the Windows 8 OS I am actually deploying right? Assuming that is the case then
is there some variable in MDT that stores version information about the OS you are currently deploying? If so can I use that in CustomSettings.ini to specify different settings for specific OSes I deploy?

Rens,
First thanks for responding. Next please don't take my response the wrong way but this is a bit of a pet peeve of mine. Maybe I'm just "doing it wrong" but I have used the TaskSequenceID trick in the past and thats actually where my problem lies.
Too many people are recommending this course of action without including the caveats. Your response implies that using TaskSequenceID is as simple as just adding "TaskSequenceID" to priority and then creating entries based on the TSIDs themselves.
In reality getting this to work is far more challenging. One needs to only check the following threads (and several others) for the issues other people are having when they try to use TaskSequenceID in CustomSettings.ini:
http://social.technet.microsoft.com/Forums/en-US/e17a1952-d1f7-41ef-8231-0d6fcc41882e/mdt-2012-settings-per-task-sequence?forum=mdt#f0810428-e6fd-468e-8c76-ca18b210c191
http://social.technet.microsoft.com/Forums/en-US/320aafee-07d2-4b96-9138-a902fec7edf5/mdt-2012-custom-rules-by-tasksequenceid-not-working-now
In fact, following the steps outlined here was the *only* way I was able to get TaskSequenceID to work for me:
http://www.the-d-spot.org/wordpress/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/
Even then its causing some erratic issues in some areas like button lag in the Wizard because ZTIGather has to run twice and pre-checked Applications in the wizard still installing even if they are unchecked. Since my needs are more OS-specific (as opposed
to Task Sequence specific) I was hoping for a better solution. I suppose I can check BDD.log but I was hoping someone here had already encounter this same issue and hit upon a solution they could share.
Anyone?

MDT 2012 Replace computer task sequence

Hello all,
I am using MDT 2012 Update 1 for upgrading over 200 machines from Windows XP to Windows 7.
Some of these machines are going to be REFRESH scenario. I have the task sequence for REFRESH scenario and it is working as expected.
However, I do not know how to create REPLACE scenario task sequence. From what I understand, I need to create two tasks sequences. I have created a task sequence that capture user's data and upload it to a share.
But how do I create a restore task sequence that restores that data to another computer after installing OS? What do I need to in the restore task sequence that either prompts me to select where to restore the data from or knows where the data is?
In SCCM there is computer association, but I have not been able to figure out how to do it purely using MDT.
Any expert help is greatly appreciated.
Thanks in advance,
SinghP80

Right, you will need 2 task sequences in a replace scenario. The REPLACE task sequence captures the user state from the running OS. Then you use a NEW COMPUTER task sequence (I called mine RESTORE) that restores the user state back after installing
the OS, which will boot from media or PXE. RESTORE gets all of its values from the Default and Jackson sections. My apologies, my customsettings.ini is butchered and has comments and junk in it that I should remove to clean it up. And you will
have to edit the code as described in the settings per task sequence thread for my cs.ini to work. And, I set my OSDComputerName=%assettag%. I set my Dell asset tags in the BIOS with the Dell CCTK tool.
http://social.technet.microsoft.com/Forums/en-US/e17a1952-d1f7-41ef-8231-0d6fcc41882e/mdt-2012-settings-per-task-sequence?forum=mdt
[Settings]
Priority=ByLaptopType, ByDesktopType, ByIsVM, DefaultGateway, TaskSequenceID, Default
Properties=MyCustomProperty
[DefaultGateway]
192.168.122.1=Jackson
[Jackson]
DeployRoot=\\192.168.122.6\FDO_Offices
SkipComputerBackup=NO
BackupDir=Captures
BackupShare=\\192.168.122.2\f$
UDShare=\\192.168.122.2\f$\usmtstorage
OSDComputerName=%AssetTag%
UDDir=%OSDComputerName%
SLSShareDynamicLogging=%DeployRoot%\Logs\%OSDComputerName%
SLSHARE=\\192.168.122.2\F$\Logs
MachineObjectOU=OU=Computers,OU=Jackson,OU=Branches,DC=xxxxxxxx,DC=xxxxxxxx,DC=xxxxxxxxxx
UserDataLocation=\\192.168.122.2\f$\usmtstorage\%OSDComputerName%
ComputerBackupLocation=\\192.168.122.2\f$\captures
UserID=xxxxxxxxxx
UserDomain=xxxxxxxxxx
UserPassword=xxxxxxxxxxxx
[ByLaptopType]
Subsection=Laptop-%IsLaptop%
[ByDesktopType]
Subsection=Desktop-%IsDesktop%
[ByIsVM]
Subsection=IsVM-%IsVM%
[Laptop-True]
SkipBitLocker=NO
BDEInstall=TPM
BDEInstallSuppress=NO
BDEWaitForEncryption=FALSE
BDEDriveSize=512
BDEDriveLetter=S:
BDERecoveryKey=AD
;BDEKeyLocation=\\192.168.122.2\f$\bitlocker_keys
BDEAllowAlphaNumericPin=Yes
[Desktop-True]
SkipBitLocker=YES
[IsVM-True]
SkipBitLocker=YES
[Laptop-False]
[Desktop-False]
[IsVM-False]
[Default]
XResolution=1
YResolution=1
BitsPerPel=32
ApplyGPOPack=NO
HIDESHELL=NO
DISABLETASKMGR=YES
;BackupDrive=ALL
SkipProductKey=YES
SkipLocaleSelection=YES
UserLocale=en-US
UILanguage=en-US
SkipTimeZone=YES
TimeZoneName=Central Standard Time
KeyboardLocale=en-US
_SMSTSOrgName=Office of xxxxxxxxxxxx
SkipAdminPassword=YES
AdminPassword=xxxxxxxxxxxxx
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipDeploymentType=YES
SkipSummary=Yes
MandatoryApplications001={aa888a5e-849a-4522-a4e4-57b39dfa29c2} ;you'll want to remove this
[NEWCOMPUTER]
SkipUserData=YES
DeploymentType=NEWCOMPUTER
OSInstall=Y
;OSDComputerName=
SkipComputerName=NO
SkipFinalSummary=Yes
FinishAction=LOGOFF
SkipTaskSequence=NO
SkipDomainMembership=YES
JoinDomain=xxxxxxxx
DomainAdmin=xxxxxxxxxxxxxx
DomainAdminDomain=xxxxxxxxxxx
DomainAdminPassword=xxxxxxxxxxxxx
SkipCapture=YES
DoNotCreateExtraPartition=NO
[CAPTURE]
SkipUserData=YES
TaskSequenceID=CAPTURE
DeploymentType=CUSTOM
BackupFile=MASTERCAPTURE.wim
SkipAdminPassword=YES
AdminPassword=xxxxxxxxxx
SkipCapture=NO
DoCapture=YES
[REFRESH]
SkipUserData=NO
TaskSequenceID=REFRESH
DeploymentType=REFRESH
DoCapture=NO
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
USMTMigFiles003=MigDocs.xml
USMTMigFiles004=migexcludexternaldrives.xml ;you'll want to remove this
USMTMigFiles005=migmydocs.xml ;and this
;USMTMigFiles006=migwallpaper.xml
;USMTMigFiles006=MigNetPrinters.xml
; USMTMigFiles007=config.xml
;ScanStateArgs=/v:5 /o /c /vsc /all /localonly
ScanStateArgs /v:5 /o /c /ue:%computername%\*
LoadStateArgs=/v:5 /c
;BackupDrive=ALL
;OSDComputerName=%OSDComputerName%
SkipComputerName=NO
OSInstall=Y
SkipFinalSummary=Yes
FinishAction=LOGOFF
SkipTaskSequence=NO
SkipCapture=YES
DoNotCreateExtraPartition=NO
SkipDomainMembership=YES
JoinDomain=xxxxxxxxxxxx
DomainAdmin=xxxxxxxxxxxxx
DomainAdminDomain=xxxxxxxxxxx
DomainAdminPassword=xxxxxxxxxxxxxx
BackupFile=%OSDComputerName%.wim
[REPLACE]
TaskSequenceID=REPLACE
DeploymentType=REPLACE
SkipComputerName=NO
DoCapture=NO
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
USMTMigFiles003=MigDocs.xml
USMTMigFiles004=migexcludexternaldrives.xml ;remove this
USMTMigFiles005=migmydocs.xml ;and this
;USMTMigFiles006=migwallpaper.xml
;USMTMigFiles006=MigNetPrinters.xml
; USMTMigFiles007=config.xml
;ScanStateArgs=/v:5 /o /c /vsc /all /localonly
ScanStateArgs /v:5 /o /c /ue:%computername%\* /ue:xxxxxxxxxxxx\administrator
LoadStateArgs=/v:5 /c
;BackupDrive=ALL
SkipUserData=NO
SkipAdminPassword=YES
AdminPassword=xxxxxxxxxxx
SkipCapture=YES
DoCapture=NO
SkipComputerBackup=NO
BackupFile=%OSDComputerName%.wim
[RESTORE]
TaskSequenceID=RESTORE
DeploymentType=NEWCOMPUTER
DoCapture=NO
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
USMTMigFiles003=MigDocs.xml
USMTMigFiles004=migexcludexternaldrives.xml
USMTMigFiles005=migmydocs.xml
;USMTMigFiles006=migwallpaper.xml
ScanStateArgs /v:5 /o /c /ue:%computername%\*
LoadStateArgs=/v:5 /c /ue:%computername%\* /ue:xxxxxxxx\xxxxxxxx
SkipComputerName=NO
SkipUserData=NO
SkipDomainMembership=YES
JoinDomain=MSS
DomainAdmin=xxxxxxxxxxxx
DomainAdminDomain=xxxxxxxxxxx
DomainAdminPassword=xxxxxxxxxxxxx
DoNotCreateExtraPartition=NO
SkipFinalSummary=Yes
FinishAction=LOGOFF
SkipComputerBackup=NO
Bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\192.168.122.6\FDO_Offices
UserID=xxxxxxxxxx
UserDomain=xxxxxxx
UserPassword=xxxxxxxxxxxx
SkipBDDWelcome=YES

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.

Different task sequences available on different machines??

Hi there,
hopefully someone has seen this before as i'm a bit confused here. I've got MDT 2013 installed and have been happily deploying to all manner of machines for months now.
But today i've noticed that different task sequences are appearing for different machines. Eg, i have a DELL Latitude E7240 that shows the task sequences as expected, however when i run the same lite touch vbs script on an Optiplex All In One (that has been
imaged off the network before), i get a completely different set of task sequences available.. when i try to select one of these, i get a message 'Bad task sequence item (missing OS)'.
This is definitely connecting to the same deployment share and they are the same PE version (64 bit). The task sequences i want to see are checked as enabled and not hidden etc..
I just don't know where to check from here, any ideas for me please??
Adam

Hi Keith,
thanks for the response, but the process doesn't get to writing logs - the bdd.log file just shows that the deployment was cancelled.
I'm trying to understand why on one machine a specific set of task sequences is available, but not on another?
I can run the deployment on my E7240 and the task sequence doesn't throw the 'missing OS' message, but on another machine the task sequences are a little different but when i try to run the one that does work on the E7240 (as it appears in the list on the
other machine) i DO get the 'missing OS' error.
weird.. ??
still very stumped...
:S
Adam Sellers

OSD Task Sequence - Network boot capture of modified OS reference VM, but without MDT?

Hi All
Guess the Title of the question sums it up really.
Is it possible to do a network-boot (aka PXE) capture of an OS that has been modified, so that its WIM is created for use within other deployment Task Sequences?
I know that this is possible via MDT's "Sysprep and Capture" Task Sequence, but this integration has not been done yet, and from time-scales is not possible. Just curious if others have found a work around via custom Task Sequence(s) of some
kind? If not will have to go with the SCCM's more manual 'Capture Media' option.
Any help much appreciated.
Kind Regards
Andrew

Hello,
It is possible to capture image without MDT integration
http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/
You can also do this manually.
You need sysprep the reference image first, then boot into win PE with either PXE or USB bootable device. Run ImageX or DISM tool to capture the image. Check this:
https://technet.microsoft.com/en-in/library/dd799291%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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">

Deploy OS task sequence fails when deploying to multiple computers

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 just rebooted the server and tried again, same result.
I keep getting a "Body text cannot contain links or images until we are able to verify your account" error when posting a hyperlink. I've had my technet account since October... weird.
Here's the snippet that's important:
<![LOG[ Console > [ 18% ] Applying progress: 14:47 mins remaining ]LOG]!><time="11:27:10.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 19% ] Applying progress: 14:27 mins remaining ]LOG]!><time="11:27:18.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 20% ] Applying progress: 14:15 mins remaining ]LOG]!><time="11:27:32.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\MSORES.DLL again (Error = 1392)]LOG]!><time="11:27:40.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 21% ] Applying progress: 14:06 mins remaining ]LOG]!><time="11:27:42.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 22% ] Applying progress: 13:49 mins remaining ]LOG]!><time="11:27:48.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 23% ] Applying progress: 13:29 mins remaining ]LOG]!><time="11:27:55.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 516)]LOG]!><time="11:28:01.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:01.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:01.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:02.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:02.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 24% ] Applying progress: 13:13 mins remaining ]LOG]!><time="11:28:07.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:13.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:14.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:15.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:16.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ ERROR ] C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll (Error = 1392)]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Error restoring image.]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > The file or directory is corrupted and unreadable. ]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 2]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FAILURE ( 5624 ): 2: Run ImageX: /apply "\\MyServer\DeploymentShare$\Operating Systems\T731 (Final) Windows 7 64 bit May 2013\T731 (Final) Windows 7 64 bit May 2013.wim" 1 C:]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="11:28:18.000+000" date="06-11-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="11:28:18.000+000" date="06-11-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

SCCM 2012 R2 With MDT 2012 AND MDT 2013 Side by Side

Currently we're running 2012 R2 CU3 with MDT 2012 integrated into it. We're looking at upgrading to MDT 2013 (whatever the latest update is). What I'm wondering, and can't seem to find any information on, is if we can continue to use our MDT 2012 boot
.wims/OSD Task Sequences/etc until such time as we create and test new ones or are we going to have to update everything right away?

Are you sure you are using MDT *2013* with ConfigMgr 2012 *R2*? That's not a supported configuration and I think there are multiple technical problems with this combination.
The task sequences themselves don't change -- because they are ConfigMgr task sequences -- but the MDT tasks must be updated to use the MDT 2013 tasks. Boot image use is partially dependent upon the OS you are deploying however only WinPE 3.1 and WinPE 5.0
based boot images are supported in R2.
Jason | http://blog.configmgrftw.com | @jasonsandys
Did you mean to ask if we were running MDT 2012 with ConfigMgr 2012 R2? Then yes we are. We did the upgrade from SP1 CU2 to R2 CU3 a couple of weeks ago but haven't upgraded MDT to 2013 yet. That's our next step but we also don't want to take down/break imaging
capability if we can help it (major college, staff/students constantly breaking stuff, etc).

Deploying Apps in MDT 2013

I am trying to deploy apps using MDT 2013 on clients machines but keep getting the
following bdd.log error. Please note I can image,
deploy drivers and packages in MDT with no issues except when I
try to deploy apps:
I have added all the applications in their
individual folder in MDT, then i created a task sequence to install
application. Each app gets their own "install application" command. Then on the client machine i run the following cmd with
elevated privillege: cscript.exe
\\ORS-WDS\DeploymentShare\Scripts\LiteTouch.WSF. The script runs after selecting the task but then disappeared and i get this bdd.log on the client:
https://onedrive.live.com/redir?resid=8D6242F28512FDE3!564&authkey=!AFojuxXjHaKXl0I&ithint=file%2ctxt

These are not the correct bdd.log files. Make sure you include the right ones. Also check the c:\windows\temp\... folder.
From the error above:
C:\windows\system32>err 0x8007051B
# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x51b
# for hex 0x51b / decimal 1307 :
ecNotRitpMaster ec.h
ERROR_INVALID_OWNER winerror.h
# This security ID may not be assigned as the owner of this
# object.
# 2 matches found for "0x8007051B"
This would suggest that you are still having permission/elevation problems.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013 - Different settings per task sequence

Similar Messages

Maybe you are looking for