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

Similar Messages

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

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

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

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

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

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

Installing Visual Studio runtimes on Build and Captures

Greetings,
I was just wondering how many of you out there install all Visual Studio runtimes in your base OS builds as part of you build and capture process. This would be the following four:
VC2005, VC2008, VC2010, VC2012 Update 4.
I'm thinking that there are so many apps these days that tend to use one or other of these versions that you might as well include them all. Is there a downside to doing this (apart from the increased OS build file size?).
Thanks
David Z

Yes. The Microsoft Visual C++ Runtime redistributable package install runtime components of Visual C++ Libraries required to run applications developed with Visual C++. They are not related to Windows.
If you deploy a x86 application on Windows 7 x64, it will require the x86 of Visual C++ Runtime.
If you deploy a x64 application on Windows 7 x64, it will require the x64 of Visual C++ Runtime.
A x86 application cannot use a x64 runtime. So yes you may need them in your image
/ Yannick Plavonil
blog: Deploiement Windows
twitter: @yplavonil
facebook:
www.facebook.com/deploiementwindows

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

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.

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

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

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

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

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

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.

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.

MDT 2013 supports build and capture win 7 SP1

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

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

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

Build and Capture

Similar Messages

Maybe you are looking for