MDT 2013 / ADK 8.1 Language Bug?

Have a new MDT 2013 Deployment with Windows ADK 8.1 Update. Using the following keyboard settings in customsettings.ini and bootstrap.ini for years:
KeyboardLocale=0807:00000807
KeyboardLocalePE=0807:00000807
The Keyboard PE settings do NOT work when the credentials for the connection to the deployment share have to be provided. Have the US keyboard layout. But when I hit F8, I have the correct Swiss German Keyboard Layout in the command window.
Any advice? Thank you in advance for any help
Franz

Hi,
Generally, you would use GPT for UEFI systems, MBR for BIOS-based systems, on UEFI-based systems, it will create four partitions (boot, MSR, recovery, OS) on a GPT disk.
It should just work, as soon as you figure out how to enable UEFI “native” mode in the firmware (BIOS) settings and then boot in “native” mode.
Alex Zhao
TechNet Community Support

Similar Messages

Is it possible to apply a GPOPACK to Windows 8.1 in MDT 2013/ADK for 8.1

We are aware that SCM does not have a basline for Windows 8.1. I have seen Johan post about adding the code to the ZTIApplyGPOPack.wsf for support for Windows 8.1. Also do we need to update GPOPack.wsf located in \Templates\GPOPacks\Name of GPO
PACK.
So what is the best approach for creating and applying a GPO PACK to Win 8.1?
Thanks

