Difference between revisions of "VMware: vSphere 5.1 VDI"

From Define Wiki
Jump to navigation Jump to search
(Created page with "== Install VMware ESXi Hypervisor == * Install the VMware ESXi Hypervisor from ISO (or network deployment) to a bare metal system. '''NB:''' Very little user interaction is re...")
 
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Install VMware ESXi Hypervisor ==
 
== Install VMware ESXi Hypervisor ==
−
* Install the VMware ESXi Hypervisor from ISO (or network deployment) to a bare metal system.
+
* Install the VMware ESXi Hypervisor from ISO (or network deployment) to a bare metal system. Very little user interaction is required during the installation. Only basic info will be requested:
−
'''NB:''' Very little user interaction is required during the installation. Only basic info will be requested:
 
 
** Disk to use for installation
 
** Disk to use for installation
 
** Password
 
** Password
  
 
== Manage with vSphere Client ==
 
== Manage with vSphere Client ==
−
* Download and install the '''vSphere Client''' for Windows (Mac and Linux versions not available at the time of writing)
+
* Download and install the '''vSphere Client''' for Windows (Mac and Linux versions not available at the time of writing) and install on a workstation.
 
* Open '''vSphere Client''' and enter:
 
* Open '''vSphere Client''' and enter:
−
** '''IP Address''' of '''ESXi''' server
+
** '''IP Address''' of '''ESXi Server'''
 
** '''Username''' of '''root'''
 
** '''Username''' of '''root'''
−
** '''Password''' as defined during the install of ESXi server
+
** '''Password''' as defined during the install of '''ESXi server'''
  
 
== Enable SSH ==
 
== Enable SSH ==
 +
* Within '''vSphere Client''' select the '''ESXi server''' from the tree list on the left pane
 +
* In the right pane, select '''Configuration''' tab
 +
* Select '''Security Profile''' under the '''Software section'''
 +
* Under '''Services''', click '''Properties...'''
 +
* From the list of services, select '''SSH''' and click the '''Options''' button
 +
* Click '''Start'''
 +
* Select '''Start and stop with host''' and click '''OK'''
 +
* Click '''OK''' to save and close the '''Services Properties''' dialog box
 +
 +
== Install nVidia GRID drivers ==
 +
* Download the nVidia '''VIB''' driver package for VMware/vSphere from the nVidia website.
 +
* Copy the driver to the ESXi system
 +
<syntaxhighlight>
 +
Jons-MacBook-Air: Jon$ scp NVIDIA-VMware-304.76-1OEM.510.0.0.802205.x86_64.vib root@10.50.0.0:/tmp/
 +
</syntaxhighlight>
 +
* Connect the '''ESXi Server''' using '''SSH''' and the root user:
 +
<syntaxhighlight>
 +
Jons-MacBook-Air: Jon$ ssh root@10.50.0.0
 +
</syntaxhighlight>
 +
* Enter '''Maintenance Mode''':
 +
<syntaxhighlight>
 +
/tmp # vim-cmd hostsvc/maintenance_mode_enter
 +
'vim.Task:haTask-ha-host-vim.HostSystem.enterMaintenanceMode-369681837'
 +
</syntaxhighlight>
 +
* Install the '''VIB''' driver:
 +
<syntaxhighlight>
 +
/tmp # esxcli software vib install -v /tmp/NVIDIA-VMware-304.76-1OEM.510.0.0.802
 +
205.x86_64.vib
 +
Installation Result
 +
  Message: Operation finished successfully.
 +
  Reboot Required: false
 +
  VIBs Installed: NVIDIA_bootbank_NVIDIA-VMware_ESXi_5.1_Host_Driver_304.76-1OEM.510.0.0.802205
 +
  VIBs Removed:
 +
  VIBs Skipped:
 +
</syntaxhighlight>
 +
* Confirm the driver is installed:
 +
<syntaxhighlight>
 +
/tmp # esxcli software vib list | grep NVIDIA
 +
NVIDIA-VMware_ESXi_5.1_Host_Driver  304.76-1OEM.510.0.0.802205          NVIDIA  VMwareAccepted    2013-04-23
 +
</syntaxhighlight>
 +
* Verify the nVidia module loads:
 +
<syntaxhighlight>
 +
/tmp # esxcli system module load --module nvidia
 +
</syntaxhighlight>
 +
* Verify the devices are present:
 +
<syntaxhighlight>
 +
