MDT and capture & sysprep existing machine

Hi,
In a few special situations I need to be able to capture and sysprep existing physical machine. In MDT there is this Sysprep & Capture task sequence template. I think it's just what I need, but I have read somewhere before that it shouldn't be used for
some reason. Is anyone actually using this?

Generally, if you are deploying to *more* than one make and model of machines, the recommended procedure is to build your images within Virtual Machines like Hyper-V (which is free on Windows 8.1), When you build using virtual machines, Windows won't need
to load any extra Drivers into your image that will be unnecessary on other machines.
However... If you have a lot of machines that are all of the same make/model and installation speed is important, then sure, imaging via a physical source is OK.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com
Customer sent us a preconfigured physical machine and we just need to capture image from that and deploy it to few hundred identical machines.
I have previously used manual sysprep process and after that use DISM to read hard disk to WIM file. Then import WIM to mdt. That works but too much manual work.

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

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?

How do I get rid of the message "To use this machine for downloads, enter you Apple ID and password" which I now see twice since I downloaded the latest version of iTunes? Once is enough and no checkbox exists to say "do not show this message.....".

When I start iTunes, how do I get rid of the message "To use this machine for downloads, enter you Apple ID and password" which I now see twice since I downloaded the latest version of iTunes. Once is enough and no checkbox exists to say "do not show this message....."

Does this apply?
If you're asked for the password to your previous Apple ID when signing out of iCloud - Apple Support

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.

MDT 2013 supports build and capture win 7 SP1

Hi,
Just want to have a check if MDT 2013 supports Build and capture windows 7 as image (wim)?
I know it is supporting windows 7 as supported OS for deployment.
Regards,

Yes it does:
http://technet.microsoft.com/en-US/windows/dn475741.aspx
Good luck!

Steps to create MDT based Build and capture TS in SCCM 2012 R2

Hi ,
I have MDT2012 update 1 with Config manager 2012 R2 integrated. If I try to create MDT task sequence in config manager console, I don't see and template for build and capture. Anyone using the build and capture, pls. share steps with me . Any help will be
appreciated. Preferably UDI based if possible. Thanks in advance.
Regards,

MDT 2012 Update 1 is for SCCM 2012 SP1
MDT 2013 is for SCCM 2012 R2
So you need to upgrade your MDT installation. After that, make sure to install the ConfigMgr integration from the start screen (menu)
http://technet.microsoft.com/en-US/windows/dn475741.aspx
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

SCCM 2012 R2: Build and Capture - Windows 8.1 prompting for network

I have upgraded my SCCM 2012 SP1 (CU2) to SCCM 2012 R2 and I am attempting to Build and Capture Windows 8.1 Enterprise. Everything is perfect except for the OS prompting for a network selection during the process, if I click "next" on that screen
the Capture finishes without incident. The same is true of the Deploy as well...
Is this a bug from my upgrade?
Portland Public Schools / Systems Administrator II

Hi LillonelC
Can you point out how and where to do this?
When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.
But when deploying to a Laptop I get the wireless Setup screen...
On beforehand Thank You!
With kind regards
We aren't using MDT but what we did was create a package called Windows 8.1 - Compnents. In it placed a file named "32Bit-Unattend.xml" and 1 named "64Bit-Unattend.xml".
During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml".
I did the same for 64-bit and used the 64-bit version.
Here is content of the 32-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<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"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x86/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Here is the content of the 64-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<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>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x64/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
If that doesn't help I can try to clarify it a bit further.
PS You won't need to do this for the deploy, only the capture.
Portland Public Schools / Systems Administrator II

MDT and MAK product key

