Previous Topic: Windows 8 VDINext Topic: Windows Server 2012 VDS


Windows 7 VDI

You can create a VDI application by first creating a Windows 7 appliance WIN7y. Each template application includes a singleton with no boot volume. The boot volume is created using WIN7y.

The following VDI reference template applications are available:

Import the VDI Template Application

Follow these steps:

  1. Go to the Download Directory on the BFC server.

    For example, /opt/bfc/applogic-versions/<release number>.

  2. Copy the file VDI_WIN7<Edition>_r<Version>.tar file to the grid controller using the following command:
    scp VDI_WIN7<Edition>_r<Version>.tar <controller IP>:/vol/_impex/
    
  3. SSH to the grid controller and untar the file using the following command:
    tar -xf VDI_WIN7<Edition>_r<Version>.tar
    
  4. Import the application as follows:
    3t app import VDI_WIN7<Edition>_r<Version> VDI_WIN7<Edition>_r<Version>.tar
    

    You can create:

SCSI-based Windows Server Appliances

Follow these steps:

  1. Select the VDI template application.
  2. Open the application in the Infrastructure Editor. You must have full access rights to the application. For more information, see application modify_acl.
  3. Right-click the singleton and select Modify Boundary in the context menu.

    The Modify Boundary window displays.

  4. In General tab - Advanced section, click the Options button for Virtualization Modes, then select Device Schema as sda|sdb|sdc|sdd.
  5. Select the Volumes tab, then select the Boot volume device as sda.
  6. Click OK.

    The Infrastructure Editor displays.

  7. Save and close the application.

Create VDI Applications based on Windows 7

Each template application includes a singleton which is has no boot volume. The boot volume is created using WIN7y as a basis. Before creating a VDI application, you must first create the Windows 7 appliance WIN7y.

In WIN7y and VDI_Win7y_rX

You can verify the version for the platform and edition on the BFC server in /root/applogic/<release>. Perform an ls VDI* and locate the number after the r. For example, for the file VDI_Win7E_r17-1.2.4-1.tar, X would be 17.

Note: In all Windows VDI, the user name property must be different than the host name.

Follow these steps:

  1. Create a new singleton using WIN7y:
  2. If installing on a Windows 64-bit, verify the executable chcp.com exists in the C:\Windows\SysWOW64\ directory.

    If not, copy from C:\Windows\System32\ to C:\Windows\SysWOW64\ .

  3. Install the Windows VDS exe by downloading self-executing installer from the grid controller using the internal interface. This interface has been configured through DHCP.

    To locate the internal IP address of the controller, execute the following command in the Grid Shell. The IP address of the DHCP server is the last enumerated interface, such as Local Area Connection 5.

    ipconfig /all
    

    Point IE at http://IP-address:8080/download and download the current Windows VDS exe. For example: VDS_Windows-*.exe.

    Right-click the exe file and download the file to the desktop.

    To install, double-click the exe file.

    Delete the exe file and empty the Recycle Bin.

  4. Delete the junction points on Windows volumes as described in the Windows appliance WIN7y.
  5. Within SSH session Bash shell:
  6. Stop the application and copy the boot volume of the WIN7y singleton to the boot volume of the VDI_Win7y_rX application.

    For example:

    vol copy my-app:WIN7y.boot VDI_Win7y_rX:VDI_WIN7y.boot 
    

    The template application is now ready for use.

Note: When you provision a VDI_WIN7* application and log in to the graphic console, you should first log in as administrator. This causes the user configured in the login(graphic) window to display.