/tmp # esxcli hardware pci list -c 0x300 -m 0xff
 +
000:004:00.0
 +
  Address: 000:004:00.0
 +
  Segment: 0x0000
 +
  Bus: 0x04
 +
  Slot: 0x00
 +
  Function: 0x00
 +
  VMkernel Name:
 +
  Vendor Name: NVIDIA Corporation
 +
  Device Name: NVIDIAGRID K2
 +
  Configured Owner: Unknown
 +
  Current Owner: VMkernel
 +
  Vendor ID: 0x10de
 +
  Device ID: 0x11bf
 +
  SubVendor ID: 0x10de
 +
  SubDevice ID: 0x100a
 +
  Device Class: 0x0300
 +
  Device Class Name: VGA compatible controller
 +
  Programming Interface: 0x00
 +
  Revision ID: 0xa1
 +
  Interrupt Line: 0x0b
 +
  IRQ: 11
 +
  Interrupt Vector: 0xb0
 +
  PCI Pin: 0x00
 +
  Spawned Bus: 0x00
 +
  Flags: 0x0201
 +
  Module ID: -1
 +
  Module Name: None
 +
  Chassis: 0
 +
  Physical Slot: 8
 +
  Slot Description:
 +
  Passthru Capable: true
 +
  Parent Device: PCI 0:3:8:0
 +
  Dependent Device: PCI 0:3:8:0
 +
  Reset Method: Bridge reset
 +
  FPT Sharable: true
 +
 +
000:005:00.0
 +
  Address: 000:005:00.0
 +
  Segment: 0x0000
 +
  Bus: 0x05
 +
  Slot: 0x00
 +
  Function: 0x00
 +
  VMkernel Name:
 +
  Vendor Name: NVIDIA Corporation
 +
  Device Name: NVIDIAGRID K2
 +
  Configured Owner: Unknown
 +
  Current Owner: VMkernel
 +
  Vendor ID: 0x10de
 +
  Device ID: 0x11bf
 +
  SubVendor ID: 0x10de
 +
  SubDevice ID: 0x100a
 +
  Device Class: 0x0300
 +
  Device Class Name: VGA compatible controller
 +
  Programming Interface: 0x00
 +
  Revision ID: 0xa1
 +
  Interrupt Line: 0x0b
 +
  IRQ: 11
 +
  Interrupt Vector: 0xb0
 +
  PCI Pin: 0x00
 +
  Spawned Bus: 0x00
 +
  Flags: 0x0201
 +
  Module ID: -1
 +
  Module Name: None
 +
  Chassis: 0
 +
  Physical Slot: 16
 +
  Slot Description:
 +
  Passthru Capable: true
 +
  Parent Device: PCI 0:3:16:0
 +
  Dependent Device: PCI 0:3:16:0
 +
  Reset Method: Bridge reset
 +
  FPT Sharable: true
 +
 +
000:008:03.0
 +
  Address: 000:008:03.0
 +
  Segment: 0x0000
 +
  Bus: 0x08
 +
  Slot: 0x03
 +
  Function: 0x00
 +
  VMkernel Name:
 +
  Vendor Name: Matrox Graphics, Inc.
 +
  Device Name: MGA G200eW WPCM450
 +
  Configured Owner: Unknown
 +
  Current Owner: VMkernel
 +
  Vendor ID: 0x102b
 +
  Device ID: 0x0532
 +
  SubVendor ID: 0x15d9
 +
  SubDevice ID: 0x0662
 +
  Device Class: 0x0300
 +
  Device Class Name: VGA compatible controller
 +
  Programming Interface: 0x00
 +
  Revision ID: 0x0a
 +
  Interrupt Line: 0x0b
 +
  IRQ: 11
 +
  Interrupt Vector: 0xa0
 +
  PCI Pin: 0x00
 +
  Spawned Bus: 0x00
 +
  Flags: 0x0221
 +
  Module ID: -1
 +
  Module Name: None
 +
  Chassis: 0
 +
  Physical Slot: 0
 +
  Slot Description:
 +
  Passthru Capable: true
 +
  Parent Device: PCI 0:0:30:0
 +
  Dependent Device: PCI 0:0:30:0
 +
  Reset Method: Bridge reset
 +
  FPT Sharable: true
 +
 +
