[MDT] Sysprep and capture, and OOBE

Hi my friends, I'm experiencing a little issue.
I want to deploy custom images with OOBE. In other terms, when a client boot his computer for the first time, I want Welcome window display, and ask for account name, etc.
But now, when I boot client computer, it auto-signs in to an administrator session and finish MDT deployment. Please help me understand.
Let's me explain how i proceed. First, I installed with an iso file my Windows, and when I get welcome windows, I enter in audit mode to add some programs etc. Then I launched my \\ServerMDT\DeploymentShare$\Scripts\LiteTouch.vbs to start Sysprep.
It reboots, and I am able to boot PXE and start capturing. Works like a charm. Now I upload my captured image in another DeploymentShare using a Standard Client Task Sequence to deploy my captured image. I updated my new DeploymentShare, etc.
The deployment looks to work great. But when it reboots, it signs in without asking for password or else, and finalize deployment. My programs are here, it is OK. But I haven't my OOBE.
What I misunderstood ? Help me guys...

OK. I finally achieve this after two long days. For those who will be interested, this is my little how to.
http://snajdan.com/?p=580

Similar Messages

Administrator Account Disabled after sysprep and capture task sequence in MDT 2010

Hi
We are currently migrating from Windows XP to windows 7. As part of our migration we have 5 base Images (for different areas of the business)
Here is what we are doing:
Create a reference machine with the source files for windows 7 Pro x86
Install applications as part of the Task sequence to build a reference machine.
Make the updates to the machine - required for the build.
Run the Sysprep and capture template to take the capture of the Reference machine.
Import the Capture into the Operating system folder within MDT2010
Create a task sequecne to deploy the image.
Deploy the Image for Testing.
Deploy the image to a machine
Update the machine with the defects
Re Capture the deployed machine and call it ver2.wim
re deploy ver2.wim
Testers test
Defects logged + additional user settings to be captured in the build
Re capture and sysprep runs says the capture has been succesful however after a reboot the administrator account is disabled.
We cant seem to capture anything from here on in. Nothing has been changed in the unattend.
Autologon is set to enable the administrator account and the password is set to blank as this is then handled by policy when the machine is joined to the domain - we have not enabled the unattended join to the domain at this point in time but it will be
for deploying the image.
Have we got our image strategy wrong? does the same rule apply about sysprep running more than 3 times on a single machine if it is captured and redeployed after a sucessfully sysprep to the same hardware or even different hardware.

Hi,
    One of the things Sysprep/WAIK do is disable the adminsitrator account.
    You mentioned that you are setting the autologing to the administrator account and that you are setting it with a blank password, you can add a simple command in to sysprep's xml to reenable the account:
<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">
<Order>1</Order>
<Path>net user administrator /active:yes</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
   Give it a try and let us know .
Best Regards, Marianok
Saludos, MarianoK
Disclaimer: While I do my best to make sure everything I post is accurate and safe, I’m certainly not perfect so all this information is provided "AS IS" with no warranties or guarantees and confers no rights. Any suggested steps or code provided should be
done under your own risk, I take no responsibilities if your system blows, the universe stops spinning, o nor for any other adverse consequence the information on this code might cause directly or indirectly.
Aclaración: Aunque hago lo posible por verificar que todo lo que posteo es correcto y seguro, Yo ciertamente no soy perfecto y puedo cometer errores, por lo tanto esta informacion es provista "AS IS" / "Como Está" sin garantía alguna y no le confiere ningún
derecho. Cualquier instrucción descripta o código incluido deben ser empleados bajo su propia responsabilidad y bajo su propio riesgo. No me hago responsable si sus datos se dañan, su si
Hi Marianok,
Thanks for your response and taking the time to read the topic we have raised. We believe we already have this step in place but perhaps we have it in the wrong area of the unattend.
Please find below our unattend file for the capture:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" 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>1</PartitionID>
</InstallTo>
<InstallFrom>
<Path>.\Operating Systems\Windows 7 Install Media x86\Sources\install.wim</Path>
<MetaData>
<Key>/image/index</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<UpgradeData>
<Upgrade>false</Upgrade>
</UpgradeData>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
<ProductKey>
<Key></Key>
</ProductKey>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" 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="x86" 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="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username></Username>
<Domain></Domain>
<Password></Password>
</Credentials>
<JoinDomain></JoinDomain>
<JoinWorkgroup></JoinWorkgroup>
<MachineObjectOU></MachineObjectOU>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName></ComputerName>
<ProductKey></ProductKey>
<RegisteredOrganization>OurCompanyNameHere</RegisteredOrganization>
<RegisteredOwner>Windows User</RegisteredOwner>
<TimeZone></TimeZone>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" 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>about:blank</Home_Page>
<IEWelcomeMsg>false</IEWelcomeMsg>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" 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>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="x86" 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="x86" 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="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>QQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Description>Temp account</Description>
<DisplayName>Temp account</DisplayName>
<Group>Users</Group>
<Name>TempAccount</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain></Domain>
<Password>
<Value>UABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</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>cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript.exe D:\MININT\Scripts\LiteTouch.wsf /start</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>2</Order>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript.exe E:\MININT\Scripts\LiteTouch.wsf /start</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>3</Order>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript.exe F:\MININT\Scripts\LiteTouch.wsf /start</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>4</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
<RegisteredOrganization>Ourcomapanynamehere</RegisteredOrganization>
<RegisteredOwner>Windows User</RegisteredOwner>
<TimeZone></TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" 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>
<cpi:offlineImage cpi:source="catalog://pr-dep-03/captureshare$/operating systems/windows 7 install media x86/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Hope this helps!

