Why have the Aero interface in Windows Server 2008?

That is a good question. Why would you need all that 3D eye candy and tie up funds in a video card that can run the aero experience? I have two reasons why.

The first reason is that some users may use Windows Server 2008 as there desktop. Yes, I have seen it. The second reason is that some users may connect via a terminal session. By enabling the “Desktop Experience” feature, as it is known in Server 2008, you are making the Aero experience available.

This also makes available the built in applications of Windows Vista. This includes such programs as Windows Calendar, Sync Center and Media Player.

To enable the Desktop Experience:
• Open the Server Manager.
• Click Features
• Right click Features and select Add Feature
• Check Desktop Experience.
• Click Next.
• Click Install.
• Allow the server to reboot.
• The shutdown may take a few minutes.
• The Resuming Configuration window may be active for a few minutes befor confirming the installation.
• Close Server Manager.
• Click Start
• Type Services.msc and press Enter.
• Right click the Themes service and select the Startup Type: to Automatic.
• Click OK.
• Right Click the Themes service and click Start.
• Right click the desktop and select Personalize.
• Click Theme.
• In the Theme drop down menu, select Vista Theme.
• Click OK.
• Wait for a few moments and the Vista look and feel will become your interface.

On a trouble shooting note, you may still not get all of the Aero experience. If this is the case, download the Vista drivers for your video card. Not all the necessary drivers may be shipped with Server 2008.

Comments

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 .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

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.

Jason Yoder, MCT

Search This Blog