MDT 2013 Sysprep Bugs

I am curious if anyone know any bugs with MDT 2013 sysprep as it relates to Windows 8.1 or any differences in sysprep from MDT to SCCM 2012 R2. Reason why I am asking is that I posted to this news group earlier today asking:
If 10 minute logon time while it goes through the screens "installing your applications ", "taking care of a few things", and "getting your apps ready" is normal when creating and capturing the image with MDT 2013. I have
also done the same test simply pushing out the install.wim with SCCM 2012 and my logon times are 2-3 minutes.
I have more information and I suspect the problem is with the sysprep process with MDT 2013. What I did is I used MDT 2013 to simply create the reference system. I then used SCCM Capture Media to capture the reference machine and create the wim. Once I deployed
that wim with SCCM I noticed logon times were about 1 minute. Much quicker than what I am seeing with creaeating the reference machine and capturing with MDT and then deploying with SCCM.
I know the initial logon times will take some time while the Modern Apps do get installed. I am just not sure why it is 95 percent faster when I don't capture it with MDT. That is why I think MDT with sysprep is the culprit.
Any help would be greately appreciated.
Thanks,
Mike
Solutions Architect

Parsing step node: Execute Sysprep TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
Description: TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
ContinueOnError: false TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
SuccessCodeList: 0 3010 TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566)
TSManager 06/30/2014 9:10:57 PM
2268 (0x08DC)
No condition is associated with the step. TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
Disable: false TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
This portion was interesting inside my SMSTS.log in the appdata/temp directory.  Hope this helps a tad.

