Failed to install updates, error code 0x87D00667

Question

_{Thursday, December 13, 2012 1:42 PM}

Hello

I get an error 0x87d00667 when trying to install software updates on a given client. Yesterday, I had associated a Maintenance Window to this client: between 2 and 3 pm, no recurrence. This morning at 5:38am, I got this error in the Deployment Status,  with the description: "No current or future service window exists to install software updates". Now I cannot deploy updates to this client, I'm stuck with this error message. Googling with this error code gives a frightening answer: "Your search - 0x87d00667 - did not match any documents." Of course I tried a lot of Maintenance Windows, rebooting etc. The only thing I can think of is deleting the client from the device collection "All systems", then removing/reinstalling the CCM client. Any other idea would be welcome.

Pierrot

All replies (6)

_{Monday, December 17, 2012 3:51 PM ✅Answered}

Interesting. Not sure honestly. This blog post may help you dig into the details and confirm this: http://blogs.technet.com/b/csloyan/archive/2010/10/24/maintenance-window-calculations-explained.aspx

However, although it is true you will be able to disable start time randomization in SP1 (this was added in 2012 to account for VDI scenarios), the randomization of the software update start time though won't be going away in SP1 (to my knowledge) because this existed before the VDI optimization scenarios were introduced and has nothing to do with these optimizations. Also, randomization of deployment start times only happens outside of maintenance windows.

Finally, this script may help: http://gallery.technet.microsoft.com/scriptcenter/How-to-Disable-the-c3b29b29

Jason | http://blog.configmgrftw.com

_{Thursday, December 13, 2012 2:29 PM}

0x87d00667 equals exactly the message you listed above "No current or future service window exists to install software updates".

Given that you just create a maintenace window, the problem probably lies with it. What timeframe (exactly) did you set in this new MW?

Jason | http://blog.configmgrftw.com

_{Thursday, December 13, 2012 2:35 PM}

I tried different timeframes. For example, at 14:05, I defined a MW from 14:30 to 19:00, recurring daily. No matter what I define, I always get the same error.

_{Friday, December 14, 2012 9:36 AM}

Before leaving the office yesterday, I set a timeframe for the next day at 5am to 10am. This morning, the updates had been installed and the clients were compliant.

_{Monday, December 17, 2012 9:45 AM}

I think I found something interesting that might be the cause of my problem: I had set the duration of the maintenance window to 1 hour. From what I found in the blogs, the start time of the update is defined by the start time as specified by the user PLUS a random value between 0 and 120 minutes (2 hours). Reason: avoid that all jobs start at the exact same time. So if you set a maintenance window duration of less than 2 hours, chances are that the computed start time will be outside the window... I've read that you can disable this random calculation, in the SP1 coming soon. I set the maintenance window duration of 4 hours and the updates have been made during this timeframe.

HTH

_{Wednesday, December 5, 2018 1:36 PM}

Hi all

I had the same issue and fixed it.

Note that each Software Update has its own Maximum Runtime option. Also the time options for a Maintenance Windows and execution of Updates, Packages etc are transformed from hours/minutes to seconds.

In my case the Maintenance Window duration was 1 hour. After the patching was failed, I've checked the UpdatesHandler.log and got the following:

3600 is a problematic update Maximum Runtime value in seconds, i.e. 60 min:

So the root cause is that as a few seconds were gone since the Update Deployment started, the MW time is not enough to install the update and it was failed with the 0x87D00667 error.

The best way to avoid the issue and make your clients to be patched is to increase the Maintenance Window duration.

I've increased my MW duration to 2 hours and the next time my clients were successfully patched. 

OK