000:086:00.0
 +
  Address: 000:086:00.0
 +
  Segment: 0x0000
 +
  Bus: 0x86
 +
  Slot: 0x00
 +
  Function: 0x00
 +
  VMkernel Name:
 +
  Vendor Name: NVIDIA Corporation
 +
  Device Name: NVIDIAGRID K2
 +
  Configured Owner: Unknown
 +
  Current Owner: VMkernel
 +
  Vendor ID: 0x10de
 +
  Device ID: 0x11bf
 +
  SubVendor ID: 0x10de
 +
  SubDevice ID: 0x100d
 +
  Device Class: 0x0300
 +
  Device Class Name: VGA compatible controller
 +
  Programming Interface: 0x00
 +
  Revision ID: 0xa1
 +
  Interrupt Line: 0x0b
 +
  IRQ: 11
 +
  Interrupt Vector: 0x41
 +
  PCI Pin: 0x6f
 +
  Spawned Bus: 0x00
 +
  Flags: 0x0201
 +
  Module ID: -1
 +
  Module Name: None
 +
  Chassis: 0
 +
  Physical Slot: 8
 +
  Slot Description:
 +
  Passthru Capable: true
 +
  Parent Device: PCI 0:133:8:0
 +
  Dependent Device: PCI 0:133:8:0
 +
  Reset Method: Bridge reset
 +
  FPT Sharable: true
 +
 +
000:087:00.0
 +
  Address: 000:087:00.0
 +
  Segment: 0x0000
 +
  Bus: 0x87
 +
  Slot: 0x00
 +
  Function: 0x00
 +
  VMkernel Name:
 +
  Vendor Name: NVIDIA Corporation
 +
  Device Name: NVIDIAGRID K2
 +
  Configured Owner: Unknown
 +
  Current Owner: VMkernel
 +
  Vendor ID: 0x10de
 +
  Device ID: 0x11bf
 +
  SubVendor ID: 0x10de
 +
  SubDevice ID: 0x100d
 +
  Device Class: 0x0300
 +
  Device Class Name: VGA compatible controller
 +
  Programming Interface: 0x00
 +
  Revision ID: 0xa1
 +
  Interrupt Line: 0x0b
 +
  IRQ: 11
 +
  Interrupt Vector: 0x41
 +
  PCI Pin: 0x20
 +
  Spawned Bus: 0x00
 +
  Flags: 0x0201
 +
  Module ID: -1
 +
  Module Name: None
 +
  Chassis: 0
 +
  Physical Slot: 16
 +
  Slot Description:
 +
  Passthru Capable: true
 +
  Parent Device: PCI 0:133:16:0
 +
  Dependent Device: PCI 0:133:16:0
 +
  Reset Method: Bridge reset
 +
  FPT Sharable: true
 +
</syntaxhighlight>
 +
* Exit '''Maintenance Mode''':
 +
<syntaxhighlight>
 +
/tmp # vim-cmd hostsvc/maintenance_mode_exit
 +
'vim.Task:haTask-ha-host-vim.HostSystem.exitMaintenanceMode-369681914'
 +
</syntaxhighlight>
 +
* End the SSH session.
 +
* Reboot the '''ESXi Server'''
 +
 +
== Install (import) the vCenter Server Appliance ==
 +
* Obtain the '''vCenter Server Appliance''' from VMware's website. (You may need to login to obtain a copy.)
 +
* From within '''vSphere Client''', go to the '''File''' menu and select '''Deploy OVF Template'''. A wizard will start.
 +
** Enter the location of the downloaded OVF file, click '''Next'''
 +
** Click '''Next''' again
 +
** Enter a name for the appliance (or accept the default), click '''Next'''
 +
** Accept the '''Disk Format''' defaults, click '''Next'''
 +
** Click '''Next''' to import the '''vCenter Server Appliance'''
 +
* The import will take a few minutes depending on the speed of the local drives and network
 +
* Right click on the '''vCenter Server Appliance''' in the left pane and select '''Power''' > '''Power On'''
 +
 +
== Configure vCenter Server Appliance ==
 +
* Within '''vSphere Client''', select '''vCenter Server Appliance''' and select the '''Console''' tab
 +
* The local console of the appliance will be displayed including the '''IP Address''' and '''TCP Port''' to connect to the system with. Enter these details into a web browser.
 +
* When prompted, enter the default username ('''root''') and password ('''vmware'''), a setup wizard will start:
 +
** Accept the licence agreement and click '''Next'''
 +
** Select '''Set custom configuration''' (so you can see the available options) and click '''Next'''
 +
