Forum Discussion
MSIX Shared Package Container for normal user
As an administrator i tested the following which does work:
1 have an AppX package installed with PackageFamilyName
2 have an MSIX package installed with PackageFamilyName
3 Created an SPC and put in both PackageFamilyNames and add to system
After starting the AppX application i see the MSIX content is mergend an can be used in the AppX.
But above is for Administrator working...but how about a normal, non-admin user?
For a non-admin user actions 1 and 2 are working, but option 3 is not working since you require administrative rights.
Anymone who can replay and tell me how I can get a SPC work for a non-admin user?
Or is that not possible and Microsoft assumes everyone is Administrator?
12 Replies
- Just come across this concept although have have yet to come across a requirement for it. I take it we are referring to this article.
https://learn.microsoft.com/en-us/windows/msix/manage/shared-package-container
If that is the case, I agree with the comments so far with it needing to be configured to allow a user launching the application to be able to communicate with other user installed MSIX packages.
It would also be worth noting that this sort of configuration feels like App-V virtual environments and there was an option in MECM to manage this by creating the relationships and it would process the xml configuration at the point of deployment. If this is intended to be an enterprise solution, it needs to be offereed in a way that it can be managed across the enterprise desktop estate.- Yes, like AppV we would like to combine two packages into one like a Connection Group (AppV).
If would be nice to combine an AppX with a MSIX package as well.
Example: AppX Power BI Desktop and an MSIX package with the middleware for the AppX package, like Oracle, Teradata etc connector drivers for Power BI Desktop- Pollewops The term "middleware" triggers me to mention this. In this sense, I interpret middleware as a apcakge with an exe (and other stuff) that is usually not exposed to the start menu, but used by other software by referencing the name of the exe.
Under App-V we tended to use Connection Groups with middleware. But that is mostly because we were dealing with middleware (like javaws.exe) that might be used by multiple applications and have backwards-compatibility issues with newer versions of the middleware that might be needed by other packaged apps.
Seeing less of this these days, rather than resorting to SPC, I find it possible to package the middleware using an ApplicationAlias inside the middleware package, which works more like the App-V RunVirtual key but has the advantage of being directly part of the Middleware package.
- Created a case for it. Seems like add-provisionedsharedpackagecontainer is a solution here.
But no detailed info is available for it at Microsoft.
Will update this thread when i have some news- I have an update...
add-provisionedsharedpackagecontainer is available in Powershell, but there is no documentation yet for it and can't be used according to Microsoft.
The Shared Package Container (SPC) can only be used for ADMINS !!!
The SPC can't be used for normal users and make it worthless for us and for all people i guess.
Microsoft still has some progress to made with MSIX to make us able to transfer our AppV packages to MSIX packages.- "The Shared Package Container (SPC) can only be used for ADMINS !!!
The SPC can't be used for normal users and make it worthless for us and for all people i guess."
I can't believe that I never noticed this. I thought that the requirement for Win11 was blocking enough, but it can't be used by standard users, WTF???
