vCenter Windows Contextualization fails - "No Context CDROM found"

[opennebula2 (sm1705)]

Hi,

i just tried to configure contextualization in a VMware vCenter (6.5) environment for CentOS and MS Windows VMs inside a new (current 5.4) OpenNebula. With CentOS (and other distros) contextualization works fine, as expected.
But with an Windows guest the contextualization is not working. The error reported in the PowerShell output (inside) VM is:

I double checked paths, languages, etc.

I also followed the documentation and installed the *.msi inside the VM.

With older ONE versions (and KVM as VMM) we had to define the files, used for contextualization, in our files datastore. This is just for KVM - AND NOT - for VMware - right?

Best,

Sebastian

[opennebula2 (sm1705)]

Hi all,

i just figured out, that my problem is located in the language of the guest OS.
In the contextualization scripts there is a path to “vmtoolsd.exe” to gather informations via the VMware API.
In a german MS Windows the path is “wrong”. The information was there:

With a “hardcoded” path in “context1.ps” everything works fine.
I’ll try to check this more clearer tomorrow morning - if it’s not my fault i’ll report further informations.

Best,

Sebastian