OSD - Build and Capture - Client reinstall

Hey guys -
In our current "reference" image, we have Office, .NET framework, and security updates integrated into the WIM.  We then advertise the WIM, and add more applications, the SCCM client itself (which doesn't exist in the WIM) and any new updates.
I've gotten our first "Build and Capture" using OSD itself - which *has* the SCCM client already in the image.
However, OSD still wants to re-install the client during the Setup Windows and ConfigMgr action.
1) Is this normal to re-install the client even if a perfectly good client is already there in the WIM?
2) Any way to avoid this?  it's just a waste of time.  In the old days we'd just re-generate GUIDs which took a few seconds versus a few minutes.
Thanks!

This is expected behaivor... This is how the product was designed...
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Similar Messages

  • Question on OSD Build and Capture

    Hello,
    I'm sorry if this is something simple but I'm having trouble finding what I need online. I built up a windows 7 device and only made changes necessary so PowerShell 4.0 was on and Java. I setup build and capture media and was able to capture the OS, but it
    didn't capture the installed components. Is there something simple I'm missing?

    More info:
    Planning for Capturing Operating System Images in Configuration Manager
    http://technet.microsoft.com/en-us/library/gg712328.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Osd build and capture with copy profile

    I used the build and capture ts from sccm 2012 r2 to create my windows 7 64bit. I did not realize I would loose the administrator customization. How to keep those changes that I was planning to use as default user setting when deploy it? 
    Thanks

    If you need to customise the image (if there are some customisations that you can't do by Group Policy) then you should create it using MDT. MDT supports copyprofile
    http://www.gerryhampsoncm.blogspot.ie/2014/03/create-customised-reference-image-with.html
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Workgroup Installing Client Fails (Build and Capture) - Windows 7 x64

    Hi, I'm trying to configure a Build and Capture TS for Windows 7 x64 but the client always fails to find my site during installation, which means I can't install updates and applications. I'm running SCCM 2012 SP1 and the ConfigMgr2012-SP1-KB2801987-X64-ENU
    hotfix has already been installed.
    I'm using the SMSMP=XX.XX (and SMSSITECODE=XXX) options but the log always says "No MPs were specified from commandline..."
    I've done a huge amount of searching and it seems like it should be possible to end up with a client installed on a workgroup computer with the correct side code (and displaying "Currently Internet"), which should allow updates to be installed
    during the TS, but I can't get it to work! Any help would be greatly appreciated.
    Here's part of my ccmsetup.log file :
    ==========[ ccmsetup started in process 2332 ]========== ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Running on platform X64 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Launch from folder D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CcmSetup version: 5.0.7804.1500 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Running on OS (6.1.7600). Service Pack (0.0). SuiteMask = 256. Product Type = 1 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Ccmsetup command line: "D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\XXX00034 /config:MobileClient.TCF /status:572 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Command line: "D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\XXX00034 /config:MobileClient.TCF /status:572 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Copying config file from D:\_SMSTaskSequence\OSD\XXX00034\MobileClient.TCF to folder D:\WINDOWS\ccmsetup\. Return result: 0x0 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    SslState value: 224 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPPORT: 80 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPSPORT: 443 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPSSTATE: 0 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPSCERTNAME: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    FSP: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMFIRSTCERT: 1 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Config file: D:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Retry time: 10 minute(s) ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    MSI log file: D:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    MSI properties: INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="XXX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="1" ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Source List: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    MPs: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    None ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    No version of the client is currently detected. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
    Updated security on object D:\WINDOWS\ccmsetup\. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
    A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
    Downloading file D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Downloading D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe to D:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 17% complete (262144 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 35% complete (524288 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 53% complete (786432 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 71% complete (1048576 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 89% complete (1310720 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 100% complete (1457840 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Download complete. ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Running as user "SYSTEM" ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Detected 928475 MB free disk space on system drive. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Checking Write Filter Status. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Unexpected row count (0) retrieved from AD. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Failed to get site version from AD with error 0x80004005 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteCode: XXX ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteVersion: ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Downloading file ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Determining source location... ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found accessible source: D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found available source D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Downloading D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.cab to D:\WINDOWS\ccmsetup\ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    File download 100% complete (9613 of 9613 bytes). ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Download complete. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)

    Thanks for the reply. You're right, I'm setting the SMSMP and SMSSITECODE in the command line of the package itself, not the TS properties box. I have tried both ways, in fact every combination I could think of and nothing seems to produce an installed client
    which knows its site (and both ways produce almost identical logs, which makes me think the properties are being ignored from either location).
    The log doesn't actually contain any error messages which seem relevant at all, but here's some chunks with all of the errors (the log was too big to post in its entirety) :
    Download complete. ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Running as user "SYSTEM" ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Detected 928475 MB free disk space on system drive. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Checking Write Filter Status. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Unexpected row count (0) retrieved from AD. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Failed to get site version from AD with error 0x80004005 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteCode: XXX ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteVersion: ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Downloading file ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Determining source location... ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found accessible source: D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found available source D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Discovering whether item 'x64/MicrosoftPolicyPlatformSetup.msi' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Couldn't find a product with MSI upgrade code '{19B9818B-7432-49E9-BC02-B126025EE235}' in the MSI database. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Item x64/MicrosoftPolicyPlatformSetup.msi has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'x64/WindowsFirewallConfigurationProvider.msi' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    File 'D:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Item x64/WindowsFirewallConfigurationProvider.msi has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'i386/Silverlight.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    32-bit Hive selected ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Item i386/Silverlight.exe has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'i386/dotNetFx40_Client_x86_x64.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Detected item 'i386/dotNetFx40_Client_x86_x64.exe' ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'SCEPInstall.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Couldn't determine site version for site 'XXX'. Let client deployment continue. ccmsetup 6/06/2014 10:58:16 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterHostedApplications. Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterEndpointsInit. Gathers information such as log file name on each endpoint to be registered on the system. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterEndpoint. Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterSystemTasksInit. Processes the CcmSystemTask table and passes this information to CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterSystemTaskRollback. Rolls back the changes made by CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterSystemTask. Registers a System Task with WMI. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:02: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action ccmsetup 6/06/2014 11:01:02 AM 2336 (0x0920)
    MSI: Action 11:01:02: CcmRegisterComponentsInit. Generates the list of components for CcmRegisterComponets action to register. ccmsetup 6/06/2014 11:01:02 AM 2336 (0x0920)
    MSI: Action 11:01:03: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:03: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:03: SmsMigrateSwDistHistory. Migrate software distribution history. ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:03: CcmInstallUtilInit. Initializing InstallUtil.exe to register .net WMI provider ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:04: CcmStopService. Stops the ccmexec service. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: StopServices. Stopping services ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: SmsUninstallPrepDrvr. Uninstalling Software Metering PREP Driver ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: SmsStopUIComponents. This custom action forces all open client UI components to stop and exit. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: SmsStopUserComponents. This custom action forces all open client UI and SCNotification components to stop and exit. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: CcmUnloadWmiProviders. Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterHostedApplicationsRollback. Rollback the registration of hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterHostedApplications. Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterEndpoint. Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterSystemTaskRollback. Rolls back the changes made by CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterSystemTask. Registers a System Task with WMI. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterPerfCountersRollback. Rolls back any changes made by CcmRegisterPerfCounters if install fails. ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmInstallUtil. Calling InstallUtil.exe to register .net WMI provider ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:33: SmsSetLUAAccessPermissions. >Gets permission for evelation on Vista and grants each COM object permission. ccmsetup 6/06/2014 11:01:33 AM 2336 (0x0920)

  • Build and Capture TS fails in "Prepare Configuration Manager Client" task

    I have a ConfigMgr 2012 R2 + CU1 I use for Windows 7 deployment.
    I have made a "build and Capture" TS in ConfigMgr that I use to build my reference image.
    When I run the TS it fails at the "Prepare Configuration Manager Client" step where I get the following error:
    The task sequence execution engine failed executing the action (Prepare Configuration Manager Client) in the group (Capture the Reference Machine) with the error code 2147749938
    Action output: ... 1 instance(s) of 'SMS_MaintenanceTaskRequests' successful
    Successfully reset Registration status flag to "not registered"
    Successfully disabled provisioning mode.
    Start to cleanup TS policy
    getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=80041032 (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,463)
    ns.Query(sQuery, &spEnum), HRESULT=80041032 (e:\qfe\nts\sms\framework\tscore\utils.cpp,3666)
    End TS policy cleanup
    TS::Utility::CleanupPolicyEx(false), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,564)
    pCmd->Execute(), HRESULT=80041032 (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)
    Wmi query 'select *from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0x80041032
    Failed to delete policies compiled by TaskSequence (0x80041032)
    Failed to prepare SMS Client for capture, hr=80041032
    Failed to prepare SMS Client for capture, hr=80041032. The operating system reported error 2147942402: The system cannot find the file specified.
    If I disable the "Install Software Updates" part of my TS it will run without probems. It installs 154 updates during the build.
    I have seen another reference to this problem on this forum but why should the large number of the updates be the reason why the task sequcens cannot prepare the SCCM client for capture.
    Sounds to me that it's a BUG :-(
    Thomas Forsmark Soerensen

    I'm glad I'm not the only one running into this.  I've been racking my brain for the past few days trying to figure out where I went wrong. 
    SCCM 2012 R2 CU1
    Installation properties in TS: SMSMP=mp.f.q.d.n FSP=mp.f.q.d.n DNSSUFFIX=f.q.d.n PATCH="%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp;%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2938441\Client\x64\configmgr2012ac-r2-kb2938441-x64.msp"
    Drop Windows 7 WIM that has all the updates Schedule Updates (offline servicing) installed (169 of 277)
    Apply several updates offline (the dual-reboot Windows 7 updates among others)
    Run Windows Updates more than once to be sure I get everything
    Breaks at the preparing client for capture step
    Is this:
    a bug?
    a known issue
    something that's just frowned upon for no technical reason?
    I'd love to hear from an SCCM guru [at Microsoft] on what the heck is going on here.

  • 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

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

  • 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

  • Install Updates step fails in Build and Capture (error code 87D00272)

    Hello,
    I was really hoping someone could help me with this.
    Background information:
    - We have a CM07 server in a production environment.
    - I've set up a CM12 RTM server, following the guides in this forum, with the hopes of migrating soon.
    - I wanted to do OSD from scratch to learn more and to take advantage of new features in CM12.
    - I have a few virtual machines running for testing OSD/apps (these are the only clients managed by my CM12 server).
    - Since it's not possible to have two WDS servers running at the same time AFAIK (without using registry tweaks, the F11 trick, that by the
    way doesn't work for me) I have created a bootable TS media that I mount on the virtual machines whenever I want to test OSD.
    Now, to my problem:
    I can't figure out why my Build and Capture TS is failing on the Install Software Updates step. smsts.log file says: Failed
    to RefreshUpdates, hr=087d00272, followed by: Failed to run the action: Install Software Updates. Component is disabled (Error: 87D00272; Source: CCM).
    I have read about similar issues occurring in CM07 capture task sequences since the machine is joined to a Workgroup. The proposed solution was adding SMSSLP=FQDN to the client installation properties, but since that functionality is moved to the MP in CM12,
    it should be enough to specify SMSMP=FQDN in my case. It's not working anyway. Tried it to a Deploy TS also, where the machine is domain joined, but I got the same error.
    The error code 87D00272 returns no results on Google. This stumps me, as someone surely has had the same problem? Here are the relevant portions
    of the smsts.log file
    If someone had the chance to look at this, I would greatly appreciate it. Thank you!
    Refreshing Updates InstallSWUpdate 2012-06-13 10:15:33 228 (0x00E4)
    spInstall->RefreshTargetedUpdates( spCallback, &bAlreadyCompleted ),
    HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
    \installswupdate.cpp,467) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
    Failed to RefreshUpdates, hr=0x87d00272 InstallSWUpdate 2012-06-13 10:15:34 228
    (0x00E4)
    RefreshTargetedUpdates(spInstall, spCallback, bAlreadyCompleted), HRESULT=87d00272
    (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
    \installswupdate.cpp,1295) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
    RefreshUpdates(), HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment
    \installswupdate\installswupdate.cpp,906) InstallSWUpdate 2012-06-13 10:15:34
    228 (0x00E4)
    InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle),
    HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
    \main.cpp,248) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
    Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 2012-06-13
    10:15:34 228 (0x00E4)
    Process(pInstallUpdate, tType), HRESULT=87d00272 (e:\nts_sccm_release\sms\client
    \osdeployment\installswupdate\main.cpp,304) InstallSWUpdate 2012-06-13 10:15:34
    228 (0x00E4)
    Process completed with exit code 2278556274 TSManager 2012-06-13 10:15:34
    912 (0x0390)
    ---------! TSManager 2012-06-13 10:15:34 912 (0x0390)
    Failed to run the action: Install Software Updates.
    Component is disabled (Error: 87D00272; Source: CCM) TSManager 2012-06-13
    10:15:34 912 (0x0390)
    MP server http://CFGMGR-SRV.zenit.brummer.se. Ports 80,443. CRL=false. TSManager
    2012-06-13 10:15:34 912 (0x0390)
    Setting authenticator TSManager 2012-06-13 10:15:35 912 (0x0390)
    Set authenticator in transport TSManager 2012-06-13 10:15:35 912 (0x0390)
    Sending StatusMessage TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting message signatures. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting the authenticator. TSManager 2012-06-13 10:15:35 912 (0x0390)
    CLibSMSMessageWinHttpTransport::Send: URL: CFGMGR-SRV.zenit.brummer.se:80  CCM_POST
    /ccm_system/request TSManager 2012-06-13 10:15:35 912 (0x0390)
    Request was succesful. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Set a global environment variable _SMSTSLastActionRetCode=-2016411022 TSManager
    2012-06-13 10:15:35 912 (0x0390)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager
    2012-06-13 10:15:35 912 (0x0390)
    Clear local default environment TSManager 2012-06-13 10:15:35 912 (0x0390)
    Let the parent group (Setup Operating System) decides whether to continue execution
    TSManager 2012-06-13 10:15:35 912 (0x0390)
    The execution of the group (Setup Operating System) has failed and the execution has
    been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 2012-06-13
    10:15:35 912 (0x0390)
    Failed to run the last action: Install Software Updates. Execution of task sequence
    failed.
    Component is disabled (Error: 87D00272; Source: CCM) TSManager 2012-06-13
    10:15:35 912 (0x0390)
    MP server http://CFGMGR-SRV.zenit.brummer.se. Ports 80,443. CRL=false. TSManager
    2012-06-13 10:15:35 912 (0x0390)
    Setting authenticator TSManager 2012-06-13 10:15:35 912 (0x0390)
    Set authenticator in transport TSManager 2012-06-13 10:15:35 912 (0x0390)
    Sending StatusMessage TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting message signatures. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting the authenticator. TSManager 2012-06-13 10:15:35 912 (0x0390)
    CLibSMSMessageWinHttpTransport::Send: URL: CFGMGR-SRV.zenit.brummer.se:80  CCM_POST
    /ccm_system/request TSManager 2012-06-13 10:15:35 912 (0x0390)
    Request was succesful. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Launching command shell. OSDSetupHook 2012-06-13 10:15:45 1932
    (0x078C)
    executing command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 2012-06-13
    10:15:45 1932 (0x078C)
    executed command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 2012-06-13
    10:15:45 1932 (0x078C)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:
    \nts_sccm_release\sms\client    asksequence    smanager    smanager.cpp,756) TSManager
    2012-06-13 10:16:57 912 (0x0390)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 2012-06-13
    10:16:57 912 (0x0390)
    TSManager 2012-06-13 10:16:57 912 (0x0390)
    Task sequence execution failed with error code 80004005 TSManager 2012-06-13
    10:16:57 912 (0x0390)

    I can add that I've looked at the Site Status in the Monitoring tab, and everything looks green apart from some Warnings about User and System Discovery. In Component Status, I have a warning about the Distribution Point on C$. I thought placing a NO_SMS_ON_DRIVE.SMS
    file in the root of C: would mean no stuff was placed there? I can't see anything SCCM related, but it seems that it has placed a DP on C:?
    The error message about DP is: 
    Distribution Manager has not tried to install IIS component of operating system to distribution point "["Display=\\CFGMGR-SRV.zenit.brummer.se\"]MSWNET:["SMS_SITE=PS1"]\\CFGMGR-SRV.zenit.brummer.se\". You should install and configure IIS manually. Please
    ensure RDC is also enabled.

  • 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

  • Build and Capture

    I am deploying Windows 7( 64 bit) Via SCCM 2012. It was working fine but last weekend as i wanted to update our image, tried todo a build and capture its failing at "Prepare ConfigMgr Client. The client cache is currently in use by a running program
    or by a download in progress. (Error: 87D01203; Source: CCM)" I have switched off Updates and it worked fine. I have tried to search for this errors but for the life of me unable to find answer for it so far. 
    Has any once come across this issue and fixed? please let me know.
    Thanks
    Hassan

    Hi Jorgen,
    Yes I am installing applications in Build and Capture. What i did this morning was, I  turned off Updates and did a build and capture with Apps installation only and it worked fine. Then i switched off Applications installation part of it and turned
    on Updates and it worked too. The strange thing that i saw over the weekend was that : The first time around it detects 135 updates for Windows 7, installs them and reboot the machine, then i have put in another update task just in case if there are any missing
    updates. It said that there were 127 Updates missing. Then downloads them with in a minute or so. Doesn't really installs them as it goes to reboot the machine and then continues on with the rest of TS. 
    Today when i was testing with it just updates, second time around it detected only 6 updates, downloaded and installed them as per normal and continued on with the rest of TS.
    Could it be that an update that was applicable didnt get downloaded properly on to the server?
    I am in the process of doing a Build and capture with both Updates and applications turned on. Will update this post once its done.
    Thanks alot for your reply though.
    Hassan

  • Install Software Updates in a WIndows 7 build and capture shooses wrong SUP

    Hi,
    My environment is the following.
    One SCCM 2012 R2 Primary site server in a trusted domain, MP, DP and SUP. This site is reachable from the clients on the internal  network.
    One SCCM 2012 R2 server in an untrusted forest, MP, DP and SUP. This server is NOT reachable from clients on the internal nrowotk.
    I am doing a build and capture of Windows 7 using a SCCM TS on a VM on the internal network.
    When the Install Updates task Is running the SCCM client is trying to use the SUP in the untrusted forest instead of the one in the local trusted forest.
    How do I force the SCCM client to use the local SUP instead of the one in the untrusted forest.
    According to
    http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx it should prioritize the one in the local forest, but the build and capture PC is not member of the AD so it looks like it just uses the SUP that is
    first in the list from the MP.
    The blog also states that the SUP will not be shifted to the next one in the list before 4 failed scans at 30 minutes intervals so it will take more than 4 hours before the SCCM client will try the next SUP. At that time the TS has long finished the
    Software Update task.
    I thought about creating an entry in the hosts file on the capture PC with the name of the untrusted SUP and the IP of the trusted SUP to redirect the client to use the trusted SUP. I solution that might work but that I find very ugly.
    What can I do to force the SCCM client on the build and capture PC to us the internal trusted SUP?
    Thomas Forsmark Soerensen

    The SUP info cannot be got from the Internal MP. Please review the Smsts.log file.
    Juke Chou
    TechNet Community Support

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

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

  • Build and Capture - Windows 2012 no longer possible

    Dear all
    We are using SCCM SP1 and facing since May 2013 the following problem:
    Our - until May 2013 working - Task Sequence to build and capture our Windows 2012 Datacenter Image does not capture when we install updates during this sequence.
    The following steps are working:
    - Restart in Windows PE
    - Partition Disk 0
    - Apply Operating System
    - Apply Windows Settings
    - Apply Network Settings
    - Setup Windows and Configuration Manager
    If the next step is Install Updates, it installs the updates, reboot twice, shows again the status of the task sequence and then we can see the login screen from Windows 2012 instead of starting the step "Prepare Configuration Manager
    Client".
    As soon as we disable the Install Updates step, the task sequence can go to "Prepare Configuration Manager Client" and can successfully capture a new wim.
    What could be the problem? Thanks for any hints.
    best
    JBAB

    check your windowsupdate.log and see what updates it's installing, one or more of them is causing a reboot which the task sequence does not expect or like and that is probably your issue, remove that update(s) from the deployment and start again
    Step by Step Configuration Manager Guides >
    2012 Guides |
    2007 Guides | I'm on Twitter > ncbrady

Maybe you are looking for