Tag: vSphere 5.1
I wanted to upgrade the memory on my vSphere 5.1 vCenter server to 16GB and I didn’t have hot-add enabled. I powered off the VM, connected directly to the host and re-configured the VM as required and then clicked OK.
At this point, I got an error saying “Access to resource settings on the host is restricted to the server that is managing it: X.X.X.X”.
The host things it is still being managed by vCenter so it won’t let me edit the VM. vCenter server is powered off so that I can edit the VM (as hot-add is not enabled the VM has to be powered off to change the memory amount).
This is how to fix this issue…..
In October 2014, I wrote an article about what I was looking to build in my new home test lab. Since then I have been hard at work setting it up and I have made a number of design changes since then. Here is an update on my progress…
As of September 2015, I have released version 2 of my PowerCLI Script Template, which includes a number of improvements over this version, in particular the use of the new PSLogging PowerShell module that significantly improves the creation and management of log files. This version of the template is no longer supported or maintained, so please upgrade to the new version today!
Version 2 of the template is available here – PowerCLI Script Template v2.
A while a go I posted up my PowerShell Script Template which turned out to be pretty popular with fellow PowerShellers.
I recently create another slightly modified template when working with PowerCLI, so I thought I would share it here. Here is my PowerCLI Script Template to be used for all your VMware scripts…
When you rename a virtual machine in VMware, the VM’s folder and files on the datastore do not get renamed automatically. This can make troubleshooting difficult as it will be almost impossible to find a renamed VM whilst browsing a datastore.
To fix this, you normally do a Storage vMotion of the VM, which would rename the folder and all of the corresponding VM files to the new name. Unfortunately in vCenter 5.0 and 5.1 a Storage vMotion does not rename the VM files, it will only rename the folder.
There is a fix for this so that the VM files get renamed as well. Here is how to do it…
Here is a quick fix to a problem that I had the other day, which I thought my be useful to a few people.
You logging into the vSphere 5.1 Web Client with the local vSphere Single Sign-On (SSO) user of admin@System-Domain and it fails with the error message of
associated users password is expired.
Below is the solution to this error message…