Hi community
we have a weird issue around VDI horizon
when im entering the horizon desktop on the mechin the num pad works but as soon as i start the word \ any office application
the numlock starts to go crazy and then i need to turn off so it works as numbers as any one run it to any similar issue
Try to set up a Registry setting in DEM with following key and value:
[HKEY_CURRENT_USER\Control Panel\Keyboard]
"InitialKeyboardIndicators"="2"
Try to set up a Registry setting in DEM with following key and value:
[HKEY_CURRENT_USER\Control Panel\Keyboard]
"InitialKeyboardIndicators"="2"
Hi,
What's your client and agent version?
Could you provide detailed steps to reproduce it?
So far we didn't see it in lab.
i have added the info registry that @lansti shared and for now its looks good
maybe because the office is in Hebrew
my versions are
client-2206
Agent- 8.5.0
Good, if you consider my answer as a solution, please mark it as a solution, so other people can use the same information when they see it work.
I am not the original poster, however we are also having the same issue.
vSphere Client version 7.0.3.01700
VMware Horizon Administrator | 8.4.0 build - 19067837 | Version 2111
We have a Windows 10 23H2 parent image that has the Default Profile provided by Microsoft and a profile for our Administrator. The VM is using EFI not BIOS. When using a snapshot of this VM in a Horizon pool, it creates a new profile for the user that's logging in. When the user gets logged in, the NumLock is off. When you check the HKEY_CURRENT_USER\Control Panel\Keyboard - InitialKeyboardIndicators it is set to 0.
After some research it seems that since EFI doesn't have a numlock option, Windows will default to off on newly created windows profiles.
This is only the case on Non-Persistent (Floating Assignment) VM's due to their new profile creation at login every time. Persistent VMs will not have this issue as windows will remember their previous numlock state.
I have added an attachment that details the Summary of the Horizon Pool that the VM is spun up with.
This also Band-Aid fixed our issue too.
I'm hoping that VMWare will provide a Numlock option to their EFI setup options.
Until then, this is our work around as well.