The Role-Based Administration documentation does not describe what the individual permissions actually control, and they are not self explanatory. For example, under Collection, you see several different 'modify' permissions and it isn't clear what they each control:

-Modify
-Modify Client Status Alert
-Modify Collection Setting
-Modify Folder
-Modify Resource

Please provide even a basic amount of information about what they control in the console. This will help prevent us silly sysadmins from just giving people tons of permissions so we don't have to reverse engineer what each of the settings does in order to let people do just what they need.

Thanks for your help!

The 30 Day Rollback option is available for all windows 10 users, but currently can not be automated using SCCM.

This should change, as this feature closely integrates with Microsofts testing strategy of using different branches which grow bigger in size as the rollout of a new build progresses.

When planing to integrate a similar scenario, in our case, we anticipate errors which have not been cought in testing of the previous branch and need to be able to quickly restore operations.

I am well aware that if all our applications were packaged this would not pose much of a problem but as you all know this is rarely the case.
Because of that a reinstall of the previous build (and local applications) would cause a massive loss of time (and money).

Since MS is pushing Enterprise Customers to become part of their testing chain and offers reasonable support times only with LTSB this feature - available even for home users - should be automated using SCCM.

Currently when you select a collection(s) in the console, then utilize the "Add Selected Item" button you are able to functionally add the collection(s) selected to another collection as a member, however it does not actually add the member of the selected collection(s) to the target collection just the root collection itself.

Example A:
1. Open Console and navigate to Administration \ Assets and Compliance \ Device Collections \ Select a collection.
2. Click the "Add Selected Items" button and then "Add selected items to existing device collection"
3. Select the existing collection that is to be the target

The collection itself now shows in the membership of the target collection, however the members of the collection added are not and are not utilized by the target collection.

Example B:
1. Open Console and navigate to Administration \ Assets and Compliance \ Device Collections \ Select a collection and open it.
2. Select a device or devices in the collection
3. Click the "Add Selected Items" button and then "Add selected items to existing device collection"
4. Select the existing collection that is to be the target

The devices themselves now shows in the membership of the target collection.

Since the functionality of this ribbon button is a part of the Core XML files for the console stored "%ProgramFiles%\Microsoft Configuration Manager\AdminConsole\XmlStorage\ConsoleRoot." it is not supported to modify them by Microsoft per the article here: https://msdn.microsoft.com/en-us/library/hh949647.aspx

Please update the code for this button \ process to add the members of a selected collection to the target collection truly or grey the button out when collections are selected instead of devices \ users so that the "Add Selected Items" cannot be utilized.

We find ourselves trying to go from MAC address to device in the console fairly regularly, especially when troubleshooting things like PXE from the logs (which only shows MAC address) and needing to kill off failed OSD records (which may be named "Unknown" or have a random computer name in ConfigMgr, but you're now in WinPE ready to kick off the TS again, but only have the MAC from ipconfig /all to ID the old record).

The MAC addresses are already being pulled by Heartbeat inventory, but you can't search/filter of part/all of the MAC address.

Thank you for making ConfigMgr easier to use and troubleshoot!

We are trying to create a deployment for a package as below:

Start-CMPackageDeployment -CollectionName "WOL Testing" -PackageName "Powerdown" -DeployPurpose Available -DeploymentAvailableDay 02/05/2016 -DeploymentAvailableTime 10:50

- Findings as below:

Required Deployment with Schedule and Available Day and Time:

Start-CMPackageDeployment -StandardProgram -CollectionName "Brik" -PackageName "SMS Toolkit" -ProgramName "SMS" -AllowSharedContent $true -DeployPurpose Required -DeploymentAvailableDay 2016/11/01 -DeploymentAvailableTime 11:00 -ScheduleEvent AsSoonAsPossible

Available Deployment with available Day and Time:

Start-CMPackageDeployment -StandardProgram -CollectionName "1" -PackageName "SMS Toolkit" -ProgramName "SMS" -AllowSharedContent $true -DeployPurpose Available -DeploymentAvailableDay 2016/11/01 -DeploymentAvailableTime 11:00

- As the below options might be deprecated and new ones used please find the new commsnds as well:

Old : 'DeploymentAvailableDay' New: 'DeploymentAvailableDateTime'
Old : 'DeploymentAvailableTime' New: 'DeploymentAvailableDateTime'

Not yet introduced:

Old : -FastNetworkOption is not defined New:'DownloadContentFromDistributionPointAndRunLocally'

Old : -SlowNetworkOption is not defined New:'DownloadContentFromDistributionPointAndLocally'

- New Commands as below:

Required Deployment with Schedule and Available Day and Time:

Start-CMPackageDeployment -StandardProgram -CollectionName "Brik" -PackageName "SMS Toolkit" -ProgramName "SMS" -AllowSharedContent $true -DeployPurpose Required -DeploymentAvailableDateTime "2016/11/01 11:00" -ScheduleEvent AsSoonAsPossible -DownloadContentFromDistributionPointAndRunLocally

Available Deployment with available Day and Time:

Start-CMPackageDeployment -StandardProgram -CollectionName "1" -PackageName "SMS Toolkit" -ProgramName "SMS" -AllowSharedContent $true -DeployPurpose Available -DeploymentAvailableDateTime "2016/11/01 11:00" -DeploymentExpireDateTime "2016/12/01 11:00"

=============