MattHumphreys's Posts

We had an issue with one of our virtual machines and on investigate in VROPS and log insight we have identified that there was memory compression, a spike in demand and a balloon on the VM as bel... See more...
We had an issue with one of our virtual machines and on investigate in VROPS and log insight we have identified that there was memory compression, a spike in demand and a balloon on the VM as below However on the host we can see that there is available resource to handle the request without triggering the above balloon/compress etc We cant seem to figure out why the VM has ballooning and compression when the host appears to have available capacity in itself. Any suggestions on what other metrics to look at or where we can investigate further to try and point us to the root cause of this?
Unfortunately that isnt going to be an option as the version we installed originally is not the one that I need to roll back to, I need to target a specific version that we have never installed b... See more...
Unfortunately that isnt going to be an option as the version we installed originally is not the one that I need to roll back to, I need to target a specific version that we have never installed before, I can roll it back but that would leave me with still the wrong version installed.
So I need to go to a specific version of ESXi in my lab environment in order to carry out a test to try and diagnose a fault in our production environment, we have the latest build of 6.7 install... See more...
So I need to go to a specific version of ESXi in my lab environment in order to carry out a test to try and diagnose a fault in our production environment, we have the latest build of 6.7 installed in our lab as we used it as the test bed before we rolled the upgrade out to our production servers. We had an issue with one cluster which vmware cant seem to find the root cause of without further information, they want me to test the precise steps we took in upgrading the environment in a test lab so I need to install the same version that is in the production problem cluster. The target version is an older build of 6.7, now if I add the ISO to update manager, build a baseline and apply it to the hosts will it install the older version or will I have to wipe and install and reconfigure everything?
if you just want to remove it from inventory without deleting from disk do this: Remove-VM -VM <EnterVM> -Confirm:$false If you want to delete the VM entirely from disk then do this: Rem... See more...
if you just want to remove it from inventory without deleting from disk do this: Remove-VM -VM <EnterVM> -Confirm:$false If you want to delete the VM entirely from disk then do this: Remove-VM -VM <EnterVM> -DeletePermanently -Confirm:$false These commands wont ask you for confirmation they will just do it, if you want it to ask you before doing it just remove the -Confirm:$false To add the VM back you need some details like the VMX file location, if you run these before you remove the VM from inventory you can gather that info and store it in a variable to use later: $vmdetails = Get-VM -Name <Enter VM> $vmname = $vmdetails.Name $vmfolder = $vmdetails.Folder $vmxfile = $vmdetails.ExtensionData.config.Files.VmPathName Then to add the VM back to the folder it was in before: New-VM -VMFilePath $vmxfile -Location $vmfolder To start the VM use: Get-VM -Name $vmname | Start-VM -RunAsync I have assumed you have already connected the the vcenter server before running these commands.
I will give that a go in lab test, maybe easier to change the reporting method than have to go through removing and adding the vmdk each time.
could this not do the job? Get-VM | where {($_.ExtensionData.Config.ManagedBy.Type -ne "placeholderVm" -and $_PowerState -eq "PoweredOff")}
I have found even after doing that KB procedure if you query the size using powercli for reporting (which we do as a company) it still shows the old size, the only way we have found to make it wo... See more...
I have found even after doing that KB procedure if you query the size using powercli for reporting (which we do as a company) it still shows the old size, the only way we have found to make it work correctly is to recreate the RDM pointer when increasing the size. This is quite an annoying process at least for us, pretty time consuming to gather all the information for verification and recreation of the pointer exactly as it was before on the same ID/location so the cluster can just carry on as normal. Happy to be corrected though if there is a better way.
Get-VM ENTERVMNAME | Get-NetworkAdapter -Name "ENTERNETWORKADAPTER" | Set-NetworkAdapter -Connected:$false -StartConnected:$false -Confirm:$false That should do it, if you want to do it on all a... See more...
Get-VM ENTERVMNAME | Get-NetworkAdapter -Name "ENTERNETWORKADAPTER" | Set-NetworkAdapter -Connected:$false -StartConnected:$false -Confirm:$false That should do it, if you want to do it on all adapters on a VM then it would be as follows, this script wont ask for confirmation it will just go ahead and do it. Get-VM ENTERVMNAME | Get-NetworkAdapter | Set-NetworkAdapter -Connected:$false -StartConnected:$false -Confirm:$false