RVTools 4.7.1 is a Windows .NET 4.7.2 application which uses VMware vSphere...
RVTools technology was just acquired by Dell Technologies from its original...
VMware ESXi 8 has dropped the compatibility with a lot of old CPU models, a...
One year ago, Broadcom killed the Free vSphere Hypervisor, but now, with th...
Veeam Backup & Replication 13, the next next major release, will be pro...
The Veeam Managed Hardened Repository is a bootable ISO based on Rocky Linu...
VMware® vCenter Converter Standalone provides an easy-to-use solu...
The vCenter Server Security Token Service (STS) is a Web service that issue...
The legacy C# vSphere Client for Windows is no more available for vSphere 6...
In VMware Workstation 17.6.1, when I create a Rocky Linux VM, there is no w...
Reading Time: 3 minutesNutanix has recently released a new version of Acropolis Operating System (AOS): AOS 5.8 is now the latest version. Just few months after Nutanix AOS 5.6. NOTICE: AOS 5.8 is a new AOS Feature Release or Short term Support (STS) Release, that means it isn’t a Long Term Supported (LTS). The support for all feature release version will only be for 6 months after the release date, within which period you will have to upgrade to the next feature release version.
Reading Time: 2 minutesVMware vSphere 6.7 wasn’t officially supported by Veeam Backup & Replication, as also the new vSphere 6.5 Update 2 (due to the backporting from 6.7). But now Veeam has released the Backup Replication 9.5 Update 3a version that fully supports latest vSphere versions, including vCloud Director and VMware Cloud on AWS:
Reading Time: 2 minutesVMware Workstation 14 it’s a great product and adds several features from ESXi 6.5 and 6.7 (like NVMe support). But drops too many CPU from its compatibility list and this means less support for old PCs or laptop. With an unsupported processor, you can create, configure, move the VMs, but when you try to power on them, you will receive an error message like this:
Reading Time: 3 minutesMeltdown and Spectre remediations can imply not only performance degradation, but also some management issues. For example in how EVC works as described in VMware KB 52085 (Hypervisor-Assisted Guest Mitigation for Branch Target injection). An ESXi host that is running a patched vSphere hypervisor with updated microcode will see new CPU features that were not previously available. These new features will be exposed to all Virtual Hardware Version 9+ VMs that are powered-on by that host. Because these virtual machines now see additional CPU features, vMotion to an ESXi host lacking the microcode or hypervisor […]
Reading Time: 2 minutesVMware vSphere 6.5 it’s quite popolar now, considering the deadline for the version 5.5 in this year and the direct upgrade path from v5.5 to v6.5. But maybe not everybody want to update vSphere 6.5 to Update 2, considering that there will be no upgrade path (yet) to version 6.7 and maybe other minor issues due to the backport of some features.
Reading Time: 2 minutesProbably it’s already a well know issues and it’s also resolved for the most. But there are so many systems that are isolated or system with an old patching plan, or simple you have installated a Windows Server from an old ISO. The Credential Security Support Provider protocol (CredSSP) updates for CVE-2018-0886 patch, released on May 8th 2018, if applied (on the client or the server) make not possible connect using RDP unless both endpoints have the patch applied.
Reading Time: 3 minutesThe new build of Windows 10 have a lot of new security settings and some of them can make cause issues with VMware Workstation (or potentially also other host hypervisors). One common issue when you try to power on a VM in Workstation and instead you get this error message: VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard.
| Disclaimer & Copyright
