Skipping Custom Wizard in MDT-LiteTouch Deployment

I have one deployment share in which I generate media from to create a gold image, sysprep and capture, and than a deployment where the gold image and other things are performed. As part of the deployment of the Gold Image, I want to incorporate a custom
wizard to prompt if the user wants to wipe the hard drive as I need to accomplish something greater than the included reformat once. It needs to obviously run before the format and partitioning occurs, and I only want it to appear in one of my three media.
I have created a custom XML file, made the entry DeployWiz_Definition_ENU.xml, and can successfully acknowledged the variable ("DoSanitize") value where I need to in my task sequence.... however, I am unable to skip the custom wizard the way
I am with other pre-defined wizards. I have made the condition to skip it and I have placed the condition in my customsettings.ini.
How can I skip a custom wizard if the variable is set in customsettings.ini?
Entry added to the customsettings.ini for the media I want to skip
======================================
SkipSanitize=YES
======================================
Entry added to DeployWiz_Definition_ENU.xml
======================================
<Pane id="SanitizeHardDrive" reference="DeployWiz_SanitizeDrive.xml">
<Condition><![CDATA[UCASE(Property("SkipSanitize"))<>"YES"]]></Condition>
</Pane>
======================================
Contents of DeployWiz_SanitizeDrive.xml
======================================
<Wizard>
<Global>
</Global>
<Pane id="SanitizeHardDrive" title="Sanitize Hard Drive">
<Body><![CDATA[
<H1>Do you want to sanitize the Hard Drive?</H1>
<table>
<tr>
<td>
<input type=radio name="DoSanitize" id="CaptureRadio1" Value="YES">
</td>
<td>
<Label class="Larger" for=CaptureRadio1 language=vbscript >Sanitize the Hard Drive.</Label>
</td>
</tr>
<tr>
<td>
<input type=radio name="DoSanitize" id="CaptureRadio2" Value="NO" checked>
</td>
<td>
<Label class="Larger" for=CaptureRadio1 language=vbscript >Do not sanitize the Hard Drive.</Label>
</td>
</tr>
</table>]]></Body>
<Condition><![CDATA[UCASE(Property("SkipSanitize"))<>"YES" or UCase(Property("DeploymentType"))<>"CAPTURE"]]></Condition>
</Pane>
</Wizard>
======================================
The only end user facing media will have the Sanitize Drive option available so it is not show stopper, but more of an OCD thing for me.

Thanks for your response and I see that now. I did a bit of a workaround for this and moved all applications to a temp folder in Deployment Workbench, then moved them back out in the proper order. That appeared to fix the order problem.
Yet, my original problem still stands - The applications that I have added within the last 24 hours are not showing up in Deployment Wizard. I have even tried deleting them and recreating them but it would appear that any new applications are not being
added. I do see them within the Applications.xml AND the ApplicationGroups.xml. I have created them in a normal method as I have done many times before and there is not really anything unique about the apps (the are apps with source files).
How can this be?

Similar Messages

MDT 2012 - Litetouch deploy windows 8 with different administrator account

I have created and captured a custom image of Windows 8 using MDT2012 update 1 and Windows ADK (without SCCM). In the image, I have set an account called DeployUser, with password XXX, adding it to the Administrators group, and I have disabled the User
Account Control.
I did this because the Administrator account is renamed from GPO and the password is changed every 30 days (for security reasons, the password is not disclosed to any IT support).
Next, I created a TS to deploy this image, adding the installation of some software.
In the Unattend.xml, I also added DeployUser to perform the autologon.
After the first logon with DeployUser, the TS stops and does not return any error message.
If I manually run C: \ ProgramData \ Microsoft \ Windows \ Start Menu \ Programs \ Start-up \ LiteTouch.lnk nothing happens, however, if I run it with "Run as Administrator", the TS continues normally.
Somebody who knows a solution for this?

I believe MDT LiteTouch deployments only recognize the Administrator account name for processing task sequences.
Are you joining the domain during an MDT Litetouch deployment? If so, you may want to delay joining to a domain or GPO processing. Take a look at these recommendations:
Domain Policies that break MDT 2010
It may also be possible to disable GPO processing until the end of the taks sequence via a reghack or disabling a service. Take a look at this:
How to Disable/Enable Group Policy
BTW, the task sequence engine in ConfigMgr prevents GPO processing during an OSD.
V/R, Darrick West - Senior Systems Engineer, ConfigMgr: OSD

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

