Michael Krueger
My feedback
-
358 votes
-
52 votes
Updating status to planned.
Thanks for the feedback, I filed the exact same issue in our database a while back. We’ve addressed recovery from being stuck in ProvisioningMode in our 1902 release. See https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902#bkmk_client
Next step is to clean up the task sequence.
Michael Krueger
supported this idea
·
-
1,987 votesstarted ·
AdminMark Silvey - ConfigMgr Product Team
(Engineering Manager, ConfigMgr, System Center Configuration Manager)
responded
I’m re activating this one based on the fact that we don’t show the intrusive reboot countdown after the software was installed. We still have some work to do here to make this experience meet the requested behavior.
Michael Krueger
supported this idea
·
-
69 votesMichael Krueger
supported this idea
·
-
59 votesMichael Krueger
supported this idea
·
-
5 votesMichael Krueger
supported this idea
·
-
82 votes
Refreshing the status…
We released our 1905 Technical Preview today. This release adds Packages for pre-cache and the Driver Package creation wizard is updated too.
Doc: https://docs.microsoft.com/sccm/core/get-started/2019/technical-preview-1905
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Group-applications-into-a-single-deployment-in-ConfigMgr/ba-p/624318Michael Krueger
supported this idea
·
-
1 voteMichael Krueger
shared this idea
·
-
27 votesMichael Krueger
shared this idea
·
-
15 votes
great suggestion
It would make sense to configure SQL Server Index Optimization with Ola Hallengrens Maintenance Solution and simply enable this via the Rebuild Indexes function within ConfigMgr Site Maintenance settings.