I’m sure you have ever faced a situation like my customer was getting some days ago using VMware Horizon during a PoC: Numlock seems to be ON (based on the keyboard led indicator on tradicional keyboards), number pad is not working but when you disable Numlock, numbers start working properly. This makes nightmares sometimes, isn’t it?
You might be realizing how to overcome this problem when you’re using a virtual machine, right? So, with this tip using BIOS configuration and Dynamic Environment Manager (DEM) makes its work nicely to solve this!
All you need to do is follow these two steps:
1) Configure Boot Options (if using BIOS instead of EFI mode)
Note: In case you are using EFI Mode, you can jump this section and move to next one.
In some cases, customer are still using Windows Server 2012 R2 into your datacenter and application under RDSH, that’s was my customer scenario. This operational system uses BIOS instead of EFI mode, so one configuration needs to be done first:
- Open Edit Settings into Virtual Machine side
- Select “Force BIOS setup”, so next boot virtual machine will stop into BIOS screen
- The following screen will appear. Select Keyboard Features
- Select NumLock and set it to AUTO
- Exit saving changes and power on the virtual machine
2) Configure DEM to Apply Registry Entry
- Open Dynamic Environment Manager and let’s create a Registry Settings
- Create a Name for your Settings according the following screenshot below. Let’s add the following entrance into Regedit settings:
Note: Don’t select Run Once
Windows Registry Editor Version 5.00
With that configuration, you’ll not have anymore this problem and all users will be connecting through VMware Horizon without any inverted actions caused by Numlock.
Tip: If you don’t have Dynamic Environment Manager into your license, you can configure it through Group Policy if you want to.
Thanks! Enjoy the ride!