none
Past due - will be installed

    Question

  • Hi all,

    we've been setting up app-deployment using SCCM 2012, and are going in to production in about a month. Now, we have a major problem.

    None of the required apps are installing. They're simply stuck at "Past due - will be installed".

    Indeed they are past due (all deployments are set to install as soon as possible), but absolutely nothing is happening (no it's not a matter of waiting, it's a dead halt). If we click 'install all required', everything installs perfectly. But obviously that's not an option.

    The appenforce.log doesn't seem to be doing anything either; and it's not a problem with access to install source either; since all apps download fine, and THEN go into 'Past due...'.

    I've also tried scheduling it to a time in the future, and then it just goes 'will be installed at (xx)' and once the deadline passes, it's 'past due' again.

    So in summary; absolutely nothing is happening; and we've gone over the setup a million times, everything seems to be correct. We've also tried installing the agent on a clean (non-deployed) machine; virtual machines and with and without bitlocker. No difference.

    We are seriously stuck. Help! :)

    Thursday, August 30, 2012 7:01 PM

Answers

  • Sorted it myself! It was this setting that had been inadvertently enabled. Slightly annoying that this never came up in any logs, client or server side.

    But, lesson learned. Never enable this unless you're using 3rd party software to distribute/install. It will simply stop everything required from deploying.

    So that was fun.



    • Marked as answer by st.kristobal Monday, September 03, 2012 8:14 PM
    • Edited by st.kristobal Monday, September 03, 2012 8:16 PM
    Monday, September 03, 2012 8:14 PM

