Cannot login vpxuser

I was connecting via console to one of my VMs when I noticed that the console was not connecting and was returning an error. I went in to check the host events and I noticed loads of errors, one every a few seconds, regarding the vpxuser’s login. I wasn’t alerted as the ESXi host isn’t in production yet, so wasn’t monitored.

The error I saw in the events, once I connected to the ESXi host itself was: Cannot login vpxuser@127.0.0.1.

cannot_login_vpxuser

From vCenter instead I was seeing another error stating “Cannot synchronize host ESXiHost.itdtroplets.com. Cannot complete login due to an incorrect username or password.

cannot_synchronize_host

There are a couple of things you may try, start with the first one as it’s simpler. A reboot did not work for me.

Disconnect/Reconnect the host in vCenter

  1. In vCenter, disconnect the host by right click on it and selecting Connection > Disconnect.
    • vcenter_disconnect_host
    • Note that the host might already be disconnected.
  2. Now connect to the ESXi host via the Console and press F2 to enter the System Customization.
  3. Access the Troubleshooting Options menu.
  4. Select Restart Management Agents.
  5. Go back in vCenter, right click on the host and select Connection > Connect.
    • This might ask you to specify again the username and password to use to connect to the host and throughout the Wizard you’ll see the host summary and its VMs.

Disconnect the host in vCenter, delete the vpxuser and reconnect

  1. In vCenter, disconnect the host by right click on it and selecting Connection > Disconnect.
    • vcenter_disconnect_host
    • Note that the host might already be disconnected.
  2. Connect to the ESXi host with the vSphere Client.
  3. Click on Users’s tab.
  4. Right click on vpxuser and select Remove. Confirm when prompt to remove the user.
    • esxi_remove_vpxuser
  5. Now connect to the ESXi host via the Console and press F2 to enter the System Customization.
  6. Access the Troubleshooting Options menu.
  7. Select Restart Management Agents.
  8. Go back in vCenter, right click on the host and select Connection > Connect.
    • This might ask you to specify again the username and password to use to connect to the host and throughout the Wizard you’ll see the host summary and its VMs.
    • This step will also re-create the vpxuser.
    • Should this step fail, try one more time to restart the management agents and to connect.

 

Read More

Migrate a MAK Windows key to KMS

This is meant to be a very quick guide to show how to migrate from a MAK Volume License key to a KMS activated Volume License Key. This is sometimes necessary within a big company where sometimes, in order to quickly test a new product, a MAK key is used. For instance, quite a few people had to do this for Windows 10, especially because earlier versions of Windows running as the KMS server weren’t supporting yet the new OS.

The procedure is very simple. You will need:

  • The volume license key to be retrieved from Volume Licensing Service Center.
  • Admin rights on the machine you’re going to migrate from MAK to KMS.
  • Run Slmgr.vbs /dlv before and after the procedure (take a screenshot of the output) to see the differences.

Let’s start:

  1. Open a command prompt with elevated rights (Run as administrator or Run as a different user and sign in with the admin account).
  2. Run

    Obviously, replace MYKEY-MYKEY-MYKEY-MYKEY-MYKEY with the key you’ve retrieved from the Volume Licensing Service Center.
  3. Run

    Note that this might fail with an error telling you that an activation is already in progress. If that’s the case, wait a few minutes.
  4. You are done. You may run Slmgr.vbs /dlv in order to check that all is in order. You’re goin gto be able to see that Windows is now activated with the VOLUME_KMS key.

Read More

Add Windows 10 key to existing Windows Server 2008 R2 KMS

Adding a Windows 10 key to an existing Windows Server 2008 R2 KMS should be easy enough but for some reason I found a lot of users on forum having issues with this. There was also a lot of bad information which I think are related to the fact that Microsoft didn’t include old KMS servers from the start of Windows 10’s era. This article has been written on the 1st of November 2016 and at today the steps to add a Windows 10 key to an existing Windows Server 2008 R2 KMS are just a few.

A few notes before proceeding:

  • You will have to follow these steps on all of your KMS servers.
  • slmgr has to be ran from system32 (%windir%\system32).
  • I suggest to run slmgr.vbs /dlv and take a screenshot of the info you see on screen before and after the procedure.
  • slmgr.vbs takes a few seconds before completing.

The procedure

  1. On the KMS server, check if KB3079821 is installed. If not installed it, downloading from the following link: https://support.microsoft.com/en-us/kb/3079821 . A reboot is required.
    • Repeat this operation on all of your KMS Servers.
  2. Now you need to grab the correct key: in fact you will have to get the key called Windows Srv 2012R2 DataCtr/Std KMS for Windows 10 from the Microsoft Volume Licensing Service Center. In order to get that product key, follow the steps below:
    • Log on to the Volume Licensing Service Center (VLSC).
    • Click License.
    • Click Relationship Summary.
    • Click on the License ID of the Active License you own.
    • Finally locate Windows Srv 2012R2 DataCtr/Std KMS for Windows 10‘s key.
  3. We’re ready to install this key by running the following in an elevated command prompt of the KMS Server:

    Needless to say: replace MYKEY-MYKEY-MYKEY-MYKEY with the key you’ve got from Step 2.
  4. You will receive a message that the key has been successfully installed. You will also note that Windows, on the KMS server(s) is no longer activated. Don’t worry, you will just need to run:

 

Test that everything is working as expected

You may test that the newly added key is working fine by installing Windows 10 VL to a new machine or by Migrating an existing Windows MAK key to KMS.

Read More