Did those 'used to be' CM07 clients with a service window that got upgraded to Cm12? I had that as well. leftover service windows on former cm07 clients that got converted to "local"... but were sort of half behaving like a Business Hours Window and half behaving like a MP-applied service window.
Here's the first question: they might be the legit business hours window you get by default in CM12. (In which case that's fine). The way to confirm that is if each day is it's own GUID. If each day is the same GUID, then it's a stale one that you likely what to trash. Let me know... (while I go dig up the ConfigItem I used to delete the stale cm07 one...) Sherry Kissinger On Tuesday, June 3, 2014 12:30 PM, "Iacaruso, Mike" <[email protected]> wrote: In looking in the serverwindowmanager.log I see a list of 7 inactive service windows that are running right through the active maintenance windows. I do not know how they got applied but is there a way to remove them globally? From:[email protected] [mailto:[email protected]] On Behalf Of Iacaruso, Mike Sent: Tuesday, June 3, 2014 11:10 AM To: [email protected] Subject: RE: [mssms] Software deployment maintenance windows OK I did have local service windows applied. What would be the best way to remove these for all clients? Is there a global setting that I might have applied? From:[email protected] [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Tuesday, June 3, 2014 11:00 AM To: [email protected] Subject: Re: [mssms] Software deployment maintenance windows Ok, two possibilities come to mind. 1) that's a 3 hour service window. Whatever it is you are installing, if you cumulatively manually figure out the time you have set for "how long it might take to install this"... is it more than 3 hours? or even exactly 3 hours? It might not bother to try until there is a service window big enough. 2) (less likely) locally using Client Center, check if the box has local service windows applied... and it's basically locked out every time anyway; so nothing will ever install unless you check the override. Sherry Kissinger On Tuesday, June 3, 2014 9:50 AM, "Iacaruso, Mike" <[email protected]> wrote: I don’t want to ignore the maintenance window but even when there is a window available it is still not installing. Still stating “waiting for a service window”. From:[email protected] [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Tuesday, June 3, 2014 10:34 AM To: [email protected] Subject: Re: [mssms] Software deployment maintenance windows If I'm reading this right... I think you are under a misconception. If a box is in a service window, based on ANY collection, ANYWHERE... it is in a service window. It's not "per deployment". It's "per machine". If you want a machine to ignore it's service window for any particular deployment, you need to check the box about ignoring a service window for that deployment. Sherry Kissinger On Tuesday, June 3, 2014 9:07 AM, "Iacaruso, Mike" <[email protected]> wrote: I am hoping that someone can help me with this issue, I am having issues with software not installing due to “waiting for service window”. The deployment collection does not have a maintenance window applied but logs show that the deployment is “ready” then “waiting for service window”. This is becoming very frustrating. Is there something that I am missing during the deployment configuration? I know these systems are part of another collection that have a 3 – 6am window but I am trying to deploy the software at that time anyway. Mike Iacaruso Enterprise Desktop Engineer Office of Technology Services Towson University 410-704-3965 [email protected]