If I remember correctly what I did, this is how I went about it.
1. Create the Windows 8.1 GPO Pack using LocalGPO from SCM 3.0
To use LocalGPO you have to edit "LocalGPO.wsf" to add support for 8.1.
In "Sub ChkOSVersion" just add the lines to provide support for 8.1 (and 2012 R2 while you're there)
To do this, just copy the 4 lines for 8 and 2012, paste them above the lines you just copied, and then edit them
It should look like this after the edit:
If(Left(strOpVer,3) = "6.3") and (strProductType <> "1") then
strOS = "WS12R2"
ElseIf(Left(strOpVer,3) = "6.3") and (strProductType = "1") then
strOS = "Win81"
ElseIf(Left(strOpVer,3) = "6.2") and (strProductType <> "1") then
strOS = "WS12"
ElseIf(Left(strOpVer,3) = "6.2") and (strProductType = "1") then
strOS = "Win8"
Since you are only exporting, this should be the only change that is needed. If you were doing other functions, you would need to edit those.
2. Edit "GPOPack.wsf" in your newly created GPO Pack to provide support for 8.1 (and optionally 2012 R2) in the same way you did above.
3. Copy your GPO Pack to your deployment share
4. Edit "ZTIApplyGPOPack.wsf" to provide support for 8.1 (and optionally 2012 R2) using the same copy, paste, and edit technique that was used above. The section should look similar to below:
If (Left(sOSVersion,3) = "6.3") and oEnvironment.Item("IsServerOS") then
sOS = "WS2012R2"
oLogging.CreateEntry "Using Default Windows Server 2012 R2 GPO Pack", LogTypeInfo
ElseIf (Left(sOSVersion,3) = "6.3") and Not(oEnvironment.Item("IsServerOS")) then
sOS = "Win81"
oLogging.CreateEntry "Using Default Windows 8.1 GPO Pack", LogTypeInfo
ElseIf (Left(sOSVersion,3) = "6.2") and oEnvironment.Item("IsServerOS") then
sOS = "WS2012"
oLogging.CreateEntry "Using Default Windows Server 2012 GPO Pack", LogTypeInfo
ElseIf (Left(sOSVersion,3) = "6.2") and Not(oEnvironment.Item("IsServerOS")) then
sOS = "Win8"
oLogging.CreateEntry "Using Default Windows 8 GPO Pack", LogTypeInfo
5. If you use the standard naming convention for your GPO Pack, you are done. In other words, if you name your GPO Pack "Win81-MDTGPOPack", then you don't have to worry about adding anything to your customsettings.ini. It will automatically know
to use this one for your Windows 8.1 Task Sequences.
It would be nice if Microsoft fixed all this in the next update of MDT2013 and SCM.
Hope this helps

MDT 2013, OSDComputerName in customsettings.ini issue.

Hi all just wanted to post this since I was running into this issue at my workplace. Upgraded to MDT 2013 recently, thought some more bugs would be worked out by now. One in particular I found was with my customsettings.ini. Now since I
upgraded you can obviously tell I was utilizing MDT in 2010 and 2012 versions before this. SO I simply updated my deployment share, I did not create a new one. Our current customsettings.ini was layed out as so below:
[Settings]
Priority=TaskSequenceID, Default
[Default]
_SMSTSORGNAME=%TaskSequenceID% on %OSDComputername%
SkipAdminPassword=YES
SkipApplications=NO
SkipAppsOnUpgrade=YES
SkipProductKey=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=NO
SkipComputerBackup=YES
SkipDeploymentType=YES
SkipLocaleSelection=YES
SkipUserData=YES
SkipWizard=NO
DeploymentType=NEWCOMPUTER
DoNotCreateExtraPartition=YES
KeyboardLocale=en-US
OSInstall=YES
UILanguage=en-US
UserID=(redacted)
UserLocale=en-US
UserDomain=(redacted)
UserPassword=(redacted)
TimeZone=035
TimeZoneName=Eastern Standard Time
EventService=(redacted)
[WW-STAFF-WINXP]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=YES
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[TEST-WW-WIN7X86]
_SMSTSORGNAME=WW Win7 Test Image on %OSDComputername%
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=YES
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-STAFF-WINXP-2]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=YES
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-CLASIMG-WINXP]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=NO
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-STAFF-WIN7X86]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=YES
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-STAFF-WIN7X64]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=YES
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
Now this seems pretty straight forward. Based on task sequence you choose you get alternate settings. Well since the move to mdt 2013 the alternate setting, in particular the skip computer name, skip domain membership and osdcomputer name fields
were not working. It would prompt for computer name and domain membership every time. So after a bit of troubleshooting, and NO HELP whatsoever from the researching online, I discovered it no longer will detect unless those particular exceptions
are under the default profile instead of separate task sequence id's. Hopefully this will be an easy update fix in the future, but who knows. Luckily I can still run my setups without issue with it in the default portion. Fixed customsettings.ini
below:
[Settings]
Priority=TaskSequenceID, Default
[Default]
_SMSTSORGNAME=%TaskSequenceID% on %OSDComputername%
SkipAdminPassword=YES
SkipApplications=NO
SkipComputerName=YES
OSDComputerName=(redacted)
SkipDomainMembership=YES
SkipAppsOnUpgrade=YES
SkipProductKey=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=NO
SkipComputerBackup=YES
SkipDeploymentType=YES
SkipLocaleSelection=YES
SkipUserData=YES
SkipWizard=NO
DeploymentType=NEWCOMPUTER
DoNotCreateExtraPartition=YES
KeyboardLocale=en-US
OSInstall=YES
UILanguage=en-US
UserID=(redacted)
UserLocale=en-US
UserDomain=(redacted)
UserPassword=(redacted)
TimeZone=035
TimeZoneName=Eastern Standard Time
EventService=(redacted)
[WW-STAFF-WINXP]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[TEST-WW-WIN7X86]
_SMSTSORGNAME=WW Win7 Test Image on %OSDComputername%
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-STAFF-WINXP-2]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-CLASIMG-WINXP]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-STAFF-WIN7X86]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT
[WW-STAFF-WIN7X64]
_SMSTSORGNAME=%TaskSequenceName% on %OSDComputername%
SkipTimeZone=NO
SkipFinalSummary=NO
FinishAction=REBOOT

Check your task sequence, go the the "Gather" steps, there are three of them in the default standard client task sequence, and verify that instead of "Gather locally", "Use this file to process the rules" is checked, and provide the following text: CustomSettings.ini,
do this on all the three steps, try again and let us know!
Also not sure what happens, but I would definitely paste the TaskSequenceID specified rules above the Default section. I know that priority provides in which orders the rules needed to be processed, but still I would post them above Default.
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

