Event details
Jason_Sandys
Microsoft
MicrosoftWith the store for business and education set to be retired, so is the functionality in ConfigMgr that connects to it (it'll stop working when the store for bus/ed is retired no matter what). To take advantage of the new integration that we are building, the best path is to attach your ConfigMgr site to Intune using co-management or fully move to Intune (whichever you prefer). Intune is our clear path for adding cloud value and capabilities to our Windows management ecosystem and this is clearly about the cloud. From a business perspective, it does not make sense for us to add the same functionality to both tools particularly when co-management exists and we strongly encourage customers to adopt cloud-attach in ConfigMgr (and have for a number of years now).
Hi Jason,
Do the WinGet scripts work if the MS Store is disabled?
We are in a similar situation as Paul, however we are co-managing our devices with Intune. My question is around getting the Company Portal installed on the user machines when they are starting from an OnPrem environment. We used to do this using the ConfigMgr Windows Store integration, but I understand that is being depreciated. So now, I would assume we would use WinGet with a script to install the Company Portal first, then we can proceed with using Intune to deploy Store Apps (as they will now show up for the end user in Company Portal). The problem is that we will be disabling the MS Store all together for our devices, for obvious reasons, we do not want our users to be able to install whatever they want from the store at any time. But with the store disabled, will the Windows Package Manager (WinGet) still be able to install apps that we approve? Of course to be able to direct people to the Company Portal, we need to first figure out how to install the Company Portal.
Thanks.