Hello everyone,

We are trying image using the ADK winpe boot image, however the pvscsi driver apparently is not a valid version to work with the Server 2012/Win 8 ADK.  When I do diskpart, it cannot find any disks.

Anyone have any idea?  I've tried pulling the driver from my Server 2012 Test machine.

I need the x86 and x64 versions (I'm building via x86 only though).

Thanks,

Graeme

Hi everyone,

I have MDT 2012 update 1 which I use to deploy Win7Sp1 with Light Touch dep. and NET Framework 1.1 with SP1 slipstreamed. My problem is that the Application Compatibility Assistant would not allow NET framework to be installed, any ideas how I can disable application compatibility before MDT runs NET framework install?

Thank you

Hi,

I am following the exact steps given in http://social.technet.microsoft.com/Forums/en-US/mdt/thread/192a81d5-0ff4-48d7-93ff-12f0c5a9f439/.

I have enabled set Windows RE = yes in customsettigs.ini and enabled TS As well.

Installations happened smooth without any errors but I am not able to figure out if DaRT winre.wim is placed on recovery partition and is working for system in case windows recovery is needed. Is there any procedure that can verify if things are good?

I can see some message in Log file during the TS execution. it is trying to look for REAgentC.exe and couldn't able to find it seems.

FindFile: The file REAgentC.exe could not be found in any standard locations. ZTIWinRE 3/20/2013 7:22:28 PM 0 (0x0000)
About to run command: C:\Windows\System32\REAgentC.exe /info /target C:\Windows ZTIWinRE 3/20/2013 7:22:28 PM 0 (0x0000)

Regards,

To best explain here are the steps I've taken to create my custom WIM file.

1. Using VMWare workstation I installed Win 7 x64, ran updates, and installed the base programs for my image.

2. Ran Sysprep and Captured an image of this machine. (This is run by LiteTouch.vbs as a task sequence I created in Deployment Workbench.)

3. On a test computer I PXE booted and selected my image from the Task Sequence Wizard. Another part of my wizard has choices for which programs you would like to install once the OS is completed. (Office 2013, Google Chrome, etc.)

4. Windows 7 installs and I am taken to the login screen - - I log in with Administrator account.

5. At this point the Task Sequence should continue on with the Installation of Applications but this never happens.

From here I browsed to my deployment share and to the Scripts folder and double click the LiteTouch.vbs to try and continue the task sequence. I receive an error that a Dirty Environment was found. I have tried to figure out why my task sequence isn't completing when I first log into Windows. Has anyone else experienced this issue?

Howdy!

Trying to push an image to an Asus P9X79 using MDT 2012 (working fine for all other machines/motherboards) and after I click Finish to start the image, it will hang at "Preparing disk 0 partitions" and just sit there.  No error pops up and it doesn't progress past this.  Hard drives are configured as RAID 1 and have tried breaking and recreating RAID as well as formatting and un-partitioning the HDD's.  Hoping someone has seen this before and can help out.  Thanks!

Jared

I'm using 2 user exit scripts as well as another custom property to set computername.  In the end it looks like this

OSDComputerName=%Site%-%SysModel%-%SysSerial%

After much testing (via cscript //nologo \\server\deploymentshare$\scripts\ztigather.wsf /debug:true /inifile:\\server\deploymentshare$\control\customsettings.ini) , I can confirm the OSDComputerName variable I'm setting in my CustomSettings.ini (CS.ini hereinafter) is getting set properly.

I successfully deployed a test image to sample machine & I found myself looking at the Computer Name setup screen that was pre-filled with just 'PC'.  I clicked next & let the rest of the task sequences complete.  At the end I looked at the BDD.LOG in C:\Windows\Temp\DeploymentLogs where I could see the variable was set, but not used.

Property OSDCOMPUTERNAME is now = WA-X20-1234567
Using from [DEFAULT]:" OSDCOMPUTERNAME = WA-X20-1234567
...further down...
No value found for ComputerName
...further down...
//settings[@pass="specialize"]/component[@name="Microsoft-Windows-Shell-Setup"]/ComputerName not found in C:\MININT\Unattend.xml, unable to update.
...further down...
No value found for ComputerName
...further down...
//settings[@pass="specialize"]/component[@name="Microsoft-Windows-Shell-Setup"]/ComputerName not found in C:\MININT\Unattend.xml, unable to update.

I checked the Unattend.xml for the Task Sequence in question and the ComputerName property (Under 4 specialize -> x86_Microsoft-Windows-Shell-Setup_neutral) is blank, and the 'Write Empty String' isnot checked.

What have I done wrong?
Should the 'Write Empty String' be checked?
Is it expecting '%ComputerName%' or '%OSDComputerName%' in the 'ComputerName' property of the Unattend.xml?
Do I have to create a new VBScript to set the environment variable? (essentially negating what I've already done in the CS.ini)

Many thanks!

Hi guys,

my Situation: MDT 2012 RC1 running on Server 8 Beta, WAIK for Windows 7 installed.

I created a deployment share, imported an OS (Server 2008 R2) and created a Standard Task Sequence. When i want to update the deployment share now it fails with the following error message (complete output below):

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

=== Processing LiteTouchPE (x86) 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 x86 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\x86\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
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-mdac
Copy: D:\DeploymentShare2\Control\Bootstrap.ini to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Bootstrap.ini
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_PE_x86.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Unattend.xml
Copy: C:\Program Files\Microsoft Deployment Toolkit\Templates\winpeshl.ini to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Windows\system32\winpeshl.ini
Copy: D:\DeploymentShare2\Scripts\LiteTouch.wsf to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\LiteTouch.wsf
Copy: D:\DeploymentShare2\Scripts\ZTIUtility.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIUtility.vbs
Copy: D:\DeploymentShare2\Scripts\ZTIBCDUtility.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIBCDUtility.vbs
Copy: D:\DeploymentShare2\Scripts\ZTIDiskUtility.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIDiskUtility.vbs
Copy: D:\DeploymentShare2\Scripts\ZTIDataAccess.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIDataAccess.vbs
Copy: D:\DeploymentShare2\Scripts\ZTIConfigFile.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIConfigFile.vbs
Copy: D:\DeploymentShare2\Scripts\ZTIGather.wsf to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIGather.wsf
Copy: D:\DeploymentShare2\Scripts\ZTIGather.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTIGather.xml
Copy: D:\DeploymentShare2\Scripts\Wizard.hta to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Wizard.hta
Copy: D:\DeploymentShare2\Scripts\Credentials_ENU.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Credentials_ENU.xml
Copy: D:\DeploymentShare2\Scripts\Credentials_scripts.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Credentials_scripts.vbs
Copy: D:\DeploymentShare2\Scripts\WizUtility.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WizUtility.vbs
Copy: D:\DeploymentShare2\Scripts\Wizard.css to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Wizard.css
Copy: D:\DeploymentShare2\Scripts\Wizard.ico to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Wizard.ico
Copy: D:\DeploymentShare2\Scripts\BackButton.jpg to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\BackButton.jpg
Copy: D:\DeploymentShare2\Scripts\plusicon.gif to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\plusicon.gif
Copy: D:\DeploymentShare2\Scripts\minusico.gif to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\minusico.gif
Copy: D:\DeploymentShare2\Scripts\Summary_Definition_ENU.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Summary_Definition_ENU.xml
Copy: D:\DeploymentShare2\Scripts\Summary_scripts.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Summary_scripts.vbs
Copy: D:\DeploymentShare2\Scripts\LTICleanup.wsf to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\LTICleanup.wsf
Copy: D:\DeploymentShare2\Scripts\BDD_Welcome_ENU.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\BDD_Welcome_ENU.xml
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_Choice.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_Choice.xml
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_Choice.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_Choice.vbs
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_DeployRoot.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.xml
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_DeployRoot.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_DeployRoot.vbs
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_Initialize.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_Initialize.xml
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_Initialize.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_Initialize.vbs
Copy: D:\DeploymentShare2\Scripts\SelectItem.jpg to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\SelectItem.jpg
Copy: D:\DeploymentShare2\Scripts\WelcomeBanner.jpg to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeBanner.jpg
Copy: D:\DeploymentShare2\Scripts\btnout.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\btnout.png
Copy: D:\DeploymentShare2\Scripts\btnover.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\btnover.png
Copy: D:\DeploymentShare2\Scripts\btnsel.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\btnsel.png
Copy: D:\DeploymentShare2\Scripts\LTIGetFolder.wsf to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\LTIGetFolder.wsf
Copy: D:\DeploymentShare2\Scripts\NICSettings_Definition_ENU.xml to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\NICSettings_Definition_ENU.xml
Copy: D:\DeploymentShare2\Scripts\ZTINicUtility.vbs to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTINicUtility.vbs
Copy: D:\DeploymentShare2\Scripts\ZTINicConfig.wsf to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ZTINicConfig.wsf
Copy: D:\DeploymentShare2\Scripts\BackButton.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\BackButton.png
Copy: D:\DeploymentShare2\Scripts\FolderIcon.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\FolderIcon.png
Copy: D:\DeploymentShare2\Scripts\ItemIcon1.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\ItemIcon1.png
Copy: D:\DeploymentShare2\Scripts\MinusIcon1.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\MinusIcon1.png
Copy: D:\DeploymentShare2\Scripts\PlusIcon1.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\PlusIcon1.png
Copy: D:\DeploymentShare2\Scripts\SelectItem.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\SelectItem.png
Copy: D:\DeploymentShare2\Scripts\header-image.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\header-image.png
Copy: D:\DeploymentShare2\Scripts\NavBar.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\NavBar.png
Copy: D:\DeploymentShare2\Scripts\Computer.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\Computer.png
Copy: D:\DeploymentShare2\Scripts\WelcomeWiz_Background.jpg to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\WelcomeWiz_Background.jpg
Copy: D:\DeploymentShare2\Scripts\DeployWiz_Administrator.png to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Scripts\DeployWiz_Administrator.png
Copy: D:\DeploymentShare2\Tools\x86\BDDRUN.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Windows\system32\BDDRUN.exe
Copy: D:\DeploymentShare2\Tools\x86\WinRERUN.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\WinRERUN.exe
Copy: D:\DeploymentShare2\Tools\x86\CcmCore.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\CcmCore.dll
Copy: D:\DeploymentShare2\Tools\x86\CcmUtilLib.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\CcmUtilLib.dll
Copy: D:\DeploymentShare2\Tools\x86\Smsboot.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\Smsboot.exe
Copy: D:\DeploymentShare2\Tools\x86\SmsCore.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\SmsCore.dll
Copy: D:\DeploymentShare2\Tools\x86\TsCore.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TsCore.dll
Copy: D:\DeploymentShare2\Tools\x86\TSEnv.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TSEnv.exe
Copy: D:\DeploymentShare2\Tools\x86\TsManager.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TsManager.exe
Copy: D:\DeploymentShare2\Tools\x86\TsmBootstrap.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: D:\DeploymentShare2\Tools\x86\TsMessaging.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TsMessaging.dll
Copy: D:\DeploymentShare2\Tools\x86\TsmBootstrap.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TsmBootstrap.exe
Copy: D:\DeploymentShare2\Tools\x86\TsProgressUI.exe to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TsProgressUI.exe
Copy: D:\DeploymentShare2\Tools\x86\TSResNlc.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\TSResNlc.dll
Copy: D:\DeploymentShare2\Tools\x86\xprslib.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\xprslib.dll
Copy: D:\DeploymentShare2\Tools\x86\00000409\tsres.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\00000409\tsres.dll
Copy: D:\DeploymentShare2\Tools\x86\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Deploy\Tools\x86\Microsoft.BDD.Utility.dll
Copy: C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\MDTUpdate.2732\Mount\Windows\system32\winpe.bmp

System.Management.Automation.CmdletInvocationException: Cannot create a file when that file already exists.
 ---> System.IO.IOException: Cannot create a file when that file already exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

I checked on Folder C:\Users\ADMINI~1.TES\AppData\Local\Temp\2\ but it's empty...

Any idea what the problem might be? WAIK? Server 8? If you need any more information just let me know.

//EDIT Looks like this is related to the Windows Server 8 OS, as i just did exactly the same on a Windows 2008 R2 SP1 Server and it works like a charm...

Thanks in advance.

Stefan

Hi all,

I'm sorry if my english is not correct, but I'm French.

I come here because I have a problem with MDT 2012, WDS and Windows ADK.

When I run the deployment through PXE boot, the deployment failed with the error "Failed to verify ... my WIM file ...".

With the command prompt, I saw that the extension of my wim file isn't right (it's like that ".w?è"). But on my MDT local server, the wim file extend is correct.

Have you got any suggestion ?

Thanks.

I keep getting the above listed error when trying to update the rules on one of my deployment shares.  I've even gone so far as to remove the read-only flag on everything in the share, it doesn't help.

As a workaround, I've been editing the CustomSettings.ini directly, but I'd really like this to work.  Any ideas?

As an aside, the 'Alert me when someone responds to this post' never seems to work here.  And yes, I've checked my spam folder as well...

I keep getting the above listed error when trying to update the rules on one of my deployment shares.  I've even gone so far as to remove the read-only flag on everything in the share, it doesn't help.

As a workaround, I've been editing the CustomSettings.ini directly, but I'd really like this to work.  Any ideas?

Hello,

   I have created and organized my 'Out-of-Box Drivers' groups for the specific models we deploy to. I have created specific 'selection profiles'. I get when you update the deployment share that it injects these drivers into your WinPE to get everything to work.

My question is I thought once the OS was installed (i.e. Win7ProSP1) that once I went into my 'Device Manager' the driver levels would be of the ones I d/loaded from the manufacturer site. Looking at my video and networking sections it appears they are just running what came with Win7.

Example:

Networking = 03/26/2010

Video = 04/25/2009

ZT

Hello Everybody,

I have a problem with the settings of Timezone.
My OS Installations is configured in customsettings.ini completely silenty and it works. But after the Installation, if the installed Client starts up (and after initilisation of Hardware), i get the guiwindow for asking the timezone (Configure Windows? Timezone and Time...??)??
My Image is a selfcreated install.wim (with sysprep before)

my Customsetting:
OSInstall=YES
SkipBDDWelcome=YES
_SMSTSOrgName=  Deployment
SkipComputerName=YES
SkipTaskSequence=YES
TaskSequenceID=1
SkipDomainMembership=YES
SkipUserData=YES
JoinDomain=******
DomainAdmin=*****
DomainAdminPassword=*****
UserDataLocation=NONE
SkipProductKey=NO
SkipLocaleSelection=YES
UILanguage=de-DE
UserLocale=de-DE
KeyboardLocale=0407:00000407
SkipTimeZone=YES
TimeZone=110
TimeZoneName=W.Europa Standard Time
SystemLocale=00000407
InputLocale=de-DE
SkipAdminPassword=YES
AdminPassword=******
ApplyGPOPack=NO
SkipCapture=YES
SkipBitLocker=YES
SkipSummary=YES
SkipFinalSummary=YES
FinishAction=LOGOFF
EventService=http://****:9800

Have someone an idea??

Hi,

I've searched the Forum and goggled for an answer to this problem. I found lots of people with the same problem and lots of answers but none of them worked.

My problem is setting "Location" property from MDT deployment TS. I'm currently using MDT 2010 Update 1 and I'm deploying a bare-metal machine with Windows XP SP3 (English language). I'm trying to set the following settings:

• Keyboard - en-US and pt-PT
• Language - Portuguese
• Locale - Portugal
• Time Zone - GMT Standard Time (085)

 Everything works fine, except the "Location" property (Regional and Language Options -> Regional Options tab) that is set for "Hungary"(!?!?) and not "Portugal"!!!

CustomSettings.ini

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
_SMSTSOrgName=IGFCSS - Deployment Sistema Operativo
OSInstall=Y
SkipAppsOnUpgrade=NO
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipTimeZone=YES
SkipLocaleSelection=YES

TimeZone=085
TimeZoneName=GMT Standard Time
UILanguage=pt-PT
SystemLocale=00000816
UserLocale=00000816
KeyboardLocale=0816:00000816
GeoID=193

UserID=mdtusr
UserDomain=fefss
UserPassword=<somesecurepassword>

JoinDomain=fefss
DomainAdmin=mdtusr
DomainAdminPassword=<somesecurepassword>
DomainAdminDomain=fefss
MachineObjectOU=OU=Computadores,OU=IGFCSS,DC=fefss,DC=seg-social,DC=pt

 Bootstrap.ini

[Settings]
Priority=Default

[Default]
DeployRoot=\\IGFCSS-WSUS\DeploymentShare$
_SMSTSOrgName=IGFCSS - Deployment Sistema Operativo
UserID=mdtusr
UserDomain=fefss
UserPassword=<somesecurepassword>

Sysprep.inf

[RegionalSettings]
    LanguageGroup=1
;    Language=00000409
    InputLocale=pt-PT
    UserLocale=pt-PT
    UILanguage=en-US

[GuiUnattended]
    AdminPassword="somesecurepassword"
    OEMSkipWelcome=1
    OEMSkipRegional=1
    TimeZone=085
    AutoLogon="Yes"
    AutoLogonCount=999

Unattend.txt

[RegionalSettings]
; IF this section is used the Winnt32.exe /copysource:lang setting must be specified
    InputLocale_DefaultUser=0816:00000816   ; Specifies the Inputlocal and keyboard setting for default user
    UserLocale_DefaultUser=00000816   ; Locale ID for default User
    InputLocale=0409:00000409,0816:00000816    ; Locale\Keyboard combinations to be installed
    Language=en-US     ; Lanugage locale to be installed
;    LanguageGroup=    ; Language Group to be installed
    SystemLocale=00000816    ; System Locale to be specified
    UserLocale=00000816    ; User Locale setting

[GuiUnattended]
;    Arguments=     ; Used with Detached programs to provide arguments
    OEMSkipRegional=1    ; Indicates Regional info GUI to be skipped in setup
;     EncryptedAdminPassword=No   ; For OEMs allows use of hashpwd.exe cannot be used with autologon
    TimeZone="085"    ; Sets Timezone 010=Mountain
    OemSkipWelcome=1    ; Used to skip welcome screens in GUI setup
;    ProfilesDir=""    ; Allows to change default location of profiles
    AutoLogon="Yes"    ; Indicates that system should autologon after reboot
    AutoLogonCount=999    ; Number of times to auto logon
;    DetachedProgram=""    ; Specifies programs to run concurrently with Setup
    AdminPassword="<somesecurepassword>"

I have tried many possibilities for attempting to get the keyboard layout to default to french instead of english - can someone please help me to find what the settings would be for French?

I am refreshing from XPX86SP2 -> XPX86SP2. Old operating system is French. WIM is French. OS Resource Files are French. The Refresh works fine, except that the Keyboard selection is en-us by default - while it *should* be fr-fr default.

Of course I would like to avoid writing my own custom script as Andrew hates to see....

I tried:

In the customsettings.ini

InputLocale=040C:0000040C

In the Unattend.txt

Keyboardlayout = "France"
Language = 040C
LanguageGroup = 1

I've also looked very closely into Andrew Barnes' blog post from 2010 here (which is what has got me as far as I am now...).

Any help would be greatly appreciated. Thanks.

Started new post from: here

We are using MDT 2012 Update 1 to create Lite Touch deployment via Media. After burning ISO to a USB 3.0 drive, we boot from it and starts deployment until some point in time where after a reboot there is a long hang at "Starting Windows" (5-8min later) Windows starts but the USB Drive appears to have been corrupted or formated, as I am prompted to Format Drive + deployment is asking for correct media to continue?

What is the issue here?

Hello All

So MDT 2012 is supposed to support Windows Embedded POSReady.

I get an error when BCDBoot runs the following command

BCDBoot.exe V:\Windows /l en-AU /s v:

(by the way Microsoft there is only one English in the world and thats the Queens English :) )

I get the error 193

Anyone had any luck with MDT 2012 and WES7 or POSReady 7?

Cheers

Robert

HI im facing issue when executing the Litetouch.vbs for executing the setup.exe for one of our products. Please find the steps that im following

1. I have created MDT share for the product

2. On executing the LiteTouch.vbs, the setup for the product hangs indefinately and it doesnt respond. When i kill the bddrun.exe "The yellow screen is shown saying deployement is not sucessfull" but actually setup resumes. 

Im not getting why bddrun.exe gets hanged. This happens only for my product. and all standard products like SharePoint Foundation server, notepad++ etc works fine. 

Please help!

Hey guys,

I've just setup a new deployment share and now have a custom .wim (with all updates) that I just captured using the Capture and Sysprep task sequence.  I've created a separate Standard Client task sequence for the installation and have updated the deployment share.

I'm testing this using VMware workstation 9, so I've setup my VM and pointed the CDrom to the litetouchpe_x64.iso.  The VM boots up and the installation kicks off fine.  It reboots and sets up devices, but when it starts to apply system settings I get the following error:

Install dialog box:

Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist.

Now I've not made any manual changes to the unattend.xml file (maybe that's the problem?).

