OK, I am stumped I can't get this to work... I am running this on a Windows 7 Professional 64bit Box joined to the domain (I have domain admin rightswith Microsoft Windows AIK & Microsoft Deployment Toolkit 2012 installed.

1. Add new Deployment Share - accept all defaults
2. Import Operating System from Windows 7 Professional cd created from iso downloaded from Microsoft
3. Create Task Sequence - accept all defaults
4. Unchecked x86 checkbox on Deployment Share Properties
5. Update Deployment Share
6. Receive the following output:

=== Making sure the deployment share has the latest x86 tools ===
=== Making sure the deployment share has the latest x64 tools ===

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.
Added component winpe-hta
Added component winpe-scripting

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 0xc150003a

An error occurred while loading DISM. The DISM tool may be corrupt. 
Try reinstalling DISM.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Exit code = -1051721670

DISM /Add-Package failed for component C:\Program Files\Windows AIK\\Tools\PETools\amd64\WinPE_FPs\winpe-wmi.cab, rc = -1051721670.
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-fmapi

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 0xc1500023

An error occurred while attempting to access the image at C:\Users\tleanna\AppData\Local\Temp\MDTUpdate.5084\Mount.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Exit code = -1051721693

DISM /Add-Package failed for component C:\Program Files\Windows AIK\\Tools\PETools\amd64\WinPE_FPs\winpe-mdac.cab, rc = -1051721693.
Added component winpe-mdac
Copying files...
Copying WIM to the deployment share.
Creating an ISO.
Copying ISO to the deployment share.

=== Completed processing platform x64 ===


=== Processing complete ===

I create the boot CD and all it does is reboot the machine... What is going on?

I'm performing a refresh using MDT 2010 Update 1. IT is a Win7X64->Win7X64 using a captured W7X64 WIM image. All assets are zh-CN.

I keep failing during the OS install action of the task sequence I see:

The Lang.ini of the OS supporting files contains:

[Available UI Languages]

zh-CN = 3

[Fallback Languages]

zh-CN = zh-cn

My Unattend.xml has the following under the generalize pass, Microsoft-Windows-International-Core-WinPE

<SetupUILanguage>

	<UILangauge>zh-CN</UILangauge>

</SetupUILanguage>

<InputLocale>0804:00000804</InputLocale>

<SystemLocale>zh-CN</SystemLocale>

<UILanguage>zh-CN</UILanguage>

<UserLocale>zh-CN</UserLocale>

The Imagex.exe /INFO output of the captured WIM has:

<Languages>
    <Language>zh-CN</Language>
    <Default>zh-CN</Default>
</Languages>

I found this article that explains that If my Unattend.xml is corrected to look as it indicates, I should be able to bypass this issue. I have found that this is not the case.

Here is a thread that is related to this one, but does not answer/solve my problem.

Anyone else run into this? Any help is greatly appreciated.

I have a custom XP to Window7 "migration" written in MDT 2010 that works like a charm. However it does not work in MDT 2012. I start with a Replace task sequence that I have customized to do a USMT to the server, then drop a local WinPE that reboots into a different NewComputer task. The User Exit analyzes that state of the computer, looking to files, etc, to determine which TaskSequnceID to select, 2 is the Replace and 3 is the NewComputer. I have one userexit.vbs that contains all the logic and it is 100% successful at determining the phase and selecting the right task sequence number under MDT 2010. However it does not work under 2012. This is also a move from PE 3 to PE 4 in case that matters.

It finds the _SMSTaskSequence on the drive after the reboot and this auto-selects the wrong task. It appears that the end of task sequence 2, Replace, does not clean up after itself before it reboots. How do I get it to clean up and not leave the tsenv.dat pointer file behind when it reboots into the local WinPE?

I can post my task sequences and custonsettings.ini with userexit.vbs if need be, but as the user exit is over 1000 lines it take a lot of space. After a full day of troubleshooting I am convinced the root is this failure to clean up prior to the reboot.

