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

Similar Messages

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 2010 Windows 7 custom image import problelm

I am unable to import a Windows 7 OS from a wim image file any more. I get "Path 'C:\Distribution\Operating Systems\Old OS Folder' does not exist" when I try to import. I believe the folder it is looking for was one where I had imported a custom image with setup files. I have since added Windows 7 operating systems from the DVD for source files and had deleted the image operating system it is looking for. I can still import a Windows XP custom image just fine.
It is creating the folder and copying the wim, but it does not show up in the Deployment Workbench under operating systems. Any ideas? I assume the problem is coming from having imported the wim with setup files previously.

Hi,
just came across similar problem.
Custom .wim image not visible after importing to MDT.
imagex /info returns long wim description for another custom wim but much shorter for this one.
I tried to change wim name and description property - but nothing worked for me.
So I applied the original image to folder and then recaptured it with imagex I am using (newest WAIK).
Now the imagex /info is ok.
Btw you cannot notice the difference with
dism /Get-WimInfo
It is now visible in MDT.
Can you please explain what you did.
i am using image capture cd generated using SCCM to capture the wim file.
1 image i imported successfully. Every image since then after import it does not show up in deployment workbench. i have no idea what to do.

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.

How can i using MDT 2010 to deploy multiple partitions Windows 7 image?

Hello,
I am planning using MDT as a deploy windows 7 solutions. My Windows 7 is setup on parition 1 "C:" and users profile on parition 2 "D". I am already capture WIM for each paritions. How can i using MDT 2010 to deploy multiple partitions for Windows 7
image? together
Thanks

Having the users folder on a separate partitions is a bad idea because the Windows Setup was not really designed for it, it's more of a afterfix. In addition to that the deployment solutions in general have problem dealing with multiple partions.
Put it this way - The big warning text in the WAIK documentation about redirecting the users folder to another drive is there for a reason. It will break future offline servicing.
It doesn't mean it can't be done, it just means it will take you three times (at least) longer to setup/troubleshoot your deployment solution, and you will be in a world of pain the next time you want to re-image the machine.
This quote from a good friend of mine (Andreas Hammarskjold) describes it very well:
Generally I would always recommend to only have ONE partition these days. Going down the route of making multiple partitions is like having multiple wives/girlfriends/lovers… it’s all fun and games for a while but ends with disaster
- Andreas H.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Microsoft Updates after Windows 7 Deployment using MDT 2010 Update 1

Hello,
After I deploy Windows 7 using MDT 2010 Update 1, i'm prompted to download and install updates. Updates which were installed prior to the capture process. During the capture process, does something reset Windows Update and makes it think the updates were
not installed?
My process of building a custom image is as follows:
1. PXE boot and kick-off a build task sequence (install OS + drivers + soe applications). (protectmypc = 3 in unattend.xml)
2. Download and install all Microsoft Updates, configure the OS, configure third-party applications.
3. Map a network drive to my deployment share, run litetouch.vbs and kick-off a capture task sequence.
4. PXE boot and kick-off a deployment task sequence. (copy profile = true, protectmypc = 1 in unattend.xml)

I'm getting updates but they are new updates. We have updates turned off through Group Policy and after an image is deployed it is attempting to install updates which should not be installed through Windows. I also have the protectmypc setting set to 3
and have updates turned off before capture. Something is searching for updates and during the deployment process and I need to find out how to stop this from happening. Someone has to know where these updates are coming from.
Joseph N. Sunderman | IT Professional

Sweet - MDT Update 1 UDI Success - However, "Windows 7 Deployment Complete" dialog hatred