I'm attempting to deploy an image that I have recently captured with MDT. I was able to capture the image without any problems and after capturing, it booted up properly. But now when I go to deploy the image using a Standard Task Sequence it
errors out. It does boot into WinPE and gets to the installing operating system portion then spits out the following 8 errors:
(5624):2: Run ImageX: /apply "\\PDC31089\DeploymentShare$\Operating Systems\Win7_BUP_1-31-14\Win7_BUP_1-31-14.wim" 1 C:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015F8; Source: Unknown)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005After I receive the error messages if I attempt to restart the computer and allow it to boot up it just comes up with:"An operating system wasn't found. Try disconnecting any drives that don't contain an operating system"
I have tried the following to resolve this issue:
Create a new deployment share with only network drivers added and the one .WIM that was captured with MDT as well as one Task sequence.
Update to MDT 2013
Update Deployment share and completely regenerate Boot images
Tried starting deployment from within Windows by mapping the drive and executing litetouch.vbs
Also tried starting deployment using USB boot disk
I'm running out of ideas and seem to keep getting the same 8 error messages. It's very aggravating and am hoping that someone can point me in the right direction.
I've included some log files on Skydrive at: https://skydrive.live.com/redir?resid=6375A8F9E8089918%21105

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

MDT LITETOUCH Win 7 Deployment

Hey Yall,
My windows 7 deployment via MDT Litetouch sometimes tries to login as domain\correctusername which it should be local\correctusername while going through the task sequence. I have to manually login during some installations to the local admin so the task
sequence will keep rolling. I believe this has something to do with it is pulling GROUP POLICY after one of the reboots and it is interfering with my deployment. Any help will be appreciated. Thanks

MDT needs to login as a local administrator in order to complete installation.
By default MDT will setup the AutoAdminLogon to use the local administrator account.
If you disable, or join a domain that disables the local administrator account through group policy, that will break MDT installation.
The recommended solution is to create a OU that does *not* have any group policies that break AutoAdminLogon to the local administrator account, and join to that OU first. ... THEN... move machines some time later from the first "install" OU to the full
OU.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Dell Laptops E7440 & E7240 - Issues with connecting to MDT 2012 deployment share

Hi,
Good afternoon.Need help on this please
-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.
-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.
-Laptops and desktops are on same network .
-For OS deployments we have MDT 2012.
-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible
cause:invalid credentials. Retry : Try again to connect to the deployment share.’
-Have injected all possible network & storage drivers mentioned by Dell & Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.
-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address
in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.
Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.
The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.
-Have also tried combination of network & storage drivers from Dell website (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.
-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .
-This very litetouch iso connects to MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause
this happens even with brand new shipped laptops with your inbuild win 7 OS.
-Have tried all options suggested on internet,tested all the drivers suggested but no luck.
-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc individually as well as in combinations but the issue persists.
-If you google many express similar issues with these laptop models.
Though I used the drivers suggested by various bloggers,nothing worked for me.
Any help on this is appreciated.Thanks in advance.

Hi,
I have several E6420, O3010 and since a week also some E7440 and E7240 on site.
I never had issues using the current Dell PE package for MDT.
At the moment my PE contains only the drivers from the Dell PE 3.0 package (WinPE3.0-Drivers-A13-D67JC)
and all my systems mentioned abobe have no issues connecting to the deployment share.
(btw: I have also some older E6400, E6410 and O390 I do no longer support, they
are supported by the pack Dell-WinPE-Drivers-A05.CAB according
to the Dell site, but I just started a deplymenst on a E6410 and is is also workign with just the latest PE pack)
I'd
suggest you start over with your deplyoment share using at least MDT2012 Update 1.
Create a folder "PE" under "Out-of-Box Drivers" and extract latest Dell PE pack and import he drivers there
Create a selection profile e.g. "PE Drivers" and include just the "PE" folder created above
When configuring the Windows PE settings of your deployment share select "PE
Drivers" selection profile for the driver injection in the "Drivers and Patches" to keep the PE image free of not needed drives.

Litetouch deployment failed 0x80004005

can not deploy win7 with mdt 2012.
FAILURE ( 5627 ): -1073731515 0xC0000135: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB: Source: Unknown)
The execution of the group (Install) has failed and the execution has been aborted.
Operation aborted (Error: 80004004: Source: Windows)
Failed to run the last action: Install Operati ngSystem. Execution of task sequence failed:
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task swquence. Code 0x80004005
I keep getting this error message and not sure what it could be. Any idea????

The log is very long. Here is the first part of it.
<![LOG[Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property Debug is now = FALSE]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-N42LK45\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch"
context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-N42LK45\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-N42LK45\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="14:34:23.000+000" date="08-16-2013" component="LiteTouch"
context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-N42LK45\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-N42LK45\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS TargetDisk: \\MININT-N42LK45\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[GetPartitions: 2]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-N42LK45\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch"
context="" type="1" thread="" file="LiteTouch">
<![LOG[Target Partition not big enough: \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-N42LK45\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-N42LK45\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch"
context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Drive: D:]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found FirstPossibleSystemDrive: D:]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property SMSTSLocalDataDrive is now = D:]LOG]!><time="14:34:24.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to get Current ID.]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE or WinRE.]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentMethod is now = UNC]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = X:\Deploy]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = X:]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = PREINSTALL]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentType is now = NEWCOMPUTER]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = PREINSTALL]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property inifile is now = Bootstrap.ini]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Object Initialization -------------------------]LOG]!><time="14:34:27.000+000" date="08-16-2013" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Initialization ------------

