Let’s say we face some special issues with intune.
We currently have 50 terminal windows kiosk pcs running win10 with our own appxbundle. I am quite new to the project and for me it’s quite hard to get into the intune stuff, because it’s not working properly.
The first issues occurred when updating our app about 2 weeks ago. There is a major issue our tests didn’t cover and we therefore needed to hotfix it asap. 3 days later we uploaded the fix to intune.
It’s been 2 weeks now and 20-25% of our terminals haven’t received an update. And here it goes. I tried really everything to update the 5-10 stations to the newest version. At first I started with simply syncing them with intune. 6-24h later, ok still no update there, maybe let’s do a restart. 24ish hours later still no update, let’s dis- and reconnect to intune. Still old version. But newest version is in WindowsApps, kiosk mode simply doesn’t choose it.
The only kinda consistent way for now was re-installing windows. But that’s currently not possible remotely and therefore super annoying and not scalable for the future (we want to have 1000 terminals next year).
My questions are:
Are there any real solutions for not only installing the appxbundle with the current version on the terminals, but also specifying them for the kioskuser? I realize that intune is creating new kioskusers along the way, but it simply chooses the wrong version. Even when choosing the correct version in the first place, it sometimes resets to the old version some device restarts later.
What is the best revert-update strategy? When uploading the appxbundle there is simply no guarantee to ever get an update. Whatever you do manually.
I am in contact in parallel with microsoft support, but they want to take a look into the special devices 1 by 1. I assume it will take long time.
Maybe I get some idea of how to fix the consistency issues in our system.
I tried:
- re-connecting intune
- multiple restarts
- restarts/manual sync after days
- new configuration with only specific new app version instead of updating -> old kiosk user is chosen
- contact microsoft support -> “they will take a look into it”
- manual AppxPackage register, but this only applies to logged in user -> no login for kiosk user available
m_dev is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.