Hi,
I am using MDT Toolkit Update 1 integrated into SCCM 2007 (R3 SP2) to create Windows 2008 R2 OS deployments. Recently, I was asked to have the ability of the engineer deploying the OS to be able to choose what applications get installed as part of
the build. Thaaa... I thought, this may be a problem. ... Then I discovered UDI and became very happy.
Anyway, it seems UDI was really geared toward deploying Windows 7...but its working for Windows 2008 R2 too (at least, in my environment). I was able to use UDI to present the diaglog box for the engineer to pick what applications that want installed
as part of the build without any problems. However, at the very end of the OS deployment, a deployment complete dialog box is displayed...
"Windows 7 Deployment Complete" - with three tabs...
Actual screen shot of this dialog box:
http://andysal.files.wordpress.com/2010/07/12.png
1) Is there a way to disable this diaglog?
2) Is there a way to change this dialog to say "windows 2008" instead of "Windows 7?
Thank you...

1) Yes, just disable the "Run OSD Results" step in the task sequence.
2) Yes, you can edit the OSDResults.exe.config file to change the text and images displayed.
-Michael Niehaus
Senior Software Development Engineer
[email protected]
http://blogs.technet.com/mniehaus

MDT windows 7 Deployment issue with Network driver

I am deploying windows 7 64bit using MDT 2010. the PC I am deploying to is HP proDesk 600 G1 SFF, and the NIC card is intel (R) I217.
When I deploy the customised image, there is no problem during the WinPE stage, I can press F8 and run ipconfig /all to see all the NIC details, which means the correct driver is injected to the PE image.
The issue comes after the OS installation completes, after rebooting into the system and auto login as admin, the error pops up indicating no connection to the deployment share, it is actually the NIC driver not installed!
I checked the Hardware ID, it is PCI\VEN_8086&DEV_153A&SUBSYS_18E7103C&REV_04
I can find this ID in drivers.xml under deploymentshare/control, I believe this indicates there is a driver available for it.
but in the deployment log ztidrivers.log, it shows
<![LOG[Skipping Device PCI\VEN_8086&DEV_153A&SUBSYS_18E7103C&REV_04 No 3rd party drivers found. 11]LOG]!><time="09:21:02.000+000" date="05-07-2014" component="ZTIDrivers" context="" type="1"
thread="" file="ZTIDrivers">
I can install the driver manually with no issues.
I downloaded different versions of the driver and tried hundred times but result is the same.
anyone can point me to the right direction? I have been struggling with this for quite a while.
Thanks

Hi,
You should inject driver to install image which will finally present in system you installed.
Hope this helps.

Windows 7 Embedded & MDT 2010 Update 1

Hi,
Is it possible to deploy Win 7 Embedded with MDT 2010 U1 ? Is it supported by MS ?
Thanks,
Regards.

Hi,
Yes you can. Please see this video
Deploying Windows Embedded Standard 7 with Style
regards,
Blog Microsoft |
Déployer Windows 7 |
Améliorer les performances de Windows 7

How can I get a better driver for my 1394b Hostcontroller in my Macbook pro 2010 to solve the problem, that it is too slow under Windows 7 installed with bootcamp ?

How can I get a better driver for my 1394b Hostcontroller in my Macbook pro 2010 to solve the problem, that it is too slow under Windows 7 installed with bootcamp ?
WIndows can't find a better one than the installed LSI Conformed 1394 Hostcontroller

Read and follow the Bootcamp Installation instructions that you were offered to view when you ran Bootcamp Assistant.
Run Bootcamp Assistant again and select the option to download the Bootcamp Support software. Follow the instructions. Then boot into Windows and install the Windows Support software you downloaded and saved.

MDT and Macs running Bootcamp – worked in MDT 2010, now does not in MDT 2012