Issue: MDT Litetouch is automatically making my drives GPT

I know GPT is better but I do not need MDT Litetouch automatically formatting my drive as it due to my enterprise encryption software does not support GPT, only MBR which is the old standard. If someone could please point me into the correct direction
of changing this in MDT Deployment Workbench would be greatly appreciated as I am having problems finding a solution on the Google.

I am using the USB method. Which I have been enable UEFI in bios to boot to it ( which if there is another way that would be a great suggestion.) Is having my image on USB what is causing GPT?

Litetouch deployment failed, Return Code = -2147023504

I suddenly started getting this error on all my task sequences. I created a new vanilla sequence and got the error on it as well. It doesn't matter if I select a x86 image task or x64. This is across multiple pieces of hardware as well. Please Help!
<![LOG[LTI beginning deployment]LOG]!><time="11:01:31.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Event 41016 sent: LTI beginning deployment]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: "X:\Deploy\Tools\X86\TsmBootstrap.exe" /env:SAStart]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[Property LTIDirty is now = TRUE]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Command completed, return code = -2147023504]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147023504 0x80070570]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147023504 0x80070570]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

I found the issue with this. Apparently the computers I was running these sequences on had previous deployments run and interrupted on them. Even though the deployment wizard wasn't flagging them as "dirty" clearly there was something hanging around
on the HD that was causing issues. I used diskpart to run a quick format on the OS volume and all is good.
Maybe this will help someone googleing in the future.

Custom Wizards (using Wizard Framework)?

