Allow us to pre-provision appx application types in the Task Sequence
ConfigMgr supports .appx deployment, but sometimes we want these on every machine, so our preferred way would be to do this in the Task Sequence.
Currently, the Add Application step in the Task Sequence doesn't let us browse for .appx packages.
Please consider adding support these during OSD.
It would be great if you would add this option to help with Local Experience Pack .appx install .
Definitely a must with WinX becoming more appx based for most of the useful apps.
However, it would be nice to also have the ability for SCCM to be able to remove all default appx packages from a windows image so that we have full control over exactly what apps are installed by default as part of OSD & TaskSequences.
Frank Rojas commented
This currently is documented as not supported:
The applications must meet the following criteria:
The application must have a deployment type of Windows Installer or Script installer. Windows app package (.appx file) deployment types aren't supported.
In other words if this feature was added it would be a new feature request, not a bug that needs to be fixed. Just FYI.
I tried to to install Company Portal appxbundle during the OSD in Task sequence. Il doesn't work! Please fix this!
Apps are becoming very difficult to work with in ConfigManager.
Need the ability to provision to all users during OSD and also to force an update to installed apps during OSD.
Users log in to a system and many of the apps are outdated (My Office -> Office) or worse, have changed name (photos -> Edit Videos).
Please add this, we have a number of appx apps in our environment now that we can't install during OSD.
As more and more apps are available, this becomes a necessity.
I vote for appx during OSD and in task sequences.