Skip to main content

Virtual Machine Console in vCenter is Opened by VMware Workstation

If you have VMware Workstation and VMware Remote Console both installed on Windows 10 you may see vCenter virtual machine console in vSphere Web Client is opened by VMware Workstation instead of VMware Remote  Console. If you see same case your VMware Remote Console may be hijacked. I call it "hijack" since there is no easy way to revert it back.


There is only one article I found in internet talks about same issue. VMware Workstation 12 Hijacks VMware Remote Console. I tried the way but somehow it doesn't work on my computer. Probably I'm Windows 10. So I dig into it a little bit, found following workaround eventually.

  1. Find where is vmrc.exe of VMware Remote Console installed. In my case it's located in C:Program Files (x86)VMwareVMware Remote Consolevmrc.exe.

  2. Run regedit to open registry editor.

  3. Go to HKEY_CLASSES_ROOTvmrc change the value of key DefaultIcon to "C:Program Files (x86)VMwareVMware Remote Consolevmrc.exe" "%1".

  4. Go to HKEY_CLASSES_ROOTvmrcshellopen change the value of key command to "C:Program Files (x86)VMwareVMware Remote Consolevmrc.exe",0.

Note: You must only change the file path but do not modify any other parameters in the keys.

Now try open the console again.

If you installed VMware Workstation, VMware Remote Console, VMware vSphere Client and VMware Client Integration Plug-in...or these staffs just like me. Then you may have a high chance see the problem. VMware requires a specific order to install these applications on same computer. The order is VMware Remote Console → VMware Workstation → VMware vSphere Client → VMware Client Integration Plug-in。Please refer VMware KB Installing the VMware Remote Console fails with the error: VMInstallHcmon – Failed to install hcmon driver. (2130850) for detail.

Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $