Levi Stevens
My feedback
-
322 votesLevi Stevens
supported this idea
·
-
440 votesLevi Stevens
supported this idea
·
-
736 votes
Try this out over CMG in #SCCM TP 1906
Levi Stevens
supported this idea
·
-
1,265 votesplanned ·
AdminMark Silvey - ConfigMgr Product Team
(Engineering Manager, ConfigMgr, System Center Configuration Manager)
responded
Updating this one to planned. We have work in this area that should address the general set of comments that are in this suggestion. While we aren’t doing the NEVER reboot, we definitely hear you that you need more than a 24 hour window. We should have more details to share in the next TP so stay tuned for updates soon.
Levi Stevens
supported this idea
·
-
812 votesLevi Stevens
supported this idea
·
-
136 votesLevi Stevens
commented
Ran into this issue today. We have a collection based on the AD Computer Description field. The field was cleared in AD, and the computer didn't drop out of the collection because the discovery field in the system class was not cleared. I had to delete the SCCM record and let the client report in again to clear this.
Levi Stevens
supported this idea
·
-
69 votesLevi Stevens
commented
This is something I do to optimize my OSD. Including setting the restart timer to 0 with the variable.
-
20 votesLevi Stevens
commented
Seeing this issue still on 1710, placing the NO_SMS_ON_DRIVE.SMS does not help
-
1 voteLevi Stevens
shared this idea
·
-
188 votes
Updating status to planned.
We shipped our 1905 Technical Preview today.
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/624318This preview contains the first release of the task sequence debugger. We’ll continue working on it to address more of the asks in this item.
Levi Stevens
commented
Any update on this?
-
1 vote
Thanks for the feedback. Updating status to noted.
The download behavior is from Software Center and would hold true for any deployment using Download and Execute so changing for Task Sequences may have knock on effect for SWD etc.
One thing you may want to look at it our Task Sequence Pre-Cache available in 1611 Tech Preview https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1611#pre-cache-content-for-available-deployments-and-task-sequences – that allow you to pre-cache all statically referenced content ahead of availability time so no download is seen and all content is local. You can also conditionally download OS Upgrade Packages
Levi Stevens
commented
Bob - We may not always want to pre-cache content, and I think it would be GREAT if you also provided a download status for all in-progress downloads via Software Center, if there are 9 patches and 3 software packages in the download queue, show the download status for all of them! The task sequence should just "aggregate" these when running a Task Sequence.
Levi Stevens
shared this idea
·
-
4 votesLevi Stevens
shared this idea
·
-
310 votesLevi Stevens
commented
This would be huge. We use TS for our Office 365 and CRM rollouts, and don't really want users logging back on until it is finished.
Levi Stevens
supported this idea
·
I would also ask, that when checking for content availability, it only checks for content were the step is applicable, or the model is applicable. If I am imaging a Dell Latitude 5591, don't throw up an error because you cannot find the content for the Dell Latitude E6430U model. Some of our sites can take a long time to replicate packages, I would rather not have ALL OSD blocked until the driver package is 100% replicated.