SCCM 2012 R2 and MDT 2013 Task Sequence Bugs

Any links that list issues with the default MDT 2013 deploy task sequence: UEFI, local administrator password, Machine OU settings, OS installation partition and computer replace scenario.

Hi,
If you want to file bugs or feature requests, you'll need to go to the MDT and ConfigMgr connect site:
https://connect.microsoft.com/ConfigurationManagervnext/Feedback
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Workbench says ADK is not present - MDT 2013

Hey everybody!
I'm doing some deployment testing with MDT but I can't seem to get past a particular error. When I open the Deployment Workbench, it asks me to download the ADK for Windows 8.1. However I can only find ADK for Windows 8 or Windows 8.1 Update 1, no download
for JUST 8.1 (Microsoft, you confused the heck out of people with this one :p).
I also am trying to run the Windows 8.1 Update ADK but it says I need to install the Windows 8.1 ADK before I can install the latest version.
Any suggestions on this? Microsoft should've left all version links up and running for deployment purposes.

It's best to completely ignore the "Components" node in MDT 2013 because it's out of date and incorrect. (It will be removed in the future.) If you have the ADK for Windows 8.1 installed and are using MDT 2013, you're good.
Thanks,
-Michael Niehaus
Senior Product Marketing Manager, Windows Deployment
http://blogs.technet.com/mniehaus
[email protected]

Installing Windows ADK and MDT 2013 without Internet

Hi
I have Windows 8.1 Update 64 bit
on a computer without Internet.
I would like to install Windows ADK
and MDT 2013. What's the proper procedure to
do this?
Thanks
Bye
Balubeto

You need to download the pieces from an internet-connected machine. They can they be copied (USB or whatever) to any machine, even those without an internet connection, to do an installation.
To get the necessary ADK pieces, download ADKSETUP.EXE and run it on the internet-connected machine. It will offer an option to download all the rest of the ADK pieces (make sure you select the right components) into a folder you specify.
The MDT installation is a single MSI file.
Thanks,
-Michael Niehaus
Senior Product Marketing Manager, Windows Deployment
http://blogs.technet.com/mniehaus
[email protected]

Windows ADK and MDT 2013 components

Hi
I noticed that Windows ADK is
installed in its 32 bit version even though I have
Windows 8.1 Update 64 bit.
It is correct?
Then, I installed MDT 2013
64 bit.
Now, where can I find a detailed description
about the components of this MDT?
Having to customize, deploy and create some
DVDs of Windows 8.1 Update
32/64 bit, what components
should I download?
Thanks
Bye
Balubeto

Yes, there are some weird historical reasons why the AIK goes to "\Program Files (x86)" and MDT goes to "\Program Files". Don't over think it too much, yes it's confusing.
Some recommendations (what I install on my machine):
Your deployment Server box should be running Windows Server 2008 R2 x64 or Server 2012 x64.
You should be deploying only Windows 7 or newer (Windows 8.1) or Server 2008 R2 or newer (2012)
Use the latest AIK
http://www.microsoft.com/en-us/download/details.aspx?id=39982 the ADK is platform agnostic, it will install on x86 or x64, but of course your server should only be x64
Install the latest MDT 2013
http://www.microsoft.com/en-us/download/details.aspx?id=40796 x64 version.
MDT documentation *.chm is in the MDT install directory.
AIK documentation *.chm is in the ADK install directories.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013 Sysprep Bugs

I am curious if anyone know any bugs with MDT 2013 sysprep as it relates to Windows 8.1 or any differences in sysprep from MDT to SCCM 2012 R2. Reason why I am asking is that I posted to this news group earlier today asking:
If 10 minute logon time while it goes through the screens "installing your applications ", "taking care of a few things", and "getting your apps ready" is normal when creating and capturing the image with MDT 2013. I have
also done the same test simply pushing out the install.wim with SCCM 2012 and my logon times are 2-3 minutes.
I have more information and I suspect the problem is with the sysprep process with MDT 2013. What I did is I used MDT 2013 to simply create the reference system. I then used SCCM Capture Media to capture the reference machine and create the wim. Once I deployed
that wim with SCCM I noticed logon times were about 1 minute. Much quicker than what I am seeing with creaeating the reference machine and capturing with MDT and then deploying with SCCM.
I know the initial logon times will take some time while the Modern Apps do get installed. I am just not sure why it is 95 percent faster when I don't capture it with MDT. That is why I think MDT with sysprep is the culprit.
Any help would be greately appreciated.
Thanks,
Mike
Solutions Architect

