It would be great to export just task sequence xml file so it can be added into git repo in multi admin enviorment
It would be great just to get drop in task sequence to export task sequence xml file to it can be uploaded to external repository as way to keep track of changes in any change management system1 voteplanned · AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for your feedback.
Updating status to planned, see https://docs.microsoft.com/en-us/mem/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Our 2006 release is now in the opt-in phase (fast ring)
Support Information: https://aka.ms/cmcssreleaseinfo
This releases adds the Community Hub https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/community-hub which addresses some of the User Voice asks you have added for task sequence version control, auditing, revision history etc.
The Hub is nascent and we will continue to iterate, improving and adding new features.
As part of this process we would appreciate your comments and feedback on the Hub.
Run scripts brought a brand new model to handle client troubleshooting, but it can run from collections only.
it would have been super useful to be able to run it on a machine\category from the Deployment Status node and then maintain clients with in progress \ unknown \ active \ inactive state.
today when we have a list of computers who didn't report their status we need to manually create a collection with these clients to run a scripts and there's not even a built-in way to create a collection from the asset details1 voteplanned · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We plan to add this to more places in the UI in future releases. Thanks for the feedback.
When Support Center runs App Deployment Evaluation cycle locally, it uses Schedule 121, which is OK. However, when it’s connected to remote machine, it uses Schedule 123, which was deprecated at some point.
Future release of Support Center should always use schedule 121.1 voteplanned · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We will look into fixing this for our next release.
- Don't see your idea?