1,854 votesstarted · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We’ve released our 2001.2 Technical Preview.
For more info:
This release has some update to the task sequence as a deployment type. See
172 votesplanned · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This feature will evolve from the “run scripts” features that first showed up in ConfigMgr 1706 tech preview. It lets you build a library of powershell, and execute them on demand. We will evolve DSC capabilities into this feature too.
17 votesNoted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
This makes sense to me. Surprised no more support than this..
680 votesstarted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Nudging this to started again… as there are even more updates in #MEMCM 2001.2 and 2002 tech previews.
An error occurred while saving the commentTom Brisby commented
The server group functionality is nice, but I've been struggling to find any documentation describing what happens when deployments are applied to collections with this setting enabled. With no custom node drain or resume scripts applied, are the nodes simply rebooted without any sensitivity to the cluster resources? Are there any example node drain/resume scripts available? What I'd eventually like to see is a more true integration of Cluster aware updating and how that process proceeds with SCCM. Right now, SCCM can be used to select specific patches to place in a SUG and then deploy them, but using SCCM to patch clusters is still nebulous and feels..dangerous. Cluster aware updating is much healthier for the clusters, but doesn't have any connection to SUGs in SCCM meaning that WSUS has to be directly managed as well.