Skip to main content

Installing Windows Server 2012 Hyper-V

By

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.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
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...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more