WOOOHOOOOO
vCenter 5 upgrade leaves convertor red in health for service status
I ran into an issue where an upgrade to vCenter 5 left some trails of convertor behind… very annoying as i want it to be all green!!
here is the fix
get ldp, you don’t have to if you are server 2008 r2
run click cmd run as admin
ldp.exe
connection -> connect to your vc
connection -> bind
view -> tree
leave base dn blank
double click dc=virtualcenter,DC=vmware,DC=int
double click on OU=Health,DC=virtualcenter,DC=vmware,DC=int
double click on
OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int
double click on random string below it
(CN=GUID,OU=ComponentSpecs,OU=Health,
DC=virtualcenter,DC=vmware,DC=int)
right click
(CN=com.vmware.converter,CN=ED9D182F-7F51-42FF-B546-ADB0F518351,OU=ComponentSpecs,OU=Health,
DC=virtualcenter,DC=vmware,DC=int)
and choose delete
restart vc, log back in, and go click refresh!
welcome back all green!!
Alan
find vms with resource settings and set ram
[powershell]
$vms = Get-VM
foreach ($vm in $vms){
$vmre = $vm | Get-VMResourceConfiguration
if ($vmre.MemLimitMB -ne ‘-1’){
$rp = $vm | Get-VMResourceConfiguration
$rpvmmb = $rp.MemLimitMB
write-host $vm ", mem granted= " $vm.memorymb ", mem resources = " $rpvmmb
}}
[/powershell]
cooler one to only show when they don’t match!
[powershell]
$vms = get-vm
foreach ($vm in $vms){
$vmre = $vm | Get-VMResourceConfiguration
if ($vmre.MemLimitMB -ne ‘-1’){
$rp = $vm | Get-VMResourceConfiguration
$rpvmmb = $rp.MemLimitMB
if ($vm.memorymb -ne $rpvmmb){
write-host $vm ", mem granted= " $vm.memorymb ", mem resources = " $rpvmmb
}}}
[/powershell]