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

Similar Messages

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?

Adding Dot Net 4 msu to Win 7 deployment

Immediately after win 7 deploys, I have an application I wrote in dot net that needs to run (it will handle installing all the required software for that machine). It requires .Net 4
So I downloaded dotNetFx40_Full_x86_x64.exe and expanded the files. Inside there are a bunch of .MSU files so I assume I can add these into the OS deployment by attaching them to the unttend.xml file.
I imported the MSU files into the Workbench Packages folder. The source files are on some random share and now there are .cab files in the deployment share under packages.
From the OS deployment task sequence I chose to edit the xml in the WSIM. I choose insert package and selected the 6.1 64bit .cab file. It shows up under updates in the answer file list. I notice that the action is Install and the Path
is f:\OSDeployment\Packages\Update\.....
When the OS deployment runs, it fails. When I removed this package, it works again. The errors are cryptic at best but I THINK it's saying it can't find the files.
1. Could that be becuase the f:\.... path variable is junk during deployment? f doesn't exist so maybe I need to replace that with a UNC path?
2. The source files I extracted at the beginning of this process don't look like they were all moved to the packages folder... is that right? Should they be in a specific place?
3. ?

It's not really a task sequence line as much as adding an application in the deployment workbench. There is always a "install applications" line in the default task sequence but generally you don't actually have anything to install.
Frankly it's better just to have .Net framework loaded as part of the image (fat image where the 'fat' are MS core components like this rather than something really ugly like MS Office)

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?

MDT 2012U1 / Windows 8 deployment - impossible to add a role when deploying windows with language pack

Hello,
I am having a problem deploying Windows 8 with language packs and adding at the same time a role/feature (netfx3).
What I have done is creating a Standard Client Task Sequence. In the task sequence I have added, in the State Restore phase, the step Install Roles and Features (where only .Net Framework 3.5 is selected). I have configured nothing else !
If I use this task sequence, everything is ok; Windows 8 is well deployed and NetFx3 feature is installed.
Now, if I add one or more language packs in the MDT console and select them when using the previously created task sequence, the deployment fails with one error : ERROR - NetFx3 role processing with DISM.exe failed, rc = -2146498529.
The language packs are well installed but as the error message says, NetFx3 is not installed.
In the ZTIOSRole.log I can find this :
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1"
thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoles.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoleServices.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NetFx3]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41003 sent: ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread=""
file="ZTIOSRole">
<![LOG[Already connected to server HPZ820 as that is where this script is running from.]LOG]!><time="12:55:05.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64\sources\sxs]LOG]!><time="12:55:05.000+000" date="10-24-2012" component="ZTIOSRole" context=""
type="1" thread="" file="ZTIOSRole">
<![LOG[About to execute command: cmd.exe /c C:\windows\system32\DISM.exe /Online /Enable-Feature /FeatureName:"NetFx3" /Source:"C:\MININT\sources\X64" /LimitAccess /All /NoRestart /logpath:C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_Dism.log >> C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_DismConsole.log]LOG]!><time="12:55:24.000+000"
date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - NetFx3 role processing with DISM.exe failed, rc = -2146498529]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = NETFX3]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Role processing complete.]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="12:55:58.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
If I take the same log file from a machine where I have used the same task sequence but without deploying language packs, I can find that :
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1"
thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoles.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoleServices.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ NetFx3]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41003 sent: ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread=""
file="ZTIOSRole">
<![LOG[Already connected to server HPZ820 as that is where this script is running from.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64\sources\sxs]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context=""
type="1" thread="" file="ZTIOSRole">
<![LOG[About to execute command: cmd.exe /c C:\windows\system32\DISM.exe /Online /Enable-Feature /FeatureName:"NetFx3" /Source:"C:\MININT\sources\X64" /LimitAccess /All /NoRestart /logpath:C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_Dism.log >> C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_DismConsole.log]LOG]!><time="14:00:20.000+000"
date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[NetFx3 role processing succeeded, rc = 0]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = NETFX3]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Role processing complete.]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="14:03:51.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
As you can see, in both logfile, the source are copied from the same folder.
Does anyone have an idea ? what am I missing ?
I have easily reproduced the problem on another computer (installing ADK/MDT, installing OS and creating task sequence).
Thanks in advance for your help.
Marc.

