Build and capture task sequence stops after apply windows updates

Hi
SCCM 2012 SP1 CU4. Deploying Windows 7 SP1.
Pulling my hair out over this one. I successfully performed a build and capture installing some applications. When I choose to install Windows updates, the updates install, the system reboots then doesn't continue. Applications don't install, image isn't captured.
I've tired using the default B&C TS and receive the same results. I've amended the TS to as follows, as suggested in a technet forum post: https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd
Looking at smsts.log there's errors relating to not accepting the license agreement, but I didn't think this would stop the TS. 
Can someone point out why the deployment stops?
https://dl.dropboxusercontent.com/u/23479177/smsts-20141113-182413.log 
Cheers

This is very common scenario you´re having! :)
For OSD and for Capture I always create myown Software Update Group, which lets me totally control, what updates goes to the image and which doesn´t. I then edit membership of update and tag or un-tag update to the group.
I suggest you do the following:
1. Create manual Computer record and add it to OSD Capture collection.
2. Create SUG for OSD Capture and un-tag updates which are listed in KB2894518. But that might not be enough.
3. Deploy TS to the OSD Capture collection.
4. Create/modify virtual machine with MAC matching the computer record.
5. Run PXE and hook Capture TS.

Similar Messages

  • 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

  • Build and Capture task sequence fails at 'Prepare ConfigMgr Client for Capture' step

    The scenario is as follows:
    Task Sequence is a Build and Capture of Windows 7 SP1 x64 Enterprise
    There are 17 Applications installed split into 2 'Install Application' steps due to the 9 item limit
    129 Software Updates are installed
    SCCM 2012 RTM
    I have built and captured on this system previously however there were no 'applications', just traditional SCCM 'packages'
    All task sequence steps run successfully until it gets to the 'Prepare ConfigMgr Client for Capture' step and it fails here. Here are the relevant parts of the SMSTS.log file:
    <![LOG[No certificates to delete]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1013">
    <![LOG[Deleting Client properties from file C:\Windows\SMSCFG.INI succeeded.]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:922">
    <![LOG[Reseting the Trusted Root Key successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1088">
    <![LOG[Deleting instance of 'CCM_Client' successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:170">
    <![LOG[Successfully reset Registration status flag to "not registered"]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:309">
    <![LOG[Successfully disabled provisioning mode.]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1273">
    <![LOG[Start to cleanup TS policy]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2773">
    <![LOG[getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,389)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient"
    context="" type="0" thread="2880" file="wminamespace.cpp:389">
    <![LOG[ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,2800)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2800">
    <![LOG[Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="utils.cpp:2800">
    <![LOG[End TS policy cleanup]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2821">
    <![LOG[TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,457)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880"
    file="preparesmsclient.cpp:457">
    <![LOG[Failed to delete policies compiled by TaskSequence (0xffffffff)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:457">
    <![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:472">
    <![LOG[pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="main.cpp:136">
    <![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="main.cpp:136">
    <![LOG[Process completed with exit code 4294967295]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="commandline.cpp:1098">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="instruction.cxx:3011">
    <![LOG[Failed to run the action: Prepare ConfigMgr Client for Capture. 
    Unknown error (Error: FFFFFFFF; Source: Unknown)]LOG]!><time="15:35:21.046-660" date="11-13-2012" component="TSManager" context="" type="3" thread="2152" file="instruction.cxx:3102">
    It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
    and removed - however I would rather avoid this very time consuming process if possible.
    I have also testing this using 'capture media' in the full OS and that also fails at the same step with the same errors in the smsts.log
    The only workaround I have for now is to let the task sequence fail at the 'Prepare ConfigMgr Client for Capture' step, then I uninstall the SCCM client using 'ccmsetup.exe /uninstall' and use the 'capture media' method - obviously with no SCCM client installed,
    it skips the 'Prepare ConfigMgr Client for Capture' step and goes straight to the 'Prepare OS' step and then to the actual capture to the WIM step.
    Anybody else seeing this or have any suggestions?
    My Microsoft Core Infrastructure & Systems Management blog -
    blog.danovich.com.au

    It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
    and removed - however I would rather avoid this very time consuming process if possible.
    You dont have to test it 18 times....
    Just test with 50% of the applications first, if it fails, test with 25% and then on of the time...
    You should be able to find the application, within 4-5 tests...
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter
    @ronnipedersen

  • 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

  • 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!

  • MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

    Hi There,
    The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
    customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
    The test machine I have been using is the Surface pro 2.
    The interesting part is after a failure is if I start the process over again ,  boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
    I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
    This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
    I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
    I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
    I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
    been edited to search and apply ther split .swm files.  This works well.
    After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt  do anything.
    I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
    Thank You in advance!

    Hi,
    Thanks Again for taking a look.
    I checked the sysprep log in the image and they look fine. No errors.
    As requested here are some logs. Let me know if I can provide anything else.
    BDD.log
    litetouch.log
    SMSTS.log
    Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
    remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
    The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

  • Print Management Console displays no printers after applying Windows Update for Windows Server 2012 R2 (KB2995388)

    After installing optional Windows Update for Windows Server 2012 R2 (KB2995388) on a print server upgraded from Windows 2012 to Windows 2012 R2, the Print Management Console wouldn't display locally shared or remotely shared printers. Another print server
    could see the printers on this server, but it couldn't see it's own. Removal of the patch resolved the issue.

    Hi,
    à
    Removal of the patch resolved the issue.
    Thanks for sharing in the forum. Your time and efforts are highly appreciated.
    On current situation, would you please let me confirm something more?
    Please check if this update rollup package (KB2995388) install successfully.
    Please run sfc /scannow command to scan all protected system files after installed this update.
    If be possible, please re-install Print Server feature on the server after installed this update. Any find?
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Build & capture task sequence fails during software update installation

    I'm sure this has been discussed a thousand times already, so I hope no one minds talking about it at least one more time.  About 6 months ago I created a reference image using a build and capture task sequence within SCCM.  After discovering
    there were certain updates that would kill a task sequence (because they required multiple restarts), I was able to exclude these updates from deployment so that my task sequence completed successfully.  Fast forward to today.  I'm working on updating
    our reference image to include the last 6 months of updates.  Again, I'm having trouble with the task sequence failing to complete.  I have excluded all of the updates mentioned in
    Microsoft KB article 2894518.  I'm able to build the image with all software updates up until 6/30/2014.  When I deploy my software group that contains updates from 7/1/2014 to 12/31/2014,
    however, the task sequence fails.  I'm pulling my hair out trying to figure out which update may be causing the issue, and trust me, I don't have much hair as it is.  So, here's my question to all of the experts out there.  What is the best
    method of debugging this issue and finding which update may be the culprit?  The log files really are confusing, so I'm hoping there are some common codes or phrases I can search for within those files.  Any and all help is much appreciated.  Thanks...

    >   I'm working on updating our reference image to include the last 6 months of updates. 
    Since this is a Build & Capture task sequence and not joined to the domain, you'll need to treat it
    like a workgroup computer.  Here are the big three things that usually trip things up:
    1.  Initial Management Point:  The Setup Windows and ConfigMgr step should have the SMSMP=<fqdn>
    property specified, as the device won't be able to see the list of MP's in Active Directory
    2.  Content Location:  Make sure the reference machine's IP address falls within an IP Range
    or Subnet ID boundary, since it can't use a AD Site boundary as a workgroup machine.
    3.  Win 7 - NTLM Fallback:  Windows 7 devices may need
    hotfix KB2522623 installed (as a package/program or with offline servicing) to ensure they fall back to NTLM properly when they fail to authenticate with Kerberos.
    If you have those 3 things taken care of, then you should copy all the logs off of the machine while the
    error message is still being displayed, zip them, and then share them out through OneDrive or Dropbox.
    I hope that helps,
    Nashs
    Nash Pherson, Senior Systems Consultant
    Now Micro -
    My Blog Posts
    If you found a bug or want the product to work differently,
    share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

  • Build and Capture - waiting to install

    I am using SCCM 2012 RTM and have started seeing an issue with our Build and Capture Task Sequence.  When performing a build and capture the system will not install anything for a day or so and anything that is advertised to it gets stuck in a "Waiting
    to Install..." status in the Software Center UI.
    When looking at the execmgr log for the client I see the following items that stick out to me:
    <![LOG[On policy activation ignore disabled policy Configuration Manager Client Upgrade Program]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="2" thread="3956"
    file="execreqmgr.cpp:7489">
    <![LOG[Mandatory execution requested for program Configuration Manager Client Upgrade Program and advertisement CM120000]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context="" type="1"
    thread="2512" file="execreqmgr.cpp:3533">
    <![LOG[Creating mandatory request for advert CM120000, program Configuration Manager Client Upgrade Program, package CM100003]LOG]!><time="10:53:36.947+300" date="01-23-2013" component="execmgr" context=""
    type="1" thread="2512" file="execreqmgr.cpp:3658">
    <![LOG[Program Configuration Manager Client Upgrade Program change to state WAITING_ENABLED]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2512"
    file="executionrequest.cpp:4618">
    <![LOG[Execution Request for advert CM120000 package CM100003 program Configuration Manager Client Upgrade Program state change from NotExist to WaitingDisabled]LOG]!><time="10:53:36.979+300" date="01-23-2013" component="execmgr"
    context="" type="1" thread="2512" file="executionrequest.cpp:503">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM100003",ProgramID="Configuration Manager Client Upgrade Program", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:53:36.979+300"
    date="01-23-2013" component="execmgr" context="" type="1" thread="2512" file="event.cpp:410">
    <![LOG[Policy arrived for child program insNCR-MPOSUIControls-1.0]LOG]!><time="10:57:50.240+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
    <![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:50.287+300" date="01-23-2013" component="execmgr" context=""
    type="1" thread="3956" file="event.cpp:410">
    <![LOG[Mandatory execution requested for program * and advertisement CM120006]LOG]!><time="10:57:50.865+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:3533">
    <![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:51.037+300" date="01-23-2013" component="execmgr" context=""
    type="1" thread="3996" file="event.cpp:410">
    <![LOG[Creating mandatory request for advert CM120006, program *, package CM10001F]LOG]!><time="10:57:51.053+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956"
    file="execreqmgr.cpp:3658">
    <![LOG[Policy arrived for child program insRCS-FLIB_2_PlatformRuntime-5.5.5007]LOG]!><time="10:57:51.084+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996" file="execreqmgr.cpp:6847">
    <![LOG[The created request is a Task Sequence request]LOG]!><time="10:57:51.115+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="execreqmgr.cpp:1065">
    <![LOG[Execution Request for advert CM120006 package CM10001F program * state change from NotExist to WaitingDependency]LOG]!><time="10:57:51.678+300" date="01-23-2013" component="execmgr" context="" type="1"
    thread="3956" file="executionrequest.cpp:503">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM10001F",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:51.678+300"
    date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
    <![LOG[An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task.]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr"
    context="" type="1" thread="3956" file="executionrequest.cpp:8829">
    <![LOG[Request a MTC task for execution request of package CM10001F, program * with request id: {7BCB5674-DC91-49D8-9C52-0765E9D86984}]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context=""
    type="1" thread="3956" file="executionrequest.cpp:8848">
    <![LOG[Execution Request for advert CM120006 package CM10001F program * state change from WaitingDependency to Ready]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1"
    thread="3956" file="executionrequest.cpp:503">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CM10001F",ProgramID="*", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:52.443+300"
    date="01-23-2013" component="execmgr" context="" type="1" thread="3956" file="event.cpp:410">
    <![LOG[MTC task with id {7BCB5674-DC91-49D8-9C52-0765E9D86984}, changed state from 0 to 1]LOG]!><time="10:57:52.443+300" date="01-23-2013" component="execmgr" context="" type="1" thread="2932"
    file="execreqmgr.cpp:6268">
    <![LOG[Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="10:57:52.959+300" date="01-23-2013" component="execmgr" context=""
    type="1" thread="3996" file="event.cpp:410">
    <![LOG[Policy arrived for child program insRCS-Software_Retrieval_Agent_TAB-5.4.1]LOG]!><time="10:57:53.053+300" date="01-23-2013" component="execmgr" context="" type="1" thread="3996"
    file="execreqmgr.cpp:6847">
    <![LOG[MTC queeued a task for SWD execution request with program id: *, package id: CM10001F for execution.]LOG]!><time="10:57:53.068+300" date="01-23-2013" component="execmgr" context="" type="1"
    thread="2932" file="execreqmgr.cpp:6481">
    <![LOG[Package CM10001F, program * is ready but can not be started because package , program  is currently running.]LOG]!><time="10:57:53.068+300" date="01-23-2013" component="execmgr" context=""
    type="1" thread="2932" file="executionrequest.cpp:9083">
    When I use the same Task Sequence (or any other deployment) on a system built from our old .WIM created with the same Build and Capture Task Sequence they always install immediately.  I am thinking it has something to do with the default SCCM Client
    upgrade package available by default, but I had our SCCM owner verify that has been disabled in the hierarchy.
    The deployments are set to ignore maintenance windows and things of that nature.  It appears to be an issue with the agents state when it comes up out of the build process.  It checks in with the Site and processes assignments for Compliance (DCM)
    without issues as well.  The build and capture new WIM/System builds just seem to not want to install anything.
    What makes this issue even more odd is that if I leave the system on for several days sitting at the "Waiting to Install..." state, the agent finally works out whatever issue it is stuck on and begins to work without issues.  If I don't use
    the WIM for several days after it was created, the WIM will also stop experiencing the issue too.
    Has anyone else run into this too?  This was working a couple months back and I went to create a new WIM in December and it hasn't work correctly since.
    Thanks..Jon
    Jon Kaloz

    I have identified the source of the problem, but no solution yet.   The blocking program is found under SMS_MaintenanceTaskRequests in the local client WMI Namespace Root\CCM\SMS_MaintenanceTaskRequests.  The GUID that is found in there has
    a matching TaskID to a TaskID found in the SMSTS from the Build and Capture Task Sequence logs.
    This is found in the SMSTSLog from the Build and Capture process showing the same Task GUID referenced (followed by a failure I cannot find good info on).  C:\SMSTSLog\SMSTS.log
    <![LOG[Set command line: "C:\_SMSTaskSequence\OSD\CM100035\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\CM100035 /config:MobileClient.TCF /status:644]LOG]!><time="14:21:37.225+300" date="01-24-2013" component="OSDSetupHook"
    context="" type="0" thread="2132" file="commandline.cpp:705">
    <![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\CM100035\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\CM100035 /config:MobileClient.TCF /status:644]LOG]!><time="14:21:37.225+300" date="01-24-2013"
    component="OSDSetupHook" context="" type="1" thread="2132" file="commandline.cpp:801">
    <![LOG[Process completed with exit code 0]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="commandline.cpp:1098">
    <![LOG[Install succeeded. Blocking other instances of ccmsetup.]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:1215">
    <![LOG[Installed Client]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:1273">
    <![LOG[Start to cleanup TS policy]LOG]!><time="14:23:30.568+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2773">
    <![LOG[TS Deleted 0 instances]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2816">
    <![LOG[TS Policy cleanup done]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2817">
    <![LOG[End TS policy cleanup]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="utils.cpp:2821">
    <![LOG[Setting variable to indicate a client installation was done]LOG]!><time="14:23:30.600+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:1284">
    <![LOG[Registering the task sequence with the execution manager in the newly installed operating system.]LOG]!><time="14:23:30.615+300" date="01-24-2013" component="OSDSetupHook" context="" type="0"
    thread="2132" file="installclient.cpp:915">
    <![LOG[Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE.]LOG]!><time="14:23:30.615+300" date="01-24-2013" component="OSDSetupHook"
    context="" type="2" thread="2132" file="installclient.cpp:918">
    <![LOG[Saving the new active request handle for the task sequence: {01DE9356-CDBD-4051-B465-F87886A61BF5}]LOG]!><time="14:23:30.615+300" date="01-24-2013" component="OSDSetupHook" context="" type="1"
    thread="2132" file="installclient.cpp:931">
    <![LOG[Failed to create instance for IMTCTokenHandler interface, hr=0x80070005]LOG]!><time="14:23:30.662+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132"
    file="installclient.cpp:949">
    <![LOG[Waiting for ccmexec process to start]LOG]!><time="14:23:30.662+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:950">
    <![LOG[CoCreateInstance succeeded]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="installclient.cpp:961">
    <![LOG[Succesfully registered the tasksequence with the execution manager]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="installclient.cpp:994">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:24:01.693+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132" file="commandline.cpp:228">
    <![LOG[Set command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="14:24:01.693+300" date="01-24-2013" component="OSDSetupHook" context="" type="0" thread="2132"
    file="commandline.cpp:705">
    <![LOG[Executing command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="14:24:01.693+300" date="01-24-2013" component="OSDSetupHook" context="" type="1"
    thread="2132" file="commandline.cpp:801">
    <![LOG[==========[ TsProgressUI started in process 3912 ]==========]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="TsProgressUI" context="" type="1" thread="3956" file="winmain.cpp:329">
    <![LOG[Unregistering COM classes]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="TsProgressUI" context="" type="1" thread="3956" file="winmain.cpp:204">
    <![LOG[Shutdown complete.]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="TsProgressUI" context="" type="1" thread="3956" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="commandline.cpp:1098">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="utils.cpp:2075">
    <![LOG[Moving logs to SMS client directory]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="basesetuphook.cpp:1356">
    <![LOG[LOGGING: Resetting log path.]LOG]!><time="14:24:01.850+300" date="01-24-2013" component="OSDSetupHook" context="" type="1" thread="2132" file="tslogging.cpp:1803">
    These are the contents of the maintenancecoordinator.log showing the Task with the same GUID starting, but never registering a completion.  After 12 hours (43200 second timeout) it will finally continue on and work as it should.
    <![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:23:46.662+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="536" file="taskqueue.cpp:727">
    <![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:23:55.912+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="4084" file="taskqueue.cpp:727">
    <![LOG[Adding task for client "tasksequence": id - "{01DE9356-CDBD-4051-B465-F87886A61BF5}", pri - 0, service window - 0, max time for sw - 43200.]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator"
    context="" type="1" thread="2556" file="taskqueue.cpp:259">
    <![LOG[Signaled task '{01DE9356-CDBD-4051-B465-F87886A61BF5}' (agent 'tasksequence').]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="2556"
    file="taskqueue.cpp:1344">
    <![LOG[Done scheduling task. Winning task '{01DE9356-CDBD-4051-B465-F87886A61BF5}' (agent 'tasksequence')]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1"
    thread="2556" file="taskqueue.cpp:1261">
    <![LOG[Task "{01DE9356-CDBD-4051-B465-F87886A61BF5}" (agent 'tasksequence') is reporting back on starting.]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context=""
    type="1" thread="2556" file="taskqueue.cpp:399">
    <![LOG[Successfully started task '{01DE9356-CDBD-4051-B465-F87886A61BF5}' (agent 'tasksequence').]LOG]!><time="14:24:00.678+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1"
    thread="2556" file="taskqueue.cpp:1517">
    <![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:27:36.544+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="2464" file="taskqueue.cpp:727">
    <![LOG[Removing tasks for agent "RebootCoord".]LOG]!><time="14:53:27.219+300" date="01-24-2013" component="MaintenanceCoordinator" context="" type="1" thread="3820" file="taskqueue.cpp:727">
    I am not sure why the task is still hanging around on the system after the build and capture sequence completes.  There are no errors during the B&C TS and I have removed everything from it as well to only be an OS install with no changes.
    Jon Kaloz

  • SCCM 2012 SP1 - Build and Capture - ReCapture impossible

    Hi all
    i upgrade my SCCM 2012 RTM to SCCM 2012 SP1 yesterday. Today i started a recapture of my Windows 7 and Windows 2008 R2 Base Image.
    For that i have 2 VMs located in different SCCM Collections. And a Build and Capture Task Sequence is deployed to the collections.
    Before SP1 the behavior was:
    - Reset Required PXE Deployment in SCCM for the VMs
    - Start VM
    - VM boots with PXE
    - VM installs and capture the Installation
    And that i could do all the time so often as i want.
    Now with SP1 it is the same procedure but just for one time. After one success Build and Capture Task, the vm is unable to do the task sequence again. The VM is booting into the PXE and then i can see in the smsts log:
    There are no task sequences available to this computer
    But there are. The Task Sequence is set to "Always rerun".
    The only "fix" is to completely recreate the computer item in sccm.
    What is here wrong? Is this a known bug?
    best
    JBAB

    Hi, your problem is that when you deploy the task over the collation you only specified "media and PXE" was available to and probably the machines that you try to capture already had the sccm client. You can try to deploy the sequence task to a collation
    including the the option "configuration manager, media and PXE", or you can also deploy the task sequence to de "unknown devices" collation and delete the objects of the two virtual machines in configuration manager

  • Install Software Updates Step fails during Build and Capture

    I have run into a problem while attempting to use the Install Software Update task during a build and capture task sequence.  I have MDT 2012U1 integrated into SCCM 2012.
    The Install Software steps find and use the Deployment Points fine and the Use Toolkit steps similarly are able to download their source files from the distribution points using the Network Access account.  The Install Software Updates step, however
    fails with an access denied error in the CAS.log.
    I have found that I can work around this problem by setting the DP to allow anonymous access.  After checking this box, the software updates install during the build and capture task sequence.  Unchecking the Allow anoymous makes the problem recur.
    I would like to not have to have the "allow anonymous access" enabled on the DPs for obvious reasons.  Other packages download correctly from the DP with anonymous access disabled - they use the network access account.  Install Software Updates
    is the only step that seems unable to use that account to talk with the DP.
    Is this a known issue?  Is there a work around?

    Thanks for the information. I will give that a try.  I do have the SMSMP & SMSSLP (not sure I need this one in 2012) filled in in the Configmgr client install settings.  Before I did that, it couldn't even find the SUP.
    I am a little skeptical that the hotfix will fix my problem since most packages are downloading from the DP fine - it is only Software Updates that are failing to download.  On the other hand, it is clearly a permissions issue since allowing anonymous
    on the DP resolves the issue, all be it in a way I am uncomfortable maintaining in the long run.
    That KB replaces a lot of key Windows system files.  Hopefully, it won't cause more problems than it solves.
    ---additional thought
    I wonder, could it be that Packages that work without this KB have package share settings with "Copy the content in this package to a packages share on Distribution Points" cleared/unchecked?  This setting is not available for patch packages
    - so I wonder if it is enabled by default behind the scenes.  That could explain why the patch packages are affected and not the other regular application packages I have are not.  All my regular packages so far do not have the
    "Copy the content" box checked. Clients would be accessing the packages differently I suppose based on whether it was through a packages share or through the new SCCM 2012 package storage thing with the hashing.

  • Client with Patch fails to install - Build and Capture

    Hi,
    We recently hit an issue where our Build and Capture task sequence, previously fully working, was deleted. As such I've had to rebuild it from documentation. So far so good. However when I now test it out, the sequence fails during the installation of the client.
    It appears to be due to access to the patch, however I can't work out why. The installation flags are:
    /mp:sccmpri01.domain.com CCMLOGMAXHISTORY=4 PATCH=\\SCCMPRI01.domain.com\HotFixes\KB2938441\Client\i386\configmgr2012ac-r2-kb2938441-i386.msp
    And the share is set for the network access account to have read/write/execute, and everyone to have read access. As it's a build and capture the machine is in a workgroup not the domain.
    The error I'm getting is most detailed in the ccmsetup folder under the client.msi.log
    MSI (s) (EC:4C) [15:51:37:441]: Unable to create a temp copy of patch '\\SCCMPRI01.DOMAIN.COM\HOTFIXES\KB2938441\CLIENT\I386\CONFIGMGR2012AC-R2-KB2938441-I386.MSP'.
    MSI (s) (EC:4C) [15:51:37:441]: Note: 1: 1708
    MSI (s) (EC:4C) [15:51:37:441]: Product: Configuration Manager Client -- Installation failed.
    MSI (s) (EC:4C) [15:51:37:441]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1635.
    I'm a little lost as to what to try next. If I install without the patch it's alright but then fails as soon as it hits the next step in the sequence.
    Any help would be great!

    You can use a UNC path in the PATCH command (but I would not recommend it) but i expect that the process above evidently does not have share or file permissions to the msp file.
    The way I do it is simply to copy the 32 and 64 bit msp's into the folder that is created by default:
    \\Server\SMS_sitecode\Client
    That way, all you need to do is update your client package, and then change the command line so that it references the local msp file instead of UNC path.

  • Getting Updated image through Config manager Build and capture process

    Hi guys,
    Looking for some pointers on getting the almost fully patched image out of configuration manager build and capture process.
    I need below pointers:
     - What and where to advertise\deploy software packages target? since its a new deployment, I believe it should be targeted to all unknown computers.
    - How many times should I call 'install update' step in TS and where?
    - What is the best way to patch image (if something is missed out during image capture) offline (since its config manager 2012 R2). when I pull schedule update list for offline schedule, does that only pull updates that are required for that image or it
    pulls everything available as updates?
    - I have done offline patch of image but still once the image is deployed it pulls office updates. Looks like , offline service just injects OS patches..right?
    Regards,
    Regards,

    - Where? That depends upon what you what. But, going by the letter of what you asked, you shouldn't deploy any applications or packages if you want them on your newly images systems, you should make them a part of the TS using Install Software and Install
    Application tasks.
    - How many times? You should only need one although depending upon what you are deploying and if you are using offline updates, some folks add more. I typically use two one right after the Setup Windows and ConfigMgr task (just like the task sequence wizard
    builds for you) to update the OS and "things" in the image and one at the end to catch additional updates for apps and components added during the TS. Note that you also have to initiate an update scan cycle for additional install update tasks to work. Do
    this by adding a run-command line task before the second Install Updates task with the proper WMIC incantation.
    - Offline Updates only injects CBS updates into the image which are typically just core OS updates. You should also update your image though to include non-CBS updates. Using a build and catpure task sequence makes this easy.
    Jason | http://blog.configmgrftw.com

  • MDT Capture Task Sequence not working correctly

    Hello All<o:p></o:p>
    I need some help to tell me what I am doing wrong. I am using Hyper V and trying to capture a image of Windows 7 x64. From within the OS I run the
    Litetouch.wsf from the deployment share. I get the normal MDT Wizard windows. I pick my capture task sequence and everything looks like it is running fine sys prep happens and I but back into windows PE I start to process the rules again and I am taken
    back to the Select task sequence screen in WinPE.  If I pick the capture task sequence again the deployment fails. <o:p></o:p>

    (posting for anyone else that found this page, this was my fix)
    I had the same problem as the initial poster apart from what I wanted to capture was a 'real' pc.  The reason my 'capture' task sequence wasn't booting into WinPE from the local disk and continuing on with the capture was because the local disk was
    being wiped when the boot wim - LiteTouchPE_x64.wim, was being run. 
    A few weeks prior to me wanting to capture a PC I'd been working out how to stop the occasional error when you boot a PC off the WDS server - “The Task Sequence Has Been Suspended”.  I was particularly interested in stopping this error as I want to
    remotely start a Win7 install on a PC, this error would stop the install happening but I wouldn't see this error and end up visiting the PC only to find the install hadn't really started.  After googling around, I found a page that explains how to edit
    the unattend.xml file in the boot image - LiteTouchPE_x64.wim, in the xml file to run the command wscript.exe X:\Deploy\Scripts\LTICleanup.wsf.  Sounded good so I done what the page said (myitforum.com/cs2/blogs/cnackers/archive/2010/10/20/microsoft-deployment-toolkit-lite-touch-lti-the-task-sequence-has-been-suspended.aspx)
    but it didn't stop the message appearing.  In the end I fixed this problem by adding the line 'SkipWizard=YES' in my customsettings.ini file.  I didn't remove the LTICleanup.wsf from unattend.xml, it didn't seem to do any harm, that was until I tried
    to capture a PC.
    When I ran though my 'sysprep and capture' task sequence, the PC would sysprep ok and then reboot, ready to capture it.  Instead of the 'capturing a WIM file' sequence I was expecting to see, I, like the original posted got shown the list of available
    task sequences window.  If you try again to run the capture sequence, it will fail as this has to be started in a running Windows environment, not in WinPE.  After several hours wondering what is going wrong, I dawned on me what was going wrong,
    the LTICleanup.wsf was being run when the boot image was being run and wiping my disk, a disk that was ready to run an existing task sequence, the capture sequence, no wonder it was failing.  Removing the LTICleanup.wsf command from within unattend.xml
    or rebuilding the boot image (by running 'Update Deployment Share' within MDT 2010) fixed the problem, the capture now worked.
    Hopefully this will help someone else like me who was wondering what was going wrong with a capture.

  • SCEP Build and Capture

    Is it a best practice to install SCEP together with its definition updates during build and capture? If yes, will the definition updates get installed during the "Install Software Update" step?

    Hi,
    Yes they will get updated, I normally don't include it in the image though but if you decide to do check out Chris Nackers post on how to install SCEP in a Task Sequence and update it as well, it is also great when deploying SCEP in the TS.
    http://www.chrisnackers.com/2012/10/18/configuration-manager-2012-installing-endpoint-protection-during-a-task-sequence/
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

Maybe you are looking for

  • RVS4000 problem with QOS

    Hello. I have problem with bandwidth management on my RVS4000. That is the way how i done it: All traffic (TCP & UDP on all ports) IP range 192.168.0.2 - 192.168.0.2 (My IP adress) Guaranted download speed 1kbps Maximum download speed 5000kbps after

  • Strange images suddenly apprearing

    Strange images.. A girl with bleeding teeth suddenly appeared in my gallery. I dont have any idea how this photo can appear in my gallery. did this happen before?

  • Floating screen within Photoshop Elements

    I am running Photoshop Elements 12 on a Macbook Pro with a Retina Display.  In Photoshop Elements Organizer the screen is floating up above the menu bar and I can not access the menu to create new albums, close program, or see the top of my photos at

  • Calling Fortran from Java

    Is it possible to call Fortran code from java??

  • Language for app development?

    Hello. I am going to design an app for iOS/Android/Windows Phone. I will be the concept/UI designer and will team up with a developer at a later date. What language should this be developed in, and what is the best way to make it accessible to all of