All replies

  • Has the content been send to a DP that can be reached the the clients and Is the content being found/downloaded?  Check the CAS.log to see if the client is finding an applicable DP with the content.

    Or is it possible that your deployments are set to wait on a maintenance window that your might not have setup.  For required installs, you would have to configure the deployment to ignore the maintenance window.

    Thursday, August 30, 2012 7:04 PM
  • Yes, as mentioned; the content downloads first, and then goes straight to 'Past due'; so I can't imagine that has anything to do with it.

    All deployments have checked Software Installation and System Restart to be performed outside maintenance windows. No MW have been defined; but we tried that too. Without any luck.

    Thursday, August 30, 2012 8:33 PM
  • Have you checked CAS.log and ContentTransferManager.log though? There might be an error downloading content that may not be reflected in the Software Center.

    Jason | http://blog.configmgrftw.com

    Thursday, August 30, 2012 9:43 PM
  • Not sure what it's supposed to look like, but it looks ok to me:

    CTM job {95F230B7-68FA-4EDB-BC1C-42FCC932823E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA    ContentTransferManager    30.08.2012 22:29:14    2808 (0x0AF8)
    [CCMRDC] GenerateTargetFile() called with OldFile as "C:\Windows\ccmcache\a\install_flash_player_ax.exe", NeedsFile as "C:\Windows\ccmcache\q.BDRTEMP\Temp\work\install_flash_player_ax.exe!!!!needs", 0 Deltafiles and AssembledFile as "C:\Windows\ccmcache\q\install_flash_player_ax.exe"    ContentTransferManager    30.08.2012 22:29:14    2808 (0x0AF8)
    CMergeDeltaOperation::_ProcessFile - Created merged file C:\Windows\ccmcache\q\install_flash_player_ax.exe.    ContentTransferManager    30.08.2012 22:29:15    2808 (0x0AF8)

    Same for CAS.log. Can't see any errors there either.

    Friday, August 31, 2012 6:46 AM
  • So are the files needed actually in the local ccmcache on the targeted client system?

    Jason | http://blog.configmgrftw.com

    Friday, August 31, 2012 1:23 PM
  • Do you have maintenance windows setup by any chance? You may want to check execmgr.log or maintenanceCoordinator.log
    Friday, August 31, 2012 2:44 PM
  • So are the files needed actually in the local ccmcache on the targeted client system?

    Jason | http://blog.configmgrftw.com

    Yes they are!

    kubi:

    No maintenance windows, but I've tried setting that before.

    Maintenancecoordinator doesn't give me anything I can understand; but this is for the last deployment I tried:

    Adding task for client "CITaskMgr": id - "0d71d14f-bc3f-499c-917a-28ee46d03dcd", pri - 20, service window - 0, max time for sw - 7200.    MaintenanceCoordinator    30.08.2012 20:47:26    3708 (0x0E7C)
    Signaled task '0d71d14f-bc3f-499c-917a-28ee46d03dcd' (agent 'CITaskMgr').    MaintenanceCoordinator    30.08.2012 20:47:26    3708 (0x0E7C)
    Done scheduling task. Winning task '0d71d14f-bc3f-499c-917a-28ee46d03dcd' (agent 'CITaskMgr')    MaintenanceCoordinator    30.08.2012 20:47:26    3708 (0x0E7C)
    Task "0d71d14f-bc3f-499c-917a-28ee46d03dcd" (agent 'CITaskMgr') is reporting back on starting.    MaintenanceCoordinator    30.08.2012 20:47:26    1064 (0x0428)
    Successfully started task '0d71d14f-bc3f-499c-917a-28ee46d03dcd' (agent 'CITaskMgr').    MaintenanceCoordinator    30.08.2012 20:47:26    1064 (0x0428)
    Removing task '0d71d14f-bc3f-499c-917a-28ee46d03dcd' (agent 'CITaskMgr') from the queue.    MaintenanceCoordinator    30.08.2012 20:48:23    1064 (0x0428)
    Removed task 0d71d14f-bc3f-499c-917a-28ee46d03dcd for client CITaskMgr    MaintenanceCoordinator    30.08.2012 20:48:23    1064 (0x0428)
    Removing tasks for agent "RebootCoord".    MaintenanceCoordinator    30.08.2012 22:40:14    1784 (0x06F8)

    Friday, August 31, 2012 3:07 PM
  • I would still run this report to make sure. It could be updates or something else is running

    Friday, August 31, 2012 3:25 PM
  • Can you copy and paste servicewindowmanager.log ?

    Friday, August 31, 2012 3:36 PM
  • Bah, I don't have Reporting Services installed. Will check that.

    This is the log after I set up a 22h maintenance window (just to test):

            This is a one shot Service Window that has already finished.    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 0, hours: 00, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=90a5f436-364c-48c7-8dc7-c5014abcbea8, ScheduleString=001A8A8028592000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 09/02/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 1, hours: 05, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=45dca355-3249-4845-b8aa-72d0e604548e, ScheduleString=02D78A80381C2000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 09/05/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=87e4759c-2884-45e6-9261-c33ba53f596c, ScheduleString=02D78A80101D2000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 09/06/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 0, hours: 02, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=36da6950-3d1e-4027-be0e-7b16a4daee7e, ScheduleString=00188A80005E2000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 08/31/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 1, hours: 00, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=028bfbc0-7120-4081-a268-0e664a92ac4a, ScheduleString=00198A80005F2000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 09/01/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 1, hours: 00, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=49fd80be-ac4b-4877-974d-ecd09958926d, ScheduleString=02D78A80381B2000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 09/04/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID=ad27b0ca-8c74-43c7-8200-1f601880bd75, ScheduleString=02D78A80381A2000, Type=6    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 09/03/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 0, hours: 07, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Populating instance of ServiceWindow with ID={9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB}, ScheduleString=003F8A80B0100009, Type=1    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            StartTime is 08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Duration for the Service Window is Total days: 0, hours: 22, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    Checking to see which Service Windows should be Active.....    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Sending Message SERVICEWINDOWEVENT:START event    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Sending Message SERVICEWINDOWEVENT:START event    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    Checking Service Windows to find Next Event.....    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Next Event Time is at 09/01/12 00:00:00. Service Window with ID:36da6950-3d1e-4027-be0e-7b16a4daee7e. Is the next event the beginning of the window? No    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Inactive Service Windows List has 7 windows    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 7cb56688-692f-4fae-b398-0e3ff4413adb having Starttime=01/01/38 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 00 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 90a5f436-364c-48c7-8dc7-c5014abcbea8 having Starttime=09/02/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 1 days, 05 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=09/05/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 07 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 87e4759c-2884-45e6-9261-c33ba53f596c having Starttime=09/06/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 02 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 028bfbc0-7120-4081-a268-0e664a92ac4a having Starttime=09/01/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 1 days, 00 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 49fd80be-ac4b-4877-974d-ecd09958926d having Starttime=09/04/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 07 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = ad27b0ca-8c74-43c7-8200-1f601880bd75 having Starttime=09/03/12 22:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 07 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Active Service Windows List has 2 windows    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=08/31/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 1 days, 00 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Service Window with ID = {9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB} having Starttime=08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 22 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Scheduling the Timer Task    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
        Scheduled the timer to fire on 09/01/12 00:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:3    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Biggest Active Service Window has ID = {9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB} having Starttime=08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 22 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    ActiveServiceWindow has 28023 seconds left    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:3    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
            Biggest Active Service Window has ID = {9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB} having Starttime=08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
                Duration is 0 days, 22 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    ActiveServiceWindow has 28023 seconds left    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:12:57    4204 (0x106C)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:4    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
            Biggest Active Service Window has ID = {9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB} having Starttime=08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
                Duration is 0 days, 22 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    ActiveServiceWindow has 28019 seconds left    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:6    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
            Biggest Active Service Window has ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=08/31/12 00:00:00    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
                Duration is 1 days, 00 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    ActiveServiceWindow has 24419 seconds left    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:13:01    4208 (0x1070)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:2    ServiceWindowManager    31.08.2012 17:13:03    4204 (0x106C)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    31.08.2012 17:13:03    4204 (0x106C)
            Biggest Active Service Window has ID = {9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB} having Starttime=08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:13:03    4204 (0x106C)
                Duration is 0 days, 22 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:13:03    4204 (0x106C)
    ActiveServiceWindow has 28017 seconds left    ServiceWindowManager    31.08.2012 17:13:03    4204 (0x106C)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:13:03    4204 (0x106C)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:2    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window...    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
            Biggest Active Service Window has ID = {9A9B5EAF-14CD-4791-AF3D-FC5A892E86DB} having Starttime=08/31/12 03:00:00    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
                Duration is 0 days, 22 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    ActiveServiceWindow has 28004 seconds left    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:6    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
            Biggest Active Service Window has ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=08/31/12 00:00:00    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
                Duration is 1 days, 00 hours, 00 mins, 00 secs    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    ActiveServiceWindow has 24404 seconds left    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    Program can run! Setting *canProgramRun to TRUE    ServiceWindowManager    31.08.2012 17:13:16    2440 (0x0988)
    Service shutdown notification received    ServiceWindowManager    31.08.2012 18:57:53    5328 (0x14D0)
    Begin Deleting Service Windows...    ServiceWindowManager    31.08.2012 18:57:53    5328 (0x14D0)
        Sending Message SERVICEWINDOWEVENT:END event    ServiceWindowManager    31.08.2012 18:57:53    5328 (0x14D0)
        Sending Message SERVICEWINDOWEVENT:END event    ServiceWindowManager    31.08.2012 18:57:53    5328 (0x14D0)
    Deleted All Service Windows...    ServiceWindowManager    31.08.2012 18:57:53    5328 (0x14D0)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:6    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
            Biggest Active Service Window for Type=6 not found    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
    Program cannot Run! Setting *canProgramRun to FALSE    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
    WillProgramRun called with: Runtime:1, Type:6    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
    A Service Window of this type exists.    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
    There exists a Service Window of this Type, for this duration. The Program will run eventually.    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
    ServiceWindowManager    31.08.2012 18:57:54    4296 (0x10C8)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:6    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
            Biggest Active Service Window for Type=6 not found    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
    Program cannot Run! Setting *canProgramRun to FALSE    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
    WillProgramRun called with: Runtime:1, Type:6    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
    A Service Window of this type exists.    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
    There exists a Service Window of this Type, for this duration. The Program will run eventually.    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
    ServiceWindowManager    31.08.2012 18:57:54    3444 (0x0D74)
    ServiceWindowManager::FinalConstruct entered    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
    Initializing Creation of ServiceWindowHandler    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
    ServiceWindowHandler::Successfully registered for Time Change Events    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
    Refreshing Service Windows.....    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
        Populating instance of ServiceWindow with ID=7cb56688-692f-4fae-b398-0e3ff4413adb, ScheduleString=02D78A80381A200002D78A80381B200002D78A80381C200002D78A80381D2000, Type=6    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
    CServiceWindow::CServiceWindow: Failed to initialize ServiceWindowSchedule instance from schedule string (02D78A80381A200002D78A80381B200002D78A80381C200002D78A80381D2000)    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
            This is a one shot Service Window that has already finished.    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
            Duration for the Service Window is Total days: 0, hours: 00, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
        Populating instance of ServiceWindow with ID=90a5f436-364c-48c7-8dc7-c5014abcbea8, ScheduleString=001A8A8028592000, Type=6    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
            StartTime is 09/02/12 00:00:00    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
            Duration for the Service Window is Total days: 1, hours: 05, mins: 00, secs: 00    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
        Populating instance of ServiceWindow with ID=45dca355-3249-4845-b8aa-72d0e604548e, ScheduleString=02D78A80381C2000, Type=6    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
            StartTime is 09/05/12 22:00:00    ServiceWindowManager    31.08.2012 19:01:32    2072 (0x0818)
            Duration for the Service Window is Total

    Friday, August 31, 2012 5:18 PM
  • Brief update; packages install fine. Applications don't. (Just deployed the CU1 client update).

    Still no progress :S

    • Proposed as answer by DS Brown Wednesday, June 08, 2016 1:38 PM
    Monday, September 03, 2012 7:33 AM
  • Sorted it myself! It was this setting that had been inadvertently enabled. Slightly annoying that this never came up in any logs, client or server side.

    But, lesson learned. Never enable this unless you're using 3rd party software to distribute/install. It will simply stop everything required from deploying.

    So that was fun.



    • Marked as answer by st.kristobal Monday, September 03, 2012 8:14 PM
    • Edited by st.kristobal Monday, September 03, 2012 8:16 PM
    Monday, September 03, 2012 8:14 PM
  • Yeah, that's actually come up multiple times.

    That'll teach you for randomly turning things on :-)


    Jason | http://blog.configmgrftw.com

    Monday, September 03, 2012 8:57 PM
  • Yeah that one is on us. But it STILL should have been logged somewhere.

    I see it's getting renamed in SP1; so that's good at least.

    Thanks for your help though!

    Monday, September 03, 2012 9:09 PM
  • We are having the same problem yet that setting is set to false. Any thing else we can try? Running a software update eval cycle does kick them into action. 
    Saturday, November 17, 2012 2:59 AM
  • Make sure Client Settings, Software Updates tab is set to perform "Software Update Scan schedule" during the MW - ideally, at the beginning :-)
    • Edited by DeanEllerby Sunday, November 18, 2012 1:09 PM
    Sunday, November 18, 2012 12:35 PM
  • Software Updates Scans are not affected by maintenance windows.

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

    Monday, November 19, 2012 8:25 AM
    Moderator
  • Dean what do you mean by MW? 

    Are you suggesting I make sure the Software Update Deployment Eval Cycle timing hit time wise shortly after the due date? 

    Monday, November 19, 2012 11:49 AM
  • MW = maintenance window.

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

    Monday, November 19, 2012 12:40 PM
    Moderator
  • That seemed to work for me in testing.

    Until then, I was having the same issues as you.
    Thursday, November 22, 2012 10:14 PM
  • Dean can you explain better what you mean by: "Make sure Client Settings, Software Updates tab is set to perform "Software Update Scan schedule"
    Friday, November 23, 2012 2:04 PM
  • Sorted it myself! It was this setting that had been inadvertently enabled. Slightly annoying that this never came up in any logs, client or server side.

    But, lesson learned. Never enable this unless you're using 3rd party software to distribute/install. It will simply stop everything required from deploying.

    So that was fun.




    Thanks, must try this next time :P
    Friday, December 07, 2012 2:53 PM
  • I got the same problem but your solution didn't resolve my problem :-/

    This option was already on "False"

    Tuesday, February 18, 2014 10:18 AM
  • Thanks!! it works for me...

    Friday, August 08, 2014 4:38 PM
  • Right on target, my issue is resolved :D
    Thursday, April 30, 2015 6:00 PM