Greetings!
We want to install some Metro-applications via SCCM 2012 R2.
Applications are published in Windows Store. They aren't self-developed applications.
I see are two ways how to do it with SCCM 2012R2:
1. Use "Windows app package (in the Windows Store)" type. User should click on the Install button from the Application Catalog, and he will be redirected to the Windows Store. Then he shoud continue install with Windows Store.
Yes: Simple configuration with SCCM 2012R2.
No:
a) It is necessary to provide access to the Windows apps store (it is frobidden by GPO now), and make sure that users did not install any crap. Maybe we should use AppLocker to block anything except approved apps;
b) Required user liveID to install any application from the store. A lot of our users didn't have it, of course. Anyway they are wouldn't do it.
2. Use "Windows app package (*.appx,*.appxbundle)" type.
Yes: Click it and forget it. Very easy install for users experience.
No:
Difficulties with the implementation, because of:
a) Should riping *.appx file from the store (rather easy, but still bored);
b) Find and add all packages and dependencies that an application has - for example C ++ components;
c) Solve the problem with the "sideloading key" for application activation.
We decided to go the second way, but failed with the last paragraph.
We found that when we install applications from the store, Store install a special key for current application (Sideloading key), and then activate an app. If we try to install appx, without sideloading key activation, the application does not start.
When I try to start an app, I see in EventLog Microsoft-Windows-TWinUI/Operational a Error:
Activation of the app [App] for the Windows.Launch contract was blocked with error 0x80073CFC because its package is in state: Error from application of unknown origin.
So, the question is: What is the best way to install already published Metro Applications in domain enviroment without Windows Store access? And how to solve the activation problem?