Event banner
Event details
116 Comments
- We are in the early stages of planning an implementation of the Company Portal. I noted after downloading the Company Portal I am only seeing our Configuration Manager Software Center apps not the test app I created from the New Business Store from Azure. Would you be able to demo the steps needed so Company Portal only shows our Apps deployed from Intune?
- https://learn.microsoft.com/en-us/mem/configmgr/comanage/company-portal
- The company portal would show both the world, but the software center only MECM , if it's having the client apps workload fully moved to intune then it would be only Intune apps
Thanks for participating in today's session of AMA: Microsoft Store and Windows app management! For reference, the panel covered this topic at around 16:00.
- We are looking to use winget for some application deployment. Is there a way to force winget to use Delivery Optimization so all devices don't reach out to the internet
Thanks for participating in today's session of AMA: Microsoft Store and Windows app management! For reference, the panel covered this topic at around 15:00.
- Should we manually remove the MSfB connections in ConfigMgr and Intune?
Deleted
- MCM 2303 prerequisite check creates a warning: "[Completed with warning]:Configuration Manager support for Microsoft Store for Business and Education has been deprecated since November 2021 and will soon be retired in the upcoming releases. For more information see: https://go.microsoft.com/fwlink/?linkid=2209682."
Thanks for participating in today's session of AMA: Microsoft Store and Windows app management! For reference, the panel covered this topic at around 12:00.
- W/ the Microsoft Store app been useless if ‘Private Store only’ is configured it leaves one functionality missing: Check for updates of Inbox apps / Store based apps. The use case is devices been off for some time e.g., days, or even weeks. Windows does not immediately check for app updates; it can take up to 24 hours to get updates. But these updates can be security critical. So, we trained the users to check manually via the Microsoft Store app. We tried to rebuild the functionality w/ winget. But the property to identify Store based apps is not supported in filters or search. So, this leaves only a full winget export and text parsing or hardcoding a list of apps to be checked by winget for available updates.
- If the Store is blocked with policy, will the apps installed from the private or old store continue to update properly? Will the built in apps update properly if the store is blocked?
- When disabling the Store with policy - ADMX settings - "Turn off the Store application" Group Policy states: If you enable this setting, access to the Store application is denied. Access to the Store is required for installing app updates. Does this language need to be updated? Will app updates still install for built-in apps and store apps deployed from Intune if the CSP is also configured to AllowAppStoreAutoUpdate or Group Policy setting to turn off automatic download and install of updates is disabled?
- KevinMineweaser_MSFT
Microsoft
Michael, Thanks for your question. For WSfB and inbox apps, the Store can be disabled and the apps will continue to be serviced. See https://learn.microsoft.com/en-us/windows/configuration/stop-employees-from-using-microsoft-store#block-microsoft-store-using-configuration-service-provider for configuration information. -Kevin- When disabling the Store with policy - ADMX settings - "Turn off the Store application" Group Policy states: If you enable this setting, access to the Store application is denied. Access to the Store is required for installing app updates. Does this language need to be updated? Will app updates still install for built-in apps and store apps deployed from Intune if the CSP is also configured to AllowAppStoreAutoUpdate or Group Policy setting to turn off automatic download and install of updates is disabled?
Thanks for participating in today's session of AMA: Microsoft Store and Windows app management! For reference, the panel covered this topic at around 08:00.
- What is the migration path from old company portal to "new" company portal? We tried to migrate, but some clients still have errors installing the "new" company portal. WinGet operation result: Operation result = InstallError Installed version = Reboot required = False Installer Error code = 0 Installer extended error code = -1978335202 Installer exception message = Ausnahme von HRESULT: 0x8A15001E Execution result: Action status: Failed Enforcement state: Error Reboot status: Clean Error code: 0]LOG]!><time="09:38:49
- Bryan Keller
Just to clarify, there is no new Company Portal, just a new method of modeling the app and managing new installs using Intune. So if the app is already on the device, it will not reinstall using the new app type. It will be detected as already installed and will not reinstall. So you should not expect successful install on devices already running Company Portal.
Hi Bryan Keller , that is clear, thank you for you correction.
We removed via the "old" method the company portal.Now the error occurs during the deployment via the "new" method.
Any ideas? Company Portal is currently not installed. Some fragments left?
- When deploying the Company Portal app from the new store in Intune, the installation fails for existing devices that have the Company Portal app installed from the old store. Will the existing installation of the Company Portal App update properly? Do we need to uninstall the Company Portal from the old store and reinstall from the new store?
- Bryan Keller
The app is already on the device so it will not be reinstalled. The app will install on newly provisioned devices however. There is no reinstall for apps that already exist on devices, the app that was already there previously will preserve all data and continue to be serviced.
Thanks for participating in today's session! For reference, the panel covered this topic at around 10:00.
When deploying new store apps we see a lot of Status failed errors in Intune, where we did not have many errors deploying Microsoft Store apps, often with below error.
The application was not detected after installation completed successfully (0x87D1041C)
What is causing the issue and when is this getting fixed?
Is this related to "Install behavior :User"? Why can't we change it to SYSTEM?
- Bryan Keller
Yes the issue is the app was previously installed per user. For Store UWP, you can't flip the install context. The best approach here is to uninstall the per-user app, then resinstall under System context.
- App was deployed through the store for business under system context. As we had to replace them with the new store apps, as the store was retiring, i don't really see how to deploy the apps in system context. How do we do that? We are not going to uninstall thousands of apps per user...
Same here. Have an open case with MS. Ours started happening when we switched from User mode to System mode.
- Some organisations have completely on premise environments - i.e. managed via Config Manager only. What enhancements are planned for app management for this use case, i.e. 1. Will MSIX AppAttach support appear within Config Manager? 2. Is the App-V EOL date of 2026 likely to get extended to give more time to let MSIX catch up?
- The original concept behind the original store was to try and standardise packages into a new and reliable MSIX derived format. With the new store the acceptance of Win32 apps, whilst it will increase the adoption by vendors, does not encourage those vendors to re-release their apps in MSIX format, creating additional effort on administrators to "repackage" those apps in MSIX to support delivery to AVD (via AppAttach), etc. 1. What is the roadmap for MSIX to improve the success rate of repackaging. 2. Will there be any automated conversion of Win32 apps in the store to MSIX (for admins to leverage).
Thanks for participating in today's session of AMA: Microsoft Store and Windows app management! For reference, the panel covered this topic at around 29:00.
