I really like the recent improvements to customize and brand Software Center. However, it we are only able to target Computer collections. We have a need to be able to target a USER collection.

For example, we want our end-users to see a different Software Center then our Admin and Tech users.

In future development, could you consider expanding this option?.

Also, it would be nice to be able to differentiate applications deployed to Users vs. Computers from within Software Center. One thing I miss about the old Software Center is it only showed advertisements to Computers, and you had to go to the Catalog to see Available User advertisements. Being able to change the view is software center to hide/show Catalog apps vs computer advertised apps would be useful.

Thanks.
Joe

The alert stating that SWC itself can not be loaded is displayed prominently over the SWC application running on-screen. Add either more details as to the actual reason for this dialog, like in other areas in the product, or separate messages to describe the fault less generally and with more suitable advice than "try later' as appropriate.

This is specifically not a bug in itself, but a shortcoming in the error trapping mechanism for multiple issues. Typical malfunction of the Provisioning Mode is just one possibility this and can be enumarated clearly in the context of MORE DETAILS. Cosmetically it appears as gibberish where SWC is clearly loaded and the nuance of component-level failures is lost on the average person.

Sometimes it's useful to allow a user who has been away for some time to defer an installation for the same amount of time (in days) that other users had (e.g. Win10 Feature Updates) rather than defer until a hard deadline. It would be great to specify that an installation or update could be deferred by the user for X amount of time since the first time they were actually notified. Perhaps as a bonus also have the ability to still have a hard deadline furhter in the future.

e.g. Users have 2 weeks to install the feature update from the time they are notified but has a hard deadline of 1 months from now. If a user was on vacation for 3 weeks they only get the remaining 1 week to defer. If a user was on an extended vacation and came back after the month was up they get the update immediately.

It would be of benefit to our organization to specify whether or not a deployment will display a toast notification stating that "New software is available". Reason is that we sometimes we are required to deploy a newer minor reversion that appears as a full application, but it may be an application the user already has installed. An example of that would be Google Chrome. The user will receive a popup notification that new software is available, but when they go into the Software Center nothing "new" to them will be displayed.

We have consider disabling all notifications in the client settings, but this will turn off the notification "changes are required by administrator" when Software Updates are deployed, which we need to have on.

We have also considered special deployments for those cases which the deployment is set as required with "Hide in Software Center and all notifications". We do not want it hidden, we just don't want it to display toast notifications.

Our overall concern about the "new software" notifications appearing is that users may get annoyed by them if it is only a newer version for an application they already installed. We are implementing a new method of software deployment to our organization and this is something we have considered. I would gladly like to know if there are any alternatives that we can perform right now.

I'd like to see the ability to give Task Sequences friendly/localized named, like you can with apps/packages. In fact, replicating the entire "Application Catalog" tab of an application properties dialog in the task sequence properties dialog would be even better. This would also give the option of TS-specific descriptions/icons/keywords/categories/etc.

My reasoning is that our organization is effectively multi-tenant, and we're required to name our task sequences and other content with prefixes denoting department. This makes for annoying and unfriendly TS names when listed in Software Center or the task sequence list of WinPE. I see no reason why endpoints should be required to show the technical TS name in these lists when the TS is already targeted to relevant collections.

For backwards compatibility, the regular TS name could be shown when a localized name is not given.