Koenraad Rens
My feedback
-
99 votes
Koenraad Rens supported this idea ·
-
3 votes
Koenraad Rens shared this idea ·
-
0 votes
Koenraad Rens shared this idea ·
-
3 votes
Koenraad Rens shared this idea ·
-
39 votes
Koenraad Rens supported this idea ·
An error occurred while saving the comment -
22 votes
An error occurred while saving the comment Koenraad Rens commented
You don't need to deploy your patches to the collections you use to configure the maintenance windows. Create a seperate collection with all the servers and deploy your patches to that collection.
-
11 votes
Koenraad Rens supported this idea ·
-
79 votes
Updated by bobmn for sangeev/OSD
An error occurred while saving the comment Koenraad Rens commented
A simple popup Task Sequence Step would give flexibility.
I'm currently using a Restart Step to give the messsage, but it times out after 9999 seconds.
(Or don't count down when I enter 9999 seconds :-))Even better would be a popup with a Yes/No or OK/Cancel option and a TaskSequence variable that contains the choice.
Koenraad Rens supported this idea ·
-
147 votesstarted ·
AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Updating status to started. See https://docs.microsoft.com/en-us/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Configmgr 2003 Technical Preview released today and has a new SDK method for task sequence progress.
For more info:
Doc: https://docs.microsoft.com/en-us/configmgr/core/get-started/2020/technical-preview-2003#bkmk_tsapi
Blog: https://techcommunity.microsoft.com/t5/configuration-manager-blog/onboard-clients-to-microsoft-defender-atp-using-memac-and/ba-p/1266085This should address some of the asks here, please try it out and let us know your feedback.
Koenraad Rens supported this idea ·
-
95 votes
Koenraad Rens supported this idea ·
-
479 votes
Koenraad Rens supported this idea ·
An error occurred while saving the comment Koenraad Rens commented
To me it seemed strange this used the maintenance window.
We are upgrading from 1511 to 1607 and using the automatic upgrades for the first time. We gave the upgrade 14 days.
Clients wait until the maintenance window. But at that moment ccmsetup only creates the Upgrade Task which will be started somewhere in the future. It didn't seem this task respected the Maintenance Window.
In our site with maintenance windows once every week, most upgrades will be started at the end of the 14 days period.
I also encountered several problems which were fixed by rebooting the sms agent host service.
Let ccmeval restart the service when it hasn't restarted in X days. This would also fix issues that aren't explicitly detected with ccmeval.