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
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!
JoeDeployWiz_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 -
SCCM 2012 R2 OSD Task Sequence option
Hi, What to have an Install Applications step option that will identify computer record names with embed names for example
embedded name XXX inside a computer record for example:
Tabletxxx01
Tabletxxx02
Tabletabc01 - this computer record would skip the TS step.
Thanks!Hi,
Here are an example on a WMI query checking for a computername using wildcards,.
http://fritschetom.blogspot.com/2012/03/sccm-task-sequence-add-wmi-condition.html
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
OSD don't continue after reboot(restart computer task sequence)
I create a restart computer task sequence(reboot into"currently installed default operating system") after install some softwares
but I found the OSD will stop after reboot. why it will stop? how to fix it?
the The following is log files.
smsts-20140530-095634
Successfully completed the action (Patch IE9_Patches_1405) with the exit win32 code 0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
MP server http://PRI1.ABC.COM. Ports 80,443. CRL=false. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Setting authenticator TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set authenticator in transport TSManager 2014/5/30 9:56:34 1808 (0x0710)
Sending StatusMessage TSManager 2014/5/30 9:56:34 1808 (0x0710)
Setting message signatures. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Setting the authenticator. TSManager 2014/5/30 9:56:34 1808 (0x0710)
CLibSMSMessageWinHttpTransport::Send: URL: PRI1.ABC.COM:80 CCM_POST /ccm_system/request TSManager 2014/5/30 9:56:34 1808 (0x0710)
Request was successful. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2014/5/30 9:56:34 1808 (0x0710)
Clear local default environment TSManager 2014/5/30 9:56:34 1808 (0x0710)
Updated security on object C:\_SMSTaskSequence. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a TS execution environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Save the current environment block TSManager 2014/5/30 9:56:34 1808 (0x0710)
Successfully save execution state and environment to local hard disk TSManager 2014/5/30 9:56:34 1808 (0x0710)
Start executing an instruction. Instruction name: Reboot. Instruction pointer: 44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSCurrentActionName=Reboot TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a local default variable SMSRebootMessage TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a local default variable SMSRebootTimeout TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSLogPath=C:\WINDOWS\CCM\Logs\SMSTSLog TSManager 2014/5/30 9:56:34 1808 (0x0710)
Expand a string: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
smsts
Expand a string: TSManager 2014/5/30 9:56:34 1808 (0x0710)
Command line for extension .exe is "%1" %* TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set command line: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
Start executing the command line: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
!--------------------------------------------------------------------------------------------! TSManager 2014/5/30 9:56:34 1808 (0x0710)
Expand a string: WinPEandFullOS TSManager 2014/5/30 9:56:34 1808 (0x0710)
Executing command line: smsboot.exe /target:HD TSManager 2014/5/30 9:56:34 1808 (0x0710)
========================= [ smsboot.exe ] ========================= Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
Command line: '"smsboot.exe" /target:HD' Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
SMSTSRebootDelay=3 Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
SMSTSRebootMessage=正在安装新的 Microsoft Windows 操作系统。必须重新启动计算机才能继续。 Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
SMSTSRebootRequested=HD Reboot 2014/5/30 9:56:34 2572 (0x0A0C)
Process completed with exit code 0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
!--------------------------------------------------------------------------------------------! TSManager 2014/5/30 9:56:34 1808 (0x0710)
Successfully completed the action (Reboot) with the exit win32 code 0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
MP server http://PRI1.ABC.COM. Ports 80,443. CRL=false. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Setting authenticator TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set authenticator in transport TSManager 2014/5/30 9:56:34 1808 (0x0710)
Sending StatusMessage TSManager 2014/5/30 9:56:34 1808 (0x0710)
Setting message signatures. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Setting the authenticator. TSManager 2014/5/30 9:56:34 1808 (0x0710)
CLibSMSMessageWinHttpTransport::Send: URL: PRI1.ABC.COM:80 CCM_POST /ccm_system/request TSManager 2014/5/30 9:56:34 1808 (0x0710)
Request was successful. TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2014/5/30 9:56:34 1808 (0x0710)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2014/5/30 9:56:34 1808 (0x0710)
Clear local default environment TSManager 2014/5/30 9:56:34 1808 (0x0710)
Updated security on object C:\_SMSTaskSequence. TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a global environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a TS execution environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a global environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a TS execution environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Save the current environment block TSManager 2014/5/30 9:56:35 1808 (0x0710)
Successfully save execution state and environment to local hard disk TSManager 2014/5/30 9:56:35 1808 (0x0710)
Reboot to local harddisk TSManager 2014/5/30 9:56:35 1808 (0x0710)
_OSDGinaIsConfigured variable set to TRUE TSManager 2014/5/30 9:56:35 1808 (0x0710)
_SMSTSServiceStartType variable set to TSManager 2014/5/30 9:56:35 1808 (0x0710)
Command line for extension .exe is "%1" %* TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set command line: "bcdedit.exe" TSManager 2014/5/30 9:56:35 1808 (0x0710)
Executing command line: "bcdedit.exe" TSManager 2014/5/30 9:56:35 1808 (0x0710)
Process completed with exit code 0 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Calling RebootSystem() TSManager 2014/5/30 9:56:35 1808 (0x0710)
OSD type of task sequence. ignore the service window setting TSManager 2014/5/30 9:56:35 1808 (0x0710)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2014/5/30 9:56:35 1808 (0x0710)
Path variable OSDrive converted from C: to CE0B39280000100000000000: TSManager 2014/5/30 9:56:35 1808 (0x0710)
Updated security on object C:\_SMSTaskSequence. TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a global environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a TS execution environment variable _SMSTSNextInstructionPointer=45 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a global environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Set a TS execution environment variable _SMSTSInstructionStackString=17 20 26 TSManager 2014/5/30 9:56:35 1808 (0x0710)
Save the current environment block TSManager 2014/5/30 9:56:35 1808 (0x0710)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 2014/5/30 9:56:35 1808 (0x0710)
==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
Executing task sequence OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 2014/5/30 9:57:59 908 (0x038C)
Debug shell is enabled OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
Successfully enabled debug command shell support. OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
Configuring local administrator account OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
Re-assign all drive letters... OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
The drive information which has no drive letter can not be found. No need to re-assign driver letters. OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
Installing SMS client OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
Client already installed. OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)
Moving logs to SMS client directory OSDSetupHook 2014/5/30 9:58:00 908 (0x038C)Hi,
I suspect the IE require reboot and TS cannot catch this. So the TS cannot resume its state.
Also, see the KB below.
http://support.microsoft.com/kb/2894518
Juke Chou
TechNet Community Support -
Dear,
We do not have Orchestrator running in our SCCM 2012 R2 environment. Though I wonder if we could accomplish the following scenario with it:
Task sequence Windows 7 => Orchestrator step which queries assigned installations to the computer object and installs them one by one.
Could you advise?
Kind regards,
Stev.
SteveWonB> > Define "assigned to computer objects". How is this done technically?
Well, computer objects are members of collections via AD memberships, like the collection "W7-Google-Chrome" (exists of 100 computer objects).
Deploy of packages is done to these collections. So a computer member of "W7-Google-Chrome" will automatically get Google Chrome.
Some computers are member of 30 collections, some of 80.
Goal is to have the task sequence run all applications/packages assigned (with their reboots if needed).
Kind regards,
Steven
SteveWonB -
SCCM 2012 SP1 - OSD Task Sequence - Auto Apply Drivers
I have a basic task sequence created, capture User State, reboot into Windows PE, Apply Operating system, apply Windows Settings, Auto Apply Drivers, Setup Windows and Configuration, Install Applications, Restore User state
The problem I'm having is auto Apply the drivers. My test system is a Dell Opitiplex 3010, with a realtek PCI GBE Family Controller being the only driver added to the driver database.
During the task sequence, I see it down loading the driver, then proceed though the whole sequence. The system restarts and brings up the login. Here is the problem, the network drivers don't install, so the system is still in a workgroup, with no user state
restore.
I repeat the task, this time during the Setup Windows and Configuration, I press F8, and copy the _SMSTaskSequence folder to C:\temp.
Once the task in complete, I see the network drivers saved in _SMSTaskSequence\Drivers & \contentCache. I able to install the network drivers from this location.
What am I missing, why are the network drivers not being setup correctly in Windows 7?
From the \logs\SMST.LOG, I can see the driver being installed correctly, but one the sequence is complete the driver has not been installed.
From the SMSTS.LOG:
Installing driver "Realtek PCI GBE Family Controller" OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Copying "C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5" to "C:\_SMSTaskSequence\drivers\1". OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Successfully installed driver "Realtek PCI GBE Family Controller". OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Entering ReleaseSource() for C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5 OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
reference count 1 for the source C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5 before releasing OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Released the resolved source C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5 OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Microsoft ACPI-Compliant System'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Microsoft Basic Render Driver'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel(R) 82802 Firmware Hub Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic volume'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'ACPI Fixed Feature Button'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'HID-compliant mouse'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Motherboard resources'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'CD-ROM Drive'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'USB Root Hub'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'System timer'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic USB Hub'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'USB Input Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'ACPI Power Button'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'High Definition Audio Controller'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Motherboard resources'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Microsoft System Management BIOS Driver'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'PCI Simple Communications Controller'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'HID Keyboard Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic volume'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic Monitor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'USB Input Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Exiting with return code 0x00000000 OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Process completed with exit code 0 TSManager 3/21/2014 5:52:37 PM 1300 (0x0514)
!--------------------------------------------------------------------------------------------! TSManager 3/21/2014 5:52:37 PM 1300 (0x0514)
Successfully completed the action (Auto Apply Drivers) with the exit win32 code 0 TSManager 3/21/2014 5:52:37 PM 1300 (0x0514)Yes, I open a dos box during the Windows Setup, xcopy SMSTaskSequence to C:\temp
Then once Windows install is completed, I login to the local Admin account(only thing available), device manager and install the network driver from C:\temp\SMSTaskSequence\drivers\1
From Earlier in Setupact.log:
PnPIBS: C:\_SMSTaskSequence\drivers is listed as a driver path in unattend.xml ...
2014-03-25 12:27:22, Info PnPIBS: Found the file rt64win7.inf
2014-03-25 12:27:22, Info PnPIBS: Added driver C:\_SMSTaskSequence\drivers\1\rt64win7.inf to the list of drivers. -
Win 7 Pending Reboot after Task Sequence
SCCM 2012 SP1/MDT 2012 Win 7 Task sequence. All working fine but I'm finding that any line of business applications that are trying to install as at the end of the TS via the primary user are failing because of a pending reboot
I've tried adding another restart step in the TS but it is still pending a reboot. Checked a few post and looking in SessionManager\PendingFileRenameOperations there is a tmp file with no associated entry which I understand to be a delete operation and indeed
after a manual reboot it all disappears, but I'm confused as to why the TS should leave the system requiring a reboot
Can I fix/troubleshoot this in any way ?
Ian Burnell, London (UK)Try to identify the application that caused the registry key to be set and see what the exit code was of the installation of that application. The task sequence will respond to an exit code of an application and not to a registry key.
A dirty work around could be to set the task sequence variable SMSTSPostAction to something like
cmd /c shutdown /r /t 0 /f to trigger a restart when the task sequence is finished.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Task sequence fails after upgrading to 2012 R2 and MDT 2013
After upgrading to 2012 R2, my task sequence fails after the Setup Windows and ConfigMGR & Restart Computer. Instead of continuing to run the task sequence and load up the MDT Toolkit Package, it just stops at the Windows 7 login screen.
Do I need to create new toolkit & settings packages with MDT 2013 settings? Or do I just need to create a new task sequence?
I can't figure out what log to look at on the VM that I am imaging. If someone can point it out maybe there's some useful information. Thanks.
My task sequenceIt sounds a lot like that it could be failing at the client installation. Please take a look at the client installation logs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Here are the log files from c:\windows\ccmsetup\logs .. I took a glance and things run with success 0 which should mean no error right? The system also has the client installed with the CU2 patch.
Client Logs
Searched a bit online and people are saying it's due to the incorrect boot image. I was using a WinPE 5.0 I created on this TS but I'm going to make another and see where it goes.
This was the solution. -
MDT 2012 Suspend Task Sequence Problem
Hi ,
I have been using LTISuspens.wsf without problem in my MDT 2010 and MDT 2010 U1 for a long time. Recently I have create my test MDT 2012 and I have problem with this task.
I have created the new Run Command line cscript.exe "%SCRIPTROOT%\LTISuspend.wsf" in State Restore section. The build and capture TS is stopping correctly and I have the LTISuspend icon on the desktop. After resuming the TS, it going correctly through, running
sysprep, pop in again Set Network Location window, I can see it is running “Apply Windows PE (BCD)” step and then stops. There is message “suspended” and “The task sequence has been suspended true Use the…..”
Any ideas what I am doing wrong?
My customsettings.ini is from MDT 2010 and there they are fine.
I am capturing Windows 7.
Thanks
VinnieHi,
A few suggestions below for each of your issues.
Issue 1 is that you don't see any task sequences in the wizard
- Have you updated your deployment point after upgrading to 2012? if not then do this now
- Have you updated your boot media with the newly generated Litetouch_x86.wim (meaning your boot CD, boot USB or WDS)
The thinking behind this is that if you are using MDT 2010 boot media to try and speak to an MDT 2012 DS then you will have the same problem.
Issue 2 is that you've had the TS running in the past but it's broken for one reason or another.
- Have you recreated your Task sequence using the MDT 2012 client template? There are (minor but critical) differences in the logic between the versions of MDT and the new task sequence template has been updated as such. Using an MDT 2010 template with
MDT 2012 scripts can cause this.
These are 3 things that cause similar issues to you following an upgrade. -
Using a Hyper-V VM, I take snapshots of my base image build between major sections (automatic updates, application installation, scripts and extras, etc.) with the intention of being able to go back to that area and look at it for troubleshooting's sake.
Each of these snapshots is manually taken during a pause in my MDT task sequence (using LTISuspend). I would like to be able to roll back to these snaphots make edits to the task sequence (obviously to sections that haven't yet run), then resume and
see the changes implemented - but I don't know where the task sequence file(s) resides on VM being imaged, or if that can be changed after kicking it off at the very start of the build.
Is it possible to replace the task sequence file (and any other necessary files) that are cached locally on the VM during the imaging process? Where are those files located? Or any other way to implement changes to my task sequence so I wouldn't
have to start the image build completely from scratch?
This build takes about 6 hours. Having to make even the slightest modification causes me to lose an entire day, so this would be golden even if I have to manually edit certain files!Hi,
Based on my known, you cannot edit the task sequence after starting the deployment.
However, I suggest you ask this issue in MDT forum for more professional solution:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn
from your interaction with us. Thank you for your understanding.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Remove sccm 2012 client package from task sequence
Hello, is possible to remove the sccm client package from task sequence ? i am deploying OS to workgroup computers and i dont want install the sccm client . I am using MDT to create the task sequence.
Erickson MartinezNo, if you are using a task sequence in ConfigMgr (MDT integrated or not) then a client package is mandatory. The only way to get rid of the client is to deinstall it at the end of the task sequence (for example by using the SMSTSPostAction variable).
Another option, if you don't want the client, is to use MDT to deploy those machines. But that would cause an extra deployment mechanism to maintain.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
I am trying to update office via the SCCM 2012 R2 OSD task sequence. I know offline updating only updates the core components in the WIM and I'm trying to figure out how to add office updates as well. I am aware of using powershell to try and kick off
a WU scan as seen here:
http://myitforum.com/myitforumwp/2012/01/24/use-powershell-commands-to-assist-with-patching-during-sccm-image-build/
But the kicker is we don't use SCCM to update the workstations (Solo WSUS install). Is there a way to do this (maybe set the client in the TS to switch on SUP, then off again when it goes off into production) rather than have to build a new image every month?You could use the ZTI_WindowsUpdates.wsf script from MDT.
http://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/
How does it work?
The task sequence steps run a script called ZTIWindowsUpdate.wsf. The script uses the
Windows Update Agent API to manage the downloading and installation of updates. All audit information is written to the
ZTIWindowsUpdate.log file. If you find any unusual error codes in your log returned from the API (although I never have) you can compare the codes
here. The script will also check and update the
Windows Update Agent(WUA) as needed at the start.
In its default state, the ZTIWindowsUpdate.wsf script will connect to Microsoft Update then search for and download all available updates including Security Patches, Drivers, Browser Updates and Service Packs. This is essentially the same
as opening the GUI and selecting check for updates.
Daniel Ratliff | http://www.PotentEngineer.com -
Maintenance windows applies only to task sequences doesn't work
Problem:
SCCM 2012 R2 CU4
Task sequence deployment run outside maintenance windows when the maintenance windows is set to apply only to task sequences.
When the maintenance windows is set to apply to All deployments, the task sequence deployment run inside maintenance windows as expected.
The maintenance task defined was as:
Name: Maintenance Windows of Collection Coll_A
Time: 10:30am to 06:00am
Date: 20th March 2015
Apply this schedule to: Task Sequences
The task sequence defined was as:
Deployed to Collection Coll_A
Time: Run as soon as possible
The task sequence run at 9:48am on a workstation that is member of Coll_A.
There aren't other maintenances windows on others collections.
Below the workstation's serviceWindowsManager.log:
https://onedrive.live.com/redir?resid=BFBF530F33D996FD!123&authkey=!AI0dFPZ89XCL7xs&ithint=file%2clogWhen was the client added to the collection? Was it able to retrieve those MW policies before it received the TS?
Torsten Meringer | http://www.mssccmfaq.de
1_the client was added at the 9:30am.
2_Yes it is.
I have done another test and the result is the same:
_ first setting up the maintenance windows in Coll_A,
_ then insert the client in Coll_A and force a machine policy evaluation
_then deploy the task sequence in collection Coll_A -
Task sequences won't run after "Setup Windows and ConfigMgr"
In my Task Sequence for SCCM 2012 R2, no task sequences that occur after the "Setup Windows and Configuration Manager" step will run if I add to the Installation properties:
PATCH="\\server.domain.com\D$\SMSPKGSIG\PHX00033.2\configmgr2012ac-r2-kb2905002-x64.msp"
I believe this hotfix is necessary because I had to install on the server to fix the speed of downloading the WIM file. And I believe it says I need to append this PATH= switch to the install.
Is my path used incorrectly or something? Because that is the actual path to the file.
My task sequences will run fine if I remove it and just leave the SMSMP=server.domain.com in the install properties.Your path would then be :
PATCH="C:\_SMSTaskSequence\OSD\JJJ00033.2\configmgr2012ac-r2-kb2905002-x64.msp"
I suggest that you plan for further patches. Create a directory with all your future hotfix in it.
Ex: D:\SCCMHotFixes\KBNumber\x64
Your "Patch" parameter will grow over time, when a new hotfix will be release, you'll need
to add it after this one and so on...
I always use the _SMSTSDataPath without any problem, you could also try this.
PATCH=""%_SMSTSMDataPath%\OSD\JJJ00033.2\configmgr2012ac-r2-kb2905002-x64.msp"
Benoit Lecours | Blog: System Center Dudes -
SCCM 2012 MDT 2012 UDI Require domain credentials to run task sequence
We are in the process of moving to SCCM 2012 integrated with MDT 2012 for OSD from using MDT 2012 by itself. We're trying out UDI task sequences and have noticed a pretty gaping hole in functionality vs MDT 2012 by itself: password protecting a task sequence.
In MDT 2012 there was a built-in feature that required domain credentials to run a task sequence. If one exists using SCCM/MDT 2012, I haven't been able to find it. I've only found stuff like this http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/ which
would allow you to set a password, but not authenticate against AD. So, I'm wondering if there are any options to protecting a task sequence with domain authentication?
My understanding is that the Refresh and Replace StageGroup only run when you kick off a UDI task sequence in Windows. That means I have to make a task sequence available to the Configuration Manager Client in order for a tech to run a Refresh/Replace. And,
that in turn means that the UDI task sequence will be visible to all users since it needs to be available to their computer. Or, am I completely missing how UDI OSD should flow? If so, then I hope someone can correct me.
I'd appreciate any help or advice you can give. Thanks.Hi,
I am sorry to say that you are correct in your conclusions. There is no builtin way in ConfigMgr/MDT/UDI to require a domain username/password to run a task sequence, your option from Windows-noob.com is one way of solving it.
Regards,
jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec
Thanks for the info. What about workflow? How do you usually handle UDI in Replace and Refresh scenarios? Do you deploy the task sequence to collections that users can access?
Maybe you are looking for
-
How to find the back ground job details
Hi All, I have a back ground job running from many days, now we would like to know when this job was created on what date this job actvlly created and schuduled. Please informe me how to check this. Thanks & Regards, Muralikrishna
-
Programati​cally updating a cluster in a cluster
I have a cluster that contains several arrays and a cluster of controls. I am trying to create a method for a user to select one of the controls in the inner cluster and update the value. I am trying to populate a ring control with a list of the co
-
Help with get-aduser -filter command
Hi! I'm having problems with getting user info from displayname function searchuzv { $uzvinfo=$InputBoxuzv.text; $uzvcheck = Get-ADUser -filter "DisplayName -like '*$uzvinfo*'" If i run Get-ADUser -filter "DisplayName -like '*$uzvinfo*'" line separat
-
Email notification sending problem
Anyone can help me regarding my email notification sending. I have a program developed in netbeans which sends an email notification. Using the jar file generated when building/compiling the program, i created a batch file to run the jar. When i trie
-
Still puzzled by RF pass through
T2100 box. The RF passthrough on/off setting does not seem to do anything. If the box is either on or in low eco standby the RF signal is passed through. If it is in high eco standby (or off) the signal is not passed through. Thisi regardless of the