September

First things first, if you prefer to consume video content, the same content that is in this blog post is in the video below. If you prefer to read, please skip past the video and read on! Secrets Management Microsoft have recently released an update to a PowerShell module they’ve been working on for a short while now which is everything to do with management of secrets. Version 3 of the Secret Management PowerShell module was released last week and it is a decent update from version 2, so much so that it includes breaking changes, as can be expected with preview releases.

This is a short post and I’ll cut straight to it. I’m really happy to announce that I’ve published my first course with Pluralsight, Extending PowerShell. The course is aimed at helping you learn and understand PowerShell Modules and is part of a larger learning path for PowerShell 7 that is being produced currently on PowerShell. I have worked hard to make this demo heavy in a way that you can follow along with each task, and I hope you do, as the hands-on is where the knowledge gets solidified.

Last night I was working in an environment that has a reasonably well locked down NSX distributed firewall, and I was having some issues with PowerCLI. PowerCLI 10.2 on Windows, connecting to vCenter Server 6.7, to be specific. Port 443 was allowed from the jump host to vCenter Server, but I was seeing some odd issues still. I was trying to run an as built report for the environment, but I could not seem to establish a connection to NSX manager when running the script, and VUM cmdlets that are called in the script were also failing, such as:

Blink and you will miss it! For those that weren’t aware, VMware disclosed a security vulnerability with the vCenter Server VIX API which has been patched, but this also impacted VMware Infrastructure Navigator (VIN) as it used the VIX API to build service mappings. As per the VMware KB article that announced this information, if you are running vSphere 5.5/6.0 you essentially have two options. Continue using VIN on an unpatched environment (not recommended), or use a new management pack for vROps that replaces VIN functionality called the Service Discovery Management Pack.

One of the quieter announcements from VMworld US 2017 was that of VMware Skyline. No, not the Nissan sports car! As a VMware customer, VMware Skyline is a platform that provides VMware visibility in to your environment with the aim of providing proactive and predictive recommendations, based on the configuration in your environment, cross referenced with VMware guidance, KB articles and lessons learned from other customers' environments. In the event that you log a case with VMware, Skyline also provides the Global Support Services (GSS) team access to information about your environment, without needing to spend hours gathering logs, configurations or sitting on a Webex with an Engineer while they get familiar with your environment and specific configurations.

I’ve always tried to use and recommend using the ‘least privileges’ model when designing and implementing systems. But we’ve all been there, when the same service account is being used to connect everything to vCenter, and said account has been assigned the full administrator role and propagated within vCenter. I’m getting my lab set up again and I needed to install VMware Update Manager (VUM). I realised that in the lab previously I have just done as I mentioned before and used a high privilege service account thinking “it’s just a lab”.

A long last, VMware have made a tool available and supported to migrate from a Windows installation of vSphere 5.5 across to the vCenter Server Appliance (VCSA) 6.0U2. VMware gave us a teaser with a fling in 2015, but this was taken down and there have been hints dropped via Social Media and most recently some good sessions for the migration tool at VMworld 2016. Prior to this tool, migrating from a Windows install to the VCSA was not a trivial task.

Introduction This article will walk through the steps required to repoint a vCenter Server 6U1 or later node to a different Platform Services Controller (PSC) node. Scenario one will walk through the steps if the destination PSC is located within the same vSphere SSO site, where as scenario two will walk through the steps if the destination PSC is located in a different vSphere SSO site. This is almost the same process, but repointing a VC to a PSC in a different SSO Site than the original PSC requires an additional step.

Introduction Starting with vSphere 6, there are two main roles to a core vCenter infrastructure. The vCenter Server (VC) and the Platform Services Controller (PSC). During deployment, administrators are presented with two deployment options: Embedded. With an embedded deployment, the VC and PSC roles are installed on the same node External. With an external deployment, the PSC and VC roles are installed onto separate nodes. External deployment also enables the enhanced linked mode feature for vCenter Server Prior to 6.

Edit: At the time of publishing, the main page at www.vmworld.com is not rendering correctly (it is just showing a blank white page where the videos should be), though it was a few days ago. The URL that should be displaying on the vmworld URL below is http://www.webcastregister2016.com/vmware/form.php, and you can go directly to this URL to access the videos if the URL below is not working when you try.