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

Similar Messages

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.

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?

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$

Log and capture big problem

I am using FCP 3 (fully registered) i hit the log and capture NOW feature, and the screen brightness drops in half and a message that says I have to restart my computer and freezes up my computer. The message is in 4 different languages making me think that it may be a computer error rather than a FCP message.
I deleted my FCP plist file, and the FCP user data, preference file and the POA cache file. Problem is still there.

That's a kernel panic - whole system stalling.
Do you have both FCP 7 and FCP X installed?
If so, did you follow installation instructions provided by Apple:
http://support.apple.com/kb/HT4722

[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

Using the default Sysprep and Capture template fails on reboot with BOD UNMOUTABLE_BOOT_VOLUME

On a 2012 r2 server with MDT 2012 I am using the default template to capture a Win 8.1 64 bit master image to deploy to 60 Dell e7440 laptops. When I start the cscript litetouch.wsf thru command prompt, the litetouch wizards starts sysprep starts to
work and when it goes to reboot BOD UNMOUTABLE_BOOT_VOLUME.
The only way around the BOD is to PXE boot to the deployment server and LiteTouch continues to create WIM but fails. Click finish and the laptop boots as if it was the first time so sysprep worked.
Any help is appreciated.

Here is the process prior to rebooting.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\>cscript \\deploy2012\deploymentshare$\scripts\litetouch.wsf
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS
Microsoft Deployment Toolkit version: 6.2.5019.0
Property Debug is now = FALSE
ZTIUtility!GetAllFixedDrives (False)
New ZTIDisk : \\DSISPA-CAGN2QU\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYS
ICALDRIVE0"
New ZTIDisk : \\DSISPA-CAGN2QU\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYS
ICALDRIVE0"
New ZTIDiskPartition : \\DSISPA-CAGN2QU\root\cimv2:Win32_DiskPartition.DeviceID
="Disk #0, Partition #2"    \\DSISPA-CAGN2QU\root\cimv2:Win32_LogicalDisk.Devic
eID="C:"
New ZTIDisk : \\DSISPA-CAGN2QU\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYS
ICALDRIVE0"
New ZTIDiskPartition : \\DSISPA-CAGN2QU\root\cimv2:Win32_DiskPartition.DeviceID
="Disk #1, Partition #0"    \\DSISPA-CAGN2QU\root\cimv2:Win32_LogicalDisk.Devic
eID="D:"
New ZTIDisk : \\DSISPA-CAGN2QU\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYS
ICALDRIVE1"
ZTIUtility!GetAllFixedDrives =    C:
No task sequence is in progress.
Found OS Disk: C:
Found FirstPossibleSystemDrive: C:
Property SMSTSLocalDataDrive is now = C:
Not running within WinPE.
Property DeploymentMethod is now = UNC
DeploymentMethod = UNC
Property DeployRoot is now = \\deploy2012\deploymentshare$
Validating connection to \\deploy2012\deploymentshare$
Mapping server share: \\deploy2012\deploymentshare$
Already connected to server deploy2012 as that is where this script is running f
rom.
Mapped Network UNC Path Z: = \\deploy2012\deploymentshare$
DeployRoot = \\deploy2012\deploymentshare$
Property DeployDrive is now = Z:
DeployDrive = Z:
Property PHASE is now = VALIDATION
Property DeploymentType is now = REFRESH
Phase = VALIDATION
About to run command: wscript.exe "\\deploy2012\deploymentshare$\scripts\ZTIGath
er.wsf" /inifile:Bootstrap.ini
Command completed, return code = 0
Validating connection to \\DEPLOY2012\DeploymentShare$
Mapping server share: \\DEPLOY2012\DeploymentShare$
Already connected to server DEPLOY2012 as that is where this script is running f
rom.
Found Existing UNC Path Z: = \\DEPLOY2012\DeploymentShare$
About to run command: wscript.exe "\\deploy2012\deploymentshare$\scripts\ZTIGath
er.wsf" /nolocalonly
Command completed, return code = 0
Validating connection to \\DEPLOY2012\DeploymentShare$
Mapping server share: \\DEPLOY2012\DeploymentShare$
Already connected to server DEPLOY2012 as that is where this script is running f
rom.
Found Existing UNC Path Z: = \\DEPLOY2012\DeploymentShare$
Property LTIDirty is now = TRUE
About to run command: MSHTA.exe "\\DEPLOY2012\DeploymentShare$\Scripts\Wizard.ht
a" /definition:DeployWiz_Definition_ENU.xml
Command completed, return code = 0
Validating connection to \\DEPLOY2012\DeploymentShare$
Mapping server share: \\DEPLOY2012\DeploymentShare$
Already connected to server DEPLOY2012 as that is where this script is running f
rom.
Found Existing UNC Path Z: = \\DEPLOY2012\DeploymentShare$
Property DeployDrive is now = Z:
DeployDrive = Z:
Property ResourceRoot is now = \\DEPLOY2012\DeploymentShare$
DeploymentType = CUSTOM
ResourceRoot = \\DEPLOY2012\DeploymentShare$
Property ResourceDrive is now = Z:
ResourceDrive = Z:
Property _SMSTSPackageName is now = Lite Touch Installation
SMS Task Sequencer found at \\DEPLOY2012\DeploymentShare$\Tools\X64, copying to
C:\MININT\Tools\X64
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\CcmCore.dll to C:\MININT\Tools\X
64\CcmCore.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\CcmUtilLib.dll to C:\MININT\Tool
s\X64\CcmUtilLib.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\Smsboot.exe to C:\MININT\Tools\X
64\Smsboot.exe
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\SmsCore.dll to C:\MININT\Tools\X
64\SmsCore.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TsCore.dll to C:\MININT\Tools\X6
4\TsCore.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TSEnv.exe to C:\MININT\Tools\X64
\TSEnv.exe
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TsManager.exe to C:\MININT\Tools
\X64\TsManager.exe
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TsmBootstrap.exe to C:\MININT\To
ols\X64\TsmBootstrap.exe
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TsMessaging.dll to C:\MININT\Too
ls\X64\TsMessaging.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TsProgressUI.exe to C:\MININT\To
ols\X64\TsProgressUI.exe
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\TSResNlc.dll to C:\MININT\Tools\
X64\TSResNlc.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\xprslib.dll to C:\MININT\Tools\X
64\xprslib.dll
Copying \\DEPLOY2012\DeploymentShare$\Tools\X64\00000409\tsres.dll to C:\MININT\Tools\X64\00000409\tsres.dll
Copying \\DEPLOY2012\DeploymentShare$\Control\WIN8MASTER-V2\TS.XML to C:\MININT\Tools\X64
Copying C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to C:\MININT\Tools\X64\VARIABLES.
DAT
LTI beginning deployment
Event 41016 sent: LTI beginning deployment
About to run command: "C:\MININT\Tools\X64\TsmBootstrap.exe" /env:SAStart
Property LTIDirty is now = TRUE
New window pops up... Generalize phase sysprep plugins...
Then reboots, it starts loading files before the BOD

ADK 8.1 Update 1 breaks sysprep and capture

I have three different MDT-installations providing me with one fully automated ref.image i then use in two different systems depending if the computer is in school or in other community service.
i recently updated the ADK to the one released just a few days ago (http://www.microsoft.com/en-US/download/details.aspx?id=39982) and now my ref.image capture process is broken. the capture will not
happen and i get this error message:
Error creating an image of drive C:, rc = 1
ZTI ERROR - Non-zero return code by ZTIBackuo, rc = 1
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Create WIM. Execution of task sequence failed.
Incorrect function. (Error: 00000001; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task Sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. COde 0x80004005
i also have this issue in one of the other installations which also is used to provide our computer supplier with a correct WIM-file.
so, i did what most people would do i guess... i reinstalled the older version of ADK and now i got it working in both my enviroments used to create WIM-files...
how can i provide information in order to solve this issue?
i would guess i rather have the new ADK installed instead of the old one, but the new one is not working properly.

If you are still having problems, please upload your bdd.log and smsts.log files to a public site like OneDrive and share the link here.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

CMP and capture-schema problems

I am trying to deploy a CMP on Sun App Server 8, and I'm having a few problems. I am quite new to both CMP and Sun App Server 8.
I've created a simple table Room in mySQL DB, containing only id (varchar) and description (varchar). I'm running this command to capture the table schema
capture-schema -username username -password pwd -dburl jdbc:mysql://localhost/test -driver com.mysql.jdbc.Driver -out test.dbschema
Do I need to enter the -schemaname and -table parameters as well? I'm assuming that since the url is pointing directly to the test schema in mySQL and it only contains the room table, I don't need these 2 parameters.
test.dbschema gets generated, but when I use the deployment tool and create the database mappings to the entity bean using this schema file, no mappings are created.
Any help?

Hello,
I have similar problem and I'm really confused about it.
Working with:
Java System Application Server Platform Edition 8.1 2005Q1 UR1
mysql DataSource and Container Managed Persistence
mysql-connector-java-3.0.8-stable-bin.jar
I have problem with deploy:
Fatal Error from EJB Compiler -- JDO74025: JDOCodeGenerator: Caught an Exception validating CMP bean 'Sets' in application 'isvl' module 'isvl-EJBModule': JDO72335: If the table sets for the bean corresponding to the generated class isvl.model.set.SetBean470758938_JDOState is mapped as the primary table, it must have a primary key.Choose a different primary table or verify that the contents of the schema file are correct.
Choose a different primary table or verify that the contents of the schema file are correct. at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:274) at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:615) at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:563) at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java :340) at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:209) at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:284) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:176) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.j ava:107) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:146) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPh ase.java:71) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeplo ymentService.java:633) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentSe rvice.java:188) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentSe rvice.java:520) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:143) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:172)
Have you seen this problem?
Thanks.

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.

Log and capture problems for HDV using FCP 5.0.1

I cant seem to get a picture in my log and capture browser when using HDV. The screen says my camera is connected, I see timecode correctly rolling in sync with my cameras timecode, I can use the controls, but no picture on the screen?
When I hit capture now, the capture screen pops up and gives a message "waiting for data from device".
we shot at 720p at 25fps, there is no capture preset for this in my version of FCP. Could this be the problem? Please help!!

Thanks for responding.
It's a mac osx 10.4.11 and a 2 ghz intel core duo. I'm using easy set up in final cut pro, but there is no option for hd fire wire basic (which apple support told me to look for). The only hd options are 1080i50, i60 and 720 p30. The other hd options are for the apple intermediate codec. When I use the easy set up for hd 1080i60, then go to log and capture, it doesn't give me the preview window to set in's out, batch capture etc. It only lets me capture straight from the camera and I have to manually stop it and start it which is a major pain. Plus the clips need to be rendered once I put them in a timeline. I've shot and edited on mini dv with final cut for nearly 7 years, but now that i've tried to upgrade and shoot hd mini dv, all of these problems have arrived in capturing. I'm starting to think my version of final cut pro (5.0.1) just doesn't work with hd, unless it's very time consuming. Any ideas?

Officejet Pro 8600 e. Problem scanning from Scan and Capture App in Win 8.1

Officejet Pro 8600 e. New.
Installed on HP Envy 23 Touch. Running Windows 8.1.
Wireless set up. Prints fine. Problem is scanning from the HP Scan and Capture Software App in Win 8.1
Using Scan and Capture App I can scan photos fine. They come out clear. Scanning documents in GRAY has multiple bands/lines in gray over the entire page running vertically. Scanning documents in COLOR are fine.
Also, if I scan from the printer directly using the touch screen on the printer, the scan output is fine.
I did the Scan utilty to discover any errors and it did not show any. I think it's a software error. I am going to uninstall the HP Scan App and then reinstall. So, I will do the uninstall/reinstall and report back.
Also, I would like to know if there is a desktop program for scanning? I would prefer to use that instead of the Modern HP Scan and Capture App.
Thanks....
This question was solved.
View Solution.

Hi artrum,
I understand you've been experiencing issues scanning from your Officejet 8600 using the Windows Scan and Capture program. I will certainly do my best to help you with this!
From what you've explained, I believe you're correct, it does seem like it's an issue just with the Windows Scan and Capture program and as you've been able to scan from the front panel of the printer you definitely have the HP software installed. What I'd like to do is have you use the HP Scan software, where you should no longer run into issues.
To access the HP Scan software and be able to access it easily from your desktop I'd like you to follow the steps below:
1. Go to your start screen and just start typing File Explorer. You should be able to then open it to access your computer's files.
2. Then open Local Disk (C: ), followed by Program Files (x86), followed by HP, then HP Officejet Pro 8600, followed finally by bin.
3. In the bin folder you should see HPScan. You will want to right click on HPScan and go to Send To and then select Desktop.
Now you should see HP Scan on your desktop and be able to open it and scan through that application.
Hope this helps, have a great day!
Please click “Accept as Solution ” if you feel my post resolved your issue, as it will help others find the solution faster
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
**MissTeriLynn**
I work on behalf of HP

I have a 17" Macbook pro with flickering red and cyan(blue) lines across the screen. The issue disappears temporarily when I tap on the computer, and the problem does not occur when I use external display or try to screen capture the problem.

I purchased my Macbook (17") through a certified apple tecnition in August 2012, it was refurbished and the motherboard was completely replaced. I do a lot of photo editing, but I have been unable to do so because of the red vibrating lines that interrupt my screen. The issue disappears temporarily when I tap on the computer, and the problem does not occur when I use external display or try to screen capture the problem. I brought the computer back to the technition I purchased it from and he said that it was a problem with my fan, so I have two new fans but the issue is still occuring. He says he doesnt know whats wrong. Does anyone have any information on this issue?
Here is an image of the issue
http://www.flickr.com/photos/67839707@N08/8884847081/

I recommend having your Mac serviced by someone competent. A force sufficient to "blow apart" the fans was clearly excessive and may have damaged the display cable, as well as any number of other problems.
Dust is properly cleaned with a vacuum, preferably one designed for computer service, and they are not cheap.
Compressed air should never be used. It just blows dust everywhere, often into places where it can no longer be removed.

Sysprep and Capture TS problems

Similar Messages

Maybe you are looking for