Parsing step node: Execute Sysprep TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
Description: TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
ContinueOnError: false TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
SuccessCodeList: 0 3010 TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566)
TSManager 06/30/2014 9:10:57 PM
2268 (0x08DC)
No condition is associated with the step. TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
Disable: false TSManager
06/30/2014 9:10:57 PM 2268 (0x08DC)
This portion was interesting inside my SMSTS.log in the appdata/temp directory. Hope this helps a tad.

MDT 2013 deploying OS from USB Flashdrive failed - need to click OK everytime

We are using MDT 2013 with ADK 8.1 and deploying Windows 7 x64 using media (USB Flashdrive). We can successfully deploy Windows 7 x64b using ethernet cabel but not via USB-Flashdrive. This problem appears on all our HP EliteBook
Series, old as new computers series. We can boot into WinPE 64 bit and start the proper task sequence, all image is applied then after restart, after the logon screen appears there is an error saying that cannot find "USB media?".
But after clicking "OK" it works fine until next reboot, same thing again, but the drive is recognized!
I downloaded all USB drivers from HP website that holds USB 2.0 and 3.0 and drivers that contains open driver files like .inf and .dll files and injected them with the "Profile" that contains all drivers and packages.
It seems like it needs a timeout because of the script is trying to early to find the USB-flashdrive.
Any ideas?
Sorry for language, but you get the Point.
Best regards

Hi,
I would like you to clarify following questions with me:
1. Did you keep the USB plugged in during the restarting?
2. Have you make any task sequence to install applications after log in? If so, have them been installed properly?
Then, please help to collect a boot trace to let me know the details:
How to collect a good boot trace on Windows 7
http://blogs.technet.com/b/jeff_stokes/archive/2012/09/17/how-to-collect-a-good-boot-trace-on-windows-7.aspx
Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
Kate Li
TechNet Community Support

MDT 2013: bootstrap.ini not applying username and password for share access

