Installing Windows Server 2012 Hyper-V

Windows Server 2012 Hyper-V server is essentially Windows Server 2012 Server Core that is designed in only run Hyper-V. You do not have to worry about purchasing a license for Hyper-V server. The Host OS is free. You do need to properly license any virtual machines (VMs) that you run on the Hyper-V server however.

Setup is a breeze. It was, for the most part, just like installing Server Core. It is also very fast. Just download the installation software from Microsoft. For this deployment, I plugged a keyboard, mouse , and monitor into my target server so I can observe all the action. Really, there is not much to watch once you get things started.

Once the server starts up, you need to give it a password for the local administrator account. Then SCONFIG opens up. Use SCONFIG with the following options to place this server in your domain and make it manageable.

8) Give this server a static IP address.

1) Add to the domain. You can also rename it with this option.

7) Allow remote desktop connections to this server.

At this point, you can unplug the monitor, keyboard, and mouse.

Once the Hyper-V server reboots, go ahead and configure either your Windows Server 2012 graphical server or Windows 8 client with RSAT to manage this server.

In Server Manager, click All Servers.

Right click All Servers and select Add Server.

In the name field, type the name of your Hyper-V Server and click Find Now.

Select your server from the list and click the right pointing arrow.

Click OK.

In a few minutes, your Hyper-V server will be manageable from your Server 2012 or Windows 8 client.

Open Hyper-V on your graphical client.

Right click Hyper-V Manager and select Connect to Server.

Type the name of your server and press Enter.

You can now manage the VMs running on this Hyper-V Server.

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 .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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...

Jason Yoder, MCT

Search This Blog