We are using MDT2010 and now MDT2013 for years now. I must make a new deploymentshare for 64 bit Windows 7 but cannot find in my documentation where to put the MAK key in MDT for later activation when Windows 7 is deployed.
I have looked in MDT where i have put the MAK key but cannot find it anywhere, not in custom settings / bootstrap.ini, any task sequence etc.
Searching the Internet the MAk key must be put when importing a operating system into MDt but i have never done that. After deploying Windows 7 to a client i activate the system at once, the MAk product key is somewhere stored, i have done that myself but
do not know where.....
Is there some standard point where i must put the MAK key in MDT, when syprepping and capture task sequence or in a deployment task sequence or in the customsettings.ini / bootstrap.ini within the capture deployment or deploymentshare?
This is neccessairy because i want to capture and deploy a new Windows 7 but now 64 bit in MDT so the key must be put somewhere..
It can be put in the virtual machine that is goiing to be captured. After installing WIndows in the VM put in the product key, but maybe this key is lost when importing and deploying thru MDT...
It can be somewhere in the sysprep and capture task sequence although i cannot find it
In the deployments task sequence cannot find them here also
Int he rules.ini or bootstrap.ini of the captureshare or deploymentshare but here also not found..
freddie

When you sysprep the machine the license will be removed. You can either add it to the unattend file or you can write a script to install the key and force it activate Windows, your choice. The easiest would be to just add the key to the unattend.
I have a script for machines that will be off campus and out of reach of our KMS server. In this example I install the Office MAK and activate it, but as for Windows I just added that key to the unattend. Specialize-->Microsoft-Windows-Shell-Setup
oShell.Run("cscript " & oENV("ProgramFiles(x86)") & "\Microsoft Office\Office15\ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX")
oShell.Run("cscript " & oENV("ProgramFiles(x86)") & "\Microsoft Office\Office15\ospp.vbs /act"),0,True
If this post is helpful please vote it as Helpful or click Mark for answer.

Sysprep - Fatal error occurred while trying to sysprep the machine

On the 4th attempt to sysprep a Windows 7 Enterprise system, I get the dreaded, 'A fatal error occurred while trying to sysprep the machine.'
The setuperr.log shows:
2010-08-04 13:57:58, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 31
2010-08-04 13:57:58, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
I've seen articles referring to the Windows Software Licensing Rearm program may have issues running more than three times in a single Windows image and to add <SkipRearm>1</SkipRearm> in the /unattend file... but this did not help.
The Windows Media Player Network Sharing Service has also been disabled which is often referred to in other posts.
The KB article: http://support.microsoft.com/kb/947212/en-us indicated that the resolution is to re-create the image for the machine... This is very frustrating. I'm hoping that there is
a better resolution???
How do you sysprep a machine more than three times to avoid this error?
Thanks!!
930193

I had a problem Where Runing slmgr /dlv returned 0 and could not sysprep a
32 bit Win 7 Installed on C:drive
Here is what I did to succeed whit Sysprep.
Disable UAC
Based on
This :
open notepad and copy paste the following:
@ECHO OFF
setLocal Enabledelayedexpansion
for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do (
if exist %%d:\windows\system32 (
     SET drv1=%%d:\windows\system32
    reg load HKLM\MY_SYSTEM !drv1!
    reg delete HKLM\MY_SYSTEM\WPA /f
    reg unload HKLM\MY_SYSTEM
   GOTO END
:END
ECHO Done, Rebooting system...
timeout 3
wpeutil reboot
Then in notepad chose file>save as, in File Type select "All Files", name it "c:\reset.bat"
Reboot Your Pc, after bios screen press F8, Select "Repair Your Computer", select your keyboard layout, enter your credentials if needed,
then select the last option "Open Command Prompt"
type "c:\reset.bat" or "d:\reset.bat" (Sometimes Your Windows Partition get a different letter on the repair environment)
Back on Windows follow step five if needed.
Check under slmgr /dlv you have more than 0 under "Remaining Windows Rearm count"
Download pstools.zip from
here, extract content an copy psexec.exe to %windir%\System32
run psexec.exe and accept the license agreement so it won't bother when running afterwards, close it.
open notepad and copy paste the following:
@ECHO OFF
echo Stopping Windows Media Player Sharing Service..
echo.
net stop wmpnetworksvc
echo.
echo Deleting Old Sysprep Logs...
echo.
del /f /s /q %windir%\System32\sysprep\panther\*.*
echo.
echo Adding Required Sysprep Registry Keys...
echo.
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform" /v SkipRearm /t REG_DWORD /d 00000001 /f
REG ADD HKLM\SYSTEM\Setup\Status\SysprepStatus /v GeneralizationState /t REG_DWORD /d 00000007 /f
REG ADD HKLM\SYSTEM\Setup\Status\SysprepStatus /v CleanupState /t REG_DWORD /d 00000002 /f
psexec -i -s REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Cleanup /v "{EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80}" /t REG_SZ /d "C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE" /f
psexec -i -s REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Generalize /v "{EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1}" /t REG_SZ /d "C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE" /f
psexec -i -s REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Specialize /v "{EC9FE15D-99DD-4FB9-90D5-676C338DC1DA}" /t REG_SZ /d "C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE" /f
echo.
echo Uninstalling MSDTC...
echo.
msdtc -uninstall
timeout 10
echo.
echo Reinstalling MSDTC...
echo.
msdtc -install
timeout 10
echo.
echo Cross Your Fingers, Finally Running Sysprep...
echo.
%windir%\System32\sysprep\sysprep /generalize /oobe /shutdown /unattend:unattend.xml
Change Last Line to suit your needs, ie: if you are not using an unnattend answer file, then delete /unattend:unattend.xml"
Then in notepad chose file>save as, in File Type select "All Files", name it "%windir%\System32\do.cmd"
if you use an unattend.xml file copy it to %windir%\System32\sysprep folder.
Once you are ready run %windir%\System32\do.cmd
Hope it helps,

Install Updates task not working during Build and Capture in SCCM 2012

Working with a new SCCM 2012 installation.
We are trying to get a Build and Capture TS to install all updates for Win7SP1.
All packages are deployed to DP, build and cap machine is in a collection with all updates deployed to it. Agent installation parameters include "SMSMP" "SMSSLP" parameters. Machine is not being attached to the domain during OS install.
Updates can be pushed to existing domain machines, so obviously the updates themselves are working.
The task sequence works correctly to install the image, but "Install Updates" task just sits there and eventually times out. (No indication of updates being installed.) If this task is working, shouldn't I see a Downloading Updates progress bar, or was that
eliminated from 2012?

Same issue for me except I'm running 2012 R2 my B&C runs forever on Install Software Updates, eventually just rebooting and coming back to the login screen of Windows 7 without ever finishing the Install Updates.
Been working on it litteraly for weeks.
1- Tried adding .Net 4.52 as an application installation thinking maybe it would resolve the issue
2- Tried installing via Run Command Line + DISM all hotfixes that require 2 reboots as per (https://support.microsoft.com/en-us/kb/2894518)
3- Tried to simply REMOVE the same hotfixes from my Software Update Groups alltogether.
4- Injected all applicable software updates through Offline Servicing in the SCCM Console (Schedule Updates) on the Windows 7 DVD wim file. That way my logic was that once it would hit the Software Updates, there would be a lot less to install.
I'm at the point where I had to open a case with Microsoft Premier Support as of yesterday. So, nothing new to report yet. But yes, this is a true pain in the ***.
For the sake of comparison, I am running 4 Update Groups: one containing patches up to 2012. Another one for 2013, 2014 and 2015. I have patches for Windows 7 + Office of all categories except Service Packs.
If someone has any ideas, feel free to chime in.

Logging and Capturing

As a result of this thread: http://discussions.apple.com/message.jspa?messageID=3857627#3857627
I did a test of various ways to capture footage into FCP. Sorry for saying this again but I’m new to FCP - after 20 some odd years editing with proprietary, Avid and Premiere Pro NLE’s. I mention this [again] because it is hard to teach an old dog new tricks, and some of the bias that I’ve gathered along the way might show up in the way I approached this.
I have four one hour HDV tapes recorded on a Sony HC1; I used the same camera that created the tapes to down convert and capture standard definition NTSC anamorphic DV. Each taped averaged about 70-80 clips.
Tape 1
The first tape I logged the clips using the controls in the log and capture window. Fairly straightforward, but the HC1 was not very responsive to the J/K/L keys and the image in the capture window was very low resolution during scrubbing and searching. This made the process of logging slower than it should be. Once logged, batch capturing was fairly quick [about 1:12:00:00 to capture a 60 minute tape] and pretty much what I expected.
This was not a very efficient way to capture 70-80 clips, a lot of time wasted with pre and post roll. If you had fewer, 20-50 this might be the better way to capture but for what I was doing this was my least favorite way.
Tape 2
After entering the clip information into the log window I hit K key and capture “Now” button and captured the entire tape. I was a little concerned at what would happen when timecode ran out at the end. Nothing happened, it stopped and the clip appeared in the capture bin – all was good.
Once captured I created a custom Browser window with only the columns I wanted to log and make subclips: [following Steve Braker’s instructions]
1) Loaded the master clip into the viewer.
2) Set in and out points for the first clip.
3) Command-U to create a subclip.
4) Re-named the subclip, added description and label.
5) Click in Viewer and
6) Repeated steps 2-5 until 70 clips later it was complete.
Steve suggested deleting or moving the master clip, however checking the folder in the finder where the master clip was store revealed that this process didn’t produce individual clips. Apparently the subclips are simply pointers to the master file so I didn’t delete it.
This process was surprisingly fast but I still ended up with a single file that was approximately 5GB’s which made this process almost useless for working with subclips in Motion2 for example.
Tape 3
Marked an [in and out] in 20 minute intervals to create three master clips for this reel.
1) Loaded the master clip part 1 of 3 into the viewer.
2) In the Mark menu selected DV Start/Stop
3) After FCP placed markers at the scene breaks I “clicked the disclosure triangle” next to the master clip to reveal all of the markers in the Browser.
4) Selected all of the markers to highlight them
5) Chose Modify>Make subclip after which the subclips appeared in the same bin as the master clip and markers [note* at this point I checked my hard drive to find there was still only one contiguous master file for these subclips.
6) Re-named each subclip, added description and label and then placed them in a separate bin and placed the subclips that I didn’t want to keep in a bin to be deleted. [temp trash]
7) Highlighted the subclips that I wanted to convert to Independent clips
8) Chose File>Media Manager
9) Chose Use Existing from the “Media referenced by selected clip” drop down.
10) Selected the “Delete unused media from selected clips.”
11) Chose Clip Names from the “Base media file names on” drop down (Oops, sorry that’s for a PC) pop-up menu.
12) Un-checked the “Duplicate selected clip and place into new project.” This placed the independent clips in the same folder on your hard drive as the master file for the subclips. I suspect although I did not test it that if I had this checked I could choose a different folder?
13) Held my breath and clicked OK!
14) That’s when FCP started treating me like a total idiot “are you sure you want to do this, you’d better be because there’s no going back. Are you really, really sure…” Anyway for me since this is the only project on this machine I didn’t even read the warnings [yes I am an impatient idiot] **** the torpedoes full steam ahead..
15) Done! NOT Quite yet. You’d think that since I un-checked the “Duplicate selected clip and place into new project,” that FCP would be smart enough to place the new clips in my project window. Didn’t happen, had to control click and import files.
This process requires a bit more explanation. I had 16 subclips that I converted to independent clips, after which I deleted all associated subclips and markers. When I imported files there were only seven clips in the folder where the master clips was saved [now deleted as part of this process].
On further inspection all of the footage that I wanted was there, HOWEVER, by using the DV Start/Stop to create markers and then using those markers to create subclips if there are two or more clips with continuous timecode it consolidates them into one contiguous clip thereby defeating the purpose of creating the subclips in the first place. I’m guessing but if I hadn’t deleted some of the subclips I didn’t want to convert I would have ended up with the same large file with a different name.
The manual recommends that you delete the master clip from the Browser before converting the subclips into individual clips. I was suspicious of the need to do this so I left it and after the conversion it did what I expected, became offline. It was a good thing because I could use it to recapture. Also, any logging with description and labels etc is history it is not included in the new independent clip.
Tape 3 Part 2
I won’t bore everyone with going through the steps I’ll just explain how this one was different.
1) I didn’t use the DV Start/Stop option, instead marked I/O separately leaving at least 2 frames between edits to make sure there was discontinuous timecode.
2) I also didn’t bother naming or logging at this point and left whatever ridiculous name the subclip process assigned.
3) The settings in the Media Manager were all set from the previous conversion hit OK [this time read the warnings which would have done nothing to correct the previous attempt].
4) 12 subclips went in and 12 new independent clips came out.
5) Once I had the new clips I logged and added descriptions and labels etc…
Although this sounds like a very convoluted process, and it is certainly much more difficult than it needs to be, by the fourth tape it was predictable and quite fast.
I will say though that because FCP consolidated any continuous clips without warning you really have to pay attention to detail. And it would be nice if we could use the log & capture window for this process so any descriptions, labels etc would be carried forward to the new clip.
Certainly not as easy to accomplish as it is in PPro but definitely possible. There might be more functionality that I just missed, if so please let me know. Anything that can be done to simplify this would be helpful.
Mac Pro. 5GB RAM. 1TB SATAII RAID 0. Mac OS X (10.4.8) FCP 5.1.2

When you delete the master clip from the browser, you aren't deleting the media file it referenced. So the subclips reference that same original captured QT movie, it's just not in your project.
It will work. try it. It's how I've been working for about 6 years now. I don't have problems with subclips at all doing anything I want to with them.
Subclips are nothing more than reference files that reference a portion of a master clip. A Master clip is nothing more than a reference to the media file that you're capturing... it's not the media it's a reference to it.
Subclips are how FCP was really intended to be logged I think. I don't like long captures at all, and would prefer to actually capture the way you did the first time... but because it takes longer, I usually don't have time to do things that way. However, if you do things that way, you can add descriptions etc. to the logged clip in the Log and Capture window, if that helps your workflow.
The responsivness you lack with your HDV camera is because it's HDV... HDV doesn't contain all of the pixels of every frame, so to see a single frame the computer has to do a lot of processing to show it to you. It's an MPEG stream, which uses whole frame information every 8 or 15 frames only. The rest of the frames are the difference between the frames only on the recorded tape, thus the work and slow response to HDV logging and capturing.
P2 on the other hand, would make ALL of this MUCH easier to deal with. For one thing, each take is an individual file, and it's an all I frame format so it's easier for the computer to deal with. It renders 8 times faster than HDV does... no "conforming" necessary.
Jerry

Windows 7 64bit Build and Capture Task Sequence keeps failing. Need to Offline Patch

Hi All,
I have been having problems running my SCCM 2007 R3 Build and Capture Task Sequence for Windows 7 64bit since MS released the October 2014 patches. (Having problems described in KB2894518, but can't get workaround to work)
So my next step is to try to apply the patches directly to the install.wim file using dism and "Offline Servicing". I'm hoping this will allow my TS to finish, and also adds the benifit of making my TS much faster to run every month. So I followed
the steps in
this post, and injected 165 updates into the install.wim file (extracted from Win7 ISO). Now, I've copied the updated WIM into my Operating System install package and updated the distribution point. But the Install Software Updates step still installs 160
updates (same as before the Offline patch injection). The only thing that seems faster is that the download of the updates is instantaneous. So it seems like the Offline patch injection just copied the patch installer files to the WIM, but did not actually
install them.
I remember reading a post by Niall C. Brady or Jason Sandys about exactly how they inject patches into a WIM, but have been unable to re-locate the post. Does anybody out there have a tried and true method for offline injection of patches into install.wim
for use with SCCM Build and Capture task sequence? thanks!

My recommendation would be to use MDT to build your images instead:
http://technet.microsoft.com/en-us/library/dn744290.aspx
This will make your life much easier with the patching of the image :)
You can use Nickolaj's great MDT Factory tool to set up an MDT Build machine from scratch:
https://gallery.technet.microsoft.com/MDT-Factory-Tool-100-8e68123b
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

MDT and capture & sysprep existing machine

Similar Messages

Maybe you are looking for