I need to also add that in the unattend file for the WinPE I have a VBScript that is called prior to the litetouch engine and it is not being run either. It is as if rebooting to the local PE doesn't even read the unattend.xml in the root of the WinPE like it did under PE3 and MDT 2010. Is it possible that WinPE 4 is not reading the unattend, or needs it to be in a different "format" somehow?

"Anything worth doing is worth over doing." Heinlein

we have  acquired a new  company, say skid row, there are around 400 computers,, our company is called  megadeth

i want to  format each and every  400 computers from  skid row and install the image  from megadeth to the skid row  company computers using mdt 2012

the thing is

skid row computers are running windows xp 32 bit and   windows 7 32 bit  professional and  ultimate

i want to change them all to windows 7 64 bit  enterprise edition

the computers got  c drive and d drive

if i am able to wipe the c drive  only and  install the new operating system without touching the  d drive

i am in heaven, because d drive contains  the data and i dont want to back it  to a external portable drive and stuff and restore it later on

any help would be  of great help

To be successful in life, you need to work smarter and not harder, and dont forget to drink your milk and say your prayers

I am moving off mdt 2010  and going to MDT 2012 with database integration.  I have set up the database to use names pipes and granted the MDT user DB_datareader rights.  I have created the needed share and have the following in my cs.ini

[CSettings]
SQLServer=xxxxxxxx
Database=MDT_Test
Netlib=DBNMPNTW
SQLShare=test$
Table=ComputerSettings
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR

In the bdd.log you can see it successfully connects to the share, but then errors out connecting to the database using the ANONYMOUS LOGON. 

