![]() But the web-based version of the vSphere Client received too many complaints from system engineers, with the strongest ones referring to speed, usability, design, and even its architecture. A Web client working in a browser looked like a logical step forward. In the era of smartphones and cross-platform applications, a decision to support only Windows-based applications looks like a dead end. ![]() What was wrong with the previous vSphere management tools? The biggest disadvantage of the Windows-based vSphere client was its dependency on the Windows platform. In vSphere v5.0, VMware introduced a new, shiny Web client, which was intended to replace the Windows-based vSphere Client. So, if your environment had vSphere v4.0, v4.1, and v5.0, you'd have to re-install all your clients. Every new release of vSphere required installing a new version of that client. Prior to vSphere 5.0 release, there was only one tool for vSphere management provided by VMware – a Windows-based application called vSphere Client. the PastĪs all software vendors develop management tools to provide the best user experience and deliver more convenient, user-friendly, and platform-independent products, we have witnessed an evolution from Windows-only applications to Web-based, platform-independent ones including HTML5 vSphere Web Client. By Dmitriy Yegarmin HTML5 vSphere Web Client vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |