Viewのダイナミックグラスは、多様なコントロールが可能だ。簡単な話、スマホやタブレットから部屋毎に多段階の透明度制御が出来る。それだけではない。ダイナミックグラスには3つの制御エンジンがある。反射制御（Glare Control Module）と熱制御（Heat Control Module）、そして日光制御（Daylight Control Module）だ。反射制御はリアルタイムに日光の角度を計算してガラスの濃さを制御する。熱制御は太陽のエネルギー計算からエアコンのエネルギー節約を行い、日光制御は各方向尾の建物外壁に取り付けた光センサーによって透明度を制御する。
The vCT ships as a virtual appliance with all the required VMware components to set up your Horizon View environment. After providing a Windows Server 2008 R2 SP1 ISO, an ESX host (not managed by vCenter), a few parameters, and licenses, the tool will provision your environment dynamically and automatically. The vCT deploys the following components:
Virtual machine with Active Directory Domain Controller configured (or you may integrate with the existing DC in your environment)
Virtual machine with Horizon View Connection Server installed
Virtual machine with Horizon View Composer installed
vCenter Server Appliance virtual machine deployed and configured
As of ESXi/ESX 4.0, it is no longer necessary to handle snapshot LUNs via the CLI. Resignature and Force-Mount operations have full GUI support and vCenter Server does VMFS rescans on all hosts after a resignature operation.The snapshot LUNs issue is caused when the ESXi/ESX host cannot confirm the identity of the LUN with what it expects to see in the VMFS metadata. This can be caused by replaced SAN hardware, firmware upgrades, SAN replication, DR tests, and some HBA firmware upgrades. Some ESXi/ESX host upgrades from 3.5 to 4.x due to the change in naming convention from mpx to naa have also been known to cause this. However, this is a rare occurrence.
For the space reclamation feature to work correctly, ensure that:
VMware Tools provided with vSphere version 5.1 or later are installed on the virtual machine.
The virtual machine is using virtual hardware version 9 or later.
In the View Administrator console, the Reclaim VM disk space option is selected for the vCenter Server. For more information, see Allow vSphere to Reclaim Disk Space in Linked-Clone Virtual Machines in the VMware Horizon View 5.2 Administration Guide.
In the View Administrator console, the Reclaim VM disk space option is selected for the desktop pool. For more information, see Reclaim Disk Space on Linked-Clone Desktops in the VMware Horizon View 5.2 Administration Guide.
The virtual machine is powered on before you initiate the space reclamation operation.
There is space that can be reclaimed. This space exists when data is deleted from the guest OS. Sending files to the Recycle Bin does not delete them.
The virtual machine is using SCSI disks.
Change Block Tracking (CBT) is disabled on the parent virtual machine.
It is important to understand the requirements and limitations around using Emergency Restore:
DNS must be available and configured properly for the VDP appliance and the vSphere host on which the VDP appliance is running.
Emergency Restore can only restore a VM to the vSphere host on which the VDP appliance is running.
A restored VM is placed in the root of the vSphere host inventory.
VM is restored as a new VM – ensure that the name provided for the VM is not already in use on the vSphere host to avoid overwriting and existing VM.
Restored VM will be in a powered off state – the VM can be manually powered on after the restore is complete.
The vSphere host running the VDP appliance must be disassociated from vCenter Server for Emergency Restore to work. This can be accomplished by using the vSphere Client (not vSphere Web Client) connected directly to the vSphere host. “Disassociate host from vCenter Server…” is located in Host Management on the Summary tab (when the host is selected in the left window panel of the vSphere Client). This must be done prior to performing the Emergency Restore.