How to open the firewall on Server Core R2 to Hyper-V management

Server core is an excellent platform to host your Hyper-V environment. With the removal of the GUI, you lose potential attack vectors and gain more hardware resources that would otherwise be consumed in supporting the GUI. Below are the steps to install Hyper-V on server core and manage it.

Once we have confirmed that our Server Core can communicate on the network, add the Hyper-V role

Type Start /w ocsetup Microsoft-Hyper-V and press Enter. The command is case sensitive.

When prompted, click Yes.

After the reboot, enable remote administration by entering this line:

netsh advfirewall firewall set rule group=“Windows Management Instrumentation (WMI)” new enable=yes

If you are running Server Core R2, you can use the SConfig command.

Type Sconfig and press Enter

Select option 4

Select option 1

At this point, you should be able to use a Windows 7 machine with RSAT installed to remotely manage your Hyper-V environment.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.

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