I'm fairly new at MDT so forgive me if this is something simple, which I imagine it is.

Thanks,

Marc

Hi Again!

I'm going to make my own version of windows 8 and caputure it via Hyper-v. The only problem I have is that i get this: 
A Connection to the deployment share could not be made .
Connetion: OK Possible error: invalid credentials

my bootstrap.ini is: 

[Settings] 
Priority=Default 
[Default] 
DeployRoot=\\SCCM\MDTBuildLab$
SkipBDDWelcome=YES 
UserDomain=Volltech 
UserID=BuildAccount 
UserPassword=123lol!

CustomSettings.ini like this:

[Settings]
Priority=Default 
[Default] 
_SMSTSORGNAME=Lab 
OSInstall=Y 
SkipAppsOnUpgrade=NO 
SkipAdminPassword=YES 
SkipProductKey=YES 
SkipComputerName=YES 
SkipDomainMembership=YES 
SkipUserData=YES 
UserDataLocation=AUTO 
SkipLocaleSelection=YES 
SkipTaskSequence=NO 
SkipTimeZone=YES 
SkipApplications=NO 
SkipBitLocker=YES 
SkipSummary=YES 
SkipBDDWelcome=YES 
SkipCapture=NO 
DoCapture=YES 
SkipFinalSummary=NO
TimeZone=004 
TimeZoneName=Pacific Standard Time
JoinWorkgroup=WORKGROUP

I've tried to change the network adapter to legacy network adapter, but it was still no go.

Any help?