I customized my bootstrap.ini file to skip the welcome screen, set keyboard locale, and enter a service account username and password for share access. The welcome screen skip and keyboard locale work beautifully but it's not applying the share username/password/domain
at all.
bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\mydeploymentserver\DeploymentShare$
UserID=myuserid
UserDomain=mydomain.com
UserPassword=mypassword
KeyboardLocale=en-US
SkipBDDWelcome=YES
I verified that the unattend.xml file on the MININT volume during deployment had all of this information populated correctly:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallFrom>
<Path>\\mydeploymentserver\deploymentshare$\Operating Systems\Windows 7 x64 with District Software - 06222014\Windows 7 x64 with District Software - 06222014.wim</Path>
<MetaData>
<Key>/IMAGE/INDEX</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username>myusername</Username>
<Domain>mydomain.com</Domain>
<Password>mypassword</Password>
</Credentials>
<JoinDomain>mydomain.com</JoinDomain>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName>eos-vm-02</ComputerName>
<RegisteredOrganization>Regional School District 19</RegisteredOrganization>
<RegisteredOwner>Information Technology</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>http://www.eosmith.org</Home_Page>
<DisableWelcomePage>true</DisableWelcomePage>
<DisableFirstRunWizard>false</DisableFirstRunWizard>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TapiConfigured>0</TapiConfigured>
<TapiUnattendLocation>
<AreaCode>""</AreaCode>
<CountryOrRegion>1</CountryOrRegion>
<LongDistanceAccess>9</LongDistanceAccess>
<OutsideAccess>9</OutsideAccess>
<PulseOrToneDialing>1</PulseOrToneDialing>
<DisableCallWaiting>""</DisableCallWaiting>
<InternationalCarrierCode>""</InternationalCarrierCode>
<LongDistanceCarrierCode>""</LongDistanceCarrierCode>
<Name>Default</Name>
</TapiUnattendLocation>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>administratorpassword</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>administratorpassword</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<RegisteredOrganization>Regional School District 19</RegisteredOrganization>
<RegisteredOwner>Information Technology</RegisteredOwner>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>
... and the bdd.log file appeared not to read the username and password at all:
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property Debug is now = FALSE]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Cleaned up a dirty deployment.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS TargetDisk: \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[GetPartitions: 2]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Target Partition not big enough: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Drive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found FirstPossibleSystemDrive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property SMSTSLocalDataDrive is now = D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to BCDStore.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE or WinRE.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentMethod is now = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentType is now = NEWCOMPUTER]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property inifile is now = Bootstrap.ini]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Object Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSCurrentVersion is now = 6.3.9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSCurrentBuild is now = 9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSVersion is now = WinPE]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServerOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServerCoreOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property definition is now = BDD_Welcome_ENU.xml]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property HALName is now = acpiapic]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Checking network adapter: [00000001] Intel(R) PRO/1000 MT Network Connection]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[MAC address = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[IP Address = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[IP Address = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Default Gateway = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IPAddress001 is now = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IPAddress002 is now = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property MacAddress001 is now = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DefaultGateway001 is now = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Unable to determine ConfigMgr distribution point]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Not Wizard = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WizardComplete is now = N]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WDSServer is now = mydeploymentserver.mydomain.com]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property HostName is now = MININT-U1TGFAD]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting asset info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile: The file x86\Microsoft.BDD.Utility.dll could not be found in any standard locations.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 1]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[RUN: regsvr32.exe /s ""]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 0]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[RUN: regsvr32.exe /s "X:\Deploy\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property AssetTag is now = No Asset Tag]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SerialNumber is now = VMware-42 05 2b f7 cd 5b 63 fd-83 8a 77 84 7c ed 79 05]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Make is now = VMware, Inc.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Model is now = VMware Virtual Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Product is now = 440BX Desktop Reference Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property UUID is now = F72B0542-5BCD-FD63-838A-77847CED7905]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Memory is now = 2047]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Architecture is now = X64]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property ProcessorSpeed is now = 2800]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property CapableArchitecture is now = AMD64 X64 X86]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsLaptop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsDesktop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServer is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsUEFI is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsOnBattery is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsX86 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsX64 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsSLAT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting asset info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting OS SKU info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Unable to determine Windows SKU while in Windows PE.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Determining the Disk and Partition Number from the Logical Drive X:\WINDOWS]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsHypervisorRunning is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsVT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsNX is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Supports64Bit is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsHyperVRole is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsVM is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property VMPlatform is now = VMware]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Connection succeeded to MicrosoftVolumeEncryption]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[There are no encrypted drives]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsBDE is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Processing the PREINSTALL phase.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Using from [Settings]: Rule Priority = DEFAULT]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------ Processing the [DEFAULT] section ------]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DEPLOYROOT is now = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Using from [DEFAULT]: DEPLOYROOT = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------ Done processing X:\Deploy\Scripts\Bootstrap.ini ------]LOG]!>

Basics - Server 2008 R2 - SP1, WDS, MDT 2013
Well all, I've done this at least 20 times today and the deployment share info is still wrong...
Someone else built and messed with this thing so i'm trying to fix it. We have 2 MDT servers and 1 WDS that is on the Production MDT. I've turned the test MDT off.
It was working fine, until I updated the deployment share ... after adding some drivers for the surface pro 3 for the pxe boot
Very Simple bootstrap.ini
[Settings]
Priority=Default
[Default]
DeployRoot=\\MMPDEPLOY02\DeploymentShare$
UserID=xxx
UserDomain=xxx
UserPassword=xxx
KeyboardLocale=en-US
SkipBDDWelcome=YES
It continues to show up on the client as ||mdt901w8|deploymentshare$ (test server) (pipes for \ since it makes it a link and i'm new)
I've deleted all the .wim and associated files from all locations from the deployment share\boot folder and from the wds remote install\boot\x64\images folder where they are instead of the remote install\boot\images folder that everyone refers to.
I really can't figure this one out... I know it's something simple I'm over looking but I can't see it..
Any ideas..

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

MDT 2013: WinPE Screen Resolution for Tablets not adapted

Hello guys,
I'm using MDT 2013 to deploy Windows 8.1 on tablets.
So, after generated the boot image including the right drivers inside, I boot up my tablets through WinPE (Boot on LAN).
Once WinPE initiated, I'm now in the Deployment Welcome Screen with a very low resolution. The welcome screen filled the entire screen. Worse, the next window is bigger than the screen.
So my question is, how to handle with this behaviour?
Thanks guys in advance for your help,

Hi,
Thanks for your help.
I've read few posts about injecting an Unattend.xml file in the boot image including this link you mentionned.
I'm not sure to be right but what I did is the following:
1) create a file called Unattend.xml with the following content:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
</component>
</settings>
</unattend>
2) put it in my "extrafolder" in order to be imported when I create the boot image through MDT.
3) once created, checked that the Unattend.xml file is in the root of my boot image wim file
4) import the new boot image into WDS
So, I've tested the new boot image in at least 3 different kind of computers (tablet, laptop and desktop), the result is the same: the machines restart automatically when they try to load the MDT Welcome environment.
What's wrong?

