Reboot Policy / Functionality
Hello, I would like to see a feature added that would allow us to configure a reboot policy under the following conditions: If the machine hasn't been rebooted since X amount of time has elapsed, then force a reboot during the next defined maintenance window. This functionality also requires the ability to define this maintenance window. and/or If the machine has been sitting in a 'waiting for reboot' state for X amount of time, then force a reboot during the next defined maintenance window.
Add the ability to make changes to Test Groups instead of having to delete and remake the group
As the title says, I'd like the ability to make changes to a test group for patches instead of remaking the group whenever we need to add/remove a PC.
Add build numbers to patch description for Windows 10 cumulative updates
Hi, As far as I can tell, every Windows 10 cumulative update raises the OS build number, e.g. KB4499177 [1] will take the OS to build 14393.2999 (with the .2999 being the build number updated by the patch). As the release of a cumulative update invalidates all the previous cumulative updates, I would find it extremely useful if the patch description for the updates contained the build number (.2999) - so that I could tell at a glance if the patch being listed was a genuine update, or an erroneous
Installing missing patches during deployment.
Hi Although applications can be installed automatically after an OS deployment, it should also be possible to automatically apply approved patches. At present the deployment process is slow and/or disjointed. Following OS deployment and automatic install of the DC Agent, a PC is still not listed under 'Managed System' in patch management until a patch scan has been completed. We therefore have to go to Inventory->Computers, find the new PCs to initiate a patch scan, waiting for it to complete, then
Automatic deployment as new configurations for better overview
Hi It would be very helpful if ME DC would create new configurations for automatic deployment schedules where patches will be installed. This gives us an overview on the status of those installations, because currently it happens in the background and it's not clear (unless there's an easy way to get the status of those installations already).
*WARNING* for admins using Automatic Patch Deployment
We just had a mini-crisis with desktop central patch deployment the other day as we had a mess of unapproved updates deploy through our automatic patch deployment policy. After sending our logs to support and long remote assistance session we learned exactly what caused us such a panic. I am sharing with the community to hopefully to spare anyone from a similar scenario. We got lucky in the end, the patches did not negatively affect our PCs. We will not make the same mistake twice. Chat transcript:
Scheduled Off the network updates
I think this has been discussed here before but if not I wanted to suggest it. So Desktop Central (henceforth referred to as DTC) has the ability to schedule updates. What I'd like to see is the following: During the week I schedule windows updates for all my machines to take place on the weekend/specific date/time. DTC prestages all the updates to the machine at some point before the weekend/specific date/time The local agent retains the knowledge of the date and time for the scheduled update. Regardless
Suggestion for Feature - Ability for Offline Patch Deployments with Notification and User options.
I'm proposing to have locally cached deployment option. We have users that take their laptops home every day and even for weekend. Having ability to cache patches for installation on their machine while they are not building and give them option to when to apply them. Here is a quick scenario how that would work. User is scheduled to get patches on Monday Morning between 12am a - 10am. They take laptop home on friday and don't come back into office until 9am which only leaves 1 hour of deployment
Set a duration for Automated Patch Deployment
I would like the ability to set an duration for the Automated Patch Deployment tasks. Many of our computers are laptops and customers will be gone off our network for 3 or 4 days before returning. I would like to be able to set a time limit on the length of time that a task waits to run. For example, allow the patches to retry for up to 24 hours after it begins in 1 hour increments. Currently when the people are coming back many days after a patch deployment they will get patches and reboot. If we