Sysprep and Capture Task Sequence Fails "Can not find script file C:\LTIBootstrap.vbs"

I've just installed Windows 8 on a Lenovo ThinkPad T440s using Lenovo's recovery discs. I did not join it to a domain. I logged in as Administrator, navigated to our deployment share, and ran Scripts\LiteTouch.wsf. I selected the new Sysprep and Capture
Task Sequence that I just made, told it to upload to DeploymentShare$\Captures, then started the Task Sequence.
It seemed to run fine until after the first reboot. Windows 8 configured the PC for a while, then displayed an error that it had been shut down unexpectedly. I wasn't sure if this was normal, so I just clicked OK. Then I got an error that said "Can
not find script file C:\LTIBootstrap.vbs". After clicking OK on that, I am brought to the desktop.
The image cannot be found in DeploymentShare$\Captures. Under the Monitoring section of the DeploymentWorkbench, I can see that MDT thinks the Task Sequence is still running on the machine (though it is not), with progress stuck on step 16 of 23: Execute
Sysprep. There are 0 errors and 0 warnings listed.
BDD.log is too long to post all of it, but here's the last few lines in case that's helpful.
<![LOG[BCD> The operation completed successfully.]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Run Command: C:\windows\SYSTEM32\bcdedit.exe /default {d22e7e91-9ee7-46eb-89d7-c5859e4302f0}]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCD> The operation completed successfully.]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property BootPE is now = True]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI Windows PE applied successfully]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41019 sent: LTI Windows PE applied successfully]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTIApply processing completed successfully.]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
I would greatly appreciate any assistance determining what went wrong and how to correct it. Thank you.

You might get teh c:\LTIBootStrap.vbs error if you are running SysPrep with a unattend.xml template that contains the c:\bootstrap.vbs template, yet you are *NOT* deploying the image with MDT Litetouch, instead just applying the image to the final machine.
Crack open your install.wim file and search for the unattend.xml file in the normal places to see what it is.
I am concerned about the "shut down unexpectedly" error. There should be no shutdown state information left from a captured *.wim file.
If you still need assistance, please feel free to copy the bdd.log file to a public site like OneDrive, and share the link.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Adding Office causes MDT to stop at sysprep and display "Can not find c:\LTIBootStrap.vbs"

I'm new to MDT. I can use the standard TS template to install, sysprep and capture a vanilla Windows 8.1 to an image and deploy that image to a new computer. No problem.
I added MS Office 2013 as an application. If try to add Office 2013 to the reference image, by selecting it in the setup wizard, MDT stops at the sysprep stage, the reference machine reboots, goes through the "we are setting thing up for you...",
then displays "Can not find LTIBootStrap.vbs".
I'm using a Generation 2 VM for the reference image, with the x64 boot iso media. The only way to start it is to change the boot order from file "bootmgfw.efi" back to the .iso. The capture stage then continues. The captured image
then seems to be corrupt as the local list is blank so the deployment cannot continue.
Why does installing Office 2013 to the reference image cause this problem? Vanilla OS images don't have this problem. What am I doing wrong? I'm quite new to MDT but can't find an answer to this.
Thanks.

I am running into the same error. Win 8.1 build 9600 ISO install to a gen 2 VM. Office 2013 32 bit. I can get the TS to run all the way through and capture if I leave windows updates off in the TS. As soon as I turn on the updates I get
the error (Can not find LTIBootStrap.vbs) at sysprep and capture stage. Good to know it worked for you on gen 1 VM. I am trying that now and will report.

Windows Could Not parse or process unattend answer file for pass [specialize] after WDT Litetouch 'sysprep and capture'

I setup an ACER VM6620G (Win7x86) how I wanted, including disabling the administrator account and creating an administrator user "PVA"
Navigated to \\wds\DeploymentShare$\Scripts and ran the litetouch script. Chose my "Sysprep and Capture" task.
Everything went off without a hitch until I restarted the technician pc.
I got the dreaded
"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"
I tried to deploy the captured image to the same computer and got the same error
I've scoured the internet for solutions (Shift+10 opens command prompt. Good to know!) with no luck.
I've saved the unattend.xml and looked for errors- going as far as to install an x86 Win7 virtual machine to validate the unattend.xml file in WISM
Other information that might be useful:
I never used WISM to create an unattend.xml nor did I attach one to the image.
I didn't try to copy user profiles/settings/migrate etc
I imported the captured image to WDT. Created a standard task and added 2 nodes
-Inject Drivers
-Install Application
As a side, I've got another image that I've already injected the drivers/installed the application as a test. Everything went smoothly.
+-----------------+
| Unattend.xml:
+-----------------+
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" 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>\\10.0.0.1\deploymentshare$\Operating Systems\ACER Win7 x86 Capture\ACER Win7 x86 Capture.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="x86" 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="x86" 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="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<JoinWorkgroup>WORKGROUP</JoinWorkgroup>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName>PVA-PC</ComputerName>
<RegisteredOrganization>PVA</RegisteredOrganization>
<RegisteredOwner>PVA</RegisteredOwner>
<TimeZone>"Eastern Standard Time"</TimeZone>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" 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>about:blank</Home_Page>
<IEWelcomeMsg>false</IEWelcomeMsg>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" 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="x86" 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="x86" 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="x86" 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="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value></Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value></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>PVA</RegisteredOrganization>
<RegisteredOwner>PVA</RegisteredOwner>
<TimeZone>"Eastern Standard Time"</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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="x86" 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>