Is there a good resource out there that describes how one might go about creating a custom wizard (I suppose using SAP's Wizard Framework) to be used during creation of new iViews (of a particular portal archive)? I've been looking around, but haven't found much on the topic. I have looked at the URL iView code (which implements this framwork API), and it appears somewhat involved.
Thanks,
John Schimmels

Hi John,
you know the API doc? If not - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/ep 6.0 sp2 wizard framework api
I don't remember to have seen anything in addtion
Hope it helps
Detlev

Custom Wizard in Oracle RPAS

Hi,
I am newb here. I did some research but i could not find answer for my question: How to build custom wizard in configuration tool in RPAS. The only information I found are placed in configuration guide, but it is limited just to list of icons in configuration tool.
Thanks for any info

How about starting with the documentation...
http://www.oracle.com/pls/db102/search?remark=quick_search&word=user+defined+datatypes&tab_id=&format=ranked

Uninstall previous version with Adobe Customized Wizard

Good day everyone. I am just beginning to use Adobe Customized wizard 9 to be used with SCCM (newer version of SMS). I have already extracted the exe to get to the msi file, but looking at the wizard, these options are grayed out and cannot be checked off. Actually the option to remove previous versions of Acrobat is checked (which I need it unchecked) and remove previous versions of Reader is unchecked. Any idea of the work around? We currently have in our environment versions 6-9 and we want everyone to be upgraded to 9.2. Also will this Customized wizard corrupt or change any settings for those that have both ReEader and Writer? Any help or info greatly appreciated. Thanks

You may want to try the following.
Remove all traces of Reader (not only the program) from your system using the Windows Installer Cleanup Utility. This is no longer supported by Microsoft because it can produce problems with Win 7, but you can still download it from from places like
http://majorgeeks.com/download.php?det=4459
Then, if you want to install Reader, download its installer from
http://get.adobe.com/reader/enterprise/
and perform a clean install.

MDT image deployment fails after adding applications

I've been trying to use MDT (ie deployment workbench 6.2.5019.0) to build and deploy images for quite some time now, and I am having a lot of difficulty deploying images to target computers. I've successfully built a reference image in a VM with all
the Win7 updates. I can deploy that image to HP z820 workstations while injecting drivers. Then I've tried two ways of adding applications, capturing that image and then re-deploying it to other target machines.
First, I run a standard client task sequence that will deploy and capture an image to a target machine. I put in a suspend command in the task sequence. I can then add applications and then restart the task sequence. If I don't add applications,
and I just let the task sequence do it's magic, inject drivers, add any remaining Windows updates, and then just resume, MDT will capture the image. I can then add it to my deployment share and then deploy it back to my target machine that it came from
or any other similar target. On the other hand, if I add all my applications during the suspend, MDT will capture the image, but subsequent deployments of the image will always fail on the target machine during Windows setup.
Second, I can deploy the reference image to a target, let the sequence finish, add the apps, then run a sysprep and capture task sequence. I finally got that to work. I have an image with apps that I can deploy. However, I go to a target
machine that image was deployed to, I added for example Office and Winzip. Then I run the same sysprep and capture sequence, capture the image, and when I deploy that image back, it hangs while setup is installing devices.
Why am I having so much trouble just adding applications to an image that deployed perfectly fine before, but once I add apps, I can no longer use the same task sequences to capture and deploy? These same task sequences will capture and deploy the
image without the apps, but not with the apps. I don't get it.
So, what's so special about adding applications, and also can anyone give me a good reference for troubleshooting deployment issues where sysprep and setup fail for whatever reason?

Hmmm... Applications should not cause hangs when installing drivers. In fact NOTHING should cause a hang like that... except for a bad driver. Go back and go through you driver manifest with a fine tooth comb and find the bad driver. That may include removing
all of your 3rd party drivers.
Keith Garner - keithga.wordpress.com

Has anyone added a custom wizard pane in MDT 2013?

I'm trying to add a couple of panes I created for 2012 and they don't seem to be showing up. At first I tried using the MDT Wizard Editor, but it apparently doesn't support 2013 yet. I also tried to hand edit the whole thing and that doesn't
seem to be working either.
Has anyone done this successfully? If so, could you provide some hints or walkthroughs on what might have changed in MDT 2013?

Yes, I *think* I've done all of that. I'm really just exporting work that I did to my MDT 2012 environment. It just never sees or displays my added XML files. If everything is the same between 2012 and 2013, then I'll go back to tearing
my hair out. I was hoping there was something different. Here's an example of what I have:
DeployWiz_Definition_ENU.xml
<Pane id="Partition_Size" reference="DeployWiz_Partition_Size.xml">
<Condition><![CDATA[UCASE(Property("SkipTaskSequence"))<>"YES" ]]></Condition>
</Pane>
DeployWiz_Partition_Size.xml
<Wizard>
<Global>
</Global>
<Pane id="Partition_Size" title="Partition Size">
<Condition><![CDATA[UCASE(Property("SkipTaskSequence"))<>"YES" ]]></Condition>
<Body><![CDATA[<H1>Custom Options</H1>
<p>Choose partition size for the OS disk:</p>
<table>
<tr valign=top>
<td width=100>
<img src="DeployWiz_PS.png">
</td>
<td width="100%">
<p><span class="Larger">Partition size (in GB)</span>
<input type=text id=OSDPARTITIONS0SIZE name=OSDPARTITIONS0SIZE size=2 ></p>
<p>*Note: To use 100% of the drive, choose a size larger than the disk (ie, 999GB)</p>
</td>
</tr>
</table>]]></Body>
</Pane>
</Wizard>

Deploy windows8 with custom partition using MDT 2012 update 1

Hi,
I am deploying windows 8 using MDT 2012 update 1 on SCCM 2012. I want C drive (to be quick format using task sequence) and D drive (remains same) on new system. While using diskpart , my D drive always get format . Can anyone suggest the steps.
Regards
Manish

Hi,
You could try steps in the following blog.
http://arnavsharma.net/4/post/2014/02/mdtformatting-only-c-drive-during-upgrade.html
(Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
Best Regards,
Joyce
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 2012 deploy OS from USB external drive failed - need to unplug and plug it once again

We are using MDT 2012 and deploying Windows 7 using media (USB external hard drive). We can successfully deploy Windows 7 32 bit using this method but there is a problem with deploying Windows 7 64bit. This problem appears only on HP EliteBook 840. We can
boot into WinPE 64 bit and can start proper task sequence, all image is applied then after restart, before logon screen appears there is an error saying that cannot find litetouch.vbs script. After clicking ok, I can logon to Windows and there is no usb external
drive recognized. But when I unplug and plug usb drive once again it is recognized by Windows and can be used. I can see that Windows install some drivers just after plug it again
I checked BIOS looking for some USB power options - there is no such settings. And 32 bit deployment works ok. So this is not a case. Looks for me like a problem with proper usb drivers for 64 bit. I download all drivers from HP website (driver pack and
drivers only for USB 3.0). We are using make and model matching in MDT - works ok for all the rest hardware models. Any idea how to troubleshoot it?

Not sure what's going on here. Is this a USB "Flash" drive or a USB "Hard Drive". There *Is* a distinction.
I *thought* that MDT would copy itself to the c:\minint\scripts folder to continue installation.
Next time, when you see this error, Press Shift-F10 to get into a cmd.exe prompt. Can you find litetouch.vbs on any of the drives? Does the USB Drive appear?
IF in fact, the USB Drive is not appearing after the 1st reboot, then you have a problem. Why did the USB 3.0 driver not install. Check the Driver Installation Logs to verify.
Keith Garner - keithga.wordpress.com

Skipping Custom Wizard in MDT-LiteTouch Deployment

Similar Messages

Maybe you are looking for