Skip to main content

Configuring settings for Hyper-V R2

Once the Hyper-V server has been installed, you can configure it. Open the Hyper-V Manager console.

 

Click Hyper-V Settings from the Actions pane.

 

There are two sections to the Hyper-V Settings, Server and User. The Server settings control the default locations for the VM files.

Keyboard Settings

 

clip_image002

 

This is where you decide when the “Window” key will be used on the host, and on the child. The default setting is to use it on the host, unless the VM is running in full-screen mode.

Mouse Release Key

 

clip_image004

 

For older operating systems, you may not be able to click in and outside the VM window as easily as you can for Windows 2008 and Windows 7 virtual machines. In that case, the mouse is captured and you will not be able to click on the host desktop. The Mouse Release Key is the key combination that you will use to release the mouse back to the parent operating system.

User Credentials

 

Click this if you want to use your login credentials to give you access to the desktops that are running in Hyper-V. This does not give you log in capability to the VMs. You still need to authenticate to use them. This just determines if you can even access them. If you are using Smart Cards for login, you will need to disable to feature and log in manually into Hyper-V

Delete Saved Credentials

 

clip_image006

 

This option allows for any saved credentials to be removed from Hyper-V. This will help to increase security.

Reset Check Boxes

 

This will reset Hyper-V confirmation and wizard pages back to their defaults.

You can also further configure the Hyper-V manager by determining which

elements are displayed. Click View \ Customize.

 

clip_image007

 

Checking and unchecking will show you live the results in the Hyper-V Manager window what is removed or added.

Comments

Popular posts from this blog

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