Just curious, why do you need to distinguish how the software is targeted? We always figured end users only cared about what was required and we have that filter, but curious why they would care if it was targeted to the machine or not.
@Chad Could you elaborate on what a real workflow is? We've done a lot of work on approvals this last year so would love to hear more on what gaps you still need addressed.
356 votesNoted · AdminMark Silvey - ConfigMgr Product Team (Admin, System Center Configuration Manager) responded
Thanks for the suggestion. So you are saying when a user category is added to an application it should be ‘filterable’ in Software Center even when it’s deployed as system? Why not just deploy the application to the user to get the user category?
@Doug Morrison - Makes total sense, thanks for the feedback. No more questions :)
@Dietmar - Regarding preventing users to install licensed apps to many machines: We've invested quite a bit in our approval scenarios over the last few releases and continue to do so. Approvals now can be tied to a machine so a user would have to request approval again for new machines. We've also recently shipped support to revoke approval, causing the app to be uninstalled, in a recent technical preview. Let us know if you have any more feedback on these scenarios!
Doug - It's already possible in the drop down filter... all user categories are visible there. We are tracking to addtions to this that are gaps.
1. It's not very discoverable in the UI. Users are used to the categories listed on the side..
2. User categories aren't available on the client when apps are deployed to machines.
Let me know if we're missing something else.
User categories are the way we support this today. Does categorization help? I suspect having them them in the drop down is not discoverable? If we made categories more visible to the user (similar to a folder concept, but with no nesting) would that help? In that scenario, would you still want a default "all" view or something else?
To the "creation of the app manually" comment... are you saing you'd like to be able to point to an exe and have an application created using that exe and all the content in it?
Check out the new uninstall behavior in 1804 tp.
We aren't quite ready to update the status on this, but have plans in this area. Our initial approach may not *exactly* be collection membership but would enable automated uninstall without the need for multiple deployments or multiple collections. I know that's a little vague, but we'll be able to give more clarity in the coming months. Stay tuned....
Thanks and please keep the feedback coming, it heavily influences our priorities and implementations.
Why not use a package and program for this? If you need this, it's easy to write a detection rule that is never 'installed' which would accomplish this. Is that not sufficient?
Raphael - The new software center already has this; click the 'Filter' drop down and you will see all categories. What are you seeing?
This does appear to be the same request as this: http://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8339946-compliance-settings-like-config-items-or-baselines
Do you agree?
Is that just for applications or for all deployments?