Microsoft Store template issue
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
If it works.
I just modified the code so that the emsixbundle installs in session_setup and not in install.
I'll let you try:
https://srvluti.ad.tranquil.it/wapt-tes ... EPROD.wapt
Simon
Yes, but that means one installation per user. We can't afford that kind of setup, because we have machines that can have up to 40 different people connecting to them, so that's 40 times the app's profile size, and depending on the app's size, it can quickly become enormous (for example, FileLight, which is 153MB x 40 = 6GB just for that one, and that's multiplied for each app). And don't even get me started on Photos, which is 1.1GB...
Good morning,
We realize that there are not only .emsixbundle but also emsix, eappxbundle and eappx which will all pose the same problem of not working in install for all users. This forum post at MS indicates the same situation for .eappx for example:
Sincerely
Gwenaël
We realize that there are not only .emsixbundle but also emsix, eappxbundle and eappx which will all pose the same problem of not working in install for all users. This forum post at MS indicates the same situation for .eappx for example:
We are currently reworking the package to take into account the different extensions starting with ".e" but we can do nothing regarding installations in session_setup, it is a limitation of Windows.I don't think the eappx package will work with the Add-AppxProvisionedPackagem or DISM. If you wanted to only install the package for the current users you could script the installation by getting each users SID and running something like Add-AppxPackage -Path ./Appfile.eappx -User<SID>
Sincerely
Gwenaël
