How to create and configure Virtual machine on Hyper-V?

I am knowing only about the virtualization products like Virtual PC or VMware Workstation. I want to know about the Hyper-V. I just came to know that there is no software to a host operating system runs on and with which you can also create and install VMs. This task is performed with Hyper-V Manager, which you install Windows Server can run locally on a full and Server Core remotely using it. So I am here mainly to know how to create and configure Virtual machine on Hyper-V? I am sure that you members will provide some helping solutions for me. Please help me as soon as possible. :notworthy

If you create the first VM to a newly established Hyper-V server, then the pull-down menu offers to configure network may only be the choice "not connected". The reason is that under Hyper-V still no virtual network was established, which could be assigned to the VM. Again, this process can be Hyper-V Manager from the handle, through the Virtual Network Manager in the right menu bar. There you can create a new virtual network and choose between types of "external", "internal" and "private". An external virtual network allows virtual machines to access the entire network, including Internet, if such a connection is available. The type "external" must always be tied to a physical network adapter (NIC), with only one external NIC per network is possible. If you need more, you must install additional NICs. Internal virtual networks connect the VMs on one server. They also allow communication between the host system and the guests in the VMs. Contrast, virtual private networks are even more restrictive by allowing no connection to the host.

"Connect Virtual Hard Drive" dialogue after the menu item offers the opportunity to create a VHD, are linked with an existing VM or postpone this operation later. Striking is that the Hyper-V Manager generates when creating a new virtual disk automatic dynamic VHD, although Microsoft recommends for the productive use of Hyper-V, the use of fixed-size VHD. If you would like to follow this advice, one must have a fixed VHD an external tools like diskpart to create and Hyper-V Manager, the VM link. When the Connect Virtual Hard Disks "In point of showing the Hyper-V Manager Installation Options" that booting an installation media from CD / DVD from an ISO file that allows PXE server or even from a virtual floppy. The latter can be with the Hyper-V Manager on action => => Create Disk New. The old media are still considered mainly because Windows Server 2003 requires for a full backup. If an ISO file to the remote management of Hyper-V on the client is, one could release the containing directory on the net and the VM can access it. For computers in workgroups that fails like to rights issues, so it is cheaper, the ISO file over a connection to the server to copy Remote Desktop.

Quote:

---

For computers in workgroups that fails like to rights issues, so it is cheaper, the ISO file over a connection to the server to copy Remote Desktop.
Edit/Delete Message

---

The Remote Desktop is used to remotely control remote PCs. Whose output is screen RDP to the local host transfer means, conversely, mouse movements and keystrokes go on this journey to the remote PC. However, it is often necessary to exchange files between the local client and the remote PC. By default, this option is disabled. The natural idea to have the Remote Desktop to run in a window, and copy files like the Virtual PC with CTRL + C and CTRL + V between the two computers does not work. Rather, it is necessary to make the local drive in the remote PC access. For this you have before starting the session in the client software to enable the appropriate setting. Then you can respond to the remote PC to local drives. Are you on the My Computer or Computer icon or the UNC path \\ tsclient \ [drive letter] \ [directory] (for example, \\ tsclient \ c \ program files) are accessible. Within the Remote Desktop can then transfer files between local and remote folders to copy as usual.

When you boot the newly created VM for the first time, then it starts from the specified installation media. In the Hyper-V Manager, you can see the progress of the startup process as a thumbnail. If you want access to an interactive installation on the screen of the VM, you can do it via the "Connect" from the context menu of the VM-entry. The Hyper-V Manager will then establish a RDP connection over which one of a normal Remote Desktop Connection can work with like. After successful installation of the guest operating system will be noted that this does not have network connectivity. The reason is that the wizard in the Hyper-V Manager when you create the VM set up any network adapter. This has to catch up after the passage of the wizard via the menu item "Add Hardware" under the settings of the VM. If there are for the guest, the so-called integration services, you should set it up first and then select the network adapter.

When the guest is installed and the VM is booted, you can add on the menu item installation disk load for integration services integration services. In newer versions of Windows you have to insert a disc, however, the necessary files are already on the disk. The integration services enable a closer alignment between hypervisor and guest operating systems. They include, inter alia, paravirtualized drivers for the hard disk and network access. Once in the host system is therefore a network adapter called Microsoft Virtual Machine Bus Network Adapter with before. Only now should be in the properties of the VM in hardware to add the points NIC choose. Older network card is suitable for all guests without Integration Services because it emulates a physical adapter.

Creating a new VM is configured with the Hyper-V Manager as easy as with desktop tools, such as the Virtual PC. An assistant passed through the procedure in which the settings are set for VMs. The very first steps in the designation of the VM and the entry of the directory path, followed by the allocation of memory. The integration services provide better performance in addition to the guest of useful additional features. They allow the shutdown of the guest in Hyper-V Manager, because the VM can initiate this action of the operating system. Without integration services, the OS would not be informed and to shut down the VM would act on it as pressing the reset button.