|
Stage 1) Preliminary task: Our first task is simply to launch the Local Security Policy snap-in. You have the choice of two methods: Method A) Begin by clicking on Vista's Start button, then type secpol.msc in the Start Search dialog box. Note: you must include the .msc extension. Method B) Display Vista's Administrative Tools. Right click the Taskbar, select Properties, Start Menu, Customize, Advanced; scroll to the bottom and find System Administration Tools, place the radio button next to 'Display on the All Programs menu'.
Stage 2) Configure the Security Options - Open the Local Security Policy (See Method A or B above)
- Expand the Local Polices Folder See the screenshot opposite.
- Drill down to Security Options folder.
- Scroll down, and locate the family of settings beginning with 'User Account Control'.
- Focus on: User Account Control: Behaviour elevation prompt for administrator. Double click and set to: Elevate without prompting. Check the screenshot to the right.
 - Restart you Vista computer.
- When the computer restarts, try to configure a tasks that needs UAC. For example, change the computer's display name. Press the Windows Key + Pause / Break. Select the 'Change Settings' shield..
- UAC should now be turned off, thus you should not see the 'Continue' box.

Run all administrators in Admin Approval ModeThere is an alternative, if inferior, method of turning off UAC, that is by disabling the Local Policy, Security Option: 'Run all administrators in Admin Approval Mode'. Double click and set to 'Disabled'. Unlike the Elevate without prompting technique, this method turns off UAC and compromises security. My advice is leave this setting as Enabled, and focus on the above setting: User Account Control: Behaviour elevation prompt for administrator. Guy Recommends: SolarWinds Engineer's Toolset v10 The Engineer's Toolset v10 provides a comprehensive console of utilities for troubleshooting computer problems. Guy says it helps me monitor what's occurring on the network, and the tools teach me more about how the system itself operates. There are so many good gadgets, it's like having free rein of a sweetshop. Thankfully the utilities are displayed logically: monitoring, discovery, diagnostic, and Cisco tools. Download your copy of the Engineer's Toolset v 10 Other User Account Control (UAC) SettingsAs you can see in the above screenshot, there are more server policies for the UAC. However, they are less important and control specialist situations, for example, installing applications. User Account Control: Detect application installations and prompt for elevation. For home users, the default is Enabled, meaning home users get a UAC dialog box. However, for domain users this UAC is disabled so that installation can proceed silently. There are similar UAC Policy settings for Users rather than Administrators. Only elevate UIAccess applications that are installed in secure locationsThe idea behind this policy is that Vista will only give UIAccess privileges and user rights to executables that are launched from %ProgramFiles% or %windir%. The permissions are set on these directories to ensure that the executable is not user-modifiable (which would otherwise allow elevation of privilege). Registry Change to User Account ControlGroup Policy settings ultimately work by changing the registry settings. It follows that you could edit the registry directly rather than configure through the Local Policy GUI. When you are learning and if there is a GUI, that is always the best place to start. However, there may be occasions when you need to go to the registry, for example to create a .Reg file. If you would like to examine the key UAC registry settings, then See more about ConsentPromptBehavior here. One of the underlying computer dilemmas is productivity versus security. If Microsoft make UAC too difficult, then Administrator's will investigate registry hacks that make their jobs easier, even if easier means a less secure environment. On my test network I move the imaginary productivity -v- security slider to ease of use, whereas for customers, I move the same slider over to more secure settings. Disable the UAC - Method for Non-domain UsersIn the case of Vista Machines which are not joined to a domain, Microsoft provide a menu in the Control Panel whereby you can turn UAC off. What can I say? You should not use this setting? That would be hypocritical; as someone who loves AutoAdminLogon for non production machines, then unsurprisingly, Guy will uncheck the box 'Use User Account Control...' If you would like to turn off UAC, then navigate to: - Control Panel -> User Accounts ->
- Turn User Account Control On or Off.
- Now decide if you want to untick the box which say: 'Use User Account Control (UAC) to help protect your computer'.
- Now you have disabled the User Account Control.
As I often say, my role is to show you the settings and help you to make informed decisions. In this instance your decision is this: does the security risk outweigh the irritation of having to click 'Continue' every time you wish to perform an administrative task? CMD Prompt - Run as Administrator My problem occurred when I wanted to run the command: ipconfig /release. What I received was this error message: 'The requested operation requires elevation'. Fortunately, the solution was easy; as you can see from the screen shot to the right, just right click the Command Prompt and select Run as administrator from the shortcut menu. As a result I was allowed to run ipconfig /release. There was no irritating: 'The requested operation requires elevation'. An Even Better Solution - Tick Advance BoxWhen you have found a good move in chess or bridge, always look for a better one. Applying this principle to the CMD prompt: Right-click the command prompt icon, Properties Select the Shortcut (tab) Click on Advanced (button) Tick: Run as administrator (See screen shot) |