Hello,
Workaround:
1. copy stock sxs folder to local disk (e.g c:\sxs)
2. make a direct internet connection (don't use proxy!)
3. open admin command prompt and type: DISM.exe /online /enable-feature /featurename:NetFX3 /All /Source:c:\sxs
4. after the successful install find the c:\windows\winsxs folder and sort by date
5. copy new folders (that are equal to current date) to deployment share's sxs folder (overwrite)
And now, try standard MDT install (create "Install Role And Feature" step in the Task Sequence, enable .NET install).

MDT 2012 Update 1 - Deployment - Auto Login won't Disable

Hello,
I am using MDT 2012 Update 1 with an almost vanilla Windows 8.1 and Windows 7 test box. I can deploy both images fine and get a success on my summary but both machines continue to auto login to the Administrator account. To my understanding, the Auto Login
should be shutoff via the LTIcleanup script. When I double check the script for the reg keys that are added/deleted I can confirm that this is happening but the images still continue to auto login to the admin account.
Anyone have any ideas?

Thought I would let those who are interested know. After speaking with Microsoft Premier Support they determined that you must have a password on the Administrator account. If you don't then something goofs up and causes the auto logon issues that I was
having.

MDT not proceeding to Deployment Wizard after entering credentials on target machine

I have a server configured with MDT 2012 and am using WDS on another server with DHCP and AD to push that out to client machines. Sometimes it works, other times I enter the network credentials into the wizard on the deployment client and instead of saying
'Processing Rules: Default' and proceeding to the task sequence selection, it says 'Initialization Complete'. The window then disappears leaving just the Solution Accelerators background.

Hi,
Please check the logs referred in the following article:
http://blogs.technet.com/b/askcore/archive/2012/05/08/mdt-2010-amp-2012-my-deployment-failed-what-and-where-are-logs-i-should-review.aspx

How can we Create a Media with all the OS,Applications and drivers with cutomize settings in MDT to automate the deployment

Hi,
I need to Create a media along with all the packages (OS,Drivers, Applications and customized settings) through MDT for the windows 8.1 deployment.
Can someone guide me?
Shailendra Dev

Hi,
Here are 3 great links to get you started:
http://technet.microsoft.com/nl-nl/windows/dn481547
http://c-nergy.be/blog/?p=3968
http://windowsitpro.com/windows/create-windows-7-media-deployment
This should provide you enough information to do what you want.
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT 2012 Windows 7 Deployment Stops At User Account and Computer Name Setup Page

I was given a sysprepped custom Windows 7 WIM image that was set up by a third party that didn't use MDT to create the WIM.
I created a task sequence to deploy it, but it never finishes. After the OS installs and it reboots, it comes up to the white setup page asking for a user name and computer name that looks like this image:
Is there a setting in MDT that can change that behavior?

Are you joining the computer to a domain?
It sounds like MDT did not create the unattend.xml file itself (or is there an unattend file already in the image itself?)
MDT needs to be able to autologin with the local admin account
From MDT in your task sequence - OS info - Edit unattend.xml you can check if your unattended file is correct.
Check what's in there for:
- computer name in 4 Specialize area - Windows-Shell-Setup_neutral (it should be empty if you want MDT to handle it).
- Also i think you need to have in the Specialize section, under Microsoft-Windows-Deployment_neutral - Run Synchronous an EnableAdmin insert
This will enable the local admin account
- Also check in phase 7 oobe System in Shell-Setup_neutral
There should be an autologon with a count of 999
Check if you have any Local Accounts there.
Finally read this:
When I am joining clients to a domain, can I avoid creating a local user
account on the computer?
Yes. To do this, create an image unattend file that adds a domain account to the Administrators group. In addition, you must delete the <LocalAccounts> section if it is present in your
unattend file (simply commenting it out will not work). An example file is below. Note that if domain join fails, Windows Deployment Services will not use the unattend file so you will be able to create a local account. For more information about creating
unattend files, see Automating Setup.
<?xml version='1.0' encoding='utf-8'?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:ms="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<UserAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
<DomainAccounts>
<DomainAccountList wcm:action="add">
<DomainAccount wcm:action="add">
<Group>Administrators</Group>
<Name>DomainAdmin</Name>
</DomainAccount>
<Domain>DomainName</Domain>
</DomainAccountList>
</DomainAccounts>
</UserAccounts>
</component>
</settings>
</unattend>
I tried opening the unattend.xml from the MDT workbench, but it errors out saying it cannot be done because the captured image is x86.

MDT 2010 Windows 7 deployment problem

Hi all,
we are using mdt2010 update 1 for quite some time now.
currently we want to deploy windows 7. we have two domains A & B, both in the same forrest A.
Deployment in domain A succedes, but in domain B i get:
<![LOG[SMS Task Sequencer found at <our server>\DeploymentShare$\Tools\X64, copying to C:\MININT\Tools\X64]LOG]!><time="16:27:08.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\CcmCore.dll to C:\MININT\Tools\X64\CcmCore.dll]LOG]!><time="16:27:08.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\CcmUtilLib.dll to C:\MININT\Tools\X64\CcmUtilLib.dll]LOG]!><time="16:27:09.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\Smsboot.exe to C:\MININT\Tools\X64\Smsboot.exe]LOG]!><time="16:27:09.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\SmsCore.dll to C:\MININT\Tools\X64\SmsCore.dll]LOG]!><time="16:27:09.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TsCore.dll to C:\MININT\Tools\X64\TsCore.dll]LOG]!><time="16:27:09.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TSEnv.exe to C:\MININT\Tools\X64\TSEnv.exe]LOG]!><time="16:27:09.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TsManager.exe to C:\MININT\Tools\X64\TsManager.exe]LOG]!><time="16:27:09.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TsmBootstrap.exe to C:\MININT\Tools\X64\TsmBootstrap.exe]LOG]!><time="16:27:10.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TsMessaging.dll to C:\MININT\Tools\X64\TsMessaging.dll]LOG]!><time="16:27:10.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TsProgressUI.exe to C:\MININT\Tools\X64\TsProgressUI.exe]LOG]!><time="16:27:10.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\TSResNlc.dll to C:\MININT\Tools\X64\TSResNlc.dll]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\xprslib.dll to C:\MININT\Tools\X64\xprslib.dll]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Tools\X64\00000409\tsres.dll to C:\MININT\Tools\X64\00000409\tsres.dll]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying <our server>\DeploymentShare$\Control\DWP5.0_1\TS.XML to C:\MININT\Tools\X64]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to C:\MININT\Tools\X64\VARIABLES.DAT]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 0]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copy File: <our server>\DeploymentShare$\Tools\x86\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x86\]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x86\Microsoft.BDD.Utility.dll"]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 0]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copy File: <our server>\DeploymentShare$\Tools\x64\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Verifying that the Disk and Partition exists]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Disk and Partition]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DestinationLogicalDrive is now = C:]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Logical Drive was determined to be C:]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: "C:\MININT\Tools\X64\TsmBootstrap.exe" /env:SAContinue]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147024891 0x80070005]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="16:27:11.000+000" date="12-09-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
- smsts.log revaels no extra usefull info.
- Running on the failed machine with cscript //nologo litetouch.wst /debug:true /debugcapture:true reveals no extra usefull information..
Funny thing is, if I deploy on a fresh vm, targeted for domain B, all goes well !!!. If is deploy to domain A, and again to domain B, it failes.
So why won't tsmbootstrap start ??
Please help,
Cheers Erik

