Skip to main content

Question: How do you turn off User Access Control in Windows Server 2008?

User Access Control is the source of frustration for many, and a job savers for others. It is also the source of one of my favorite Mac vs. PC commercials. Windows Server 2008 has UAC built is, as does Vista which is the client for Server 2008. You can turn off UAC in the same fashion in Server 2008 as you can in Vista. I recommend against it though. UAC is a key feature of Windows 2008 security. There are ways to modify its behavior. First, how to turn it off.

To turn off UAC
1. Click Start, and then click Control Panel.
2. In Control Panel, click User Accounts.
3. In the User Accounts window, click User Accounts.
4. In the User Accounts tasks window, click Turn User Account Control on or off.
5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
7. Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window.


If you access your server with an account that is in the local Administrators group, you can change the default behavior of the UAC prompt from prompt for credentials, to the less annoying prompt for consent. Here is how it works.

• Click Start --> Administrator Tools --> Local Security Policy. (You can also do this through group policy.)
• Expand Local Policies --> Security Options.
• Open the properties for User Account Control: Behavior of the elevation prompt for Administrators in Admin Approval Mode.
• Here you can:
o Elevating without prompting (Not recommended, but it leaves UAC turned on for non-administrators).
o Prompt for credentials (You have to provide a username and password.
o Prompt for consent (You just click Continue).

Reference: http://technet.microsoft.com/en-us/library/cc709691.aspx#BKMK_S3

Class: 6421A Configuring and Troubleshooting a Windows Server 2008 Network Infrastructure

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .