VMWare vSphere VM options disabled

[Iteeee]

Hi,

Yesterday, i have migrated VMs from Hyper-V on my VMWare, everything worked fine.

But now, i realized that on all my migrated VMs i can't modify anything. When i open the VM parameters, the "OK" button is greyed out as well as some others parameters.

If i connect directly on the ESXi host, here, i can modify normally.

I have try to follow this articile, https://kb.vmware.com/s/article/2048748, but i think i have no problem in relation with it.

Can somebody help me with this case please ?

[e_espinel]

Hello.
Welcome to VMware.
It requires the version and Build that is installed on the vcenter server and ESXi host.

What browser are you using? Have you tried another browser (for example Firefox ESR).

[Iteeee]

Hi,

About my vcenter : 

• Version :7.0.2
• Build :17958471

About my ESXi

VMware ESXi, 7.0.2, 17867351 

But i am able to modify options on an other VM who wasn't migrated. I have tested on Firefox, same issue.

Thank you

[cyberwookie]

Did you try with the administrator@vsphere.local account? 

Also what HW version do the VM's get after conversion to Vsphere?

[Iteeee]

Yes, i am connect with the local admin. administrator@mydomain HW, you mean compatibily of the material ? If it's correct i am in version ESXi 6.7 et versions ultérieures (VM version 14). But i already tryed to upgarde it to the last version ESXi 7.0 U2 et versions ultérieures (VM version 19) but always same issue.

[cyberwookie]

Then security should not be the culprit.

Can you remove the VM from inventory, and then add it again from a local ESXi host?

And could you please post the .vmx file of one of your troublesome vm's?

[Lalegre]

Hey @Iteeee,

Try to take a snapshot of that VM, delete all the snapshots and try the modification again.

Let us know how it goes.

[Iteeee]

Hey,

I just tryed your solution , but same.

[Iteeee]

Already try it, same, can't modify the settings...

You can find attach at this mail a .vmx file that doesn't work.

[e_espinel]

Hello.
Based on your comment that when you connect directly to the ESXi host you can modify the VM parameters, then you could try the following on an individual basis:
1. remove the ESXi host from the vcenter, reboot the ESXi Host and then log it back into the vcenter Server.
2. On one of the VMs with the problem, uninstall the VMtools, reboot it and then reinstall the VMtools.

[cyberwookie · Accepted solution]

ok, one of the things i see in the VMX is the presence of a E1000 card.

Please remove it (if you can actually still remove devices from the VM)

It also complaints about the CD drive, better remove this as well

If that still does not work, you can do 2 things:

1) Replace the VMX with my VMX:

I run your VMX through my VMware ESXi, 7.0.2, 17867351 machine.
The moment i registered it, it changed it a little bit, that might just do it.
I can edit the VM (ignore the 0 Mb disks in the screenshot)

2) Create a clean windows2012 vm and rebuild the VM with the existing disks
- copy the disks to the newly created 2012-vm if you have enough disk space, or move them if you do not
- copy the scsi entries from your converted VM to the new clean 2012-vm

My VMX that is actually editable on my ESXi host:

