What issues might we run into enabling UAC when we start our migration to Windows 10?
We're starting to prepare for Windows 10. One of the things we've
done in Windows 7 is to disable UAC through AD policy. This seems to be
problematic in Windows 10 because of the Windows Store apps - users
can't access silly things like their calculator with UAC disabled. I
don't have my hands in AD, so I don't know if there is a better way to
resolve this, but if we re-enable UAC, what do I need to know/watch out
for with my KACE appliances? I've found some individual articles with
little references to UAC, (example here) but nothing compiled... any help?
another possibility is looking into the various options of automated Win 10 readiness checks. This *is not* a silver bullet, but will however give you a very good heads-up on possible issues that various applications that you run might have. We offer such a solution which you can have a look at here...
I can't comment on your answer, so I'll have to open a new answer...
You can "wrap" appx-apps in MSI's for machine deployment (our tool does this) AFAIK SCCM does this as well to allow deployment per machine as well. You can also go down the "hard way" and wrap them in power-shell. Did you see my comment about sending you a pdf document?
UAC is not just about restricting access to certain things, or pseudo "hardening" of the OS, but also affects things like how an application works in regards to the file and registry system due to the pseudo virtualisation. You'd have to ensure that your current Win7 apps work with UAC enabled on your current OS before migrating and that's just the tip of the iceberg. Could you be a bit more precise on what specific aspects you are looking at? Just the deplyoment of the OS, standard settings, windows store (appx) apps etc.