MDT 2013 - Create New User

Hello,
I've recently setup MDT 2013 to deploy some customized images that we deploy to student laptops, that were sysprep-ed and captured with ImageX. I've uploaded the custom image WIM files to MDT, and setup a task sequence. Almost everything works,
thanks to Microsoft documentation and searches of this forum for various questions I've had, however I'm stuck on two items:
1.) MDT forces an administrator account to be created during the process. That's not such a huge issue, but I'd like to disable the administrator account at the end of the task sequence. I'm not sure where/what to add to do this.
2.) We would like the machine, after imaging, to deploy the generic Windows Welcome, as if it had just been purchased from the OEM. This way when the student receives the imaged laptop, they can create their own personal account. These laptops are
not bound to AD. Right now, when the task sequence finishes the systems are logged in as an administrator. Again, I'm not sure what code to add to the task sequence (and where) to accomplish this.
Any information or links on what I'm looking for would be greatly appreciated. I'm sure that both these items are possible, but I'm not using the proper terminology on my searches to find the information I'm looking for. Thanks!

I question the usage of MDT in this scenario. I also question your premise that your users should go into OOBE Setup.
MDT is designed to assist IT departments in getting windows up on machines in a End to End scenario.
MDT prompts which Task Sequence, Language/Locale/TImezone, Applications, drivers, and User Data Migration Status. Once the TAsk Sequence has started, MDT should be as automated as possible. No prompts, no user interaction.
What you are asking for is the opposite, you want user interaction during deployment, and rather than customizing each deployment, the image is pre-configured. (Unless you have different *types* of machines that require driver loading via MDT).
IN your case I would recommend just slapping an install.Wim up on a WDS server, and custom crafting an unattend.xml file to prompt each user for user accounts. (as long as you don't have to worry about drivers).
The other solution is to prompt the user for their new user account from the MDT wizard, and slam that into the machine during the task sequence (and removal of the Administrator account with net user administrator /active:no )
I actually created a powershell script to accomplish this:
http://keithga.wordpress.com/2013/09/24/microsoft-account-automation-in-windows-8/
This alternative solution is MDT 400 level work. Scripting required. :^(
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

WIndows Enterprise 8.1 - MDT 2013

Hi All
I'm using MDT2013 and ADK 8.1.
I am trying to create a new Windows 8.1 ent build and am having a few strange issues...
I have created a standard TS for the initial build, when I deploy the TS everything works as expected except the build doesn't seem to have all the Modern UI apps installed. At first I assumed this may be a slight change MS made and the builtin
administrator account just doesn't have them installed anymore.. But when I create a new local user account and log in I still don't have any of the apps installed. All that is present on the start screen is IE - Store - File explorer - Skydrive
and desktop, things like weather, news, sport and so on don't seem to be installed in the default user profile..
I manually built a machine from the media and the apps do seem to be installed. I know during the default install the default admin account gets disabled and a new account is created. This account does have all the apps installed, so on here
when you add a new user these apps are present..
Am I missing something here (hopefully something simple :-))? is there something specific I need to add to my unattend.xml file to allow the apps to be installed? do I need to create a new user account during the build to allow the apps to install?
I followed the same process when I created a windows 8.0 build and didn't have any of these issues.
Thanks for any advice.. Simon

I have had the same issues. We are just migrating a school to full windows enterprise 8.1 -- God Help us.
The first issues we had were related to USMT5 not beiong available. Disabling these steps from the task sequence rectified it and the build to 8.1 is now very quick. However there are no APPS such as News and many more - they're simply not present on the
machine.
We have 150 machines to automatically set running on Friday night 20th 12 -2013 .... the expectation is we can complete the whole build on Monday and Tuesday and be able to eat a Turkey the following day. I'm worried this isn't going to be the case and I'm
expecting Turkey sandwiches.
Enough laughter:
New build of MDT 2013 complete with all the latest ADKs associated with it including VAMT 3.1 (SQL) becasue that's the only quick way to licence them. (keys not compatable with older versions or even when wrapped into MDT TS).
Using a USB drive to deploy the same media results in a good install. Auto build using MDT gives you just 5 Apps.
1. IE
2. Store
3. File Explorer
4. SkyDrive
5. Desktop
That's it -- no good to me or many others on here by the looks. It would appear from reading JECOMPUTER4MEs last post that he may be onto something with the administrator accounts, however this surely can't be regarded as a good fix and it's certainly
not something my timescales allow for. In all honesty it would be quicker using USB media and then manually carrying out a domainjoin.
A few of the apps are available to pin to the start. Which is fine as we can sort this using GPO, these apps are things like Travel and Photos. However there are still a plethera of standard apps missing such as news, weather, calendar and finance to mention
a few.
Watch this space, I'm having to work for a fix as soon as possible and hope someone can post some helpful pointers into this forum soon.
Thanks
Matt

MDT 2013 - Different settings per task sequence

Hi,
I'm trying to create different settings for different TaskSequenceIDs. For one TS I wanted to join the pc to a workgroup and do SkipApplications=YES and for the other TS I wanted to join a domain and do SkipApplications=NO. But I can't get it to work for
some strange reason.
I've tried and tested this solution https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content but it doesn't work.
I tried this too : http://www.the-d-spot.org/wordpress/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/ but it doesn't work.
Perhaps MDT 2013 acts different then 2012 and 2010???? It would be nice if you could help me out on this one. :-)
Paul

