Plain Virtualization

There are all the articles available and most of them are on Horizon View 5.2 with Lync 2013.  However these are still valid there is nothing changes.  One great article which I refer to when doing my Proof of Concept (POC) with my customer is here .  The document that the article refers to is a must read and its pretty clear.  But some confusion that came to my mind when doing so here are some of questions you might have. On the endpoint, it has to be a physical machine running Windows which can be 32 bit or 64 bit.  The LyncVDI plugin needs to be the same bit level as the Office (where Lync is usually installed with) or the Standalone Lync that is installed in the virtual desktop. Note: Do not install Lync Client on the end points where Lync VDI plugin is installed.  And no USB redirection should be done for the camera or audio device which will be used by Lync for video and audio. On the end point, you will need three things: Horizon View Clie...

With the release of vSphere 5.1 Update 1, all components that has a dependency with vCenter would be updated.  That would include vCenter Heartbeat, Site Recovery Manager, vCenter Orchestrator, vSphere Storage Appliance, vCloud Director, vSphere Data Protection and not forgeting VMware Converter Standalone. As we all know that VMware Converter Standalone is free comparing with other Converter products which are chargeable by per system/VM.  But the reason that most of us would go to other solutions because we have systems with GPT disks or UEFI firmware interface. With the release of VMware Converter Standalone 5.1, it now has new features with the support of UEFI source machines as well as GPT support and many other which you can refer to the Release Notes .  Of course with the new release it will also support the latest OS like Windows 8 and Windows 2012 and file format EXT4. Though this support came a little bit late, but at least now we are able to save a littl...

As the virtualization has grown more mature during the years, many users has asked me this  question, especially users who have just ride on the virtualization journey.  There isn't a right or wrong answers however what do you want to achieve at end state.  Do you have what you wanted keeping it at the current state? Let us take look why run the vCenter as physical machine. - Do not feel comfortable running management server as a virtual machine, prefer all management server as a physical machine - Uncomfortable to run the vCenter as part of the virtual infrastructure - Easy to locate the vCenter physical server when required Why run the vCenter as a virtual machine? - Able to enjoy protection from VMware Hight Availability - Able to have DRS perform on vCenter (consider DRS exception or DRS infinity on vCenter) - Less hardware maintenance and better utilize hardware - For higher availability, run vCenter Heartbeat however two set of vCenters is required. So...