.encoding = "UTF-8"
nvram = "CT-SRV-UPT-01-Convert.nvram"
svga.present = "TRUE"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
floppy0.present = "FALSE"
svga.vramSize = "8388608"
numvcpus = "2"
memSize = "4096"
firmware = "efi"
tools.upgrade.policy = "manual"
sched.cpu.units = "mhz"
sched.cpu.latencySensitivity = "normal"
scsi0.virtualDev = "lsisas1068"
scsi0.present = "TRUE"
ide1:0.startConnected = "FALSE"
ide1:0.deviceType = "atapi-cdrom"
ide1:0.fileName = "auto detect"
ide1:0.present = "TRUE"
scsi0:0.deviceType = "scsi-hardDisk"
scsi0:0.fileName = "CT-SRV-UPT-01-Convert_3.vmdk"
sched.scsi0:0.shares = "normal"
sched.scsi0:0.throughputCap = "off"
scsi0:0.present = "TRUE"
scsi0:1.deviceType = "scsi-hardDisk"
scsi0:1.fileName = "CT-SRV-UPT-01-Convert_2.vmdk"
sched.scsi0:1.shares = "normal"
sched.scsi0:1.throughputCap = "off"
scsi0:1.present = "TRUE"
serial0.startConnected = "FALSE"
serial0.fileType = "pipe"
serial0.fileName = "\\.\pipe\com_1"
serial0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "V1403 LAN"
ethernet0.addressType = "static"
ethernet0.address = "00:15:5D:0A:E0:05"
ethernet0.present = "TRUE"
displayName = "CT-SRV-UPT-01-Convert"
guestOS = "windows8srv-64"
bios.hddOrder = "scsi0:1"
bios.bootOrder = "cdrom,hdd"
toolScripts.afterPowerOn = "TRUE"
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
toolScripts.beforePowerOff = "TRUE"
tools.syncTime = "FALSE"
tools.guest.desktop.autolock = "FALSE"
uuid.bios = "2c 18 cc 42 d2 50 79 4f-a8 88 75 d3 a9 00 a9 97"
vc.uuid = "50 18 39 3a 57 04 75 ff-51 13 9d e2 5e 91 e4 fb"
pciBridge0.present = "TRUE"
pciBridge0.pciSlotNumber = "17"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge4.pciSlotNumber = "21"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge5.pciSlotNumber = "22"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge6.pciSlotNumber = "23"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
pciBridge7.pciSlotNumber = "24"
cpuid.coresPerSocket = "2"
scsi0.pciSlotNumber = "160"
veeamIrMountId = "120780fe-c358-4343-ad3e-3782a976281f"
ethernet0.pciSlotNumber = "32"
monitor.phys_bits_used = "45"
numa.autosize.cookie = "20022"
numa.autosize.vcpu.maxPerVirtualNode = "2"
scsi0.sasWWID = "50 05 05 62 d2 50 79 40"
softPowerOff = "FALSE"
vm.genid = "8439165403742171507"
vm.genidX = "-2560593216616970051"
vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "8388608"
toolsInstallManager.lastInstallError = "0"
toolsInstallManager.updateCounter = "2"
svga.guestBackedPrimaryAware = "TRUE"
tools.remindInstall = "FALSE"
guestInfo.detailed.data = "bitness='64' buildNumber='9600' distroName='Windows' distroVersion='6.3' familyName='Windows' kernelVersion='9600' prettyName='Windows Server 2012 R2 Standard Edition, 64-bit (Build 9600)'"
migrate.hostLog = "CT-SRV-UPT-01-Convert-5ac384ef.hlog"
sched.cpu.min = "0"
sched.cpu.shares = "normal"
sched.mem.min = "0"
sched.mem.minSize = "0"
sched.mem.shares = "normal"
migrate.encryptionMode = "opportunistic"
ftcpt.ftEncryptionMode = "ftEncryptionOpportunistic"
sched.swap.derivedName = "/vmfs/volumes/d5ea41ed-fe21067c/CT-SRV-UPT-01-Convert/CT-SRV-UPT-01-Convert-8ed0c751.vswp"
uuid.location = "56 4d fa 16 90 64 d5 6b-6e 8c a9 61 2e 79 13 38"
vmci0.pciSlotNumber = "33"
vmci0.id = "-1459574377"
cleanShutdown = "FALSE"
extendedConfigFile = "CT-SRV-UPT-01-Convert.vmxf"
sched.cpu.affinity = "all"
serial0.allowGuestConnectionControl = "FALSE"
ide1:0.autoDetect = "TRUE"
scsi0:0.redo = ""
scsi0:1.redo = ""
SCSI0:1.ctkEnabled = "TRUE"
SCSI0:0.ctkEnabled = "TRUE"
ctkEnabled = "TRUE"
virtualHW.scheduledUpgrade.state = "done"
config.version = "8"
virtualHW.version = "19"
guestinfo.toolsInstallErrCode = "1641"
guestinfo.driver.vmci.version = "9.8.16.0"
guestinfo.driver.vsock.version = "9.8.17.0"
guestinfo.driver.wddm.version = "8.17.02.0012"
guestinfo.vmtools.buildNumber = "17337674"
guestinfo.vmtools.description = "VMware Tools 11.2.5 build 17337674"
guestinfo.vmtools.versionNumber = "11333"
guestinfo.vmtools.versionString = "11.2.5"
guestinfo.Cb.InstallStatus = "3013"
guestinfo.Cb.LauncherVersion = "1.0.0"
vmotion.svga.mobMaxSize = "8388608"
vmotion.svga.graphicsMemoryKB = "8192"
viv.moid = "6bcac1f0-a7db-4399-b4ad-8fa24c0e9307:vm-16658:tGlUT8FRaZT3NqJ0CG3JU0lsUJi4unhdLDl9aqWzuy8="

[scott28tt]

@cyberwookie 

You could have used a "spoiler" for the VMX content to make it easier to scroll through the thread.

This is the toolbar icon to add a spoiler: 

And this is the effect:

Spoiler

An expandable section for those that want the detail, perfect for VMX content, the output of CLI tools, text from log files...

[Iteeee]

Hello E_espinel,

I tried your both solutions, same again =( 

[e_espinel]

Hello.
In summary only in some VMs you can not modify their configuration from the vcenter server web client.
If you enter directly to the ESXi host, you can modify the configuration of the VMs without problems.

In the vcenter server we use the vSphere client version 7.0.2.XXX that is part of the vCenter Sever.

On the ESXi Host we use the client host (also called web client) client version 1.34.X

I suspect that the problem is in the vSphere client of the vcenter server.

[Iteeee]

Hello guys,

Solution found !

I created a new VM without drive and i attached the existing vmdk of an failure VM.

I did a Vmotion of storage right after, and now i have the vmdk rename in my VM's folder, perfect.

Thank you everybody for help