I haven’t been able to find much info on this so I thought I would try here and see if anyone can help.
We’ve been using MDT 2010 for the last couple of years to install Windows 7 on Macintosh’s running Bootcamp and it’s been working fine.
We recently upgraded to MDT 2012 and the same process we used to use for this does not work anymore and I would like to find out how to make it work on 2012.
Here’s how the process works:
First, setup Bootcamp on the Mac. This creates another partition on the Mac for the Windows OS (partition 3 for MAC OS 10.6 and lower, partition 4 for OS 10.7 Lion because of the recovery partition).
Unfortunately Bootcamp cannot create NTFS partitions so it formats it as FAT32.
We then create a standard client task sequence using MDT and the Windows 7 source files (not a custom image) and give it a name to make it obvious it’s for Mac’s – “Windows 7 for Macintosh running Bootcamp”.
We edit that task sequence and disable the built in “Format and Partition Disk” step since we don’t need to create the partition, only format it as NTFS.
We then create a custom diskpart.txt file called BootCamp_Lion.txt with the following contents:
SELECT DISK 0
SELECT PARTITION 4
FORMAT FS=NTFS QUICK OVERRIDE
We place this file in the “Extra directory to add” location we’ve specified in the Win PE Customization section so it is located on the root of X:\ when it boots into Win PE.
We then add a command line to the task sequence: diskpart.exe /s x:\BootCamp_Lion.txt
to format the existing bootcamp partition as NTFS. Then in the “Install Operating System” step we set it to apply to a specific disk and partition – Disk 0, Partition 4.
This installs Windows 7 on the Bootcamp partition and leaves the Mac OS intact and has been working fine in MDT 2010.
Now with MDT 2012, the task sequence starts fine, formats the partition, installs Win 7, but when it comes up in the full OS for the first time I get the error “Unable to find the SMS Task Sequencer.
The deployment will not proceed.” And the task sequence stops.
I know the partitioning part has changed in 2012 and have read that you can get this error if you deploy to something other than disk 0, partition 1 but I’m wondering if I can accomplish the same thing that I used to have working in 2012.
Is there a different way I can do this? Any help would be appreciated.
Thanks,
Robb

Hi Guys
I have been having the same problem.
What I have done to get around it is
add a custom command as we all did in MDT 2010 to format partition 3 or 4 depending on the version of OSX
don’t disable the Format and Partition Disk task but tick in create active partition then remove the partition properties and then click on options and check
continue on error
then under install operating system change the partition that you want to have windows installed on
Once the deployment has completed you will receive the message that deployment has completed but with one error
Hope this helps
Regards
Matthew

MDT 2012 Suspend Task Sequence Problem

Hi ,
I have been using LTISuspens.wsf without problem in my MDT 2010 and MDT 2010 U1 for a long time. Recently I have create my test MDT 2012 and I have problem with this task.
I have created the new Run Command line cscript.exe "%SCRIPTROOT%\LTISuspend.wsf" in State Restore section. The build and capture TS is stopping correctly and I have the LTISuspend icon on the desktop. After resuming the TS, it going correctly through, running
sysprep, pop in again Set Network Location window, I can see it is running “Apply Windows PE (BCD)” step and then stops. There is message “suspended” and “The task sequence has been suspended true Use the…..”
Any ideas what I am doing wrong?
My customsettings.ini is from MDT 2010 and there they are fine.
I am capturing Windows 7.
Thanks
Vinnie

Hi,
A few suggestions below for each of your issues.
Issue 1 is that you don't see any task sequences in the wizard
- Have you updated your deployment point after upgrading to 2012? if not then do this now
- Have you updated your boot media with the newly generated Litetouch_x86.wim (meaning your boot CD, boot USB or WDS)
The thinking behind this is that if you are using MDT 2010 boot media to try and speak to an MDT 2012 DS then you will have the same problem.
Issue 2 is that you've had the TS running in the past but it's broken for one reason or another.
- Have you recreated your Task sequence using the MDT 2012 client template? There are (minor but critical) differences in the logic between the versions of MDT and the new task sequence template has been updated as such. Using an MDT 2010 template with
MDT 2012 scripts can cause this.
These are 3 things that cause similar issues to you following an upgrade.

MDT 2010 Deleted task still running

