January 2020, VMware informed their customers that LDAP and Integrated Windows Authentication Identity Stores, will cease functioning as Microsoft is disabling LDAP on Active Directory. Have you not yet configured this in your environment? Read on!
So, you’re ready to upgrade your environment to a higher SimpliVity version right? Good stuff! It’s great to keep your environment up-to-date to receive new features and security updates.
For SimpliVity, you would typically use HPE SimpliVity Upgrade Manager. However, this software sometimes seems to have a mind of its own and will not launch, or actually fire off your upgrade.
This post is dedicated to using the CLI as a way to upgrade your environment, and is from this day on also my personal preferred method.
This article is about upgrading your HPE SimpliVity environment, including all of the components that come with this upgrade: VMware vSphere, firmware and your third-party software.
I will describe the global steps, time estimation, do’s and don’ts and tips from my side as I have a lot of experience performing these kind of upgrades.
The information in this article is based on HPE SimpliVity 4.0.0.
Increasing the amount of vCPUs in ESXi is a simple admin task when working with a single or low number of virtual machines. However, performing this on a large number of virtual machines can be an intensive task.
This article is about my use case and how I resolved this with a script, which can be found at the bottom.
At my current assignment, I got busy with the replacement of an existing vCenter Server and migration of all linked objects. This included migrating the vSphere Distributed Switch Port Group objects, settings and permissions.
Exporting the vSphere Distributed Switch configuration is an easy-to-do job using the GUI. However permissions are not included. This post is dedicated to the script I wrote to export and import these permissions.
This article focuses on some free backup solutions for VMware vSphere as VMware’s home-brewed vSphere Data Protection is End-of-Life and will not support any releases after vSphere 6.5.
Last week I got busy with upgrading four VDP appliances for a customer. I’ve come across quite some challenges and issues during this task that I’d like to share these with you in case you are facing the same task.
Monitoring is one of the most important aspects of an IT environment. This post focuses on integrating Paessler’s PRTG Network Monitor with VMware vSphere 6.5.
While new versions of vSphere are being released and deployment methods have been changed, it’s currently not so straight forward to deploy a vSphere lab inside Fusion and Workstation. This due to the fact that there is no OVF-based vCenter Server Appliance install available anymore (as of vSphere 6) and there is some manual fiddling required to make this work. This article will describe the steps you need to take for deployment.
Starting with vSphere 6, components for license, certificate management and SSO are being handled by the PSC (Platform Services Controller). This new part of a vSphere installation can be configured to be highly available.
I came across an issue where a fresh installation of vCenter Server 6.0 using an external high availability deployment of PSC would fail with a certificate or invalid credentials error. This article describes the issue and how it was solved.