A.3 Microsoft Windows Server 2012 R2 Hyper-V

To install the Corente Gateway Software on Windows Server 2012 R2 Hyper-V, complete the following steps:

  1. Begin by downloading the new Corente Virtual Services Gateway’s configuration file to your computer’s hard drive via App Net Manager. Copy the org.xml file to a virtual floppy image. This can be done using WinImage or another similar tool.

  2. Next, open Hyper-V Manager and create a new Virtual Machine. This will open a wizard that will guide you through the steps of creating a new VM. After specifying the name and location of your new Corente Virtual Services Gateway VM, complete the next screens as follows:

    1. Specify Generation: Select Generation 1 and click Next.

      Figure A.35 Specify Generation

      This screenshot shows how to select a virtual machine generation to the new virtual machine in Hyper-V Manager.

    2. Assign Memory: Allocate 1 GB for the VM’s memory and click Next.

      Figure A.36 Assign Memory

      This screenshot shows how to allocate memory to the new virtual machine in Hyper-V Manager.

    3. Configure Networking: Select appropiate network adapter/s and click Next.

      Figure A.37 Configure Networking

      This screenshot shows how to configure networking for the new virtual machine in Hyper-V Manager.

    4. Connect Virtual Hard Disk: Select Create a Virtual Hard Disk and provide it with a name. If you would like, change the default path where the disk will be stored. Allocate 40 GB to the hard disk and click Next.

      Figure A.38 Connect Virtual Hard Disk

      This screenshot shows how to create a virtual hard disk and add it to the new virtual machine in Hyper-V Manager.

    5. Installation Options: Choose Install an operating system from a boot CD/DVD-ROM. Under Media, select Image file (.iso). Browse or enter the path to the Corente Gateway Software .iso file that you downloaded to your hard drive. Click Finish.

      Figure A.39 Installation Options

      This screenshot shows how to install an operating system on the new virtual machine in Hyper-V Manager with Install an operating system from a boot CD/DVD-ROM selected.

  3. Your new VM has been created. Edit its settings by right-clicking its name under the Virtual Machines heading and selecting Settings….

    Figure A.40 Edit Virtual Machine Settings


  4. On the left side of the window that is displayed, select Network Adapter. On the screen that is displayed, click the Remove button to remove the Network Adapter.


  5. Now select Add Hardware on the right side of the window. Select Legacy Network Adapter from the list and click Add. Make sure Local Area Connection – Virtual Network is selected when you add.

    If you are creating a VM in the Inline configuration, repeat step 5 to add a second Legacy Network Adapter to the VM. (Peer configuration uses one adapter; Inline configuration uses two.)

    Select OK when you are done to save your changes.

    Figure A.42 Add Legacy Network Adapter


  6. When you are finished adding the network adapter(s), edit the Hyper-V Virtual Network Manager Settings. On the left side of the window that is displayed, select Local Area Connection – Virtual Network. On the screen that is displayed, under the Connection Type heading, select External and then select the desired physical interface (repeat for all NICs). If you added a second legacy network adapter (for an Inline configuration), repeat step 6 to bind that adapter to the appropriate physical interface. Click OK when you are finished.

    Figure A.43 Edit Manager Hyper-V Settings


  7. Finally, install the Corente Gateway Software. Begin by bringing up the console for the Corente virtual machine. Right-click the name of the VM and select Connect….

  8. On the console, make sure that the .iso file for the Corente Gateway Software is attached and set as the virtual disc in the virtual machine’s CD drive. Select Media from the options at the top of the window, then highlight DVD Drive. If there is no option to eject the Corente Gateway Software .iso file, then select Insert Disk to point to the location of the .iso file.

    Figure A.44 Attach .iso file

    This screenshot shows the console installation screen with the .iso file for the Corente Gateway Software attached in the CD drive of the virtual machine in Hyper-V Manager.

  9. Next, make sure that the floppy image is not connected. Select Media from the options at the top of the window, then highlight Diskette Drive. There should be no disk listed.

    Figure A.45 No Floppy Inserted

    This screenshot shows the console installation screen with the diskette drive empty for the new virtual machine in Hyper-V Manager.

  10. Power on the virtual machine and proceed with the installation of the Corente Gateway Software, which will start automatically.

  11. Hit Enter to reboot when prompted.

    Figure A.46 Reboot Virtual Machine

    This screenshot shows that the virtual machine must be rebooted after Corente Gateway Software installation.

  12. Once the VM has booted, you will be prompted for a configuration file. Select Media from the options at the top of the window, then highlight Diskette Drive, then select Insert Disk. Point to the virtual floppy image containing the new gateway’s org.xml configuration file that you downloaded to your hard drive in Step 1.

    Figure A.47 Download Configuration File

    This screenshot shows how to point to the previously downloaded configuration file to continue the setup of the virtual machine in Hyper-V Manager.

  13. Complete the network information on this screen. For the Download site, enter www.corente.com. Select Next and hit Enter.

    Figure A.48 Provide Network Configuration

    This screenshot shows the Network Information to be provided for the gateway configuration.

  14. Once the configuration file has been installed, eject the virtual floppy.

A.3.1 Specifications

The following features are not supported when running the Corente Gateway Software on Hyper-V:

  • Installation via a USB flash drive

  • Configuration via a USB flash drive

  • Hardware failover