Forum Discussion
Installation of new Win32 app to existing Intune Shared PCs not installing, but installs on rebuild.
Currently having an issue getting a new Win32 application deployed to existing Shared PCs.
We have 30 Win10 devices being used as shared PCs that were deployed with the shared multi-user device configuration profile using Self-Deploying mode. As they are being used by multiple different people, logon is via a local GUEST account with no user associated to them. There is another configuration profile that restricts logon only to this local account, with no company portal access.
There is a requirement to deploy a new application to these devices. A Win32 app (intuewin tool) was created (with install behavior set to System) and assigned to the dynamic group that the devices belong to. Detection method is using the existence of a registry key. This key is not there until the application is installed. Application does not get installed on these existing devices and just shows up as "Waiting for install status". It has now been over 5 days. Have rebooted the devices multiple times to restart the IME service and have the device check-in and still no joy.
Going through the IME log shows "AAD User check is failed" and "Failed to get AAD token" which is to be expected as it is using a local account. Have even tried leaving the machine at the Windows logon screen to see if the application would get installed using a device token with no luck.
The application gets installed for new builds of shared PCs and when doing a wipe and rebuild of current shared PCs, so the Win32 app and device assignment is all good. Besides assigning the application to the device group no other configuration changes were made to allow the application to be installed on new builds. It appears it is only an issue when assigning a new application to current shared PCs.
Anyone seeing the same behavior or know of a method of getting a new application on Shared PCs that are not assigned to a user? Doesn't seem right or a good way to do things, to have to wipe current machines to get a new application installed on them.
Thank you.
Have you tried to set the "SkipUserStatusPage" to enabled?
We had already a similar issue. As the "Account Setup" step has never been completed due to your construct of a shared device without user affinity, the "Intune Management Extension" is waiting (for ever) for this step to be accomplished before installing additional Win32 apps.You could try to deploy the following OMA-URI setting to your shared devices:
./Vendor/MSFT/DMClient/Provider/MS DM Server/FirstSyncStatus/SkipUserStatusPage
4 Replies
Have you tried to set the "SkipUserStatusPage" to enabled?
We had already a similar issue. As the "Account Setup" step has never been completed due to your construct of a shared device without user affinity, the "Intune Management Extension" is waiting (for ever) for this step to be accomplished before installing additional Win32 apps.You could try to deploy the following OMA-URI setting to your shared devices:
./Vendor/MSFT/DMClient/Provider/MS DM Server/FirstSyncStatus/SkipUserStatusPage
joel_grangier Thank you for response and the suggestion. We do have a "SkipUserStatusPage" configuration profile that we are using for our HAAD (non-Shared) deployments, but not our Shared PCs deployments. I will add that configuration profile to the Shared PCs and see how it goes.
The suggestion by joel_grangier to apply the "SkipUserStatusPage" CP to the Shared devices seems to be working. Once the CP was applied the new Win32 application began installing on the shared devices. Many thanks to joel_grangier
reggie_1968 : I think this a not supported
design. When you want to deploy software you have to use an add user with an license or you use an multi app kiosk pc with auto logon and kioskuser1.
