glanzmann's Accepted Solutions

Disable CSM in the BIOS. Than it uses UEFI which works.
This issue was resolved after I restartet the samba domain controller due to a failed delegation error message during datacore installation. I don't really understand how administrator@vsphere.lo... See more...
This issue was resolved after I restartet the samba domain controller due to a failed delegation error message during datacore installation. I don't really understand how administrator@vsphere.local credentials hangs on the samba ad domains delegation. But somehow it apparently does. Now VMRC is working again.
I should have searched the documenation more throroughly: For all Windows reference machines: a. Download and extract setup\GugentZip.zip from the vCAC installation package into C:\ on the refere... See more...
I should have searched the documenation more throroughly: For all Windows reference machines: a. Download and extract setup\GugentZip.zip from the vCAC installation package into C:\ on the reference machine. This will produce the folder c:\VRMGuestAgent. Note: Do not change the name of the c:\VRMGuestAgent folder. b. In an elevated command prompt, run one of the following commands: (HTTP) winservice -i -h vcac_fqdn[:portnumber] (HTTPS) winservice -i -h vcac_fqdn[:portnumber -p ssl] Where vcac_fqdn is the fully qualified domain name of the vCAC server host, and the optional portnumber is the port number for the ProxyAgentService endpoint on that host. If you don’t specify a port number, vCAC assigns the default port number 80 (HTTP) or 443 (HTTPS) for the ProxyAgentService endpoint. The name of the Windows service is VCACGuestAgentService. The installation log VCACGuestAgentService.log can be found in c:\VRMGuestAgent.
Hello, after leaving the system alone for two hours, the system recovered. My analysis is: I should have not interfered with the data collection and should have waited. Why it takes 22 mintues to... See more...
Hello, after leaving the system alone for two hours, the system recovered. My analysis is: I should have not interfered with the data collection and should have waited. Why it takes 22 mintues to collect the data is not clear however after letting system sitting there for two hours it recovered and started the data collection. Now everything is up and running again. Cheers,     Thomas