We are encountering a strange behavior with Linked Clone pools: Linked Clones Win 10 (1903) machines are unable to set resolution above 1280x1024 only using the Horizon Client while displaying correctly in FHD using Zero Client(!). Normal (not linked clones) Win 10 VMs from the same image work correctly using Horizon Client and Zero Client. All machines are in the same OU. Manually selecting FHD resolution from the settings within WIn10 on the linked clone VMs temporarily expands to FHD but within a split second are resized to 1280x1024 as if it were forced by a policy but there is no such policy enforced (the ordinary non linked clone machine works fine in the same OU. If one doesn't keep the window size below this limit the machine attempts to constantly resize to the imposed higher resolution (to no avail) and becomes unresponsive temporarily. Latest Horizon (7.9) version and Win10 build 1903. Any pointers to what could be causing the issue?
It is not a video memory RAM problem (I checked and the settings are the same for the working standard vms). I tried even setting 4K res in the pool settings, shutting down and letting Horizon reconfigure the machine - no difference.
Thanks for any feedback.
***Update: I resolved it by uninstalling the horizon agent and reinstalling it on the master image, retook the snapshot and recomposed and now it resizes correctly with the horizon client. I have no idea why it didn't work *just* with the client in the first place but evidently something didn't go quite right during the agent installation!