Project Server VME: Set up data exchange between the host computer and VME virtual machine
Applies to: Project Server 2010
Topic Last Modified: 2011-09-11
This article describes how to set up communication between the Project Server virtual migration environment (VME) host computer and the VME virtual machine. This allows you to transfer the Microsoft Office Project Server 2003 databases to the VME virtual machine for upgrading, and to transfer the upgraded Microsoft Office Project Server 2007 databases from the VME. If you have added the VME to you network, you will not have to do this procedure because you can simply create a shared folder in which you can copy and paste your databases. If the VME is not on your network, you have to run through the procedures in this article to create a virtual network in Hyper-V manager. This process establishes communication between the Windows Server 2008 R2 computer that is hosting the Project Server Virtual Migration virtual machine and the VME virtual machine. After establishing communication, see Load data to the Project Server VME for information about setting up the shared folder and transferring data to the VME virtual machine.
Important
The VME is only supported on Windows Server 2008 R2 by using the Hyper-V Manager feature. The VME does not run on Windows Server 2008.
This article describes one of several tasks required to configure your Hyper-V environment for the Project Server virtual migration environment. For more information about other tasks required to configure your Hyper-V environment, see Configure the Hyper-V environment for the Project Server VME. For more information about the VME, see Overview of the VME for Project Server 2010.
Create a virtual network
You can create a virtual network on the server running Hyper-V to provide communication between the virtualization server and virtual machines by creating an Internal Virtual Network. An Internal Virtual Network allows for communications between the virtual machines and the physical computer. After creating the Internal Virtual Network, you have to add a network adapter to the VME virtual machine.
The following procedures provide the basic instructions to create a virtual network in Hyper-V Manager.
To create an Internal Virtual Network
On the VM host computer, click Start, click Administrative Tools, and then click Hyper-V Manager.
On the Hyper-V Manager page, in the Actions pane, click Virtual Network Manager.
On the Virtual Network Manager page, in the Create virtual network section, in the What type of network you want to create? list, select Internal. Then click Add.
In the New Virtual Networks page, in the Name field, type a name for the new network. Review the other properties and modify them as necessary. Click OK to create the virtual network and close the Virtual Network Manager.
To add a network adapter to a virtual machine
Click Start, click Administrative Tools, and then click Hyper-V Manager.
On the Hyper-V Manager page, in the Virtual Machines list, select the virtual machine that you want to configure (ProjectVME).
Note
The virtual machine you select must not be in a Running state.
In the Actions pane, in the menu for the virtual machine that you selected, click Settings.
On the Settings page, in the Add Hardware section, choose a network adapter or a legacy network adapter. Network adapters can only be added to a virtual machine when the machine is turned off. (For more information about each type of adapter, see the Additional considerations section below.) Click Add.
In the Network Adapter section, from the Network drop-down list select the virtual network that you want to connect to.
In the MAC Address section, if you want to configure a static MAC address or virtual LAN identifier, specify the address or identifier that you want to use.
Click OK.
For more information, see the following blog post: Exchanging files between Parent and Child Partitions in Hyper-V (https://go.microsoft.com/fwlink/p/?LinkId=192759).
Additional considerations
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.
A legacy network adapter works without installing a virtual machine driver because the driver is already available on most operating systems. The legacy network adapter emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. A legacy network adapter also supports network-based installations because it includes the ability to boot to the Pre-Boot Execution Environment (PXE). The legacy network adapter is not supported in the 64-bit edition of Windows Server 2003 or the Windows XP Professional x64 Edition.
Important
Make sure to reboot your VME virtual machine after initial start. The reason you have to do this is that the operating system determines that the hardware you are running is different from the hardware on which the VME was created and last run, which requires a reboot.