Similar Messages

  • SCCM 2012 R2 and MDT 2013 Task Sequence Bugs

    Any links that list issues with the default MDT 2013 deploy task sequence: UEFI, local administrator password, Machine OU settings, OS installation partition and computer replace scenario.

    Hi,
    If you want to file bugs or feature requests, you'll need to go to the MDT and ConfigMgr connect site:
    https://connect.microsoft.com/ConfigurationManagervnext/Feedback
    Cheers!
    If this post is helpful please click "Mark for answer", thanks! Kind regards

  • MDT 2013 / ADK 8.1 Language Bug?

    Have a new MDT 2013 Deployment with Windows ADK 8.1 Update. Using the following keyboard settings in customsettings.ini and bootstrap.ini for years:
    KeyboardLocale=0807:00000807
    KeyboardLocalePE=0807:00000807
    The Keyboard PE settings do NOT work when the credentials for the connection to the deployment share have to be provided. Have the US keyboard layout. But when I hit F8, I have the correct Swiss German Keyboard Layout in the command window.
    Any advice? Thank you in advance for any help
    Franz

    Hi,
    Generally,  you would use GPT for UEFI systems, MBR for BIOS-based systems, on UEFI-based systems, it will create four partitions (boot, MSR, recovery, OS) on a GPT disk.
    It should just work, as soon as you figure out how to enable UEFI “native” mode in the firmware (BIOS) settings and then boot in “native” mode.
    Alex Zhao
    TechNet Community Support

  • MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

    First, let me give you some context:
    Framework: MDT 2013 with MS SDK 7.1
    Task Sequence: Standard Client TS with sysprep and capture.
    Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
    Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
    A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
    While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
    This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
    From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
    this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
    TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
    My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

    I have this issue intermittently as well.  For us, it coincided with the deployment of IP phones, which meant PoE switches all around.  However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
    boot.
    As this issue has been intermittent, I've backburnered it.  When it does happen, I just wait for the lease to arrive then rerun the wizard.
    Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
    The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on.  Basically, what Keith Garner said.  They also disabled PortFast awhile back to see if that made any difference, and it did
    not.

  • 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.

  • MDT 2013 won't capture 8.1 image, does not boot to PE to capture

    I am doing this with Server 2012 R2 and MDT 2013, and the reference machines are VMs
    I initially created a deployment share for creating windows 7 and windows 8.1 reference images and capturing and deployment worked ok. After getting into some more details i customized the deployment share customsettings  to make things easier and created
    a separate capture share for capturing new reference images. I updated permissions on the share so my service account has access to it. 
    In this share i imported the windows 8.1 os files and copied the sysprep and capture task sequence i used to capture my first reference image [from the original deployment share], but when running the task sequence it reboots and just goes back into windows,
    instead of windows PE to capture the image. 
    I copied a windows 7 capture sequence to the capture share, imported the windows 7 files and updated the task, and it rebooted into PE without a problem and copied an image. so I don't believe I have any permissions/customsettings problems with the new share.
    Im not seeing any errors jump out at me in the bdd.log but I'm new-ish to going over the logs and using MDT to start with so I may be missing the obvious. I am using SMS trace and dont see any red/yellow highlites either. 
    In windows 7 i did have the vm in audit mode when i mapped the share as an admin and started the task sequence. In windows 8.1 i am not in audit mode [after doing some research and learning more about using MDT it did not seem necessary]
    After comparing a run of the windows 7 task to windows 8 i see the boot.wim copied to the win 7 vm, but i dont see it on the win 8 vm. There is a partition created, i cant see data in it when i show hidden files. 
    rules for the capture share
    [Settings]
    Priority=Default
    Properties=MyCustomProperty
    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipCapture=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    Heres the last part of bdd.log. New here so I can't post a link yet, didnt know if i should post the whole thing here or not to start with. 
    <![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property PHASE is now = CUSTOM]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[--------- Script Start ---------]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property BootPE is now = ]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:32:24.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTIUtility!GetAllFixedDrives = E: C:]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[No task sequence is in progress.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Not running within WinPE.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentMethod = UNC]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapped Network UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Phase = CUSTOM]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentType = CUSTOM]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property ResourceDrive is now = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceDrive = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[SMS Task Sequencer already found on C:\MININT\Tools\X64]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    Thanks for your reply. 
    The pc is not in the domain when i run litetouch. It was joined after install, then i run some local gpos/scripts against it, install all of the shared printers from servers, then i put it back in a workgroup, login as the local administrator, delete the
    domain profiles and guids in the registry, briefly connected back to a domain server [not with a mapped drive] to copy a couple of files, rebooted into the local admin account an ran litetouch. 
    After running litetouch.wsf the first time in the windows 8.1 pro vm [no changes, but manual connection] it rebooted without sysprepping or taking an image
    I deleted the task sequence and created another one with "sysprep and capture" as the sequence.  i made no changes to the task sequence. did all of the above, ran litetouch, and it just reboots. sysprep does not run and windows pe does not load. 
    if i run sysprep and boot into audit mode [as a test, since my windows 7 vm snapshot was in audit mode when it runs litetouch.wsf], then run litetouch, sysprep works, then it DID capture an image, but after that image was capture and the VM rebooted, i got
    this error when loading windows 8
    "windows could not complete the installation. To install windows on this computer, restart the installation" and if i hit ok it will reboot and error out again. 
    Haven't had any issues with that VM until now. 
    I reverted to my snapshot and just ran sysprep oobe w/ generalize to see how it would react
    it failed, setuperr.log shows SYSPRP failed to remove apps for the current user. some searching gives me information on that and makes me think its related to adding/deleting user profiles? i dont actually use or update the apps at all, i have a deploy task
    that removed most of them and customizes the start screen and those seem to work without issue. 
    found this as my reference: http://support.microsoft.com/kb/2769827/en-nz
    Sysprep has an additional provider that is added in Windows 8 to clean appx packages and generalize the image. The provider will only work if the Appx package is a per-user package or an all-user provisioned package.
    and
    Resolution
    The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets:
    Import-Module Appx
    Import-Module Dism
    Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
    if i run that i get a lot of 
    [unknown user]: installed
    Do I just need to revise my process and start from scratch? or at least just never actually join the domain and user other profiles? thats a convenience thing so its not a big deal, really.
    I have an image made in a similar way that works, but doesnt have quite all the updates/changes i wanted. It captured [at the time] fine and installs without issue
    Heres an overview of what I do [i am open to some revisions on this]
    -deploy windows 8 base install from MDT
    -join domain, login with service account [just makes getting to some things easier]
    -install office 2010 pro plus w/ sp2 [i do understand that these can be set as an MDT app but the install takes a while and i dont like waiting on it if i dont have to]
    -install windows updates [no WSUs server currently, on my future to-do list, not my decision right now and i do understand the benefits of having one]
    -connect to servers and install all network printers [we have so many that i dont want to wait on the drivers when we do a big roll out soon]
    -install oracle software [i can get it to automate in windows 7, not 8, so i dont want to manually deal with it post-install]
    -install adobe reader/java [i do understand that these can be set as an MDT app]
    -leave domain, reboot, login as local admin
    -clean domain profiles/registry guids
    -make some local gpoedits [we dont have 8.1 enterprise and just want the start screen locked down]
    -install our AV network agent
    -lite touch. 
    any advice is appreciated

  • Windows 8.1 Copyprofile Issue (SCCM 2012R2 MDT 2013)

    Hi,
    We're experiencing several issues during creation of our base Windows 8.1 image.
    Running SCCM 2012 R2 with MDT 2013 Integration.
    Admin user customizations (a couple of simple UI settings and a wallpaper) are done to the Windows 8.1 image in audit mode. The OS is then sysprepped and captured via SCCM capture media.
    We are using a standard MDT integrated task sequence for a zero touch deployment.
    We are adding copyprofile to unattend.xml in the relevant MDT settings package.
    Sequence completes without error and customizations appear in the image.
    However, desktop IE11 immediately crashes unless it's run as administrator. This can be fixed by disabling protected mode (not ideal)
    All Metro/Modern apps (including IE) are also initially broken. They immediately crash and drop you back to the desktop when you run them.
    After a reboot the modern/metro apps (apart from IE) seem to reinstall and function correctly.
    Has anyone else got copyprofile working correctly for 8.1 in a SCCM/MDT task sequence?
    thanks
    James

    Hi James,
    We were able to work around this issue in the following way using SCCM 2012 R2. I know this is not how the process is documented or has worked previously but it is what worked for us.
    1. Create an unattend.xml with the copy profile setting (and whatever other settings) enabled.
    2. On the image which will be captured run all of our regular steps to customize on the administrator profile (I always set administrator pw at this point to have blank pw, don't know if still required), copy that unattend.xml locally.
    3. Do not run a standard capture using SCCM capture ISO, instead manually run sysprep specifying the unattend.xml. I.e. sysprep /generalize /oobe /shutdown /unattend:C:\Unattend.xml .
    4. Boot to either the SCCM PXE or some other environment on that computer that has network access, and access to imagex.
    5. Run an imagex capture to a network location (in our case the C: was all that was needed).
    6. Import that WIM into SCCM as part of task sequence. Also added same unattend.xml used for sysprep into the task sequence to apply settings during first boot after image.
    7. Validated our start menu icons and layout are there on the image.
    Until the behaviour changes in Windows 8.1 or SCCM, then this should get you by. Little bit of extra work in the capture but we had positive, consistent results using this method.
    Thank you! This was driving me crazy! Now it works on the first try.
    Just a side note: You should not use ImageX with Windows 8.1. Create a new WinPE Bootmedia and use DISM! ImageX is outdated.

  • 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.

  • Since upgrade to MDT 2013, can't capture Windows 7 image.

    Hi fellas,
    I use Virtual Box to create a 32- and 64-bit reference Windows 7 VM, which I then capture using an MDT Sysprep & Capture TS.  This worked without a hitch using MDT 2012.
    I recently upgraded to MDT 2013.  Since then, after the VM syspreps and reboots, I get a boot manager error saying Windows failed to start.  Status: 0xc0000260.
    Not sure where to look for any logs.  What I've done so far:
    - Upgraded to latest version of Virtual Box (4.3.18)
    - Rebuilt both VMs from scratch.
    - Deleted and recreated the deployment share and Sysprep & Capture task sequences.
    Stumped for the time being, although I could always just boot to my Win PE disc and manually capture with imagex.  But c'mon.

    Thanks for your input, but this is indeed a configuration issue, and it makes sense.
    Vbox VMs are configured according to the guest OS installed on them.  For my Windows 7 x64 VM, it's configured of course to run as Windows 7 x64.  In the MDT 2012 environment, the Windows PE version
    was 3.0, which is based on Windows 7, and hence the VM could boot to it since it was configured for it.
    But MDT 2013 uses PE 5.0, based on 8.1.  The VM crashes or throws an error when trying to boot the PE 5.0 boot image.  I went into the VM's settings and changed the Guest OS to 8.1 x64, and it booted successfully to Windows PE and captured the
    image according to the Sysprep & Capture sequence.
    Sorry for the wild goose chase fellas.  This should've been the first thing I checked.

  • 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

  • Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

    I am having an issue with creating a master image with Windows 8.1 and MDT 2013.  
    I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
    except for one issue I have run into, which is successfully capturing this image as a .WIM.
    I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
    to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
    the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE 
    I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
    Any help would be greatly appreciated.

    I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
    test results.
    IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • MDT 2013 stalls during first boot into OS

    I just built a new MDT 2013 server (on 2012 R2) and am attempting to deploy Windows 7 from it via litetouch.  I've been working with MDT 2010 for several years so I am pretty familiar with how it works and just about everything is fine with 2013 except
    for one small issue.  When the sequence boots into Windows 7 for the first time, it just sits there at the desktop and nothing happens.  This happens every time and performs the same on virtual and physical machines.  All I have to do is reboot
    the machine and the task sequence will pick right up where it left of and finish everything correctly.
    I have found similar reports that seem to be resolved by adding pauses to either the ltibootstrap, litetouch, or ztiutility scripts to give the machine additional time to initialize, but none have worked for me.  The only seemingly relevant log entry
    comes from the BDD file.  The last entry is:
    <![LOG[RUN: regsvr32.exe /s "C:\Users\wdsbuild\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="17:47:46.000+000" date="03-25-2014" component="LiteTouch" context="" type="1"
    thread="" file="LiteTouch">
    <![LOG[FAILURE (Err): -2147024770  0x8007007E: CreateObject(Microsoft.BDD.Utility) -]LOG]!><time="17:47:46.000+000" date="03-25-2014" component="LiteTouch" context="" type="2" thread=""
    file="LiteTouch">
    I question the relevance of this entry because I don't actually have to manually register the dll to get it to work again.  Everything else in the BDD and SMSTS logs looks fine and don't appear to give any indication of what is going on.
    I have also attempted to add an additional restart to the task sequence immediately following the restart that is initiated after the OS has been laid down, but since the task sequence doesn't start after that first autologin, it doesn't execute.
    Thoughts?

    +1 on the drivers. I have rarely seen this, never able to reproduce in a consistent manner.
    Here is the process:
    * MDT places a hook within the unattend.xml file applied to the operating system. It calls the script LTIBootStrap.vbs. This happens in OOBE setup. If you did not sysprep or skiped OOBE setup this step may fail.
    * LTIBootStrap.vbs calls "Litetouch.wsf /Start" to install itself in the start/run after reboot into the full OS.
    IT *might* be possible that there is some other application hooked in to run at logon that is preventing MDT from running. Using autoruns.exe from sysinternals could help in debugging.
    Alternatively, you could set HIDESHELL=YES in your cs.ini file. When this is set, MDT will add it self in the registry as a "run" command rather than within the "startup" group in the shell.
    Keith Garner - keithga.wordpress.com

  • Mdt 2013 refresh wizard canceled as soon as I authenticate

    I've been after this for a week or so now. I'm trying to run a POST OS Installation task, something I've done many times before, but always in MDT 2010. I"m now trying to kick off MDT 2013 from Windows 7 x64, and I get as far as being prompted for credentials.
    As soon as I enter my credentials, MDT quits and cleans up, immediately. Literally 1 second later according to the BDD.log. Nothing unusual seems to be recorded in the logs.
    If I try to run it again without deleting the MININT folder, it usually succeeds. If I then cancel out of the Task sequence menu without choosing anything and try it again, it fails again. Is this some type of bug? I've googled extensively, can't find anything.
    I've removed all software that has been updated recently from the PC, no AV is installed, nothing that should be stepping on anything.
    I'm running from an elevated prompt, like so:
    \\Server01\Deployment01$\scripts\LiteTouch.vbs
    Bdd.log returns this:

    just to loop back here... I replied to Joe offline via E-Mail. the case is very weird:
    I think it may have to do with the EVENTSHARE being defined in the bootstrap.ini file, somehow that is forcing MDT to setup a new connection to
    \\Server\Events$  and the dialog prompting for credentials is causing problems.
    *Still* that shouldn’t case this code to return true:
    ' Was the wizard   cancelled? 
    If so, exit
    If UCase(oEnvironment.Item("SkipBDDWelcome"))
    <> "YES"
    and oEnvironment.Item("WizardComplete")
    <> "Y"
    then
    Cleanup
    oLogging.ReportFailure "Welcome wizard failed or was   cancelled",
    5212
    End
    if
    The logs *SHOW* that SkipBDDWelcome and WizardComplete are set properly:
    Property SKIPBDDWELCOME is now = NO            
    ZTIGather           
    12/18/2014   8:45:14 AM  0 (0x0000)
    Property WizardComplete is now = Y     
    Wizard  12/18/2014   8:45:15 AM 
    0 (0x0000)
    Might be some kind of weird race condition in the Litetouch.wsf code. The progress bar UI fluff is pretty complex.
    My recommendations would be to place EVENTSHARE into the cs.ini file rather than the bootstrap.ini file to see if that fixes things.
    Otherwise just commenting out the code above, I’m not 100% sure why it’s there to begin with.
    -k
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • MDT 2013, D: Wim not applying after update from MDT 2010 to 2013

    Updated MDT from MDT 2010 Update 1 to MDT 2012 Update 1, uninstalled WAIK, Installed MDT 2013, and then ADK, Upgraded all Deployment shares along the way, and now the extra drive (D:) Wim will not apply to Drive, i have tried two different ways to handle
    the said action, the first was using the Unattend.xml, adding the  DataImage Action, the other was using an Imagex command from the MDT task sequence. neither is applying the Wim, before the upgrade this worked. has any one else had this issue? 
    Thank you, 
    Dane Zittritsch
    Thinix Support Manager

    I moved from MDT 2010 to MDT 2013 and its just not working, i have tried a few different methods, the old way we used the
    Unattend.xml and placed a install order and that always worked, but now i am trying to use Imagex and its not applying the wim, when i get in the image the D:\ (Second Drive) is missing files.  Now here is the weird part, if i re-run the task sequence
    the D WIM is applied, but that's counter productive. i will apply my TS.xml information. 
    Ts.xml
    <?xml version="1.0"?>
       -<sequence description="A complete task sequence for deploying a client operating system" name="Standard Client Task Sequence" version="3.00"> -<globalVarList> <variable name="OSGUID" property="OSGUID">{52bb4035-96e5-46f3-9d17-3d2a363895c3}</variable>
          <variable name="DestinationDisk" property="DestinationDisk">0</variable>
          <variable name="DestinationPartition" property="DestinationPartition">2</variable>
         <variable name="DestinationOSVariable" property="DestinationOSVariable">OSDisk</variable>
         <variable name="DestinationOSRefresh" property="DestinationOSRefresh"/>
         <variable name="DestinationOSDriveLetter" property="DestinationOSDriveLetter"/>
         <variable name="DestinationOSInstallType" property="DestinationOSInstallType">ByDiskPartition</variable>
    </globalVarList>
    -<group description="Initialize the TS environment" name="Initialization" expand="true" continueOnError="false" disable="false">
    - <step description="" name="Gather local only" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly"
    property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action> </step> </group> -<group description="Test"
    name="Validation" expand="true" continueOnError="false" disable="false"> -<condition> -<operator type="or"> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">PHASE</variable> <variable
    name="Operator">equals</variable> <variable name="Value">VALIDATION</variable> </expression> </operator> </condition> -<step description="" name="Validate" continueOnError="false" disable="false" startIn="" successCodeList="0
    3010" type="BDD_Validate"> -<defaultVarList> <variable name="ImageSize" property="ImageSize">0</variable> <variable name="ImageProcessorSpeed" property="ImageProcessorSpeed">800</variable> <variable name="ImageMemory" property="ImageMemory">768</variable>
    <variable name="VerifyOS" property="VerifyOS">CLIENT</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIValidate.wsf"</action> </step> -<step description="" name="Check BIOS" continueOnError="false" disable="false"
    startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIBIOSCheck.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
    property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
    -<step description="" name="Next Phase" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> </group> -<group description="" name="State Capture" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable
    name="Variable">PHASE</variable> <variable name="Operator">equals</variable> <variable name="Value">STATECAPTURE</variable> </expression> </condition> -<step description="" name="Next Phase" continueOnError="false"
    disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
    property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
    </group> -<group description="" name="Preinstall" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">PHASE</variable>
    <variable name="Operator">equals</variable> <variable name="Value">PREINSTALL</variable> </expression> </condition> -<step description="" name="Gather local only" continueOnError="false" disable="false" startIn="" successCodeList="0
    3010" type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly" property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action>
    </step> -<group description="" name="New Computer only" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DeploymentType</variable>
    <variable name="Operator">equals</variable> <variable name="Value">NEWCOMPUTER</variable> </expression> </condition> -<step description="" name="Validate" continueOnError="false" disable="false" startIn="" successCodeList="0
    3010" type="BDD_Validate"> -<defaultVarList> <variable name="ImageSize" property="ImageSize">0</variable> <variable name="ImageProcessorSpeed" property="ImageProcessorSpeed">800</variable> <variable name="ImageMemory" property="ImageMemory">768</variable>
    <variable name="VerifyOS" property="VerifyOS">CLIENT</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIValidate.wsf"</action> </step> -<step description="" name="Format and Partition Disk" continueOnError="false"
    disable="true" successCodeList="0 3010" type="SMS_TaskSequence_PartitionDiskAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="OSDDiskIndex" property="DiskIndex">0</variable> <variable name="DONotCreateExtraPartition"
    property="DONotCreateExtraPartition"/> <variable name="OSDPartitions0Type" property="Partitions0Type">Primary</variable> <variable name="OSDPartitions0FileSystem" property="Partitions0FileSystem">NTFS</variable> <variable name="OSDPartitions0Bootable"
    property="Partitions0Bootable">True</variable> <variable name="OSDPartitions0QuickFormat" property="Partitions0QuickFormat">True</variable> <variable name="OSDPartitions0VolumeName" property="Partitions0VolumeName">OSDisk</variable>
    <variable name="OSDPartitions0Size" property="Partitions0Size">100</variable> <variable name="OSDPartitions0SizeUnits" property="Partitions0SizeUnits">%</variable> <variable name="OSDPartitions0VolumeLetterVariable" property="Partitions0VolumeLetterVariable">OSDisk</variable>
    <variable name="OSDPartitions" property="Partitions">1</variable> <variable name="OSDPartitionStyle" property="PartitionStyle">MBR</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIDiskpart.wsf"</action>
    </step> -<step description="You can change the size of the partition(s) in the \Scripts\WinRE\DiskConfig.txt file. Make sure your partition is large enough to hold the recovery image if you install alot of software. Current configuration is 160GB
    for recovery, 60 for OS, 10 for scratch" name="Format and Partition Disk [Custom]" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable
    name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010 BETA\Configure-HDD.cmd"</action> </step> -<step
    description="" name="Copy scripts" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> </group> -<step description="" name="Configure" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIConfigure.wsf"</action> -<defaultVarList>
    <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
    <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Inject Drivers" continueOnError="false" disable="false" successCodeList="0 3010" type="BDD_InjectDrivers"
    runIn="WinPEandFullOS"> -<defaultVarList> <variable name="DriverSelectionProfile" property="DriverSelectionProfile">Dell OptiPlex 790</variable> <variable name="DriverInjectionMode" property="DriverInjectionMode">ALL</variable>
    </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"</action> </step> -<step description="" name="Apply Patches" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_InstallUpdatesOffline">
    <action>cscript.exe "%SCRIPTROOT%\ZTIPatches.wsf"</action> -<defaultVarList> <variable name="PackageSelectionProfile" property="PackageSelectionProfile">All Packages</variable> </defaultVarList> </step> -<step description=""
    name="Next Phase" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> </group> -<group description="" name="Install" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable
    name="Variable">PHASE</variable> <variable name="Operator">equals</variable> <variable name="Value">INSTALL</variable> </expression> </condition> -<step description="" name="[Custom] Apply D Wim " continueOnError="false"
    disable="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\DWim.exe"</action> </step> -<step description="" name="Install Operating System" continueOnError="false" disable="false" successCodeList="0 3010" type="BDD_InstallOS" runIn="WinPEandFullOS">
    -<defaultVarList> <variable name="OSGUID" property="OSGUID">{52bb4035-96e5-46f3-9d17-3d2a363895c3}</variable> <variable name="DestinationDisk" property="DestinationDisk">0</variable> <variable name="DestinationPartition" property="DestinationPartition">2</variable>
    <variable name="DestinationOSDriveLetter" property="DestinationOSDriveLetter"/> <variable name="DestinationOSVariable" property="DestinationOSVariable">OSDisk</variable> <variable name="DestinationOSRefresh" property="DestinationOSRefresh"/>
    <variable name="DestinationOSInstallType" property="DestinationOSInstallType">ByDiskPartition</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\LTIApply.wsf"</action> </step> -<step description="" name="Restart
    computer" continueOnError="false" disable="false" successCodeList="0 3010" type="SMS_TaskSequence_RebootAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="SMSRebootMessage" property="Message"/> <variable name="SMSRebootTimeout"
    property="MessageTimeout">60</variable> <variable name="SMSRebootTarget" property="Target"/> </defaultVarList> <action>smsboot.exe /target:WinPE</action> </step> -<step description="" name="Next Phase" continueOnError="false"
    disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
    property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
    </group> -<group description="" name="Postinstall" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">PHASE</variable>
    <variable name="Operator">equals</variable> <variable name="Value">POSTINSTALL</variable> </expression> </condition> -<step description="" name="Copy Scripts" continueOnError="false" disable="true" startIn="" successCodeList="0
    3010"> <action>cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/>
    <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Configure"
    continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIConfigure.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable
    name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> -<step description="Applies the D: wim to System " name="Apply Scratch Drive" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS">
    -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable
    name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"\\thinix-dev1\navyImage$\Tools\x86\imagex.exe" /apply
    "\\thinix-dev1\navyImage$\Operating Systems\navycnic-gen_20131226100000\navycnic-gen_20131226100000_ddrive.wim" 1 D:\</action> </step> -<step description="" name="Inject Drivers" continueOnError="false" disable="false" startIn="" successCodeList="0
    3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIdrivers.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/>
    <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<group description="" name="Custom
    Tasks" expand="true" continueOnError="false" disable="false"> -<step description="Makes sure there is no Boot Config files on C drive and changes them to R drive:" name="Recovery Partition" continueOnError="false" disable="false" startIn="" successCodeList="0
    3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
    property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\Re-assign
    DriveLetter.cmd"</action> </step> -<step description="" name="[Custom] Apply D Wim " continueOnError="false" disable="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList>
    <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\DWim.exe"</action> </step> -<step description=""
    name="[Custom] TDRBCD" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable
    name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
    <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\TDRBCD.exe"</action> </step> -<step description="" name="[Custom] Apply D Wim " continueOnError="false"
    disable="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\DWim.exe"</action> </step> </group> -<step description="" name="Next Phase" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
    "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Set Phase" continueOnError="false" disable="false" successCodeList="0
    3010" type="SMS_TaskSequence_SetVariableAction"> -<defaultVarList> <variable name="VariableName" property="VariableName">PHASE</variable> <variable name="VariableValue" property="VariableValue">STATERESTORE</variable> </defaultVarList>
    <action>cscript.exe "%SCRIPTROOT%\ZTISetVariable.wsf"</action> </step> </group> -<group description="" name="State Restore" expand="false" continueOnError="false" disable="true"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression">
    <variable name="Variable">PHASE</variable> <variable name="Operator">equals</variable> <variable name="Value">STATERESTORE</variable> </expression> </condition> -<step description="" name="Gather local only"
    continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly" property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/>
    </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action> </step> -<step description="" name="Post-Apply Cleanup" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
    "%SCRIPTROOT%\LTIApply.wsf" /post</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Recover From Domain " continueOnError="false" disable="false"
    successCodeList="0 3010" type="BDD_RecoverDomainJoin" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="DomainErrorRecovery" property="DomainErrorRecovery">Auto</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIDomainJoin.wsf"
    </action> </step> -<step description="" name="Tattoo" continueOnError="true" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTITatoo.wsf"</action> -<defaultVarList> <variable name="RunAsUser"
    property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile"
    property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Opt In to CEIP and WER" continueOnError="true" disable="true" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIOptIn.wsf"
    /CEIP:YES /WER:YES</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Windows Update (Pre-Application Installation)" continueOnError="true"
    disable="true" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
    property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
    -<step description="" name="Install Applications" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_InstallApplication"> <action>cscript.exe "%SCRIPTROOT%\ZTIApplications.wsf"</action> -<defaultVarList>
    <variable name="ApplicationGUID" property="ApplicationGUID"/> <variable name="ApplicationSuccessCodes" property="ApplicationSuccessCodes">0 3010</variable> </defaultVarList> </step> -<step description="" name="Windows Update
    (Post-Application Installation)" continueOnError="true" disable="true" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> <group description="" name="Custom Tasks" expand="true" continueOnError="false" disable="false"/> -<step description="" name="Enable BitLocker" continueOnError="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_EnableBitLockerAction">
    <action>cscript.exe "%SCRIPTROOT%\ZTIBde.wsf"</action> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">BdeInstallSuppress</variable> <variable name="Operator">notEquals</variable>
    <variable name="Value">YES</variable> </expression> </condition> -<defaultVarList> <variable name="OSDBitLockerTargetDrive" property="BdeTargetDriveLetter"/> <variable name="OSDBitLockerMode" property="BdeInstall">TPM</variable>
    <variable name="OSDBitLockerStartupKeyDrive" property="BdeKeyLocation"/> <variable name="OSDBitLockerCreateRecoveryPassword" property="BdeRecoveryPassword">AD</variable> <variable name="OSDBitLockerWaitForEncryption" property="WaitForEncryption">false</variable>
    </defaultVarList> </step> -<step description="" name="Restore User State" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIUserState.wsf" /restore</action> -<defaultVarList>
    <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
    <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Restore Groups" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
    "%SCRIPTROOT%\ZTIGroups.wsf" /restore</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable
    name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Apply Local GPO Package"
    continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIApplyGPOPack.wsf"</action> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable
    name="Variable">ApplyGPOPack</variable> <variable name="Operator">notEquals</variable> <variable name="Value">NO</variable> </expression> </condition> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> -<group description="" name="Imaging" expand="false" continueOnError="false" disable="false"> <action/> -<group description="" name="Prepare Only" expand="false" continueOnError="false" disable="false">
    -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DoCapture</variable> <variable name="Operator">equals</variable> <variable name="Value">PREPARE</variable>
    </expression> </condition> -<step description="" name="Copy Sysprep files" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTISysprep.wsf"</action> -<defaultVarList>
    <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
    <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> </group> -<group description="" name="Sysprep Only" expand="false" continueOnError="false" disable="false"> -<condition>
    -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DoCapture</variable> <variable name="Operator">equals</variable> <variable name="Value">SYSPREP</variable> </expression>
    </condition> -<step description="" name="Add mass storage drivers to sysprep.inf for XP and 2003" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"</action>
    -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
    <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Execute Sysprep" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
    "%SCRIPTROOT%\LTISysprep.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> </group> -<group description="" name="Capture Image" expand="false" continueOnError="false"
    disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DoCapture</variable> <variable name="Operator">equals</variable> <variable name="Value">YES</variable>
    </expression> </condition> -<step description="" name="Apply Windows PE" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE /STAGE</action> -<defaultVarList>
    <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
    <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Add mass storage drivers to sysprep.inf for XP and 2003" continueOnError="false" disable="false" startIn=""
    successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/>
    <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Execute
    Sysprep" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTISysprep.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
    <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
    </defaultVarList> </step> -<step description="" name="Apply Windows PE (BCD)" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%_SMSTSMDataPath%\Scripts\LTIApply.wsf" /PE /BCD</action>
    -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">ImageBuild</variable> <variable name="Operator">greaterEqual</variable> <variable name="Value">6</variable>
    </expression> </condition> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
    property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Restart computer" continueOnError="false" disable="false"
    successCodeList="0 3010" type="SMS_TaskSequence_RebootAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="Message" property="Message"/> <variable name="MessageTimeout" property="MessageTimeout">60</variable> <variable
    name="Target" property="Target"/> </defaultVarList> <action>smsboot.exe /target:WinPE</action> </step> -<step description="" name="Gather local only" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"
    type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly" property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action>
    </step> -<step description="" name="Create WIM" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIBackup.wsf"</action> -<defaultVarList> <variable name="RunAsUser"
    property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile"
    property="LoadProfile">false</variable> </defaultVarList> </step> </group> </group> </group> </sequence>

Maybe you are looking for

  • Frozen help

    I dropped my blackberry z10 the top left corner cracked a lil but since my pho e has been frozen, stuck on screen. It won't let me like slide to open like my screen isn't working properly. I've tried holdingbutton for 10 sec and taking my battery out

  • Workflow Release Strategy

    Hello Experts; I have a requirement for PO release strategy for a dept of 20 PM's and each PM have to release his own PO, currently the buyer drills down to the order or Network (PO account assignment) to see the person resp then send him the PO # fo

  • I need to swap devices and phone numbers!

         So here is the deal... My plan has four lines (my mother, brother, sister and I). My sister used my upgrade and renewed my contract in December (extending my contract 2 years), however I planned on dropping my phone line. So I need to swap my de

  • Downloading previously bought apps onto a new computer - Not working

    I just bought an iMac and I expected to be able to re download apps I had already bought in the App Store. When I open the App Store Application I see the list of all the apps I have got through the app store and some of them show as being available

  • Displaying week numbers in a calender

    Hi all, I read a thread from 1999 which asks about showing week numbers in a calender. A reply said that this will be added to later versions of HTML_DB. Does anybody know if this feature has been added to ver 2.0 ? If so, how is it achieved ? Many t