Skip to main content

VMware Workstation自动打开vCenter虚拟机的控制台

如果你的Windows 10电脑上装了VMware Workstation和VMware Remote Console,当你在vSphere Web Client里打开运行在vCenter上的虚拟机控制台时,VMware Workstation可能会代替VMware Remote Console自动连接到控制台。恭喜!你的VMware Remote Console被劫持了。这个问题解决起来比较复杂所以我叫它“劫持”。



English Version

网上有一篇文章谈到这个问题。VMware Workstation 12 Hijacks VMware Remote Console. 但不知道为什么在我的Windows 10电脑上没法修复。研究了一下,最终找到了一个解决方案。

  1. 找到VMware Remote Console执行文件vmrc.exe的路径. 比如我的路径是 C:Program Files (x86)VMwareVMware Remote Consolevmrc.exe

  2. 运行 regedit 打开注册表编辑器.

  3. 在 HKEY_CLASSES_ROOTvmrc 下把 DefaultIcon 键值改为"C:Program Files (x86)VMwareVMware Remote Consolevmrc.exe" "%1"

  4. 在路径 HKEY_CLASSES_ROOTvmrcshellopen下把 command 键值改为"C:Program Files (x86)VMwareVMware Remote Consolevmrc.exe",0


注意 :在这两个键值处只可修改路径不可以修改其他参数。

现在再试试看。

如果你的Windows 10和我一样装了VMware Workstation、VMware Remote Console、VMware vSphere Client、VMware Client Integration Plug-in等,那这个问题基本无法避免,因为VMware对于这几个软件在同一台电脑的安装是有顺序要求的。依次是VMware Remote Console → VMware Workstation → VMware vSphere Client → VMware Client Integration Plug-in。具体参考VMware知识库Installing the VMware Remote Console fails with the error: VMInstallHcmon - Failed to install hcmon driver. (2130850)

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 https://repo.ius.io/ius-release-el7.rpm yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm yum -y install https://packages.endpointdev.com/rhel/7/os/x86_64/endpoint-repo.x86_64.rpm yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.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 = "https://app.terraform.io/api/v2/organizations/ZHENGWU/organization-memberships?page%5Bsize%5D=100" 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 $Test.data.attributes.email