Hi All,
When viewing a newer updated version of the App package via the company portal user side, naturally The app states "install" as the available button instead of "uninstall". I understand this to be caused by this instance of the Intune package never being targeted to the device or installed by the users. Only an older no longer assigned package version.
But is there some mechanism that could cause the button to re-evaluate and state "uninstall" instead?
Such that when a user is looking at their apps list all Apps that are installed will report as such?
Currently if a user wants to opt out and uninstall the app they are first having to install, sync Company portal, then uninstall. Its a little cumbersome.
When you set an app as "Available," this is the expected behavior. Once a new version is released by the vendor, the version information in the detection method (which uses a PowerShell script) will be updated. As a result, the newly deployed app will not be detected on the system, and you'll see the app listed in the "Install" status in the Company Portal.
Once the "Install" button is clicked, the app will update (or install) to the latest version, after which the "Uninstall" button will appear.
Alternatively, you can deploy an update-only package to the devices. After the update completes, you should see the "Uninstall" button once the detection process is invoked.
For more information, you can refer to the following article:
https://patchmypc.com/intune-win32app-allow-available-uninstall
Sorry i should have clarified.
Update packages have already been deployed.
App packages have already been deployed as available.
So it is the App package, that the user for this version has not yet interacted with... That is appearing as "install".
So the app was initially installed by the user say with AppV1.
UpdateV2 goes out and installed.
AppV1 is no longer allocated to the user.
AppV2 is allocated as available.
AppV2 appears in the company portal with the "install" button" even though UpdateV2 installed previously.
Hello,
I believe I understand the end result that you are looking for, unfortunately I do not think that is something we can set, as what you are seeing is Intune functioning as expected. When a new application is deployed to a device as available, the app detection portion is not ran until the "Install" button is clicked. In fact, not even requirement rules are ran until the "Install" button is clicked. Unfortunately, there isn't a way to tell Intune to run detection on an available app without clicking the install button in the first place.
Thank you both for your time and confirmation. I suspected that this was going to be the result but thought I'd double check.