Smsts.log reveals no information? Is that the problem? Did it process any of the commands at all? The first step here is to check smsts.log.
However, yea, it looks like tsmbootstrap.exe started and returned very quickly, not good.
There are all kinds of 3rd party products that can "mysterious" problems, there are some Antivirus programs that have been know to cause problems. Can you disable the 3rd party programs?
Do a WinDiff.exe of all files under c:\minint to see if any files were not copied down.
-k
Keith Garner - keithga.wordpress.com

Win App Deployment include SQL 2008 Express - Check if any SQL Server version already exist

Hi there
I have a application that is deploying and installing correctly (Setup and Deployment Project in VS 2008) and has SQL 2008 Express as a pre-requisite. SQL Express installs fine if not found but I don't want it to be installed if any other version of SQL
Server already exists on the target computer. What do I have to adjust in the Bootstrapper package (package.xml or product.xml) for SQL Express to do this check? Is the change done within the Bootstrapper package? Do I have to create a Custom Action
in my Deployment project for this check? Any help is appreciated.
Thanks
Dweezil

Hi Dweezil,
If you use SQL Express Bootstrapper, you can add the SqlExpressChk.exe package file in the product.xml to check that if SQL Server is already exists.
However, please note that SqlExpressChk.exe is limited to only the default instance name, SQLEXPRESS, it won't detect other named instances. A registry check is required when detecting existing SQL Server with custom instance name.
For more details, please review this
blog.
There is also a similar thread for your reference.
https://dotnetinstaller.codeplex.com/discussions/245326
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