** For '''Database Settings''' accept defaults and click '''Next'''
 +
** For '''SSO Settings''' accept defaults and click '''Next'''
 +
** For '''Active Directory''' accept defaults (disabled) and click '''Next'''
 +
** For '''Review Configuration''' click '''Next'''
 +
** For '''Configure''' click '''Start'''
 +
** Click '''Close''' when finished
 +
* Configure networking (if DHCP is not desired) by selecting the '''Networking''' tab
 +
** Click '''Address''', change '''IPv4 Address Type''' to '''Static'''
 +
** Enter IP information, hostnames, DNS servers, etc
 +
** Click '''Save Settings'''
 +
* Enter the ''new'' IP address (and original port number) of your '''vCenter Server Appliance''' to confirm the system is contactable.
 +
 +
== Create a Windows Server VM to provide AD services ==
 +
<nowiki>## This will be custom to the user environment</nowiki>
 +
 +
== Create a Windows Server VM for VMware Horizon View ==
 +
'''NB:''' This VM must be domain connected but '''''not''''' the domain controller itself.
 +
* Obtain '''VMware Horizon View Connection Server''' from VMware (you may need to log in to obtain this)
 +
* Install '''VMware Horizon View Connection Server'''
 +
** Accept default options and click '''Next'''
 +
** Deselect "Bug reporting / User Experience feedback"
 +
* Install Adobe '''Flash'''
 +
 +
== Configure VMware Horizon View ==
 +
* Open a web browser from a workstation and enter the details of your '''VMware Horizon View''' server in the following format: '''https://<ip_addr>/admin'''
 +
* Login with the default username ('''root''') and password ('''vmware''')
 +
* Add you vCenter Server
 +
** Click on '''Servers''' under '''View Configuration''' (left pane), then click the '''Add...''' button (right pane)
 +
