VMware
VMware have announced their latest release of vSphere, which will soon be released for GA as vSphere 5.1.
vSphere 5.1 brings a number intresting changes from my point of view, both technically and license wise.
As was the case with vCenter Server 4.1, vCenter Server 5.0 also only supports being installed on a 64 bit OS.
If you are currently running vCenter 4.0 on a 32-bit OS you cannot upgrade. You must create a new server (physical or virtual) with a supported 64-bit OS and either start with a clean installation and database or migrate your installation and database to a new 64-bit OS server and then perform the upgrade.
To display general driver and device information:
/opt/teradici/pcoip-ctrl -I
Within the device summary your looking to confirm next to "Device" that it is "IN_SERVICE".
In the Virtual Machine summary you are able to see if any PCoIP sessions have been found and actually offloaded.
Share this blog post on social media:
Tweet
Latest Blog Posts
- vSphere 7 U1 - Part 3 - Creating a Datacenter, HA/DRS Cluster and Adding a Host
- vSphere 7 U1 - Part 2 - Deploying vCenter 7.0 U1 VCSA
- vSphere 7 U1 - Part 1 - Installing ESXi 7.0 U1
- Veeam CBT Data is Invalid - Reset CBT Without Powering Off VM
- View Administrator Blank Error Dialog/Window After Upgrade
Popular
- Reset 3COM Switch to Factory Defaults (Forgot Password)
- Disk Consolidation Needed - Unable to access file since it is locked
- SCCM 2012 - Software Center Unable to Download Software 0x87D00607
- VMware Visio Stencils - Diagram and Icon Library
- Moving BT Infinity DSL from Master Socket to Any Household Extension Socket
- WSUS Useful Client Commands WUAUCLT.exe
- Creating/Adding a Raw Device Mapping (RDM) to a Virtual Machine
Social Links
Disclaimer
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.