Single MDT Database and two Deployment shares

I have two unique Deployment shares as I have separated my Deployment shares by OS, as such I have a Windows 7 DS, and a Windows 8.1 DS. The reason behind this is shear size for the number of models I have to support, it would bloat the image over the
15GB mark it sits today.
That all being said what I am attempting to do is utilize a single database as it all houses the proper site information (all 500+ locations), however the issue I am running into is with the fact that if I have an Application bundle in my Windows 7 DS
with dependencies, and I go add the Bundle for the machine to the database in my Windows 8 DS then it overwrites the database information completely and I lose the capability to install the app bundle in my Win7 deployment.
I do understand that if I had both OS within a single DS and had multiple TS for the OS deployment and all the bundles created by OS version and utilized the logic to only install on specific OS version I could get this to work rather easily but as stated
above I support over 40 Models of PC in my windows 7 image and cannot add to its size as it is already a hassle to distribute.
Any help or suggestions would be appreciated.

Keith,
The "Completely" meant that due to the mismatched GUIDs it was overwriting the database entry for the working Deployment share when I added the new Bundle . I have since copied the Bundles from one Deployment share to the other and that seems to
have resolved most of my issues, However I am still seeing in the Applications.xml file that it pulls the applications from the Windows 7 side for Bundles if I do not have an application in that same Bundle for the Windows 8 side. This would attempt to install
even if the app was set only for the Windows 7 side as a SupportedPlatform, as it was added to the Applications.xml file and would always error out because it was unable to find the application for that GUID.
Basically I have a Bundle for all Laptops and on the Windows 7 side I have a few apps that get installed and we are not that far into Windows 8 to needs these same apps yet which is why it was empty on the Windows 8 side.
So your suggestion is indeed the solution but also wanted to make people aware that there cannot be an empty Bundle on one of the Deployment Shares if there are Apps in that Bundle on the other Deployment share.

Mdt choose appplication for deployment

hello everyone
sorry my imperfect English
after having capture my pc referent
build.
when I get there in the deployment
wizzard I no longer choosing aplication
you have a solution ?

Hello, chest27430.
Could you provide us with more information.
Upload please your TS.xml first.
What changed have you made on server?

Windows 7 MDT litetouch

We created a task sequence and captured an image with litetouch. The task sequence had a default home page set, but since then the home page has changed and we changed it in the task but can't find on the computer where to change it. Policy can not override
it and it's not anywhere in the registry.
We have new users log in all day and we have to change the home page for them manually, I would think it would be in a stored answer file somewhere but can't seem to find it.
We tried setting it through policy, changing registry but that home page always comes in as the default home page.

IE 10 home page is set through GPP so you can't override the home page set by the task sequencer, Preference's don't over ride policy. I said all this in my question.
We set policy, we tried to modify registry, but the task sequencer set it and we need to find where that info is on the PC.
The default user builds the new profile and the value is always the old home page, the default is set through the old task sequence, we need to modify existing computers.

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 LITETOUCH Win 7 Deployment

Similar Messages

Maybe you are looking for