https://skydrive.live.com Here's the end of the log file:
2013-03-27 17:39:05, Info 2013-03-27 17:39:05, Info 2013-03-27 17:39:05, Info 2013-03-27 17:39:05, Info 2013-03-27 17:39:05, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Error 2013-03-27 17:39:06, Error 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Error 2013-03-27 17:39:06, Error 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Error 2013-03-27 17:39:06, Info 2013-03-27 17:39:06, Info Also, here's my [Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
SkipDomainMembership=YES
DomainAdmin=Administrator
DomainAdminDomain=go.local
DomainAdminPassword=************
SkipTimeZone=YES
TimeZone="035"
TimeZoneName="Eastern SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
Bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\10.0.0.1\Dep UserID=Administrator
UserDomain=go.local
UserPassword=***********
KeyboardLocale=en-US
SkipAdminPassword=YES
SkipProductKey=YES
SkipBitLocker=YES /redir?resid=55C3109D61329D02!108&authkey=!AG793wDwQuFZa1s
CMI CBS_Core_Finalize:Calling cbs core finalize complete
CMI Callback_CMI_ConfigInstall: CBS startup processing re-run complete.
[0x030023] CMI Callback_CMI_ConfigInstall: Exit.
[setup.exe] UnattendSearchExplicitPath: Found unattend file at [C:\windows\Panther\unattend.xml]; examining for applicability.
[setup.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [specialize] at [C:\windows\Panther\unattend.xml].
IBS Callback_Unattend_InitEngine:Using unattend file found at [C:\windows\Panther\unattend.xml].
[setup.exe] ValidateSMIPass: serialized settings stream; status 0x00000000
[setup.exe] ValidateSMIPass: construct settings context; status 0x00000000
[setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-IE-InternetExplorer, Language: neutral, ProcessorArchitecture: x86, PublicKeyToken: 31bf3856ad364e35, VersionScope: nonSxS, /settings/IEWelcomeMsg
[setup.exe] SMI data results dump: Description = Setting is not defined in this component.
[setup.exe] ValidateSMIPass: load SMI settings; status 0x00000001
[0x060432] IBS The provided unattend file is not valid; hrResult = 0x80220001
[0x060565] IBS Callback_Unattend_InitEngine:The provided unattend file [C:\windows\Panther\unattend.xml] is not a valid unattended Setup answer file; hr = 0x1, hrSearched = 0x1, hrDeserialized = 0x0, hrImplicitCtx = 0x0, hrValidated = 0x1, hrResult = 0x80220001
IBS UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure...
IBS UnattendDumpSetting: ------Unattend setting error / warning------
IBS UnattendDumpSetting: Error code = 0x80220001
IBS UnattendDumpSetting: Pass = specialize
IBS UnattendDumpSetting: --------------------------------------------
IBS UnattendErrorFromResults: Error text = 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.
[0x0600c2] IBS Callback_Unattend_InitEngine:An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220001[gle=0x00000490]
IBSLIB PublishCriticalError: Publishing blocked message [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.]
This installation is blocked from completing due to compliance failures or invalid input; this is not an internal error.
customsettings.ini as I think it changes the unattend?
Standard Time"
loymentShare$

Winsows 8.1 Pro Sysprep and Capture

I've been using MDT for a few years now and seem to got Windows 7 deployments down. I created my first 8.1 Sysprep and Capture TS and am running into an issue. It seems to be failing at the Win PE step before sysprep. I have made sure my DS is updated, CS.ini
is correct as far as I know, MDT 2013 with 8.1 ADK... I sysprepped and captured my Win 7 images fine. This is my first Win 8.1 GM image. Is there something obvious I am missing?
------ Applying bootable Windows PE image ------
LTIApply 3/3/2014 9:01:53 AM
0 (0x0000)
LTI applying Windows PE LTIApply
3/3/2014 9:01:53 AM 0 (0x0000)
Taking ownership of C:\bootmgr LTIApply
3/3/2014 9:01:53 AM 0 (0x0000)
About to run command: takeown.exe /F "C:\bootmgr"
LTIApply 3/3/2014 9:01:53 AM
0 (0x0000)
Command has been started (process ID 1852) LTIApply
3/3/2014 9:01:53 AM 0 (0x0000)
Console > SUCCESS: The file (or folder): "C:\bootmgr" now owned by user "pcname\Administrator".
LTIApply 3/3/2014 9:01:53 AM
0 (0x0000)
Return code from command = 0 LTIApply
3/3/2014 9:01:53 AM 0 (0x0000)
Taking ownership of C:\boot LTIApply
3/3/2014 9:01:54 AM 0 (0x0000)
About to run command: takeown.exe /F "C:\boot" /R /A /D Y
LTIApply 3/3/2014 9:01:54 AM
0 (0x0000)
Command has been started (process ID 2996) LTIApply
3/3/2014 9:01:54 AM 0 (0x0000)
Return code from command = 1 LTIApply
3/3/2014 9:01:54 AM 0 (0x0000)
ResetFolder: TakeOwn for C:\boot, RC = 1 LTIApply
3/3/2014 9:01:54 AM 0 (0x0000)
ZTI ERROR - Unhandled error returned by LTIApply: Not found (-2147217406 0x80041002)
LTIApply 3/3/2014 9:01:54 AM
0 (0x0000)
Command completed, return code = -2147467259
LiteTouch 3/3/2014 9:01:55 AM
0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005
LiteTouch 3/3/2014 9:01:55 AM
0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG.
LiteTouch 3/3/2014 9:01:55 AM
0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch
3/3/2014 9:01:55 AM 0 (0x0000)
Unable to copy log to the network as no SLShare value was specified.
LiteTouch 3/3/2014 9:01:55 AM
0 (0x0000)
CleanStartItems Complete LiteTouch
3/3/2014 9:01:55 AM 0 (0x0000)
Unregistering TSCore.dll. LiteTouch
3/3/2014 9:01:55 AM 0 (0x0000)
About to run command: wscript.exe "\\server\e$\Capture\Scripts\LTICleanup.wsf"
LiteTouch 3/3/2014 9:01:55 AM
0 (0x0000)
Microsoft Deployment Toolkit version: 6.2.5019.0
LTICleanup 3/3/2014 9:01:55 AM
0 (0x0000)
Removing AutoAdminLogon registry entries LTICleanup
3/3/2014 9:01:55 AM 0 (0x0000)
VSSMaxSize not specified using 5% of volume.
LTICleanup 3/3/2014 9:01:55 AM
0 (0x0000)
Logs contained 8 errors and 0 warnings. LTICleanup
3/3/2014 9:01:55 AM 0 (0x0000)
No Windows PE image to delete. LTICleanup
3/3/2014 9:01:55 AM 0 (0x0000)

I've been using MDT for a few years now and seem to got Windows 7 deployments down. I created my first 8.1 Sysprep and Capture TS and am running into an issue. It seems to be failing at the Win PE step before sysprep. I have made sure my DS is updated, CS.ini
is correct as far as I know, MDT 2013 with 8.1 ADK... I sysprepped and captured my Win 7 images fine. This is my first Win 8.1 GM image. Is there something obvious I am missing?
------ Applying bootable Windows PE image ------LTIApply
3/3/2014 9:01:53 AM0 (0x0000)
LTI applying Windows PE LTIApply3/3/2014 9:01:53 AM
0 (0x0000)
Taking ownership of C:\bootmgr LTIApply3/3/2014 9:01:53 AM
0 (0x0000)
About to run command: takeown.exe /F "C:\bootmgr"LTIApply
3/3/2014 9:01:53 AM0 (0x0000)
Command has been started (process ID 1852) LTIApply3/3/2014 9:01:53 AM
0 (0x0000)
Console > SUCCESS: The file (or folder): "C:\bootmgr" now owned by user "pcname\Administrator".LTIApply
3/3/2014 9:01:53 AM0 (0x0000)
Return code from command = 0 LTIApply3/3/2014 9:01:53 AM
0 (0x0000)
Taking ownership of C:\boot LTIApply3/3/2014 9:01:54 AM
0 (0x0000)
About to run command: takeown.exe /F "C:\boot" /R /A /D YLTIApply
3/3/2014 9:01:54 AM0 (0x0000)
Command has been started (process ID 2996) LTIApply3/3/2014 9:01:54 AM
0 (0x0000)
Return code from command = 1 LTIApply3/3/2014 9:01:54 AM
0 (0x0000)
ResetFolder: TakeOwn for C:\boot, RC = 1 LTIApply3/3/2014 9:01:54 AM
0 (0x0000)
ZTI ERROR - Unhandled error returned by LTIApply: Not found (-2147217406 0x80041002)LTIApply
3/3/2014 9:01:54 AM0 (0x0000)
Command completed, return code = -2147467259
LiteTouch 3/3/2014 9:01:55 AM0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005LiteTouch
3/3/2014 9:01:55 AM0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG.LiteTouch
3/3/2014 9:01:55 AM0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch3/3/2014 9:01:55 AM
0 (0x0000)
Unable to copy log to the network as no SLShare value was specified.LiteTouch
3/3/2014 9:01:55 AM0 (0x0000)
CleanStartItems Complete LiteTouch3/3/2014 9:01:55 AM
0 (0x0000)
Unregistering TSCore.dll. LiteTouch3/3/2014 9:01:55 AM
0 (0x0000)
About to run command: wscript.exe "\\server\e$\Capture\Scripts\LTICleanup.wsf"LiteTouch
3/3/2014 9:01:55 AM0 (0x0000)
Microsoft Deployment Toolkit version: 6.2.5019.0
LTICleanup 3/3/2014 9:01:55 AM0 (0x0000)
Removing AutoAdminLogon registry entries LTICleanup3/3/2014 9:01:55 AM
0 (0x0000)
VSSMaxSize not specified using 5% of volume.
LTICleanup 3/3/2014 9:01:55 AM0 (0x0000)
Logs contained 8 errors and 0 warnings. LTICleanup3/3/2014 9:01:55 AM
0 (0x0000)
No Windows PE image to delete. LTICleanup3/3/2014 9:01:55 AM
0 (0x0000)
Sounds like the problem occurs because the LTIApply.wsf script fails to check for the existence of the boot folder on the system partition before the script runs the
takeown.exe command to change ownership on the folder. The
takeown.exe command fails with a "Not Found" error if the boot folder doesn't exist. This causes the Sysprep and Capture task sequence to fail.
Is your MDT 2013 a fresh install or a upgrade from MDT 2012 U1?

Microsoft Surface Windows 8.1 Sysprep and Capture

SO I have a peculiar issue. I am trying to Sysprep and Capture and MS Surface Running Windows 8.1 (Pro or Enterprise). I am able to DEPLOY images but I am unable to capture. The problem is I get no errors. I select the task sequence and it starts running
and then it gets to the configure phase and the next phase is Copy Sysprep Files. It appears to be skipping that, but it jumps right to the end and then says, Completed successfully and there are zero errors. Clearly it didn't do anything, but I don't know
how to trouble shoot it with no errors.
Any ideas? Thanks

From another TechNet post -
[Settings]
Priority=TaskSequenceID,
Default
Properties=MyCustomProperty
[Default]
_SMSTSORGNAME=Running %TaskSequenceID%
OSInstall=Y
TimeZoneName=Eastern Standard
Time
SkipAdminPassword=YES
SkipDomainMembership=YES
SkipLocaleSelection=YES
SkipProductKey=YES
SkipTimeZone=YES
SkipUserData=YES
ApplyGPOPack=NO
[MYTASKID]
_SMSTSORGNAME=Image Creator
DoCapture=YES
BackupFile=Reference.wim
BackupLocation=NETWORK
BackupShare=\\MDTSERVER\Reference$
BackupDir=Captures
Where [Default] would have your domain join information and [MyTaskID] is your TSID for your capture sequence. Then when you select the capture sequence, it will instead select the non domain join option and capture your image. Good luck.

Suspend MDT, Sysprep for disk cloning, and resume with new hardware failure.

I am able to successfully Sysprep for disk cloning after pausing the Deployment (via LTISuspend). The problem is when I attempt to resume the Deployment after duplicating the hard drive and placing in new hardware it fails immediately stating that it cannot
open the TSENV.DAT (80090005). It works fine if you resume in the identical hardware it was built in.
The hardware is identical for all computers receiving the cloned drive with the Mac Address, Serial Number, and UUID being different.
Knowing that the TSENV.DAT is encrypted, is there a way to prep it for minor hardware (mac address, uuid, and serial number only) change prior to pausing and sysprep so it does not fail?
Using MDT 2012 and Windows 7 OS.
Thanks

Let me add to what Mr. Owen described.
We have a complex MDT. It has been used for years for a globally scaled corporate desktop.
What we are looking to do to is sysprep this machine 3/4 of the way through the process, clone the drive, and then use the cloned drive on like hardware models (we used PersistDrivers in the Unattend).
I initially ran sysprep outside of the MDT. It ran successfully, however when we moved the syspreped (and cloned) drive to another hardware of identical type we got the error Mr Owen mentioned. What we hoped would happen if we called Sysprep from
the MDT directly is the TSENV would be cleaned/updated to remove any workstations specific identifiers and thus eliminate the error.

MDT, CopyProfile and network drive

I have a MDT task sequence that runs sysprep and capture. I'm using copyprofile parameter in unattend.xml and administrator profile is copied over default profile when installing Windows. When I execute MDT sysprep & capture task sequence I manually
map deployment share to z drive and launch litetouch from. It runs fine but after I install new Computer using this captured image new users will see this disconnected z drive when they logon to the Computer. How I can prevent this networ drive from being
copied to default profile?

There is a similar thread here: link
If you do not want to recreate your image
I would expect the following to work
btw: this assumes the wim file is in C:\WIMDir and the mounted dir is C:\WIMDir\temp and your wim file is called Win7x32.wim
1.Mount the Wim fie with DISM.
>dism /mount-wim /wimfile:C:\WIMDir\win7x32.wim /index:1 /mountdir:C:\WIMDir\temp
2.Load the registry Hive for the administrator.
>reg load HKU\test C:\WIMDir\temp\users\administrator\ntuser.dat
Notice the adminstrator in the path!!
3. Open regedit and delete the Z Drive
Under HKEY_USERS\test\Network\Z delete the Z drive (and any others drive you want to get rid of)
4.Unload test Reg
>reg unload HKU\test
5.Load the Default registry file
>reg load HKU\test C:\WIMDir\temp\users\default\ntuser.dat
Notice the default in the path!!
6. Open regedit and delete the Z Drive (again!)
Under HKEY_USERS\test\Network\Z delete the Z drive (and any others drive you want to get rid of)
7.Unload test Reg (again!)
>reg unload HKU\test
8. Test WIM (Just to be sure)
>dism .get-MountedWIMInfo
It should say Status: OK
9. Commit-WIM
dism /Commit-WIM /MountDir:C:\WIMDir\temp
I know you can unmount and commit in one go, but I find this is more reliable!!
10.Test WIM (Again)
>dism .get-MountedWIMInfo
It should say Status: OK
11.UnMount WIM and Commit
>dism /unmount-Wim /MountDir:C:\WIMDir\temp \commit
12.Test WIM (Again and again)
>dism .get-MountedWIMInfo
This time it should say No mounted images found

Sysprep and Windows 8.1 -- missing Metro apps after reboot?

So, I'm trying to figure out an issue with Sysprep and a clean-install Windows 8.1 64 Enterprise system:
When I sysprep the computer from my admin account with my unattend.xml file, when it reboots, I'm only getting 7 Metro apps at the start screen and
14 Metro Apps at the "all apps" screen -- things like Weather, Maps, Calendar, Mail, etc are missing -- and actually look like they aren't installed
as searching for something like "People" -- gives no results.
From what I've been able to gather, the behavior of the start screen should controlled by an appsFolderLayout.bin file, but when I first set up the initial
account (not "administrator", but the initial local admin account), that file does not exist anywhere.
I've tried creating the file manually by running:
Export-StartLayout -As Bin -Path C:\Temp\appsFolderLayout.bin
and either putting it in \Users\<myadminaccount>\AppData\Local\Microsoft\Windows
or \Users\Default\AppData\Local\Microsoft\Windows
and sysprepping again (after restoring a snapshot to the pre-sysprep/post-clean install state), but this isn’t making any difference.
When I run sysprep /generalize — the .bin file is deleted and replaced by some other default one — that I’m not sure where it is generated from.
Does anybody have any suggestions here? Windows 8.0 just worked with my unattend.xml file without having to mess with appsFolderLayout.bin, so I’m not sure what I’m missing.
Thanks!

If you are still having trouble, this is an outline of the full process I use that seems to be consistently producing good results:
- Install Windows 8.1 Enterprise with autounattend.xml, in particular, blank administrator password, add user account test, auto-logon as Administrator, run "net user test /delete" immediately after logon to get back to just having the administrator account.
There should be no reason why all that has to be done in autounattend.xml, but it is the way I do it. There are a few other mandatory settings if you want a fully-automated setup.
- At this point in time the Administrator account only shows a few tiles on the start screen, all actions are performed using the Administrator account.
- Run Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup" before the task has had a chance to run.
- Install all applications, updates and settings as you want.
- Run Sysprep, in particular blank administrator password, add user account test, auto-logon as Administrator, run "net user test /delete" immediately after logon to get back to just having the administrator account. Also importantly we set CopyProfile to
false under Microsoft-Windows-Shell-Setup specialize pass. I don't know because I haven't tried it, but I imagine that if you run this and copy the Administrator profile to the default user profile then the default user profile may be missing some apps. We
do all customization of the default user profile explicitly by loading the registry hive and editing it directly.
After the image is deployed the Admistrator account has all the standard tiles present, but two of them report errors (I think it is Music and Videos). Any other profiles have all tiles present and all apps work.
The full sysprep XML is included below in case it is useful to anybody. The company-specific settings and passwords have been blanked out, but otherwise it is the full one we use and fairly generic apart from the Australian settings. Note that this one is
for a 64-bit image.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" 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">
<SkipRearm>0</SkipRearm>
</component>
</settings>
<settings pass="specialize">
<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">
<ComputerName>*</ComputerName>
<CopyProfile>false</CopyProfile>
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>AUS Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" 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">
<SkipAutoActivation>true</SkipAutoActivation>
</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" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>XXXXXXXXXXXXXXXXXX</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>XXXXXXXXXXXXXXXX</Value>
<PlainText>false</PlainText>
</Password>
<Description>Temp Account We have to Add because setup requires it</Description>
<Name>temp</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOrganization>XXXXXX</RegisteredOrganization>
<RegisteredOwner>XXXXXX</RegisteredOwner>
<TimeZone>AUS Eastern Standard Time</TimeZone>
<AutoLogon>
<Password>
<Value>XXXXXXXXXXXXXXXXXXX</Value>
<PlainText>false</PlainText>
</Password>
<Domain>.</Domain>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<LogonCount>1</LogonCount>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>net user temp /delete</CommandLine>
<Description>Delete temp user account that we have to create</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
</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-AU</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-AU</UserLocale>
</component>
</settings>
</unattend>

Win8 sysprep and OEM drivers in a local folder

Quite simply, in Windows 7 Pro I would drop driver folders into c:\windows\inf\<added-subfolder> that would cover all the systems we support. At first boot after imaging, Windows 7 would recursively search for drivers in the default path c:\windows\inf
which includes that <added-subfolder> with many subfolders containing many other drivers.
By the time the user logon was available, everything was installed and happy. Everything worked great.
Yes it can extend the initial post-image boot time but it was worth it for an easy universal image.
Now with Windows 8.1u1 Pro I have tried the same mechanic (with 8.1u1 drivers of course) and it refuses to look in c:\windows\inf\<added-subfolder>. Sysprep and my answerfile do their job but the system doesn't begin loading any drivers until
reaching the desktop. It appears that Windows is only initially loading critical drivers and even those are only the Win8 native ones.
Has something changed or been broken that I've missed?
Injecting these drivers with pnputil is not an option. The registry bloats and breaks the image. Neither is using SCCM an option.
It's a very simple solution but so far it's refusing to work with Win8.1u1 .
Installing via Update Driver on the device in Device Manager, then pointing to the subfolder, I get:
Windows encountered a problem installing the driver software for your device.
Windows found driver software for your device but encountered an error while attempting to install it.
The system cannot find the file specified.
I guess that's something to work with. Digging ...
Update: pnpunattend run as a script from an administrative group user pops user intervention errors for unsigned drivers. Do I dare hope that if I alter my answerfile it won't?
I've added:
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" 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">
<Order>1</Order>
<WillReboot>Always</WillReboot>
<Description>PnPUnattend Install</Description>
<Path>c:\windows\inf\xinf\pnpunattend.cmd</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
and:
<settings pass="auditSystem">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" 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:action="add" wcm:keyValue="1">
<Path>c:\windows\inf\xinf</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
<settings pass="windowsPE">
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="x86" 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:action="add" wcm:keyValue="1">
<Path>c:\windows\inf\xinf</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
Where c:\windows\inf\xinf\pnpunattend.cmd is:
REM Configuring PNP Driver Installation..
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UnattendSettings\PnPUnattend\DriverPaths\1" /v Path /t REG_SZ /d "C:\windows\inf\xinf"
REM Installing PNPDeviceDrivers
C:\Windows\System32\pnpUnattend.exe AuditSystem /L > c:\windows\temp\pnpunattend.txt

Within the confines of how we create and deploy Windows systems, is there a _simple_ solution for Windows 8 that results in the same as what we did for Windows 7?
1. FAT Images are created in Hyper-V 2012.
2. All drivers for all possible systems are copied into c:\windows\inf\xinf .
3. Sysprep 1 of the VM creates the default user profile which is then copied to a local, mandatory profile path.
4. Sysprep 2 of the VM then closes the image and shuts down.
5. The VM image is captured by FOG.
6. The image is deployed by FOG to any number of platforms.
7. At first boot the OS installs all drivers, recognizing the subfolder c:\windows\inf\xinf.
8. Eventually sysprep calls a designated .vbs that is run before setupcomplete.cmd, then again by autologon as administrator for however many number of reboots/autologons that a particular system requires before releasing to a normal logon screen.
All possible drivers a system requires MUST be installed prior to any logon so that scripts launched by sysprep can work properly.
Windows 7 happily does all of this without issue BEFORE reaching any logon or scripts.
How can I mimic this behaviour in Windows 8.1u with no server or share resource?
The only way I've got Windows 8.1u to do it so far is to perform this prior to final shutdown by:
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UnattendSettings\PnPUnattend\DriverPaths\1" /v Path /t REG_SZ /d "C:\windows\inf\xinf"
C:\Windows\System32\pnpUnattend.exe AuditSystem
=-=-=-=-=-
This bloats the image by several GiB and incurs many unverified publisher prompts to continue while pnpunattend executes, but sysprep loads all device drivers prior to any logon to a destination system, which is great!
I'm looking for specific answers that work within our framework please.

Sysprep and keep license key not working

Hi,
I am using sysprep on some technet license keys. I created an unattend.xml file (below) and selected a generalise and OOB sysprep execution. However, on reboot, I still get prompted for a license key.
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" 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">
<SkipRearm>1</SkipRearm>
</component>
</settings>
Why?

Well that's why it's asking it... this is a retail media right?
If you want this to work, you have to use volume activation media and key (MAK or KMS). More info here:
http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx

MDT 2013 and Windows Embedded Standard 7

Hi Guys
I'm currently working on a Windows Embedded 7 Standard build and deployment.
Looking at the support Matrix and the video from Johan, it looks like:
MDT 2010 has support with the hacked LTIAPPLY script
MDT 2012 onwards support Embedded POS Ready - no mention of Standard.
Can you clarify:
If WES7 is supported in MDT 2013.
Is there a set of specific task sequence steps I should use for deploying WES7? I will still need to run the standard pre-install to clean disk, gather vars etc.
I have written some post build scripts, which configures the FBWF state and installs final apps, which i'll run at the State Restore phase.
Many Thanks
Ian Fraser

Can you share your experience with MDT 2013 and Windows 7 Embedded? Are you deploying the SCCM client to the clients? Any scripts you can post would be helpful.

MDT 2012 Sysprep and Installation Failure

A few days ago I tried to install a clean windows 7 installation with updates on a dell optiplex 3010,
it gave a failure and after that I didn't think much of it anymore
The next day i tried to install another 3010 and got the same error
Windows could not parse or process the unattended answer file for pass [specialize]. The setting specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
Since I am fairly new to MDT I am clueless, I went to c:/windows/panther/unattendedgc and
got this log.
2013-11-28 05:22:44, Info                         [windeploy.exe] ------------------------------------------------
2013-11-28 05:22:44, Info                         [windeploy.exe] WinDeploy.exe launched with command-line []...
2013-11-28 05:22:44, Info                         [windeploy.exe] Setup has not completed, adding pending reboot.
2013-11-28 05:22:44, Info                         [windeploy.exe] Found generalization state [0x4], setup.exe completion flag [False] -->
launching setup.exe.
2013-11-28 05:22:44, Info                         [windeploy.exe] Launching [C:\Windows\system32\oobe\setup.exe]...
2013-11-28 05:24:13, Info                         [windeploy.exe] Process exited with exit code [0x0]
2013-11-28 05:24:13, Info                         [windeploy.exe] Found completion flag [True], reboot requested flag [True] --> rebooting
computer before proceeding with deployment...
2013-11-28 05:24:13, Info                         [windeploy.exe] Making sure that SystemSetupInProgress is cleared.
2013-11-28 05:24:13, Info                         [windeploy.exe] An immediate reboot or shutdown was requested/required... rebooting / shutting
down computer
2013-11-28 05:24:13, Info                         [windeploy.exe] Flushing registry to disk...
2013-11-28 05:24:13, Info                         [windeploy.exe] Flush took 640 ms.
2013-11-28 05:24:13, Info                         [windeploy.exe] WinDeploy.exe exiting with code [0x0]
2013-11-28 05:25:18, Info                         [windeploy.exe] ------------------------------------------------
2013-11-28 05:25:18, Info                         [windeploy.exe] WinDeploy.exe launched with command-line []...
2013-11-28 05:25:18, Info                         [windeploy.exe] Making sure that SystemSetupInProgress is cleared.
2013-11-28 05:25:18, Info                         [windeploy.exe] Found no unattend file.
2013-11-28 05:25:18, Info                         [windeploy.exe] WinSAT assessment failed with error 80040154
2013-11-28 05:25:18, Info                         [windeploy.exe] Launching [C:\Windows\system32\oobe\oobeldr.exe /system]...
2013-11-28 05:25:18, Info                         [oobeldr.exe] OOBELdr.exe launched with command-line [/system]...
2013-11-28 05:25:18, Info                         [oobeldr.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_SPECIALIZE_RESEAL_TO_OOBE]
--> [IMAGE_STATE_UNDEPLOYABLE]
2013-11-28 05:25:18, Info                         [oobeldr.exe] Parsing command line arguments...
2013-11-28 05:25:18, Info                         [oobeldr.exe] Parsing the following command line: [/system]
2013-11-28 05:25:18, Info                         [oobeldr.exe] Status for unattend pass [oobeSystem] = 0x0
2013-11-28 05:25:18, Info                         [oobeldr.exe] Found no unattend file for oobeSystem pass; skipping pass.
2013-11-28 05:25:18, Info                         [oobeldr.exe] No reboot has been requested for oobeSystem unattend.
2013-11-28 05:25:18, Info                         [oobeldr.exe] Successfully ran oobeSystem pass.
2013-11-28 05:25:18, Info                         [oobeldr.exe] Launching [C:\Windows\system32\oobe\msoobe.exe]...
2013-11-28 05:25:18, Info                         [msoobe.exe] Starting service sppsvc
2013-11-28 05:25:21, Info                         [msoobe.exe] Service sppsvc reports as running
2013-11-28 05:25:21, Info                         [msoobe.exe] Successfully created first boot reg key
2013-11-28 05:25:21, Info                         [msoobe.exe] Server, exiting...
2013-11-28 05:25:21, Info                         [msoobe.exe] Running mandatory tasks
2013-11-28 05:25:21, Info                         [msoobe.exe] Doing background work directly in MandatoryTasks; eType=1
2013-11-28 05:25:21, Info                         [msoobe.exe] Successfully installed product key
2013-11-28 05:25:21, Info                         [msoobe.exe] Starting service netprofm
2013-11-28 05:25:22, Info                         [msoobe.exe] Service netprofm reports as running
2013-11-28 05:25:22, Info                         [msoobe.exe] Successfully signalled event to start up services
2013-11-28 05:25:22, Info                         [msoobe.exe] Doing background work directly in MandatoryTasks; eType=0
2013-11-28 05:25:22, Info                         [msoobe.exe] Starting service Schedule
2013-11-28 05:25:23, Info                         [msoobe.exe] Service Schedule is already running
2013-11-28 05:25:23, Info                         [msoobe.exe] Successfully verified and committed UI language settings
2013-11-28 05:25:30, Info                         [msoobe.exe] Successfully notified UI language change
2013-11-28 05:25:30, Info                         [msoobe.exe] Successfully installed Windows Recovery Environment
2013-11-28 05:25:31, Info                         [msoobe.exe] Successfully removed administrator profile
2013-11-28 05:25:31, Info                         [msoobe.exe] Exiting mandatory tasks... [0x00000000]
2013-11-28 05:25:31, Info                         [msoobe.exe] Cleaning up background work
2013-11-28 05:25:31, Info                         [oobeldr.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE]
--> [IMAGE_STATE_COMPLETE]
2013-11-28 05:25:32, Info                         [oobeldr.exe] OOBELdr.exe exiting with code [0x0]...
2013-11-28 05:25:32, Info                         [windeploy.exe] Process exited with exit code [0x0]
2013-11-28 05:25:32, Info       [0x090008] PANTHR CBlackboard::Open: C:\Windows\Panther\SetupInfo succeeded.
2013-11-28 05:25:32, Info       [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.
2013-11-28 05:25:32, Info                         [windeploy.exe] WinDeploy.exe exiting with code [0x0]
This is from a sysprep on a vm in vmware workstation. I am clueless what to do next..
I've read a lot of threads but I can't find any solution.
Can anybody help me with analogizing log files?
and which other log files might be helpfull?
regards
hidde

This can sometimes happen when you have OSDComputerName=%SerialNumber% in the CustomSettings.ini. Because you are deploying an image to VMware, VMw has SerialNumbers that are different in characters... To make a long story short, use the replace the following
command in CustomSettings.ini:
OSDComputerName=%SerialNumber%
to
OSDComputerName=#RIGHT("%SerialNumber%",15)#
15= the max number of characters allowed in a computername. This should help fix your issue.

Sysprep and Capture TS problems

I am trying to capture the image of a reference machine I have in VirtualBox. I am working in MDT 2012. The first pass on this I initiated the process from the CMD window starting the LiteTouch.wsf from in the scripts folder. This worked to a point, sysprep
worked, the VM was rebooted but this failed (VirtualBox Manager failure). I restarted the VM and the PE started and got to creating WIM and a very slow agonizing window showing the percent done. It got to 6% and stopped. I did see the WIM file getting built
but it only got to about 1.3GB. Next I tried the same VM, after recreating from a backup, and this time tried booting from a LiteTouch CD as I read is preferred in MDT2012. This failed at Sysprep. Below is the failure report.

Are you using a slow network connection to capture the image? You should have the VM configured for GigaBit between the VM and your MDT Server.
I have had problems with MDT re-running and getting confused when the target *.wim file already exists. Try deleting from the host if you have problems.
IF you still have problems, please post the bdd.log and smsts.log file to a public site like onedrive, and copy the link here.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

[MDT] Sysprep and capture, and OOBE

Similar Messages

Maybe you are looking for