At Microsoft, we dog-food just about every product that is in the pike of development and testing as it "travels" the roads to getting ready to ship. The objective of this process is to use our own products, identify UX, and help improve the product before it goes out to public. Dog-Fooding is a very religious process inside Microsoft and tons of effort goes into making this - what happens to be one of the most critical stages in our product development cycle.

User Account Control - UAC, is one of those very important features we have baked into the Windows Vista platform. It is the way to improving the security UX on our platform and changing how our users are "protected" from various security related issues we have been hit with in the past (and more).

I recieve a lot of questions from people outside Microsoft asking, "why are we going thru this pain of UAC" and, "How can I turn this thing off".

Well, there’s definitely a “clean” technical way to doing this via the local group policy in the platoform. But, Microsoft wants our users to think the the bigger picture and ask the question whether it really calls for to turn it off or leave it on. We all realize, security is a “painful “ background (and some times invoking user interaction) process that get’s in our way. That is the "nature of the beast" - and that's the reason why companies and people are spending such a big chunk of their cycles on this hot issue.

From a big picture “MSFT’s Direction on Security” standpoint, UAC plays a significant role in improving our platform and the behavior of how our users benefit from adopting Vista.

I’d leave it on – on all of my day-today dog fooding.

Why? Read Jesper’s blog – because, he’s right on with what he’s to say about UAC and Why it makes sense to keep it ON.

https://blogs.technet.com/jesper_johansson/archive/2006/06/22/438316.aspx

caio
Nagi