Posts

Showing posts with the label change

VMware New Per-CPU Licensing

If you haven't heard, VMware is implementing a new licensing on his products which will be effective 30th April 2020. This means, if you were to purchase any license prior to that, it will still have no restriction. So what is new in these licensing changes? Basically, VMware is introducing a physical core licensing to its per-CPU license. VMware software has always been licensed by per physical CPU with unlimited physical cores on that CPU. With this change, each CPU license will be limited to 32 physical cores. Will the customer be affected? Most customers, will not be affected since most servers are using Intel CPU which currently has not exceeded 36 physical cores. However, those running the latest AMD CPU, will be affected as there will be more licenses required. Here is the VMware announcement. This will apply to all VMware software. One of the questions that are commonly asked, will be if my CPU has more than 32 cores (example 48 cores) and I am using two physical C...

IT Paradigm Changed, Have you?

Last month of the year and today have a some talk over lunch with a colleague and decide to pen this down which I see lacking on the market. I have spoken to customers and also spoken to some colleagues and realize the IT paradigm as changed quite substantial.  However many are still operating the wrong way which end up even with virtualization, cloud or Software Defined Data Center, etc. it is still not helping them achieve in a big scale. Recently I did a session on BC/DR: Implementing a Holistic Strategy with VMware Solutions session at APJ vForum in Singapore.  I mentioned a few things that was abstracted from VCDX Design Defense Blueprint page 11.  This diagram has helped me in a lot of discussion and I see many are still not aware.  The five things: Availability, Recovery, Security, Manageability, Performance. Taking an example today, when a Application owner request a machine with certain specification in terms of CPU, Memory and space from an Infra p...

VMware Horizon Workspace Folder and File Sharing Detailed Walkthrough

Image
I have many people asking me how to share or what can I share to a user on Horizon Workspace.  So Here I am going to share with you some screenshot and understand what can or cannot be done. We will be able to have a preview of normal office documents, pictures as well as PDF files in Horizon Workspace.  However if its a unknown format or files that cannot be display per se e.g. zip files, it will not be display. Now let's talk about sharing of files and folder. First of all, you are able to share file or folder to outside external parties from your domain.  This enable users to share file with third parties outside the domain.  External party will not be able to install the Horizon Workspace client as his account are not connected to the internal Horizon Workspace server. Below is a screenshot on the context menu you will see when you click to share a Folder or a File. Sharing a Folder Sharing a File When you share a File you will be provided w...

vSphere 5 & 5.1 Licensing

As of today's announcement, the new vSphere licensing for 5 and 5.1 will be by per processor licensing moving forward from 27th August 2012.  This eliminate the need of vRAM entitlement which was used in vSphere 5.0 last year. This come effect for all new and existing customers on vSphere 5.0 while vSphere 5.1 is yet to be released for download.  The updated End User License Agreements (EULA) will replaces and supersede statement can be found here . This change was decided due to the feedback and confusion created when vRAM entitlement was release last year in partners and users.  Though vRAM would benefit people with bigger environment, the core processor licensing was still easier for everyone. You can read from the vSphere 5 Licensing white paper here .  You may also refer to all the resources of vSphere whether for 5.0 or 5.1 all at this place . I have the table of the license entitlement between 4.1 and prior and the new change for 5.x below: ...