@fapw, we use the database for a few years now and we're quite familiar with it. But we're going to install MDT for a client and they don't have SQL and they don't want to have it installed on one of their servers. So that's why I'm playing with the customsettings.ini.
The first I made was for a plain and simple capture, then I added Make&Model and I'm making it more and more complex. The idea is to have a final customsettings.ini that imitates - or gets as close as possible to - what we have already accomplished with
the database.
In the meantime I've read that the skip-panels-stuff is something that stands above everything and thus it's not possible to control that using properties, like f.ex. MACaddress. Well, that's alright then.
But I've got GOOD news for you all : selecting values for variables based on TaskSequenceID DOES WORK in MDT 2013 and ADK 8.1. This is what I did :
https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content
So I've downloaded the vbs, created an "external" tasksequenceid.ini which is read at the beginning of my Task Sequence and booted up the pc. When you select the tasksequence of your choice the parameters get filled in correctly ! OSDComputername
was the variable that I used to show me if the other tasksequenceid.ini file was read or not. If yes, the computername would have to be my value, if not it would be MININT-randomnumber.
Only downside of this fantastic wizard is that going back to change one of your options is not possible anymore. The moment a variable has a value, it doesn't change anymore! That particular behaviour was messing up my tests yesterday.

MDT 2013 / ADK 8.1 Language Bug?

Similar Messages

Maybe you are looking for