Search the Community

Hello, Looking for some advice on staggered deployments via maintenance windows. I need to deploy windows updates at specific times and would like to have a single deployment which applies at the collections maintenance window and not at the deployment deadline time. i.e., If I have the following Device collections: Server Group 1. Maintenance Window: 20:00 - 23:00 Server Group 2. Maintenance Window: 21:30 - 00:30 Server Group 3. Maintenance Window: 23:00 - 02:00 And have a parent Collection 'Server Group A' of which all of the above collections are members. If I then deploy a required package to Server Group A with an available time of 20:00 and a deadline of 05:00, will the installation complete within each groups maintenance window? Essentially I'd like to have one deployment that applies at different times instead of three deployments. Is that possible? Many thanks

Gents, I think I did not manage to work with maintenance windows and I have some questions : - Why am I seeing software updates in the software center during a maintenance window ? - Why can I still install updates from the software center during a MW ? - Is there a way to make a software update available only during the MW ? Sypa

I have had a few clients that have had the request of having multiple business hours for differnt sites or departments for one reason for another. When you have alot of machines its not the best idea to just bounce to each machine and set the hours so I stumbled upon this and it has been a life saver. Go to Asset Compliance > Configuration Items and right click to create a new configuraton item. You create a discovery script to get your current settings: $cmClientUserSettings = [WmiClass]"\\.\ROOT\ccm\ClientSDK:CCM_ClientUXSettings" $businessHours = $cmClientUserSettings.GetBusinessHours() $businessHoursCI = [string]$businessHours.StartTime + "," + [string]$businessHours.EndTime + "," + [string]$businessHours.WorkingDays Return $businessHoursCI It will return a value like 7,19,62 for 7 am to 7pm Monday-Friday all you would do to modify that is use the script below and the chart to add up the days. Sunday 1 Monday 2 Tuesday 4 Wednesday 8 Thursday 16 Friday 32 Saturday 64 So if you would want Sunday - Saturday it would be 127 then 5am to 7 pm you would just modify the script to look like it does below. You create a remediation script to set new business hours: $startTime = 5 $endTime = 19 $workingDays = 127 $cmClientUserSettings = [WmiClass]"\\.\ROOT\ccm\ClientSDK:CCM_ClientUXSettings" $businessHours = $cmClientUserSettings.PSBase.GetMethodParameters("SetBusinessHours") $businessHours.StartTime = $StartTime $businessHours.EndTime = $EndTime $businessHours.WorkingDays = $WorkingDays Try { $result = $cmClientUserSettings.PSBase.InvokeMethod("SetBusinessHours", $businessHours, $Null) If ($result.ReturnValue -eq 0 ) { "Success." } Else { "Failed to set SCCM client business hours." } } Catch { "Failed to set SCCM client business hours." } You can then deploy that to every machine or if you would like to have multiple business hours you would make multiple configuration items then just deploy them to seperate collections. This has come in handy for me being able to set multiple business hours across a company, I hope somebody else finds it useful. Bryan

====================================================================================================================================================================================== >> Available via download here on the TechNet Galleries! << ====================================================================================================================================================================================== I do have to admit that this tool is already available in it's final form for over a month, but it seemed appropriate to also post here about this final relase. I think this right-click action might be very usefull for most administrators. It also took quite a while before I finally made a 1.0 version of this script/ form. Now it’s there, I also have to admit that I’m even a bit proud of it! It was a nice way of getting familiar with PowerShell and WMI. With answering a few very basic questions, I'll try to provide as much information as possible. What functionalities does it provide?This right-click action shows a lot of detailed information about the collections of which a device is a member and also about the collections that the primary user of a device is a member. A quick overview of all the functionalities comes down to the following information per tab: Tab – General; The Name, Id. Limiting Collection, Last Update and Last Membership Change of the Collections. Tab – Deployments; The Name of the Collections and the Name, Type aand State of the targeted Deployments. Tab – Variables; The Name of the Collections and the Name, Value and Type of the Collection Variable. Tab – Maintenance Windows; The Name of the Collections and the Name, Start Time, Duration, Recurrence, Schedule, Type of the Maintenance Window. Tab – Power Management; The Name of the Collections, the Name of the Non-Peak Power Plan and the Name, Start Time, End Time and Wake-up Time of the devices in the Collection. Tab – Primary User: Tab – General; The Name of the Collections, Id, Limiting Collection, Last Update and the Last Membership Change of the Collections. Tab – Primary User: Tab – Deployments; The Name of the Collections and the Name, Type and State of the targeted Deployments. What does it look like?To show the power and usage of this right-click action, I created the following small movie: Where is it available?The final version of my Collection Details Form is publicly available via the TechNet Galleries and for a direct download, via ShowCollectionDetails_v1_0p.ps1. How can it be used?To use this script as a right-click action, save the script at [sCRIPTLOCATION], make sure that the folder <AdminConsoleInstallDir>\XmlStorage\Extensions\Actions\ed9dee86-eadd-4ac8-82a1-7234a4646e62 and the folder <AdminConsoleInstallDir>\XmlStorage\Extensions\Actions\3fd01cd1-9e01461e-92cd-94866b8d1f39 exist and add a XML file to those folders as specified here: <ActionDescription Class="Group" DisplayName="Custom Actions" MnemonicDisplayName="Custom Actions" Description="Custom Actions" SqmDataPoint="53"> <ShowOn> <string>ContextMenu</string> </ShowOn> <ActionGroups> <ActionDescription Class="Executable" DisplayName="Show Collection Details" MnemonicDisplayName="Show Collection Details" Description="Show Collection Details"> <ShowOn> <string>ContextMenu</string> </ShowOn> <Executable> <FilePath>PowerShell.exe</FilePath> <Parameters>-ExecutionPolicy ByPass -WindowStyle Hidden "[sCRIPTLOCATION]\ShowCollectionDetails_v1_0p.ps1" -ResourceId "##SUB:ResourceId##" -SiteCode "##SUB:SiteCode##" -SiteServer "##SUB:__Server##</Parameters> </Executable> </ActionDescription> </ActionGroups> </ActionDescription> Questions?Please don't hesitate to drop any questions, either here or via my own blog at: www.petervanderwoude.nl

Is it possible to set up multiple maintenance windows on one collection or is the solution to set up multiple collections and set up maintenance windows for each collection?

Hello, We have created Automatic Deployment Rules and collections for our Software Updates for our servers. In the Software Update collections, we have defined a specific Maintenance Window, which relates to Microsoft's Patch Tuesday as shown in attached graphic. However, we are finding that as soon as we populate our collection, the updates are being download and installed! (i.e. Outside the Maintenance Window) Obviously this isn't right. One concern I have is that a particular server can be a member of multiple collections which might have different Maintenance Windows, so any tip on how these conflicting windows "add up" would also be helpful. Can someone give a tip on whether there is a particular log or setting in the infrastructure we can refer to to investigate this?

Can anyone tell me where to look to find out why software updates would not have run/installed at deadline? We deployed updates last night with a deadline of 8:00pm. We have a nightly maintenance window from 8:00pm to 4:00am. Typically updates run without issue, but this morning I've come in to updates being available for install. Nevermind i found it. For any other n00b that may be looking. UpdatesDeployment.log on the client, as if it could be any clearer. Sorry my brain is apparently sleeping in this morning.