Browsing Posts in VMware

Reading Time: 3 minutesIn a VMware infrastructure, when you build a new VM, the default compatibility level could depend on your vSphere version, from which client you are using (the legacy vSphere Client does not ask for VM virtual hardware version in the default wizard), but also from your cluster settings. VM virtual hardware version defines exactly the compatibility level, but you can define the default level using the vSphere Web Client or the new HTML5 Client.

Reading Time: 6 minutesUsually when you upgrade to a new version of a product you may need also a new license key for it. But it’s not always true. For most of VMware’s products (for example VMware vSphere) a new license key is needed ONLY if you change the major number.

Reading Time: 3 minutesOne of the announce at last VMworld EU 2017 is the new version of VMware vSphere Integrated Containers (VIC). This new version will deliver significant new capabilities, major security enhancements and the the ability to provision native Docker container hosts using a unified management portal. VMware vSphere Integrated Containers delivers an enterprise container infrastructure that provides the best of both worlds for the developers and vSphere operations teams where containers can now be enabled and managed as “normal” virtual machines with the same concepts and skills, with no processes or tools changes required.

Reading Time: 2 minutesUsing the legacy vSphere Client is no more possible in vSphere 6.5, but with the previous version is still an option. Unfortunately, it lacks not only in all the new features but also in consistency and error reporting. A curios issue was with a vSphere 6.0 environment where a generic warning message appears on the Summary tab of the ESXi hosts. The error was a generic “Consiguration Issues” message.

Reading Time: 2 minutesVMware has just released the new major version of NSX-T 2.0 to provides an agile software-defined infrastructure to build cloud-native application environments. When Nicira product has been released was for Linux and physical platform, but after the VMware’s acquisition has been re-engineered to be integrated in the vSphere platform, with the new name of VMware NSX (now NSX-v). NSX-T is again a version for (physical) Linux system designed for management, operations, and consumption newtork resources insied a (development) organizations. NSX-T allows IT and development teams to choose the technologies best suited for their applications.

Reading Time: 2 minutesStarting with vSphere 6.0, the new PSC component include not only the SSO part, but also a certification authority for certification management of all vSphere infrastructure elements (unfortunately is not been used yet by all the other VMware’s products). This simplified not only the certifications management (with auto-enrollment for expired certificates), but also the trust between the different connections.

Reading Time: 2 minutesActually there are two different platform where you can run the vCenter Server components (including the PSC): Windows (both physical or virtual) or Linux (only with the vCSA, based on PhotonOS). Initially there was only a Windows version, then the vCenter Server Appliance (vCSA) was first introduced with the release of vSphere 5.0 and has since evolved to become the definitive deployment model for vCenter Server. Starting with vSphere 6.5 the vCSA has become the first choice and has raised the level of vCenter with new functionalities (not available on the Windows version).

© 2025-2011 vInfrastructure Blog | Disclaimer & Copyright