I'm trying to upgrade from UEM 9.3 to DEM 2009, for that i built a new image with
-Windows 10 1809
-Horizon View agent 10.1
-DEM Agent 2009
-App Volumes 2012
On the new image, i run the latest OSOT and disable the UAC.
My problem is that the privilege elevation is not working even if it's apply, and i'm still getting the UAC prompt.
Is there any special configuration to do in the image ? Or something to look at to know the real issue ?
Thanks for reply, I've tried with all the level of the UAC, from the lower to higher with no succes.
I've even tried to build a new environment for DEM 2009 with no succes.
Just want to add that with our production environment it's working fine (Windows 10 LTSB 1607, Horizon 7.10.1, UEM 9.3, App Volumes 2.18.1 and optimized with an old version of OSOT)
I'm really confused with that problem, any advice please?
I've made another test image but without optimizing with OSOT and the privilege elevation work fine, now remain to find the related registry key related to this behavior. do you think that osot disable something related to the UAC ?
I'm not sure; I vaguely recall something from a few years ago where an OSOT change to some UAC-related setting was causing issues with privilege elevation.
Can you compare the various User Account Control settings in Local Security Policy (secpol.msc | Security Settings | Local Policies | Security Options) on the working and non-working systems?
If you still have the OSOT that you used, check and see in the templates tab to see what it does, the newer ones have this
which is under the enable UAC setting
It may be worthwhile running the new osot against your image to see if it fixes it, but make sure you take a snapshot and test, since some of the older ones had different quirks you may have workaround.
You can't just uncheck them, when you check them they run actions that do something, which means it was already done. You need to revert the actual changes which takes some work, you need to see what they did and manually change them