Connect to a Virtual Machine
Applies To: Windows Server 2008 R2
Virtual Machine Connection is a tool that you use to connect to a virtual machine so that you can install or interact with the guest operating system in a virtual machine. Some of the tasks that you can perform by using Virtual Machine Connection include the following:
Connect to the video output of a virtual machine
Control the state of a virtual machine
Take snapshots of a virtual machine
Modify the settings of a virtual machine
Before you begin
Virtual Machine Connection is installed automatically when you install the Hyper-V role on a full installation of Windows Server 2008. You also can install it separately on certain versions of Windows. For more information about installing Virtual Machine Connection, see http://go.microsoft.com/fwlink/?LinkId=143558.
By default, Virtual Machine Connection uses the same credentials you used to log on to your current Windows session to also establish a session to a running virtual machine. If you want Virtual Machine Connection to use a different set of credentials, you can configure Hyper-V so that you will be prompted for credentials. For instructions, see Configure Hyper-V.
Connect to a virtual machine
To connect to a virtual machine from Hyper-V Manager
Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.
In the results pane, under Virtual Machines, right-click the name of the virtual machine and click Connect.
The Virtual Machine Connection tool opens.
Tips for using Virtual Machine Connection
You may find the following tips to be helpful for using Virtual Machine Connection:
You can move the mouse pointer seamlessly between the operating system running on the physical computer and the guest operating system when integration services are installed on the guest operating system. Integration services are included with newer versions of supported Windows operating systems. For all other supported operating systems, install integration services in the guest operating system. For instructions about installing integration services, see Install a Guest Operating System. For a list of guest operating systems which integration services are available for, see the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkID=128037).
The mouse pointer may appear as a small dot when you connect to a running virtual machine. To send mouse clicks or keyboard input to the virtual machine, click anywhere in the virtual machine window. To return the input to the physical computer, press the mouse release key combination and then move the mouse pointer outside of the virtual machine window. The default release key combination is CTRL+ALT+LEFT arrow, but the key combination can be changed by modifying Hyper-V settings.
You cannot press CTRL+ALT+DELETE on the keyboard to send that key combination to a virtual machine. You can use the menu command. From the Action menu, click Ctrl+Alt+Delete. Or, you can press CTRL+ALT+END.
You can switch from a window mode to a full-screen mode. From the View menu, click Full Screen Mode. To switch back to window mode, press CTRL+ALT+BREAK.
By default, membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure. However, an administrator can use Authorization Manager to modify the authorization policy so that a user or group of users can complete this procedure. For more information, see Using Authorization Manager for Hyper-V Security (http://go.microsoft.com/fwlink/?LinkId=142886).
If an authorized user is connected to a virtual machine through Virtual Machine Connection and another authorized user decides to use the console of the same virtual machine, the session will be taken over by the second user and the first user will lose the session. This can pose a privacy and security risk, because the second user will be able to view the first user's desktop, documents, and applications. A virtual machine session is available to all users who have been granted the Console Read or Console Read/Write operations privilege in the authorization policy. By default, this is granted to any Administrator. To avoid or fix this issue, adjust the privileges to restrict access as appropriate.