none
TaskSequence stops randomly

    Question

  • We're deploying a previously caputered Win 7 64 bit image via TaskSequence. After the OS deploy some add'l software should be installed via the TS. Randomly one task running a vbscript via a batch file hangs.

    When looking at the processes the process is gone (neither cmd.exe nor cscript.exe are running). SMSTS.log shows "Waiting for job status notification" forever. Any idea what SCCM is waiting for?

    <![LOG[Policy evaluation initiated]LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="utils.cpp:3387">
    <![LOG[Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace ]LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:370">
    <![LOG[Query path = 'CCM_SoftwareDistribution.ADV_AdvertisementID="XXX20014",PRG_ProgramID="Install",PKG_PackageID="XXX00030"']LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:401">
    <![LOG[Verified policy is compiled in 'root\ccm\policy\machine' namespace]LOG]!><time="10:50:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:426">
    <![LOG[content location count = 1]LOG]!><time="10:50:25.803-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:231">
    <![LOG[Invoking Execution Manager to install software ]LOG]!><time="10:50:25.803-120" date="08-02-2012" component="InstallSoftware" context="" type="0" thread="2220" file="installsoftware.cpp:233">
    <![LOG[Installing software for PackageID='XXX00030' ProgramID='Install' AdvertID='XXX20014' has started, jobID='{DD86D0B1-8763-4CFF-90AA-620EA0EABD07}']LOG]!><time="10:50:25.849-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:255">
    <![LOG[Setting TSEnv variable 'SMSTSInstallSoftwareJobID_XXX0030_XXX20014_Install'='{DD86D0B1-8763-4CFF-90AA-620EA0EABD07}']LOG]!><time="10:50:25.849-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:52">
    <![LOG[Waiting for installation job to complete..]LOG]!><time="10:50:25.849-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:857">
    <![LOG[Waiting for job status notification...]LOG]!><time="10:50:55.810-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:876">
    <![LOG[Waiting for job status notification...]LOG]!><time="10:51:25.787-120" date="08-02-2012" component="InstallSoftware" context="" type="1" thread="2220" file="installsoftware.cpp:876">

    Thursday, August 02, 2012 12:22 PM

All replies

  • from your log it looks like you are installing software (look at the packageID to find out what that software is)

    SMSTS.log shows "Waiting for job status notification" forever. Any idea what SCCM is waiting for?

    that can sometimes mean a window has popped up asking for somehting o0r that a script is waiting for something/keypress/whatever, but you can't see it as it's launched in system context, bring up a command prompt and open taskmgr to see if you can figure out what script is causing your problem, you can kill the wscript process and the ts should continue, but either way you need to disable this step in the task sequence and test the installation of that package using psexec as local system (psexec -ids cmd.exe context to verify that it installs correctly.



    Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

    • Marked as answer by mpfister Thursday, August 02, 2012 2:20 PM
    • Unmarked as answer by mpfister Monday, August 06, 2012 2:35 PM
    Thursday, August 02, 2012 12:52 PM
  • I know which package it hangs. When I start task manager I can't see any process of my package, no wscript.exe, no cscript.exe, no cmd.exe...

    Thursday, August 02, 2012 1:17 PM
  • And as I said, its random! Sometimes it works, sometimes it doesn't ...
    Thursday, August 02, 2012 1:22 PM
  • It might have been a popup problem. I've modified the script to make sure it doesn't happen and it finished the task this time.

    Still not clear why it sometimes worked and sometimes not. Also why no cscript/wscript process was shown in task manager.

    Hope it won't happen again. Thanks for your help

    Thursday, August 02, 2012 2:20 PM
  • Problem is back.

    Deployed the same machine 4 times, 3 times it worked, 1 time it stopped showing "Waiting for job status notification" in the log. My script writes a local log which is not created. It seems the script is not started at all.

    Any ideas?

    Monday, August 06, 2012 2:40 PM
  • You need to take a look at the execution manager log to see why your script is failing.
    Monday, August 06, 2012 10:04 PM
  • I've already looked at execmgr.log but can't see anything wrong, except when failing, execmgr.log is stopping at an early stage

    Failing

    <![LOG[Policy arrived for parent package XXX0001E program Install]LOG]!><time="16:54:44.836-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="execreqmgr.cpp:6873">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX0001E",ProgramID="Install", actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="16:54:44.851-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="event.cpp:410">
    <![LOG[Raising event:
    [SMS_CodePage(850), SMS_LocaleID(1031)]
    instance of SoftDistProgramOfferReceivedEvent
    {
     AdvertisementId = "SMS10000";
     ClientID = "GUID:394FB6D9-88E6-4B3B-BBE5-A99148DC0A40";
     DateTime = "20120806145444.851000+000";
     MachineName = "XXXX307592";
     ProcessID = 1244;
     SiteCode = "XXX";
     ThreadID = 1176;
    };
    ]LOG]!><time="16:54:44.851-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="event.cpp:729">
    <![LOG[Creating mandatory request for advert SMS10000, program Install, package XXX0001E]LOG]!><time="16:54:44.929-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="execreqmgr.cpp:3658">
    <![LOG[An existing MTC token was supplied, this execution request is not owner of MTC object.]LOG]!><time="16:54:44.945-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="executionrequest.cpp:8841">
    <![LOG[Request a MTC task for execution request of package XXX0001E, program Install with request id: {A9B52B21-D519-4028-9CA9-0BD06E92B913}]LOG]!><time="16:54:44.945-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="executionrequest.cpp:8848">
    <![LOG[Execution Request for advert SMS10000 package XXX0001E program Install state change from NotExist to Ready]LOG]!><time="16:54:44.960-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="executionrequest.cpp:503">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX0001E",ProgramID="Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="16:54:44.960-120" date="08-06-2012" component="execmgr" context="" type="1" thread="1176" file="event.cpp:410">

    **************** execmgr.log stops here!

    Working:

    <![LOG[Policy arrived for parent package XXX0001E program Install]LOG]!><time="11:49:48.335-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="execreqmgr.cpp:6873">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX0001E",ProgramID="Install", actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="11:49:48.350-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="event.cpp:410">
    <![LOG[Raising event:
    [SMS_CodePage(850), SMS_LocaleID(1031)]
    instance of SoftDistProgramOfferReceivedEvent
    {
     AdvertisementId = "SMS10000";
     ClientID = "GUID:394FB6D9-88E6-4B3B-BBE5-A99148DC0A40";
     DateTime = "20120809094948.350000+000";
     MachineName = "XXXX307592";
     ProcessID = 816;
     SiteCode = "XXX";
     ThreadID = 1488;
    };
    ]LOG]!><time="11:49:48.350-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="event.cpp:729">
    <![LOG[Creating mandatory request for advert SMS10000, program Install, package XXX0001E]LOG]!><time="11:49:48.397-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="execreqmgr.cpp:3658">
    <![LOG[An existing MTC token was supplied, this execution request is not owner of MTC object.]LOG]!><time="11:49:48.413-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="executionrequest.cpp:8841">
    <![LOG[Request a MTC task for execution request of package XXX0001E, program Install with request id: {FC6490F6-BECE-4A3F-8EA1-6609050D3C32}]LOG]!><time="11:49:48.413-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="executionrequest.cpp:8848">
    <![LOG[Execution Manager timer has been fired.]LOG]!><time="11:49:48.444-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1992" file="execreqmgr.cpp:5535">
    <![LOG[Executing program Install.cmd in Admin context]LOG]!><time="11:49:48.444-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="executionrequest.cpp:3203">
    <![LOG[Execution Request for advert SMS10000 package XXX0001E program Install state change from NotExist to NotifyExecution]LOG]!><time="11:49:48.444-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="executionrequest.cpp:503">
    <![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="XXX0001E",ProgramID="Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="11:49:48.444-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="event.cpp:410">
    <![LOG[Checking content location \\XXXSCCM01.XXX.server.net\SMSPKGG$\XXX0001E\ for use]LOG]!><time="11:49:48.475-120" date="08-09-2012" component="execmgr" context="" type="1" thread="1488" file="executioncontext.cpp:1533">
    <![LOG[Successfully selected content location

    Thursday, August 09, 2012 10:21 AM
  • The waiting for job notification , this log is in use with software update sequence,

    have you a WSUS in sccm configure?

    have a look at c:\windows\windowsupdate.log you will see what computer is waiting for and where is is trying to access .


    JEFFDEG

    Wednesday, November 14, 2012 1:52 PM
  • Hello,

    i've the same problem and it is only in 64 bit windows. Build task sequence runs sucessfully but deploy the captured image with additional packages stops every time in execmgr.

    Creating mandatory request for advert CCM2007F, program Install Silent, package CCM0003A	execmgr	03.12.2012 13:05:22	1428 (0x0594)
    An existing MTC token was supplied, this execution request is not owner of MTC object.	execmgr	03.12.2012 13:05:22	1428 (0x0594)
    Request a MTC task for execution request of package CCM0003A, program Install Silent with request id: {804723F5-BF27-4C3E-BC12-F6304B030A1F}	execmgr	03.12.2012 13:05:22	1428 (0x0594)
    Execution Request for advert CCM2007F package CCM0003A program Install Silent state change from NotExist to Ready	execmgr	03.12.2012 13:05:22	1428 (0x0594)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CCM0003A",ProgramID="Install Silent", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	03.12.2012 13:05:22	1428 (0x0594)
    

    the interesting part is "Execution Request for advert CCM2007F package CCM0003A program Install Silent state change from NotExist to Ready" in 64 bit task sequence.

    In 32 bit task sequence the packages are executed succesfully and execmgr says : "Execution Request for advert CCM2007C package ZUV003D2 program Install Silent state change from NotExist to NotifyExecution"

    Did you solved the problem?

    Monday, December 03, 2012 12:42 PM
  • i've enabled DebugLoggin and the execmgr.log say:

    Policy arrived for child program Install Silent	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    CExecutionRequestManager::OnRequestProgram - entered.	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Attempt to run program from passed location	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    \\myserver\SMSPKGD$\CCM0003A\ is a passed program location	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Creating mandatory request for advert CCM2007F, program Install Silent, package CCM0003A	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Found Policy. Validate policy is acceptable.	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    An execution request does not exist yet for this program. Creating a new request.	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    GetRequestSessionId: Sid of the caller is S-1-5-18	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    0 != _wcsicmp(szUserSid, szSystemSid), HRESULT=00000001 (e:\nts_sccm_release\sms\client\softmgmtagent\execmgr\execreqmgr.cpp,926)	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Adding location \\myserver\SMSPKGD$\CCM0003A\	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Evaluate if current request needs to be executed	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    CExecutionRequest::OnEvaluateForExecution: Evaluate Program Install Silent [Advert CCM2007F] targeted to System. Current State : 0	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    An existing MTC token was supplied, this execution request is not owner of MTC object.	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Request a MTC task for execution request of package CCM0003A, program Install Silent with request id: {3F7FF7B0-B409-41E7-868E-759584B15C8E}	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Execution Request for advert CCM2007F package CCM0003A program Install Silent state change from NotExist to Ready	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    CUIEventGenerator::NotifyProgramStateChanged entered	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    RaiseClientSDKEvent: Raising a client SDK WMI event	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="CCM0003A",ProgramID="Install Silent", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    RaiseClientSDKEvent: A client SDK WMI event is raised up successfully	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    CUIEventGenerator::NotifyProgramStateChanged succeeded	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Persisting request for program Install Silent package CCM0003A in state Ready	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Current state for CCM2007F: 7	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    The reference count for program Install Silent, package CCM0003A has been incremented to 1	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Persisting request for program Install Silent package CCM0003A in state Ready	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    Successfully created request for Package :CCM0003A Program:Install Silent Advert: CCM2007F	execmgr	03.12.2012 14:50:43	1856 (0x0740)
    


    Monday, December 03, 2012 2:30 PM
  • The funny part was: after waiting 2 days after the upload of a new capture the image suddenly could be deployed and the task sequence worked like a charm.

    I've opened a case with Microsoft support regarding my problem and it was confirmed as a bug in 2012 that hopefully will be fixed with SP1.

    • Edited by mpfister Wednesday, December 12, 2012 11:17 AM
    Wednesday, December 12, 2012 11:15 AM
  • No WSUS in SCCM here
    Wednesday, December 12, 2012 11:15 AM
  • The problem still persists in SP1.

    Can you please notify me when an fix is available?

    Thanks

    Thursday, January 03, 2013 10:42 AM
  • I had this issue on one of my VMs that I was deploying an image to.

    1 out of 5 times, it would hang on the first package install in the TS with the logs full of "Waiting for job status notification" errors, other times it was fine. Other machines on the same subnet did not have the issue.

    As it turns out, the VM host was having network connectivity issues. I saw in the host log that the NIC was frequently disconnecting from the network, and the times seemed to coincide with when it was trying to install the package. After some investigation, I resolved the frequent disconnections, and the issue went away (NIC speed duplex issue, specific to network setup).

    Interestingly, I was unable to find anywhere in the logs that network connectivity to the MP/DP had been lost. Does anyone know where this type of event would be logged?

    It would be nice if there was some way to "kick" the TS on to the next step after this occurs else you have to start again. Does anyone know how to do this (or if it is even possible) in SCCM 2012 SP1? Thanks.

    Thursday, March 21, 2013 8:37 PM
  • After I thought I had resolved the issue, it has come back again, and won't get past the first package in the TS.

    After trawling the logs it appears that execmgr.log never gets past this line

    Execution Request for advert <advertID> package <packageID> program <programName> state change from NotExist to Ready

    The only log to get updated is the SMSTSlog with the "Waiting for job status notifcation" over and over again. Also, the package never actually installs, but gets staged to the C:\ drive in the correct location (verified this by running it manually and it worked fine).

    Can someone please advise where to look next?

    FWIW I'm deploying Windows 7 x64 SP1 with slip-streamed IE10. I am going to attempt to deploy with IE9 as it was working for quite a long time without IE10 (IE9 and IE8 seemed to be OK). Perhaps this issue is related to a Windows Update? 

    Is there any update on a fix for this issue from Microsoft?



    • Edited by TheRatNZ Thursday, March 21, 2013 9:51 PM
    Thursday, March 21, 2013 9:49 PM
  • I've spent a lot of time on this issue.

    The only solution that reliably works is:

    • Build the reference machine and capture it, DO NOT UPDATE THE DPs
    • Wait at least 12h better 24h
    • Now update the distribution points

    Deployment works. Don't ask why.

    Tuesday, March 26, 2013 9:12 AM
  • mpfister

    You mentioned you had a call open with Microsoft support, what was their official response? (since now this issue is happening post-SP1).

    Tuesday, March 26, 2013 7:46 PM
  • I have been having a similar problem with a task sequence stalling and the smsts.log showing [Waiting for job status notification...] I solved the problem by adding a "Restart Computer" task straight after "Setup Operating System"

    The task sequence normally would run "Install Updates" straight after "Setup Operating system" which would reboot the computer and the remaining apps would install normally. When I created a new reference image that had no updates and no need to reboot was when this error started.

    Tuesday, March 26, 2013 11:31 PM
  • Interesting, I have this step already (MDT 2012 Update 1), it's called Setup Windows and ConfigMgr then the very next step is restart computer.

    My issue was different in that it only started once I had updates in my image.

    Wednesday, March 27, 2013 1:29 AM
  • TheRatNZ, their offical statement was: this is a bug in SCCM 2012 (w/o SP) and at that time they were not sure if it will be fixed in SP1. No more details provided...
    Thursday, March 28, 2013 1:06 PM
  • @mpfister - can you share the support call number?

    Mikhail

    Friday, April 19, 2013 6:59 AM
  • To add to this issue: experiencing the same thing during a basic WS2012 deployment (capture=WS2012 image with updates, dotnet3.5 and some features installed). No MDT TS used, using a boot media, no additional drivers.  I also installed sccm 2012 SP1 CU1.

    I have tried a lot of stuff to try and work around it: deployed many times on different VM's, add reboot after setup OS and sccm, disabled TS steps, used different captures, tried with/without CU1 client MSP patch, etc. So far nothing works. The strange funny thing is i have a Run command line step just before the package and that works every time. No problems in the ccmsetup logs or event log. This has already cost me a few days and a lot of frustration!

    It seems to be related to the Captured image though, because when I use a slightly older capture (from a week earlier, almost identical content) it works fine, time after time! Unfortunately I did not see this coming, and it's a dev deployment so I have no idea what changed (but nothing obvious IMO, mostly tuning in the packages the TS never gets to). The same is true when I use the default image from the original installation DVD.

    Looking at this thread I think I may open a call as well.


    • Edited by MoonenJH Friday, April 19, 2013 11:21 AM
    Friday, April 19, 2013 11:16 AM
  • I also have this issue.  The only solution I know works is that if you wait 4 days after the image is captured, it will all work.  (perhaps less days, but I know that after 4 days it works for me).

    You can capture the image, and even immediately distribute it to all DP's.  It won't work on day one or two.  But if you change nothing, and wait the full 4 days, it will work.  This is a major bug and needs to be acknowledged and resolved by Microsoft.

    All I can say is if you have this issue, create an image, and sit on it for a few days.

    Friday, April 19, 2013 1:46 PM
  • Thanks, will try that. I just updated DP with a fresh build and it did not work yet, but I will try to update the DP again after a few days (not changing of recapturing the image). It should work then? Or do I have to do a fresh Build & Capture and not update DP's until then?

    That would really defy all logic but I am at the point of willing to try pretty much anything! :o)


    JH Moonen

    Friday, April 19, 2013 2:17 PM
  • You can just wait.   You don't have to capture it again (or not update DP's, although now that it is deployed to your DP, I wouldn't even update them again during the wait).

    Friday, April 19, 2013 2:41 PM
  • bug confirmed :(

    added fresh image and tried to run a TS. it hangs on install package step, as mentioned here, ignoring even maximum time allowed to execute that package.

    after waiting for approx 8 hours, we've run this TS again without changing anything - and this time it did executed without any problems.

    lets hope MS guys will come up with bugfix asap.


    Mikhail

    Friday, April 19, 2013 2:58 PM
  • I can confirm that just waiting a few days actually worked!

    1. Friday: WS2012 Build & Capture made with all current hotfixes, distributed to DP
    2. Immediately after that: Tested several deployments on 2 VMs. None worked, they just stalled at the first Package with "Waiting for installation job to complete.."
      Note: a "Run command line" step just after the "Install Windows and Configmanager" and before the Package always finished without a problem.
    3. Monday (just now): deployed the same 2 VM's and they both work without a hitch!

    This is definitely one of the most weird bugs I ever came across, and it's a bit unsettling it has been around since before SP1 (and now CU1)!

    Update 23/4: Reran the whole scenario (including updating DP): OSD did not work, but after 18h of waiting the deployments worked again. Opened a case @ Microsoft.

    Update 25/4: Reran another B&C, did not update DP, then after 14h I updated the DP and the OSD worked without any problems. Doing yet another B&C now to reproduce the problem, will send OSD client debug logs to MS.


    JH Moonen



    • Edited by MoonenJH Thursday, April 25, 2013 7:16 AM
    Monday, April 22, 2013 7:08 AM
  • Hi, I'm experiencing the same issue, did you ever get a response from MS?

    Image was captured yesterday (Win2008 R2 SP1 Enterprise, SCCM 2012 SP1), and previously worked fine, now with deploying with the newly captured image, it gets stuck on the 3rd or 4th package after the Setup Windows and Configuration Manager task (the first task after is a reboot) with a "state change from NotExist to Ready" in the ExecMgr.log, where the task never actually launches.

    This does not happen with the same step on other images used within the same task seqeunce.

    Jon

    Tuesday, May 28, 2013 12:40 AM
  • They are trying to reproduce the problem in their lab, no luck so far.

    To me it always only happens on the first Package, and I can reproduce it time after time here. I have the problem only a certain amount of time after Build & Capture, it eventually goes away by itself if I wait 12h or so (typically the next day).


    JH Moonen

    Tuesday, May 28, 2013 5:42 AM
  • Jonny,

    I believe you are experiencing a different bug (given that you are able to install any apps).  The bug you are seeing is that *sometimes* when you update an application/package source, the Task Sequence will not update to look for the new version and will instead be stuck looking for the older revision (and thus fail).  To resolve this, simply remove the application from the task sequence and save it (make sure to close it out all the way with OK, not just apply) then add the application back (which will then add the correct version of the application).

    David

    Tuesday, May 28, 2013 1:25 PM
  • Hi there!

    We have just started getting this issue. I has spent the last 24 hours scratching my head about this. . .

    Doing a build and capture now then leaving 24 hours to see if it fixes it!!

    Does anyone have the support Case ID for this?

    Thanks

    Andy

    Tuesday, June 04, 2013 3:36 PM
  • Hi,

    Actually, just yesterday the MS engineer has confirmed he can reproduce the problem in their own environment. So I guess that means they should be able to figure out what's causing this weird behavior. He also noted that this may not be solved immediately with a hotfix, since the workaround is that simple (just wait 12h and you are good to go again). But at least it may get fixed in the next SP/CU or so.


    JH Moonen

    Tuesday, June 04, 2013 4:42 PM
  • Unfortunately we're facing the same issue as MoonenJH describes. We're using SCCM 2012 SP1 CU1:

    • Yesterday created new OS image (Windows 7 SP1 X64) based on build & capture task sequence
    • Distributed new OS image to distribution points
    • Update task sequence and refer to new OS image
    • Provisioning desktop
    • Task Sequence hangs on application/package deployment

    This morning restarted task sequence and runs like a charm!!! I've to make a remark regarding the distribution state of the image. I started the task sequence when the image was available on 2 of 11 distributions points. But this should make no difference in my opinion.

    Any update available regarding the Microsoft case? Please can you share the case ID so we can refer to? Thanks!


    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong



    Friday, June 07, 2013 6:36 AM
  • I only have 1 DP, so that shouldn't be the issue no.

    I'll ask the MS engineer if I can mention the Case ID here. He is still in the process of re-reproducing it, because on his last test with the CU1 client in the B&C, the problem seemed to stay away. However, I have tried this with the CU1 client CU1 before and still got the error.

    Do you have the CU1 client in B&C step, and in the Build step as well (using "Patch=..." install parameter)?

     


    JH Moonen

    Friday, June 07, 2013 7:15 AM
  • No we don't have included the CU1 client in the build & capture nor build step.

    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong

    Friday, June 07, 2013 7:25 AM
  • hi @ all, is there any update or solution about this issue. i have the same problem at one of my customers.

    I build the image with cu1 and the hoftix kb2823652 by using the patch parameter. in task sequence where I deploy the captured image, after the first reboot in running os, the first package will hang and hang and hang...

    thanks.

    tom


     
    Tuesday, June 11, 2013 10:47 PM
  • Ronny,

    Could you try including CU1 in the build to see if that helps or not? My first tests a while ago indicated was that it did not help, but at MS that seemed to solve the problem. I will retry that as well.

    ######

    So for example copy the C:\Program Files\Microsoft Configuration Manager\hotfix folder to the C:\Program Files\Microsoft Configuration Manager\Client folder and update the DPs for the client install package. Alternatively you could create a new client package just for the build and capture task sequence.

     When this has been updated on the DPs then configure the task sequence to install this hotfix in the setup Windows and Configuration manager step with the following syntax:

    PATCH=”c:\_SMSTaskSequence\OSD\<Package_ID>\hotfix\KB2817245\Client\x64\configmgr2012ac-sp1-kb2817245-x64.msp”


    JH Moonen

    Wednesday, June 12, 2013 5:43 AM
  • I'll including the CU1 in both deployments and get back to you with the outcome.


    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong


    Wednesday, June 12, 2013 9:33 AM
  • It seems this might be related to the same issue as described here (although it seems that SP1 solved it there, while for us the problem persists for SP1 and CU1):
    http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/e24d092c-3e8b-4c0d-9231-abf4550191fc

    It makes sense that the problem should be with the image itself, and that just waiting 12h seems to fix it.

    Suggestion from MS is to run this script during deployment before teh Package install step, but I guess it can be used in the B&C (just before the capture as well). I guess the "Prepare configmanager client" preparation step before capture needs some work.

    strComputer = "."
    Set objSWbemServices = GetObject("winmgmts:\\" & strComputer & "\root\ccm")
    Set colSWbemObjectSet = objSWbemServices.InstancesOf("SMS_MaintenanceTaskRequests")
    For Each objSWbemObject In colSWbemObjectSet
    strInstance = "SMS_MaintenanceTaskRequests.TaskID='"&objSWbemObject.TaskID&"'"
    objSWbemServices.delete strInstance
    Next


    JH Moonen

    Thursday, June 13, 2013 6:17 AM
  • Last friday we included CU1 in both build & capture task sequence as well as the deployment task sequence. But unfortunately no joy - installation of application/packages went wrong despite CU1. This morning we were able to deploy a machine with the newly created image without any issues - as expected.


    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong


    Monday, June 17, 2013 6:59 AM
  • What kind of machines is this task sequence deployed to? What kind of hardware do they have?
    Monday, June 17, 2013 7:01 PM
  • Hi Moiz,

    it was tested it on VM's (Hyper-V & VMware) and tons of different HP's, Dell's and no name systems.


    Mikhail

    Monday, June 17, 2013 7:52 PM
  • I have tested a bit more, and I can confirm that the problem seems to be solved when running this script just before the failing Package and rebooting the server right after that.

    strComputer = "."
    Set objSWbemServices = GetObject("winmgmts:\\" & strComputer & "\root\ccm")
    Set colSWbemObjectSet = objSWbemServices.InstancesOf("SMS_MaintenanceTaskRequests")
    For Each objSWbemObject In colSWbemObjectSet
    strInstance = "SMS_MaintenanceTaskRequests.TaskID='"&objSWbemObject.TaskID&"'"
    objSWbemServices.delete strInstance
    Next

    So in short you add the bold steps to the existing deployment TS:

    - Run the script

    - Reboot

    - Run Package (that usually fails)

    Now we need to see how this can be fixed in the Build & Capture, since that is where the problem lies. It seems to wait for some maintenance tasks that are present after B&C and that timeout after 12h, which happens to be the same time we had to wait before everything magically started working again. ;o)

    It is very similar (if not the same) as the issue described here (although they mentioned it goes away with SP1 for them:
    http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/e24d092c-3e8b-4c0d-9231-abf4550191fc


    JH Moonen

    • Proposed as answer by Ronny de Jong Thursday, June 20, 2013 12:25 PM
    Tuesday, June 18, 2013 7:09 AM
  • I have tested a bit more, and I can confirm that the problem seems to be solved when running this script just before the failing Package and rebooting the server right after that.

    strComputer = "."
    Set objSWbemServices = GetObject("winmgmts:\\" & strComputer & "\root\ccm")
    Set colSWbemObjectSet = objSWbemServices.InstancesOf("SMS_MaintenanceTaskRequests")
    For Each objSWbemObject In colSWbemObjectSet
    strInstance = "SMS_MaintenanceTaskRequests.TaskID='"&objSWbemObject.TaskID&"'"
    objSWbemServices.delete strInstance
    Next

    So in short you add the bold steps to the existing deployment TS:

    - Run the script

    - Reboot

    - Run Package (that usually fails)

    Now we need to see how this can be fixed in the Build & Capture, since that is where the problem lies. It seems to wait for some maintenance tasks that are present after B&C and that timeout after 12h, which happens to be the same time we had to wait before everything magically started working again. ;o)

    It is very similar (if not the same) as the issue described here (although they mentioned it goes away with SP1 for them:
    http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/e24d092c-3e8b-4c0d-9231-abf4550191fc


    JH Moonen


    This is a great thread, I had the exact same problem, I had to wait a day to test them. Now I am using the above script just before my "Prepare ConfigMgr Client for Capture" step in my Build & Capture task sequence and the problem has gone away.
    Thursday, June 20, 2013 2:51 AM
  • @BarneyRubble: could you boble-check that worked for you, because when I tried this just before the "Prepare ConfigMgr Client for Capture" step it did not seem to help, and the MS engineer told me they suspected that the maintenance tasks were actually created during that step?

    [Update] MS is going to investigate the bug for R2 of the next release.


    JH Moonen


    • Edited by MoonenJH Thursday, June 20, 2013 1:49 PM update
    Thursday, June 20, 2013 5:47 AM
  • What kind of machines is this task sequence deployed to? What kind of hardware do they have?

    As Moiz mentioned this seems hardware independed as it applicable to both VM's and hardware systems.

    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong

    Thursday, June 20, 2013 11:53 AM
  • Hi JH Moonen, hereby I can confirm your workaround solves the issue. We are able deploy newly created images without waiting for 12hrs running the script before Installation Software step. I am actually wondering what the status is of this bug by Microsoft as some confirmed this is solved by SP1 or CU1 - which is in our case is obvious not.


    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong

    Thursday, June 20, 2013 12:32 PM
  • Does someone having experiences with CU2 so far? I've applied CU2 but unfortunately the behavior remains. Running the script as mentioned before will still do the trick.


    Ronny de Jong | inovativ.nl | Blog: donnystyle.wordpress.com | Twitter: twitter.com/ronnydejong


    • Edited by Ronny de Jong Thursday, June 27, 2013 6:43 AM updated reply/comment
    Thursday, June 27, 2013 6:41 AM
  • Hi guys, did you hear any News from Microsoft regarding this issue?
    I have a SCCM 2012 SP1 CU2 Environment and CU2 integrated in the SCCM Client Installation Step and this issue still occurs. In the past few months i did manage SCCM 2012 Environments for about 10 customers and they all have the same issue and it's really, really annoying.
    The Script is not an Option as it Looks like it just deletes maintenance Tasks on the site Server. Thats a really poor Workaround which we want to avoid.
    I created a SCCM 2012 R2 testlab to check if it has been solved there but i don't think it will be to be honest.
    Any Updates on this are really appreciated.

    Thanks
    Stefan

    Friday, July 19, 2013 10:40 AM
  • Have you already opened a call at Microsoft then? They cannot fix anything if they are not aware of the problem (I haven't read the entire thread though). The more customers are reporting the issue the better.
    The script has to be run on the clients in a task sequence if I am not mistaken.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, July 19, 2013 10:53 AM
  • @BarneyRubble: could you boble-check that worked for you, because when I tried this just before the "Prepare ConfigMgr Client for Capture" step it did not seem to help, and the MS engineer told me they suspected that the maintenance tasks were actually created during that step?

    [Update] MS is going to investigate the bug for R2 of the next release.


    JH Moonen


    Guys, after 3 days of having pain with exactly the same issue as above. the workaround to add the script before "Prepare ConfigMgr Client for Capture" solved my issue!!!

    Packages are now installling on new task sequence using the image created on build and capture.

    • Proposed as answer by chrizvi Friday, August 30, 2013 5:46 AM
    Friday, August 30, 2013 5:46 AM
  • This is great!! I had the same problem which has been plaguing me since I first encountered this issue around August 2012. I've wasted weeks trying to solve this. At first I suspected that it may be a dodgy update creeping into the Build and Capture. The script definitely works. Huge respect for this thread!
    Wednesday, September 04, 2013 1:17 PM