Hi Guys, I have been using MDT 2010 with Litetouch for deploying Windows 7 x64 clents for the last month. I have a main task sequence which does the deployment and a test task sequence for me to try new things out.
On the test task sequence I created custom task which deletes a desktop icon, the problem now is that even after I have deleted this task it still runs even though its not in the task sequence any longer.
Even when I create a new task sequence the deleted custom task still runs! This is very strange any ideas?

Hi,
it sounds impossible :)
I think the same action might have been configured in another step, or it might be added as a dependency on some application.
To verify, you could take a look at the xml files that descrive your applications and taks sequences in .\control.
MCP/MCSA/MCTS/MCITP

MDT 2010 hangs on uefi equipped machines

Hi all,
I'm new to MDT (Started playing with the betas earlier this year), but I've been using WDS for nearly a year or so. I have an MDT 2010 server running on a Windows 2003 box with all of the latest service packs, fix packs, etc. The MDT server has been configured to deploy our install images to our test lab (We run everything from 2003 R2 up to 2008 R2). So far the MDT server (I upgraded the betas to the RTM code) has been running great on almost all of our machines, with the exception of our uEFI based machines.
We are primarily an IBM lab (We have a smattering of Dell and HP boxes, but none yet that have a uEFI Bios). We have mostly xSeries and BladeCenter products.
Our scenario:
We're running MDT 2010 in an LTI setup. No database, we just want the end user to be able to PXE boot the box, boot the Lite Touch 32 or 64 bit wim and then get the MDT screen that allows them to pick what operating system they want installed. Let the install start in the WinPE mode and then the WinPE mode reboots and continues on its installation path (DOS boot mode for the 2003 R2 installs , 2008 GUI setup, etc)
That part works fine for all of our regular xSeries (ie non uEFI) blades and servers. The user picks their OS, the preinstall phase starts, finishes and reboots out of the WinPE shell and then continues on with its next phase of the install.
Our uEFI enabled boxes (Mostly IBM HS22, x3200 M3, x3250 M3) boot into the MDT selection screen just fine. We can choose our os and the install starts in the PE phase (Sorry if I'm messing up the phase names still learning MDT as I go). Once the WinPE phase finshes, instead of rebooting (like the non uEFI boxes do) these boxes automatically open a Command Prompt window and then sit there until you close the window or type exit. I have not opened the command prompt (I know you can hit F8, but this is being done by MDT on its own). Once you manually close this window, the install continues just like it should.
I've updated alll firmware levels on these boxes to see if it might be something going on there, but no luck. MDT 2010 continues to hang (opens the command prompt) after completing the WinPE portion of the installation.
Has anybody else out there seen this behaviour? Anyone have any ideas how to correct it?
Thanks,
Jim Kosek

Hi there,
This is the original poster.
I had meant to list out our steps to correct this issue earlier this week, but this is the first chance I got to update this. Hate being the only one in on a holiday week :(
Like Keith stated above this is caused by the NETIMM.INF driver. Thanks to Keith's guidance in parsing through the log files (Especially since I had no idea where most of them were hiding) we were able to see that the NETIMM.INF driver would try and load during the Windows PE Setup phase. This driver does not appear to load correctly in Windows PE (I've been trying to get it to load into a different PE image for the better part of a year for other reasons). When this driver gets loaded during the PE phase, the installer would see that the driver did not load correctly. The installer would pop open a command prompt window to allow you to debug what went wrong. Since this driver isn't really needed for the installation, you could exit the command prompt window and your install would continue along just like it should.
If you look at your wpeinint.log file you should see something like this:
Info      Installing device usb\vid_04b3&pid_4010 X:\WINDOWS\INF\netimm.inf failed with status 0xe0000219
Info      Spent 19095ms installing network drivers
Info      STATUS: FAILURE (0xe0000219)
Warning   Applying WinPE unattend settings failed with status 0xe0000219; ignoring shutdown settings
This is what hangs the box.
When Keith first pointed me to the driver being the problem, I just removed the driver from my Out-Of-Box-Drivers and still had the issue. The NETIMM.INF file is part of the base install media so it shows up anyway. I then did just what you did by disabling the Commands on the USB Interface. This basically stops that device from being available during the install, so no device, no driver and MDT is happy and reboots like it should.
The problem I have with that solution is that all of the OS Firmware update disks from IBM want to try and communicate through that USB device when you go to update anything on that machine (uEFI code, Diagnostics, ASU, etc). So if that device is not there, then you cannot use any of the on-line flash utilities to update your machine. Not sure how many machines you have (or how often you upgrade the Firmware on them), but that might come back to bite you later. Plus you also have to remember to disable that on all of your IMM equipped machines BIOS's. And then when a user resets the Bios back to defaults that USB device gets turned back on again and you start getting calls that the deployments are hanging. I'm in a test lab and we get new machines brought to us all of the time. I may not be the one to set it up and then I have to rely on somebody remembering to change a setting in Bios. I'd rather just change it globally from my end and then I know its fixed. But to each their own.
I did like Keith suggested and edited the WIM files. I simply renamed the NETIMM.INF to NETIMM.OLD and closed the WIMs back up. I too was worried about having to change the WIM files repeatedly. I'm the one that built out our MDT server. My co-workers know enough to rebuild the deployment share if need be, but they don't use MDT enough to know about mounting WIMs and changing files and such. What I did was I changed these on our base install media. In my case, MDT picked Windows 7 to build out the 32 Bit LiteTouch.wim and 2008R2 for the 64 bit LiteTouch.wim file. Once I changed these on the original disks, all of my LiteTouch rebuilds have kept this change intact. Now if I ever change these original disks and have to completely rebuild the WIM files, I'm sure I'll forget to make that change. However I'd rather deal with that then (My end users will let me know if the installs start hanging again) instead of having to remember to change each machine's bios settings.
Now since the NETIMM.INF driver is no longer on the install media, I need some way to add that driver during the installation and not during the PE phase. What I did was to add the NETIMM.INF file into my Out-of-Box Drivers section. I then created a new selection profile called LiteTouch. I added all of my necessary drivers, with the exception of the NETIMM.INF driver, into that new LiteTouch selection group and I changed my LiteTouch Components to only load from the LiteTouch Selection group during the PE phase. I then call my All Drivers group during the installation of the Operating Systems. That way I do not get the driver during PE, but I get the driver installed during setup and I can then talk to the IMM for updates and such.
My way might not be the best way for everyone else, but it does what I need it to do.
I would like to take a minute though and thank Keith again for all of his help in troubleshooting this problem. We have a lot of remote users and this was causing them some grief because they would start a deployment and expect it to be done when they came back later. On the IMM equipped machines, they would be staring at a command prompt screen and have no idea what went wrong. I would then get calls stating that the install failed. Without Keith's help I'd still be getting those calls from our users.
Jim Kosek

MDT 2010 Vista cannot finish after joining domain

Hi,
I have a problem with deployment process after joining domain. I am deploying Vista using MDT 2010 with LiteTouch. Everything works fine. However, deployment process stops after joining domain. I suppose that autologon is disabled/don't work after joining domain and all following steps can't be started.
What is wrong with my configuration or Task Sequence?
Thanks in advance, Jan.

Hi Jan,
Thank you for your post.
As you said that the deployment process stopped after joining domain, may I know if there is any error received? If so, please let me know the details.
Meanwhile, I would like to share the following with you:
Avoiding Legan Notice that breaks MDT autologon
http://blogs.msdn.com/alex_semi/archive/2009/08/28/avoiding-legan-notice-that-breaks-mdt-autologon.aspx
Thanks.
Nicholas Li
TechNet Subscriber Support in forum
Nicholas Li - MSFT

MDT 2010 Windows 7 deployment problem

Similar Messages

Maybe you are looking for