Chapter 04
Chapter 04
Chapter 4
W hen picking the poster child for the “327 Reasons We Hated Vista” list, I’ll bet
most folks put Vista’s User Account Control (UAC) at the very top. Vista’s UAC
manifested as a pop-up dialog box that seemed to appear every time you tried to do
anything on a Windows Vista system (Figure 4-1).
Figure 4-1
UAC in action.
Arrgh!
It’s too bad that UAC got such a bad rap. Not only is UAC an important security
update, but it is also a common feature in both Mac OS and Linux/Unix. Figure 4-2
shows the equivalent feature on a Mac.
Figure 4-2
UAC equivalent
on a Mac
If every other major operating system uses something like UAC, why was Microsoft
slammed so hard when they unveiled UAC in Windows Vista? The reason is simple:
Windows users are spoiled rotten, and, until UAC came along, the vast majority of users
had no idea how risky their computing behavior was.
The problem started years ago when Microsoft created the powerful NT file system
(NTFS). NTFS uses robust user accounts and enables fine control over how users access
files and folders—but at a cost: NTFS in its pure form is somewhat complicated. To share
a folder, you need to make sure the person accessing that folder has a user account and
that you’ve configured the NTFS permissions to give that user the permissions needed
to do whatever he or she wants to do (Figure 4-3).
Figure 4-3
Typically
confusing settings
for NTFS
permissions
User accounts have always been a bit of a challenge. The only account that can truly
do anything on a Windows system is the Administrator. Sure, you can configure a system
with groups and assign NTFS permissions to those groups—and this is commonly done
on large networks with a full-time IT staff—but what about small offices and home net-
works? These users almost never have the skill sets to deal with the complexities of users
and groups, which often results in systems where the user accounts are all assigned
Administrator privileges by default—and that’s when it gets dangerous (Figure 4-4).
This chapter discusses the importance of User Account Control and examines the
changes made to it for Windows 7. I’ll also explain how to configure UAC to your
desired security level.
Before Vista, Microsoft invented the idea of the Power Users group to give users
almost all of the power of an Administrator account (to handle most of the situations
just described) without actually giving users the full power of the account. Assigning a
user to the Power Users group still required someone who knew how to do this, how-
ever, so most folks at the small office/home level simply ignored the Power Users group
(Figure 4-5).
Figure 4-5 Power Users group—almost never used at the small office/home level
Clearly, Microsoft needed a better method to prevent people from running programs
that they should not run. If users have the correct privileges, however—or the ability to
“escalate” their privileges to that of an Administrator—then they should be able to do
what they need to do as simply as possible. Microsoft needed to make the following
changes:
l The idea of using an Administrator account for daily use needed to go away.
l Any level of account should be able to do anything as easily as possible.
l If a regular account wants to do something that requires Administrator privi-
leges, the user of the regular account will need to enter the Administrator
password.
l If a user with Administrator privileges wants to run something that requires
Administrator privileges, the user will not have to reenter his or her password,
UAC was just one part of an overall strategy to limit the number of Administrator
accounts on a system. The introduction of UAC coincided with two major changes in the
way new accounts were created. First, you only created an Administrator account dur-
ing the Windows installation process (normally). Windows disabled the Administrator
account by default. (You could also add regular users during the installation process.)
Second, all other accounts were plain, Standard user accounts by default (Figure 4-7),
simplifying your choices. You could still use the old Windows NT/2000/XP groups
(Power Users, Users, Guests, etc.), but you needed to dig deep into the User Accounts
Control Panel applet to access them.
Note All references to Control Panel applets in Windows Vista assume you
are using Classic View.
Figure 4-8
Prompting for a
password in Vista
Figure 4-9
Classic UAC
prompt
Tech Tip The official name for the UAC dialog box is the “UAC consent
prompt.” When the UAC consent prompt appears in Vista, the rest of the
Desktop darkens and you cannot take any other action until you respond to
the consent prompt.
Blocked programs generate a scary-looking, red-bannered dialog like the one shown
in Figure 4-10. Note the only button you can click is Close.
Figure 4-10
Blocked program
Unverified programs lack any form of certificate to validate. In this case, you get a
yellow-bannered dialog box warning you the application is unsigned and giving you
two options: allow the program to run (Yes) or not (No). See Figure 4-11 for an exam-
ple of this.
Figure 4-11
Unverified
program
Figure 4-12
Verified program
Published by Vista programs are written as part of the core of Vista and show up with
a teal-bannered dialog (Figure 4-13).
Figure 4-13
Published by Vista
UAC uses small shield icons to warn you ahead of time that it will prompt you
before certain tasks, as shown in Figure 4-14. Microsoft updated this somewhat redun-
dant feature in Windows 7, as you’ll soon see.
UAC gives users running a program an opportunity to consider their actions before
they move forward. It’s a good thing, but spoiled Windows users aren’t accustomed to
something that makes them consider their actions. As a result, one of the first things
everyone learned to do when Vista came out was how to turn off UAC.
1. In the User Accounts Control Panel applet, you’ll see an option to Turn User
Account Control on or off (Figure 4-15). Select this option and uncheck the
checkbox to turn UAC off. Check the checkbox to turn it on again.
UAC in Windows Vista worked well, but it startled users. Suddenly, users had to deal
with UAC, and they didn’t like that. Most users simply turned UAC off and added it to
the reasons to not like Windows Vista.
UAC in Windows 7
Microsoft may be a huge company, but it still knows how to react when its customers
speak out about features they don’t like. Windows 7 unveiled a more refined, less “in-
your-face” UAC that makes the feature much easier to use.
Note All references to Control Panel applets in Windows 7 assume you are
using the Small Icon view.
Microsoft changed UAC with Windows 7, enabling you to adjust the consent form
appearance to four different personal preference levels.
In Figure 4-18, you can see a slider with four levels. The top level (Always notify)
means you want UAC to work exactly as it does in Vista, displaying the aggressive con-
sent form every time you do anything that typically requires Administrator access. The
bottom option (Never notify) turns off UAC. The two levels in the middle are new and
are very similar. Both of them do the following:
The only difference is in how they show the change. The second-from-top level will
display the typical consent form, but only when programs try to make changes. The
third-from-top level displays a consent form, but where the normal consent form dims
your Desktop and doesn’t allow you to do anything but address the form, this consent
form just pops up like a normal dialog box.
Exam Tip Make sure you know what each of the four UAC levels does.
Figure 4-19
Darkened UAC
Figure 4-20
Non-darkened
UAC
Exam Tip The default behavior for UAC in Windows 7 is the second-from-
top option, which results in a screen similar to Figure 4-19.
A program such as the Adobe program described earlier is very different from a feature
you want to change. Notice the shields, as shown earlier in Figure 4-17.
Each of these options isn’t a program—each is merely a feature built into Windows.
Those shields tell you that clicking the feature next to a shield will require Administrator
privileges. If you were to pick the Vista-strength UAC option, you’d get a UAC consent
prompt when you click one of those features. If you set UAC to any of the three lower
settings, however, you’d go straight to that feature without any form of UAC consent
prompt. Of course, this isn’t true if you don’t have Administrator privileges. If you’re a
Standard user, you’ll still be prompted for a password, just as in Vista.
Overall, the improvements to UAC in Windows 7 show that it has a place on every-
one’s computer. UAC might cause an occasional surprise or irritation, but that one more
“Are you sure?” could mean the difference between safe and unsafe computing. So go
ahead, turn UAC back on in Windows 7! UAC is well worth the small inconvenience.
Chapter Review
Questions
1. Which file system uses permissions to secure files and folders?
a. FAT16
b. FAT32
c. UAC
d. NTFS
Review Answers
1. D. NTFS is a file system that uses permissions to secure files and folders.
2. A. In Windows XP, the default account type was Administrator.
3. A, C. UAC is intended to both warn users that their actions might have serious
consequences and give more power to Standard users without needing to make
them Administrators.
4. B. In Windows Vista, you can turn UAC on or off.
5. A. You can use MSCONFIG to turn UAC on and off.
6. B. One level creates a prompt that darkens the screen and blocks other actions,
whereas the other uses a normal dialog that does not block any actions.