Reading Time: 3 minutes Duncan Epping has wrote (on 2010) a nice post with the meaning of several, not too obvious, VMware acronyms used sometime in some product name, but usually in the internal process or file name. In those post you can found also some interesting facts about the meaning and the origin of some names. Now I’ve just put a copy here and short the list alphabetically and also added some new entries:
Reading Time: 7 minutes This was a guest post on vDestination. Usually (especially in Country like mine) we common talk about the Digital divide that bring not equity, or at least not same opportunity, between different group. But this is mainly focused on the connectivity aspects and how accessing to broadband networks could be different and limited for somebody. But this it’s only one aspect and there are also others that must be considered!
Reading Time: 2 minutes ESXi is the unified version of the VMware hypervisor, but it could be installed on a host in different way: Embedded: is a OEM version usually shipped with the host Installable: is the one available from the VMware download site PXE: is used in the AutoDeploy environment If could be obvios know if you have a PXE type, how is possible find if you have an Installable or Embedded version? The destination media is not enough because you can install ESXi also over the vendor’s SD card used for the embedded versions.
Reading Time: 3 minutes I’ve already write a post with the comparison between PCoIP and RDP (PCoIP vs. RDP) and some considerations on how use each protocol in a VMware View infrastructure. Other protocols, like HP RGS (Remote Graphics Software) has been removed (from View) years ago, and protocols from other solutions (like, for example, SPICE) are not included. But now there is also the HTML5 option (Blast protocol) included with the Horizon Suite or with the Feature Pack of Horizon View (see this post on how enable it).
Reading Time: 5 minutes In a View environment the PCoIP is usually the right choice and on a LAN works really well (see also the previous post about PCoIP and RDP differences). But on a wide-area networks (WANs)you have to consider some aspects to have a reasonable reactivity or to maximize the number of remote clients: you must consider bandwidth constraints and latency issues. The PCoIP display protocol provided by VMware adapts to varying latency and bandwidth conditions, but some optimization may be needed.
Reading Time: 3 minutes In a VMware View environment usually PCoIP protocol is preferred to the RDP one due to several reasons. I don’t want to spend too much time about the latency, throughput, reactivity, user experience different between those two protocols… in most cases PCoIP is better compared to RDP. But PCoIP protocol has some limits that your have to consider in your design and mainly are described in the View Architecture Planning guide.
Reading Time: 5 minutes There are different reason where you can you loose or corrupt your partition table of your VMFS volumes: resignature from another system (for example the backup server, if connected in SAN mode), a human mistake (datastore / delete), or maybe some storage issues. In this case usually the VMFS partition is still there and also the related data: you have “only” to rebuild the right partition table. But this could really simple if you follow the recommended practice to have only one VMFS partition on each disk. In this case you have only to build […]
| Disclaimer & Copyright
