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

Similar Messages

OSD Task Sequence fails to install SCCM client

Hello,
Our OSD task sequence fails to install the SCCM client with certain images.
The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the
task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence
If we change the image specified under "Apply Operating System" step, everything works ok.
It appears there is something wrong with this particular image. Any ideas?
Logs show no errors. Let me know which logs you'd like me to post (and from which location)
There is no ccm folder under c:\windows

Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You
can mount the Image and check those settings.
RunOnce Key Reference :
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
If the above key is present in the Image, TS Engine won't resume after the reboot.
You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
The above variable is applicable in CM 2012 SP1 and R2.
Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This
can be beneficial to other community members reading the thread.

Error editing task sequence: Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" From XML into WMI

I've started getting an intermittent error editing my Windows 7 OSD task sequence. Sometimes I can open the TS to edit, but when I try to apply changes I get the error. Other times I get the error when trying to open the TS. If I try again
right away, I still get the error, but if I wait a few minutes and try again sometimes it will open the TS.
The error reads:
ConfigMgr Error Object:instance of SMS_Extended Status{Description = "Failed to load dynamic properties for class \"SMS_TaskSequence_ApplyWindowsSettingsAction\" from XML into WMI";Error Code = 2147943746;File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";Line = 3454;Operation = "ExecMethod";ParameterInfo = "SMS_TaskSequencePackage";ProviderName = "WinMgmt";StatusCode = 2147749889;}
Coinciding with this error, I show the following entries in the TaskSequenceProvider.log file:
[PID: 7608] Invoking method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Failed to protect memory buffer, hr=0x80070542
TaskSequenceProvider
Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load node Apply Windows Settings from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "PostInstall" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "Execute Task Sequence" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load XML for the task sequence into WMI 0x80070542 (2147943746)
TaskSequenceProvider
[PID: 7608] Done with method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Setting status complete: status code = 0x80070542; Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI
TaskSequenceProvider
I exported the task sequence and checked in "object.xml" for the "ApplyWindowsSettingsAction", to see if there was something odd in the xml, but I don't find anything that jumps out as being wrong. Here's the section of XML for
that step. I've removed identifying info, and replaced it with a generic term in bold.
<step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply Windows Settings" description="" runIn="WinPE" successCodeList="0" runFromNet="false"><action>osdwinsettings.exe /config</action><defaultVarList><variable name="OSDLocalAdminPassword" property="AdminPassword"></variable><variable name="OSDComputerName" property="ComputerName">%_SMSTSMachineName%</variable><variable name="OSDProductKey" property="ProductKey"></variable><variable name="OSDRandomAdminPassword" property="RandomAdminPassword">false</variable><variable name="OSDRegisteredOrgName" property="RegisteredOrgName">COMPANY NAME</variable><variable name="OSDRegisteredUserName" property="RegisteredUserName">COMPANY NAME</variable><variable name="OSDServerLicenseConnectionLimit" property="ServerLicenseConnectionLimit">5</variable><variable name="OSDTimeZone" property="TimeZone">Central Standard Time</variable></defaultVarList></step><step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply Network Settings" description="" runIn="WinPEandFullOS" successCodeList="0" runFromNet="false"><action>osdnetsettings.exe configure</action><defaultVarList><variable name="OSDDomainName" property="DomainName">DOMAIN.COM</variable><variable name="OSDJoinPassword" property="DomainPassword"></variable><variable name="OSDJoinAccount" property="DomainUsername">DOMAIN ACCOUNT</variable><variable name="OSDEnableTCPIPFiltering" property="EnableTCPIPFiltering" hidden="true">false</variable><variable name="OSDNetworkJoinType" property="NetworkJoinType">0</variable><variable name="OSDAdapterCount" property="NumAdapters" hidden="true">0</variable></defaultVarList></step>
Is there any other log I should check for a clue on this issue? What could be causing this error?

Thanks for sharing that! I tend to save contacting MS support until after I've exhausted other options. I'm always afraid that I'll spend the $500 to open a case and then it turns out to be something simple that I would have found if I had just
kept working on it myself a little longer.
It looks like that link is for an update released in February as KB3023562. I downloaded and installed it. I'll try opening/editing/saving the task sequence a few times today to see if the issue is resolved.
After I had already installed it, I thought to look up that update in configmgr. The update is listed as superseded by 2 other updates. The newest of those is KB3046049, which just installed last night with the other March patches, so it's possible
that I didn't need to install KB3023562 after all.

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

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

Getting Updated image through Config manager Build and capture process

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

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

SCCM Task Sequence no longer installs SCCM Client

I am using SCCM 2007 R3 with SP2 and MDT 2010
My task sequences were all working fine until one of the other SCCM admins "Synced all sites" by transferring the site settings of one site to all the other sites. How this broke OSD I don't know.
At this point the best I can tell is that the SCCM client is not being installed in the Task Sequence and so when it reboots to the installed OS there is no longer any communication and the task sequence fails with an error of "Windows could not configure
one or more system components. To install Windows, restart the computer and then restart the installation.
I have run out of ideas to fix it so I am asking for the collective knowledge of the Interwebs for help.

Please post the contents of C:\Windows\ccmsetup\logs\ccmsetup.log in order for us to help you further
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

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

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

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

Build & capture task sequence fails during software update installation

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

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

Build and capture 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.

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.

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.

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.

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.

Task Sequence failed to restore captured data from USB drive onto a new machine using UDI task requence

Hi,
Environment ConfigMgr 2012 R2
Replace Scenario: Capture data to a USB external drive and Restore it from USB external drive.
Steps taken:
1) Created Computer Association with New computer and Source computer
2) Deployed UDI replace Task Sequence to Source computer and captured data to a USB external drive
3) Run UDI Task Sequence from Boot Media to Restore data from USB External drive which had the captured data.
Issue:
My task sequence failed to restore data from USB external drive.
Is there a fix
Any help is greatly appreciated it.

