When sorting any area alphabetically (or using any other criteria), the view automatically jumps to the top (or bottom). This defeats the purpose of reversing a sort. For example, if I have 2000 objects in the view, and the object I am looking for starts with a "U", it makes sense to reverse the name sort to reverse-alphabetical, however, when I do that it dumps me at the bottom, meaning now I have to scroll up through 1800 objects instead of down. Please change this so that when a sort order is called for, the view stays in the same place.

My customer has +_ 600 maintenance windows using the server grouping feature .

Feature Request Nr1 : They use the node drain / node resume feature with PowerShell. They are still modifying and changing the script almost every week . That script is used for those 600 collections :

a) a central repository/place to enter the script details and be able to reuse that for each server group collection like for power management custom templates .
b) If they make a change in the “central” PowerShell repository , it keeps history ( Like application revisions ) and replaces that automatically in all Server Groups Collections where applied.

Feature Request Nr 2 : More options per server group

I would like to see a fourth option ( in the server group options) that is a combination of option b) and c) , meaning that you define a list but that from that list a number of machines in that list sequence can be patched at the same time. The reason is that you may have 20 servers in a maintenance window of 3h , then you don’t want to wait until the first one is patched , then the second one and so on . It would take way to much time to complete. If you have a predefined sequence list and you can from that list patch for example 5 servers at a time , that would help saving you time. Best one would be that you can create blocks in the sequenced list that can patch at the same time within the same maintenance window.

Feature Request Nr 3 : Powershell remoting (credential Manager)

Support for a credential manager within Configmgr where you can store certain credentials that the script (powershell remoting) need to run with ? to support a kind of “run as” scenario .

Feature Request nr 4 : Decent RBAC

Can you please create an RBAC role that only allows you to edit the maintenance windows or server group settings ? Reason is that most of the time , the business or release managers are defining their maint windows and not the server teams.

It would be great if there was a WMI class that we could query, or a method we could call, to verify if policy is targeted to a specific client. In complex OSD scenarios, there is no way to verify whether TS policy has been targeted to a device after modifying collection membership without accessing SQL directly. For example, a method that could be called with just the client GUID or resource ID and a specific Task Sequence policy GUID, simply returning True or False, would rock. This could be called every 30 or 60 seconds and the process could continue only once the method returned True.

There are multiple places where a reference to an application is only with GUID and DT name. E.g. logs.
If the DT name had version number in the name, it would easy to see what application is referenced when you have more than one version of a product and thereby more applications.

When creating an application for a Windows Installer, it would be great to have the automatic DT creation process to include the version, if provided, in the DT name.

In addition, if the creation of a script installer DT could include the names and versions from the application in which it is being created, it could ease the process of creating a script installer DT by eliminating the need to type the same text again.
It could simply prefill the text fields, so if any editing is needed, it would be possible there.

Setting the AD computer object description should be allowed inside a task sequence during the domain join operation.
Whether or not this is on the dialog box, is not important to me. I'd be happy setting a TS variable (ie. OSDComputerObjectDescription)

Alternatively, we could use a PowerShell script using different credentials (which Task Sequences also do not allow). Similar to the way
the "Run Command Line" allows the input of credentials.

Right now we have to use a kludgy "Run Command Line" using credentials and run
a batch file that calls something like: PowerShell.exe -executionpolicy Bypass -command pscommandhere
or: PowerShell.exe -executionpolicy Bypass -file .\powershellscript.ps1