Updating creator on Intune deployed laptops requires UAC elevation

[Acknowledge]

Hi,

I'd like some support regarding an issue we're experiencing.
we have deployed the PDF x-change creator application as a managed app through Intune. We've set this up with installationtype 'Microsoft Store app (new)' with the expectation that the app would be a UWP/MSIX version. This would make it possible that updates get pushed by the microsoft store, which makes our job easier.

We've noticed that Pdf X-change still needs UAC elevation when updates need to be installed. I've checked the installation and it appears that your app is a regular desktop app with it's own updates tool even when installed through the Microsoft store.

This leaves us in a bit of a predicament because the managed laptops don't have local admin rights. This means we have to manually put in the local admin credentials / Laps for all managed laptops.

I've read your intune deployement page, but it doesn't provide information about the updateprocess
https://help.pdf-xchange.com/sysadmin/i ... ntune.html

Is there a way to set this up so we can surpass the UAC elevation the applications own updater tool requests to update the app on the managed laptops? We can't be the only company using your tools in such a setup right?

Hope to hear from you guys, thanks in advance.

Cheers,
Ender Kulan

[Paul - PDF-XChange]

Hi, Acknowledge

I am afraid that you will need to run the updates as an elevated account, not the user account, yes. We do not offer an MSIS installer and there is no way to avoid the need to elevation.

You don't need to set up a special account to do this, just use the SYSTEM account.

[Acknowledge]

Thank you for responding.

Is there a registry entry we can deploy to the managed workplaces that would skip the whole update pop-up for the enduser?
We'd then just update the managed app version in Intune.

Cheers,
Ender

[Daniel - PDF-XChange]

Hello, Acknowledge

It would probably be better to install the software with the "/NOUPDATER" switch in your command line - so that the updater itself is not present in the first place.

https://help.pdf-xchange.com/sysadmin/u ... aller.html
https://help.pdf-xchange.com/pdfxp11/sw ... ers_p.html

Kind regards,