** Enter '''vCenter Server''' '''IP address'', username ('''root''') and password ('''vmware'''), click '''Next'''
 +
** For '''View Composer''' leave default setting and click '''Next'''
 +
** For '''Storage''' disable '''Acceleration''' (not vital) and click '''Next'''
 +
** Complete the wizard

Latest revision as of 14:26, 23 April 2013

Install VMware ESXi Hypervisor

  • Install the VMware ESXi Hypervisor from ISO (or network deployment) to a bare metal system. Very little user interaction is required during the installation. Only basic info will be requested:
    • Disk to use for installation
    • Password

Manage with vSphere Client

  • Download and install the vSphere Client for Windows (Mac and Linux versions not available at the time of writing) and install on a workstation.
  • Open vSphere Client and enter:
    • IP Address of ESXi Server
    • Username of root
    • Password as defined during the install of ESXi server

Enable SSH

  • Within vSphere Client select the ESXi server from the tree list on the left pane
  • In the right pane, select Configuration tab
  • Select Security Profile under the Software section
  • Under Services, click Properties...
  • From the list of services, select SSH and click the Options button
  • Click Start
  • Select Start and stop with host and click OK
  • Click OK to save and close the Services Properties dialog box

Install nVidia GRID drivers

  • Download the nVidia VIB driver package for VMware/vSphere from the nVidia website.
  • Copy the driver to the ESXi system
Jons-MacBook-Air: Jon$ scp NVIDIA-VMware-304.76-1OEM.510.0.0.802205.x86_64.vib root@10.50.0.0:/tmp/
  • Connect the ESXi Server using SSH and the root user:
Jons-MacBook-Air: Jon$ ssh root@10.50.0.0
  • Enter Maintenance Mode:
/tmp # vim-cmd hostsvc/maintenance_mode_enter
'vim.Task:haTask-ha-host-vim.HostSystem.enterMaintenanceMode-369681837'
  • Install the VIB driver:
/tmp # esxcli software vib install -v /tmp/NVIDIA-VMware-304.76-1OEM.510.0.0.802
205.x86_64.vib
Installation Result
   Message: Operation finished successfully.
   Reboot Required: false
   VIBs Installed: NVIDIA_bootbank_NVIDIA-VMware_ESXi_5.1_Host_Driver_304.76-1OEM.510.0.0.802205
   VIBs Removed:
   VIBs Skipped:
  • Confirm the driver is installed:
/tmp # esxcli software vib list | grep NVIDIA
NVIDIA-VMware_ESXi_5.1_Host_Driver  304.76-1OEM.510.0.0.802205          NVIDIA  VMwareAccepted    2013-04-23
  • Verify the nVidia module loads:
/tmp # esxcli system module load --module nvidia
  • Verify the devices are present:
/tmp # esxcli hardware pci list -c 0x300 -m 0xff
000:004:00.0
   Address: 000:004:00.0
   Segment: 0x0000
   Bus: 0x04
   Slot: 0x00
   Function: 0x00
   VMkernel Name:
   Vendor Name: NVIDIA Corporation
   Device Name: NVIDIAGRID K2
   Configured Owner: Unknown
   Current Owner: VMkernel
   Vendor ID: 0x10de
   Device ID: 0x11bf
   SubVendor ID: 0x10de
   SubDevice ID: 0x100a
   Device Class: 0x0300
   Device Class Name: VGA compatible controller
   Programming Interface: 0x00
   Revision ID: 0xa1
   Interrupt Line: 0x0b
   IRQ: 11
   Interrupt Vector: 0xb0
   PCI Pin: 0x00
   Spawned Bus: 0x00
   Flags: 0x0201
   Module ID: -1
   Module Name: None
   Chassis: 0
   Physical Slot: 8
   Slot Description:
   Passthru Capable: true
   Parent Device: PCI 0:3:8:0
   Dependent Device: PCI 0:3:8:0
   Reset Method: Bridge reset
   FPT Sharable: true

000:005:00.0
   Address: 000:005:00.0
   Segment: 0x0000
   Bus: 0x05
   Slot: 0x00
   Function: 0x00
   VMkernel Name:
   Vendor Name: NVIDIA Corporation
   Device Name: NVIDIAGRID K2
   Configured Owner: Unknown
   Current Owner: VMkernel
   Vendor ID: 0x10de
   Device ID: 0x11bf
   SubVendor ID: 0x10de
   SubDevice ID: 0x100a
   Device Class: 0x0300
   Device Class Name: VGA compatible controller
   Programming Interface: 0x00
   Revision ID: 0xa1
   Interrupt Line: 0x0b
   IRQ: 11
   Interrupt Vector: 0xb0
   PCI Pin: 0x00
   Spawned Bus: 0x00
   Flags: 0x0201
   Module ID: -1
   Module Name: None
   Chassis: 0
   Physical Slot: 16
   Slot Description:
   Passthru Capable: true
   Parent Device: PCI 0:3:16:0
   Dependent Device: PCI 0:3:16:0
   Reset Method: Bridge reset
   FPT Sharable: true

000:008:03.0
   Address: 000:008:03.0
   Segment: 0x0000
   Bus: 0x08
   Slot: 0x03
   Function: 0x00
   VMkernel Name:
   Vendor Name: Matrox Graphics, Inc.
   Device Name: MGA G200eW WPCM450
   Configured Owner: Unknown
   Current Owner: VMkernel
   Vendor ID: 0x102b
   Device ID: 0x0532
   SubVendor ID: 0x15d9
   SubDevice ID: 0x0662
   Device Class: 0x0300
   Device Class Name: VGA compatible controller
   Programming Interface: 0x00
   Revision ID: 0x0a
   Interrupt Line: 0x0b
   IRQ: 11
   Interrupt Vector: 0xa0
   PCI Pin: 0x00
   Spawned Bus: 0x00
   Flags: 0x0221
   Module ID: -1
   Module Name: None
   Chassis: 0
   Physical Slot: 0
   Slot Description:
   Passthru Capable: true
   Parent Device: PCI 0:0:30:0
   Dependent Device: PCI 0:0:30:0
   Reset Method: Bridge reset
   FPT Sharable: true

000:086:00.0
   Address: 000:086:00.0
   Segment: 0x0000
   Bus: 0x86
   Slot: 0x00
   Function: 0x00
   VMkernel Name:
   Vendor Name: NVIDIA Corporation
   Device Name: NVIDIAGRID K2
   Configured Owner: Unknown
   Current Owner: VMkernel
   Vendor ID: 0x10de
   Device ID: 0x11bf
   SubVendor ID: 0x10de
   SubDevice ID: 0x100d
   Device Class: 0x0300
   Device Class Name: VGA compatible controller
   Programming Interface: 0x00
   Revision ID: 0xa1
   Interrupt Line: 0x0b
   IRQ: 11
   Interrupt Vector: 0x41
   PCI Pin: 0x6f
   Spawned Bus: 0x00
   Flags: 0x0201
   Module ID: -1
   Module Name: None
   Chassis: 0
   Physical Slot: 8
   Slot Description:
   Passthru Capable: true
   Parent Device: PCI 0:133:8:0
   Dependent Device: PCI 0:133:8:0
   Reset Method: Bridge reset
   FPT Sharable: true

000:087:00.0
   Address: 000:087:00.0
   Segment: 0x0000
   Bus: 0x87
   Slot: 0x00
   Function: 0x00
   VMkernel Name:
   Vendor Name: NVIDIA Corporation
   Device Name: NVIDIAGRID K2
   Configured Owner: Unknown
   Current Owner: VMkernel
   Vendor ID: 0x10de
   Device ID: 0x11bf
   SubVendor ID: 0x10de
   SubDevice ID: 0x100d
   Device Class: 0x0300
   Device Class Name: VGA compatible controller
   Programming Interface: 0x00
   Revision ID: 0xa1
   Interrupt Line: 0x0b
   IRQ: 11
   Interrupt Vector: 0x41
   PCI Pin: 0x20
   Spawned Bus: 0x00
   Flags: 0x0201
   Module ID: -1
   Module Name: None
   Chassis: 0
   Physical Slot: 16
   Slot Description:
   Passthru Capable: true
   Parent Device: PCI 0:133:16:0
   Dependent Device: PCI 0:133:16:0
   Reset Method: Bridge reset
   FPT Sharable: true
  • Exit Maintenance Mode:
/tmp # vim-cmd hostsvc/maintenance_mode_exit
'vim.Task:haTask-ha-host-vim.HostSystem.exitMaintenanceMode-369681914'
  • End the SSH session.
  • Reboot the ESXi Server

Install (import) the vCenter Server Appliance

  • Obtain the vCenter Server Appliance from VMware's website. (You may need to login to obtain a copy.)
  • From within vSphere Client, go to the File menu and select Deploy OVF Template. A wizard will start.
    • Enter the location of the downloaded OVF file, click Next
    • Click Next again
    • Enter a name for the appliance (or accept the default), click Next
    • Accept the Disk Format defaults, click Next
    • Click Next to import the vCenter Server Appliance
  • The import will take a few minutes depending on the speed of the local drives and network
  • Right click on the vCenter Server Appliance in the left pane and select Power > Power On

Configure vCenter Server Appliance

  • Within vSphere Client, select vCenter Server Appliance and select the Console tab
  • The local console of the appliance will be displayed including the IP Address and TCP Port to connect to the system with. Enter these details into a web browser.
  • When prompted, enter the default username (root) and password (vmware), a setup wizard will start:
    • Accept the licence agreement and click Next
    • Select Set custom configuration (so you can see the available options) and click Next
    • For Database Settings accept defaults and click Next
    • For SSO Settings accept defaults and click Next
    • For Active Directory accept defaults (disabled) and click Next
    • For Review Configuration click Next
    • For Configure click Start
    • Click Close when finished
  • Configure networking (if DHCP is not desired) by selecting the Networking tab
    • Click Address, change IPv4 Address Type to Static
    • Enter IP information, hostnames, DNS servers, etc
    • Click Save Settings
  • Enter the new IP address (and original port number) of your vCenter Server Appliance to confirm the system is contactable.

Create a Windows Server VM to provide AD services

## This will be custom to the user environment

Create a Windows Server VM for VMware Horizon View

NB: This VM must be domain connected but not the domain controller itself.

  • Obtain VMware Horizon View Connection Server from VMware (you may need to log in to obtain this)
  • Install VMware Horizon View Connection Server
    • Accept default options and click Next
    • Deselect "Bug reporting / User Experience feedback"
  • Install Adobe Flash

Configure VMware Horizon View

  • Open a web browser from a workstation and enter the details of your VMware Horizon View server in the following format: https://<ip_addr>/admin
  • Login with the default username (root) and password (vmware)
  • Add you vCenter Server
    • Click on Servers under View Configuration (left pane), then click the Add... button (right pane)
    • Enter vCenter Server IP address, username ('root) and password (vmware), click Next
    • For View Composer leave default setting and click Next
    • For Storage disable Acceleration (not vital) and click Next
    • Complete the wizard
Retrieved from "http://wiki.define-technology.com/mediawiki-1.35.0/index.php?title=VMware:_vSphere_5.1_VDI&oldid=2276"