One of the annoying things about installing new builds of Windows 10 is that the installation process resets a number of settings to default. When you’re on the insider preview “fast ring”, new builds come every 1-2 weeks, and changing those handful of things back to their previous setting gets old pretty fast. After installing a new build today I finally decided to try automating these things using Powershell.
Month: March 2016
This is an (extremely) quick post to cover the steps required to decommission a Platform Services Controller (PSC) or vCenter Server from the vSphere single-sign on (SSO) domain. The steps below are for a VCSA; steps for a Windows VC are very similar, and are contained in the VMware KB article I used as a reference for writing this post: KB 2106736.
Here’s a quick guide on how to query and change the Platform Services Controller (PSC) being used by vCenter. Querying for the in-use PSC is possible on vCenter 6.0, but changing the PSC is only possible on 6.0 Update 1 or newer. Note that I performed these steps on the vCenter Server Appliance (VCSA), and while I have also included some commands for a Windows-based vCenter server, I haven’t tested them myself.
As VMware continues to push in the direction of unix-based appliances for their vSphere management components, those without a Unix background (like myself) are having to come to grips with the Unix versions of common administrative tasks. Increasing the disk size on a vCenter Server appliance (VCSA) is one such task. In vCenter 6.0 VMware has introduced Logical Volume Management (LVM) which really simplifies the process of increasing the size of a disk, and allows it to be done while the appliance is online. VMware KB 2126276 covers all the steps required to increase the size of a disk, but this guide will cover it in slightly more detail.