I created a query to see the deployment logs in real time. I see the TS fails when running "Request State Store" task. Here are the logs.
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11141 The task sequence execution engine failed execution of a task sequence. The operating system reported error 1: Incorrect function.
Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Error in the task sequence) in the group (Gather Logs and StateStore on Failure)
with the error code 1 Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' SwdAction = '0001' Set command line: Run command line Working dir 'not
set' Executing command line: Run command line Process completed with exit code 1 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft Deployment Toolkit version: 6.2.5019.0 The task sequencer
log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ZTI deployment failed, Return Code = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
Information Milestone POK 7/22/2014 4:13:14 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Copy Logs) in the group (Gather Logs and StateStore on Failure)
with exit code 0 Action output: ... 扴捡杫潲湵⹤潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就瑺獩瑥慢正牧畯摮氮杯潃祰湩⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯穜楴慴潴⹯潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散�潌獧䍜剏ⵐ䠳䑗塐就潃祰湩⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯作䑓敓畴坰穩牡⹤潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就协卄瑥灵楗慺摲氮杯潃祰湩⁧㩃坜义佄南停湡桴�潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就慐瑮敨屲湕瑡整摮䍇潃祰湩⁧潬⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯䉜䑄氮杯挠湯整瑮⁳潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌�Console
> Successfully resized the shadow copy storage association Return code from command = 0 Cleaning up default wallpaper registry keys Process completed with exit code 0 zticopylogs processing completed successfully. Command line returned 0.
Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Move State Store) in the group (Gather Logs and StateStore on Failure)
with exit code 0 Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript.exe "C:\_SMSTaskSequence\WDPackage\scripts\ztimovestatestore.wsf"' SwdAction = '0001' Command line for extension .exe is "%1" %* Set
command line: Run command lineWorking dir 'not set' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft Deployment
Toolkit version: 6.2.5019.0 The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ztimovestatestore processing completed successfully. Command line returned 0.
Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Gather) in the group (Gather Logs and StateStore on Failure) with
exit code 0 Action output: ... (BIOS is 'DELL - 1072009'). Property IsVM is now = False Finished getting virtualization info Connection succeeded to MicrosoftVolumeEncryption There are no encrypted drives Property IsBDE is now = False Processing
the phase. Determining theINI file to use. Using COMMAND LINE ARG: Ini file = CustomSettings.ini Finished determining the INI file to use. Added new custom property MYCUSTOMPROPERTY Using from [Settings]: Rule Priority = DEFAULT ------ Processing the
[DEFAULT] section ------Process completed with exit code 0 ------ Done processing CustomSettings.ini ------ Remapping variables. Property TaskSequenceID is now = Property DeploymentType is now = NEWCOMPUTER Finished remapping variables. ZTIGather processing
completed successfully. Command line returned 0 ReleaseSource() for C:\_SMSTaskSequence\Packages\POK0000F. reference count 1 for the source C:\_SMSTaskSequence\Packages\POK0000F before releasing Released the resolved source C:\_SMSTaskSequence\Packages\POK0000F.
Information Milestone POK 7/22/2014 4:13:03 PM MININT-P6E4T6G Task Sequence Engine 11130 The task sequence execution engine skipped the action (Use Toolkit Package) in the group (Gather Logs and StateStore on Failure) because
the condition was evaluated to be false.
Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Set Error Code) in the group (Gather Logs and StateStore on Failure)
with exit code 0 Action output: Finished with error code 0.
Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11124 The task sequence execution engine started the group (Gather Logs and StateStore on Failure).
Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11122 The task sequence execution engine skipped the group (Cancelled Wizard Group) because the condition was evaluated to be false.
Error Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Connect to State Store) in the group (State Restore) with the error code 1
Action output: ... ( 0x80070035 ) , trying to connect without username. The network path was not found. Unable to connect to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Sleeping for 15 seconds. Unable to connect to share: The network path was notfound. ( 0x80070035 ) , trying to
connect without username. The network path was not found. Unable to connect to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Sleeping for 20 seconds. Unable to connect to share: The network path wasnot found. ( 0x80070035 ) , trying to
connect without username. The network path was not found. Unable to connect to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Sleeping for 25 seconds. Process completed with exit code 1 ERROR - Unable to map a network drive to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Unable to connect to 563807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f ZTI ERROR - Non-zero return code by ZTIConnect,
rc = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
Warning Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11138 The task sequence execution engine ignored execution failure of the action (Request State Store) in the group (State Restore).
Error Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Request State Store) in the group (State Restore) with the error code 16389
Action output: ... etting Media Certificate. Sending request to MP
http://abcdefg.xyx.xyz.local. Setting message signatures. Setting the authenticator. CLibSMSMessageWinHttpTransport::Send: URL: abcdefg.xyx.xyz.local:80 CCM_POST /ccm_system/requestRequest was successful. migInfoRequestMessage.DoRequest (m_sResponse,true),
HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1098) pClientRequestToMP->DoRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2778) ExecuteRestoreRequestToMP(migInfoFromMP),
HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2903) ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\main.cpp,84) OSDSMPClient finished: 0x00004005 reply from server
is 'NoReply' ClientRequestToMP::DoRequest failed (0x80004005). ExecuteRestoreRequestToMP failed (0x80004005). ExecuteRestoreRequest failed (0x80004005).. The operating system reported error 1: Incorrect function.

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

Similar Messages

Maybe you are looking for