<![LOG[Found Existing UNC Path Y:  = \\xxxxxxxx\test$]LOG]!><time="21:42:28.000+000" date="10-29-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="21:42:28.000+000" date="10-29-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[OPENING TRUSTED SQL CONNECTION to server xxxxxxx.]LOG]!><time="21:42:28.000+000" date="10-29-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Connecting to SQL Server using connect string: Provider=SQLOLEDB;OLE DB Services=0;Data Source=xxxxxxx;Initial Catalog=mdt_Test;Network Library=DBMSSOCN;Integrated Security=SSPI]LOG]!><time="21:42:28.000+000" date="10-29-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[ZTI error opening SQL Connection: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

Does anyone have any suggestions?

thanks

I am installing an app bundle. I launch the LiteTouch.vbs file from my deployment share to initiate the install. The App Bundle installs the app and copies a config file from a UNC share to a directory on the C: drive and desktop icons from a UNC share to the Public all users desktop. The install and both file copies complete successfully but display the following warning upon completion: 

I am using the xcopy command for the copies.

Any ideas?

Hi,

i have a deployment share to deploy windows 7 x64 on the main office and every thing works fine, we have a branch office and i want them to have the same thing, so i create a deployment share on a branch server and use linked deployment share to replicate the content from the main office (replicate every thing) but i noticed that the bootstrap and customize file setting on the branch office are different from the main office (default settings). can some one help me to have the exact files

thanks in advince

hi all

we deploy windows 7 and now we plan to deploy also server! In our test we see that server use also $OEM$.  Is it posible that the server doesn't use the $OEM$ folder because there are many win7 client tools in this folder

Chris

I'm having an issue with MDT deployment not finishing. The final step should be it cleaning up the folders it put on the root of "C" and displaying the completed page. But, if I run the lightouch shortcut that is on the root of "C" it will go through the final steps as it should.

Here is my question: the image I'm installing start an application (aver media +) when you login. Could this be preventing the successful completion of the lightouch deployment? And if yes is there a way to fix it?

thanks

Kris Da San Martino

I am setting up a deployment server for my college's Computer Engineering lab. I had to do some "unconventional" things to achieve the configuration the program director wanted. The machines we are deploying to have two NICs connected to our network, and she wanted both to have static IPs based on their computer name. I achieved this by adding OSDComputer name in the priorities list and have the NIC settings listed in the deployment rules. I also edited the ZTIGather.xml to include the second set of adapter variables (OSDAdapter1IPAddress etc.) This method worked flawlessly on my test deployment to a virtual machine. I then tried it on our test hardware machine and I had a couple warnings related to the NIC settings. I reviewed the ZTINicConfig log and found that the ZTINicConfig script was running again after a reboot from the WSUS post application pass. It appears the warnings are generated because the script is trying to assign the static IP addresses that are already assigned to the NICs. Also, after the reboot I am prompted to choose a network location (home, work, public.) Is the script running again after the updates normal?

I am using MDT 2012 update 1, and my task sequence is a standard client install with no additional tasks added.

Can some one offer me with a good drivers library for MDT OS deployment?

I have been using the driver packages from the site DriverPacks.net , but I found there are often some problems with the driver pakages.

For example, a Synaptics touch pad is installed with ELAN touch pad drivers. And more similar problems often come out.

My deployment server is 2008 R2 running MDT 2012 Update 1.  I have created offline media for deployments outside of the facility where the server is located.  When I create the DVD it does not copy any custom scripts I have created and placed in the scripts directory.  When I check the DVD I only have the default scripts.  In the past this worked.  Any idea why it will not copy the custom scripts I have created?

For example, a mass of drivers is stored in a folder named "Drivers".  But they are not directly stored in the  "Drivers"  folder root. In the folder "Drivers" , there are many sub-folders, and in the sub folders there are many sub-sub folders...drivers is actually stored in these sub folders, for the need of classification management.

Now I want to import all the drivers into Out-of-Box node, and the hierarchy of the root folder and the sub folders must be the same as in Out-of-Box node.

How to?

I have a client that prefers to restore end users' Quick Launch tool bat when migrating from XP to Win 7.   They are using MDT 2010 U1 and USMT 4.   Scanstate calling MigApp.ml and MigUser.xml does capture the folder /file structure of each user ( %APP_DATA%\microsoft\Internet Explorer\Quick Launch...) but does not restore it to the expected location.   any ideas?

Thanks!

Dale

I've been using MDT 2010 with great success, unfortunately when I installed MDT 2012 and attempted the same tasks performed in 2010 I've had nothing but problems. My office is small and I don't make any direct custom changes to the ini files. Primarily I just perform basic deployments and captures.

1. When deploying Windows 7 (from original installation files not a captured image) the domain join works but the deployment fails and I'm left with the setup partition which is still configured as the boot volume. If I don't join to the domain it completes successfully.

2. When I try and capture a custom image using the litetouch.vbs script it quickly finishes and gives me a deployment completed successfully message without ever doing anything to capture the image. 

The same steps performed without any custom changes work perfectly in 2010.

All similar issues I've seen revolve around customized settings in MDT 2012. I haven't changed anything and it doesn't work.

Just from poking around in the task sequences it appears as though the Capture and Standard Task sequences are different from 2010 to 2012 specifically regarding the position of sysprep. When attempting to deploy and join to a domain it seems as though the system is trying to run sysprep after it joins the domain which just isn't going to work.

I have upgraded to latest service pack and I have started with a fresh deployment share and have actually tried this with a couple different environments. In both environments I try 2012 and it fails. I tear everything down and try it on 2010 and it works perfectly.

There are features in MDT 2012 that I would like to use, such as deploying Windows 8, so I know I can't stay with 2010 forever but as of this moment I have no choice. 

- Thanks for any help I can get or for at least reading my tale of woe crammed into a bottle and tossed into the furious sea that is the internet. 

Please：How to inject the two file into OS Deplyment Task sequence?

In My bootstrap.ini，I have already injected some codes to make Client computers join into domain.

How to make the two file run before client computer joining into domain?

the fuction of the  2  file is to change computer name to "PC&LAN adapter'MAC".

for Windows 7,the task sequence may be  start task sequence--->run the two file to change Client compter's name--->joining into domain

Otherwise，for Windows XP系统，cause windows XP must install powershell component first, so that the .ps1 file could run correctly，

so,please tell me :for the XP deployment，how to make the sequence ：  start task sequence--->Installing Powershell component--->run the two files--->joining domain


BTW：run 01.cmd first ，02.ps1 second。

01.cmd is below

ftype Microsoft.PowerShellScript.1="%SystemRoot%\system32\windowspowershell\v1.0\powershell.exe" ".\"%1""
"%SystemRoot%\system32\windowspowershell\v1.0\powershell.exe" set-executionpolicy remotesigned

02.ps1 is below

$netid=gwmi Win32_NetworkAdapter |?{$_.NetConnectionStatus}| Select-Object DeviceID 
$network=ForEach ($id in $netid ){gwmi Win32_NetworkAdapterConfiguration|? {$_.index -eq $id.DeviceID -and $_.DefaultIPGateway -ne $null}}
$hostname="PC"+($network.MACAddress.split(":") -join $null)
set-itemproperty -path HKLM:\System\CurrentControlSet\Control\ComputerName\ActiveComputerName -name "ComputerName" -value $hostname
set-itemproperty -path HKLM:\System\CurrentControlSet\Services\Tcpip\Parameters -name "NV Hostname" -value $hostname
set-itemproperty -path HKLM:\System\CurrentControlSet\Services\Tcpip\Parameters -name "Hostname" -value $hostname

I was toying with windows 8 deployment and was busy capturing a windows 8 image but when it was taking a while i checked with trace what was going.
when imagex scans the disk to capture it seems to do a lot of ignoring extended attributes before finally starting the capture.

never had this happen with windows 7 captures so i take it windows 8 uses a lot of extended attributes on files.

i read on the imagex page that it doesn't support these extended atributes but i'm sure it isn't the intention to increase deployment times by +/- 30 minutes just because imagex has to go through your disk saying it is ignoring certain attributes.

is there anyway to stop imagex from taking it's sweet time with windows 8 captures?

i am using a standard client task sequence.

Can MDT 2012 update 1 with the Windows 8 ADK be installed on a Windows 2008 R2 SP1 server?  I upgraded from MDT 2010 that was using the Windows 7 SP1 AIK to MDT 2012.  I no longer have MDT 2010 or Windows 7 SP1 AIK installed.  After this, I'm getting failures in just about everything I try to do.  The failures are all error code 1 which from my development experience usually indicates a DLL mismatch or something similar.  An example of the error is below which occurs during boot image generation.  I am logged in with domain admin privileges so I don't think it can be permissions related.  Those are usually error 5.  I have installed PowerShell 3.0.

--Thanks

We are using MDT 2012 Update 1 and DFS Replication to keep the deployment shares in sync across our offices.  When attempting to make changes we receive the error message "The deployment share is read-only, so no changes can be made".  In order to make changes we have to disable the connections in DFS and force replication, which is a pain.  Sometimes this issue occurs during hours when no replication is scheduled to take place.  Also, we are not using read-only shares in DFS-R.

Is there any solution or guidance on this issue? 

MCITP Windows 7 MCTS Windows Server 2008

Using MDT 2012.

I get the error show in the title at the beginning of the state restore phase.   It finds the task sequence info on C:, but cant file the tsmbootstrap.exe.  Any ideas?

thanks

G[Found existing task sequence state information in C:\_SMSTaskSequence, will continue]LOG]!><time="04:23:18.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="04:23:18.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentMethod is now = UNC]LOG]!><time="04:23:20.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="04:23:23.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployRoot is now = C:\MININT]LOG]!><time="04:23:26.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="04:23:27.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = C:\MININT]LOG]!><time="04:23:27.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = C:]LOG]!><time="04:23:27.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = C:]LOG]!><time="04:23:27.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = STATERESTORE]LOG]!><time="04:23:27.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="04:23:27.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = C:]LOG]!><time="04:23:28.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = C:]LOG]!><time="04:23:28.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceRoot is now = C:\MININT]LOG]!><time="04:23:28.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentType = ]LOG]!><time="04:23:28.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceRoot = C:\MININT]LOG]!><time="04:23:28.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceDrive is now = C:]LOG]!><time="04:23:29.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = C:]LOG]!><time="04:23:29.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property _SMSTSPackageName is now = Lite Touch Installation]LOG]!><time="04:23:29.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property Architecture is now = x64]LOG]!><time="04:23:29.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FindFile: The file TsmBootstrap.exe could not be found in any standard locations.]LOG]!><time="04:23:30.000+000" date="11-01-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">