How To Change Screen Resolution In Windows Server 2016
Hi Didi7,
To make sure we're on the same page is this where the option is greyed out?
+ii
Hello Alona, no information technology is non inside the UEFI configuration, you are stuck at display resolution 1280x1024 inside Windows Os.
+2
Changing resolution inside UEFI-configuration is possible but has no effect during installation. The whole installation process of a Windows VM tin but exist done with 1280x1024, and then y'all are forced to employ big monitors to succeed with the installation of Windows Server 2016 and as you cannot change the resolution during installation, you are as well stuck at 1280x1024, when Windows is fully installed and Nutanix Guest Tools, likewise every bit VirtIO drivers are installed.
Really, that's so abrasive and really not resonable to customers.
Might be fixable with an Nutanix brandish driver, don't know?
Using non-UEFI VMs during installatation of Windows Server 2016 results in the same Monitor and brandish driver, but you can change resolutions.
Is there a solution from Nutanix bachelor or is this a known bug?
Does there exist a work-effectually?
Would information technology be correct to say that the outcome you are experiencing is when connecting to the VM past using "Launch console" feature in Prism? When using "Launch console" screen resolution is picked upward from UEFI settings and Windows commuter does not have the ability to change that setting. Therefore, you would need to change the resolution settings in UEFI in order to touch on VNC connection resolution.
The matter is, VNC is intended for troubleshooting, debugging and such rather then every bit a all time access tool.
Does the issue appear when you connect via RDP mail service the installation? RDP is using a different driver hence y'all should be able to arrange the screen equally required.
Have you considered deploying VMs from an image? This way you tin can skip the installation phase entirely and make it at initial set upward. I would recommend to sysprep the OS prior to making an image out of it. AFAIK, sysprep defaults the resolution to 1024 ten 768 – something to keep in listen.
Hither is a KB describing the consequence that you encountered specifically KB-4792 AHV | How to change display resolution on Windows VMs running in UEFI mode.
+ii
Quote: Would it be correct to say that the upshot you are experiencing is when connecting to the VM by using "Launch console" characteristic in Prism?
Yes admittedly, but equally long equally there is no network connexion, one is forced to apply the VNC Panel until everything is setup and I am talking about VM-template generation, where in that location are no network connections availaible, as here they stay disconnected. Updates, like Cumulative Updates in Windows Server 2016 are done via ISO medias. Later on syspreping and cloning those VM-templates, they get connected to networks and so RDP is used of course.
I really know a lot of Hypervisor platforms and have xv years of experience with VMware and the likes, only never had any problems to change the brandish resolution via the console, even if it's only 640x480 and a change to 800x600 is only possible, but that I am forced to change the display resolution in the UEFI-firmware and that display resolution change within Windows is no longer possible, is unique to Nutanix AHV VMs imho!
Of form, if you utilise RDP, the client defines the resolution, that's not the question I originally had.
And yes, afterwards those templates are generated (without any network connection) and completely configured for further distribution, those VMs are shutdown with sysprep and generalized!
I decided to go along to create not UEFI-firmware Windows VM-templates at the moment, because this display resolution problem is annoying. Unfortunately I am forced to transfer some Hyper-V Generation 2 VMs to Nutanix AHV and there I will attempt to ready the default resolution to 1024x768 in UEFI-firmware, but iirc this had no effect to how the Windows setup display resolution came up, merely equally I am unsure, I volition give it some other endeavor.
Regards,
Didi7
+two
Ok, I continued my tests on UEFI-firmware based Windows 2016 VMs and finally plant out, that brandish resolution in Windows 2016 VMs simply changes, when changing the default resolution in UEFI-firmware and merely if you lot enter UEFI-firmware configuration afterward a reboot and go out. The display resolution changes to the one you choose in UEFI-firmware.
As soon as y'all power off the Windows Server 2016 VM again, the display resolution returns to 1280x1024 once more and cannot be changed within Windows. If you reboot (not ability off) the Windows 2016 VM, enter UEFI-firmware with F2 and exit once more, the display resolution changes again to the 1 you chose in Nutanix UEFI-firmware settings.
That's what I telephone call abrasive and should be changed from Nutanix asap, but mayhap I am the only 1 claiming information technology's annoying, at least in our company several users find it annoying.
Whatever comments from Nutanix are welcome!
Regards,
Didi7
+4
I sympathize your concern and have tested the same in my lab on AOS v.15 with AHV20170830.395. This indeed is a necessary characteristic and works well in Hyper-V and VMWare. As you lot take mentioned its specific to UEFI and LEGACY VMs doesn't testify the behaviour. Information technology'south because, to change the display resolution, legacy Graphics cards based on VGA standard exposed their helper routines via VGA BIOS. OS drivers would raise a BIOS to interrupt INT 10H for the corresponding VGA bios routine to be invoked, which would in turn phone call into the firmware helper for driving the menu in a item resolution.
With UEFI, there is no VGA. All UEFI-compliant cards provide GOP protocol handlers to drive the bill of fare accordingly for changing display resolution.
To fully implement dynamic resolution irresolute capabilities, the Bone driver must be able to telephone call into platform firmware (BIOS or UEFI) at runtime (using VGA or GOP). Notation that in the absence of resolution change capability, the invitee Os volition accept to inherit any resolution (and hence framebuffer size) the firmware had initially set for information technology while setting upwards the display device at boot.
+ii
Hi Sudhir,
interesting! Well, other Hypervisors like Hyper-V and VMware have no display resolution change bug with UEFI-VMs nether Windows Server 2016.
Lets see how Nutanix can fix that!
Regards,
Didi7
is in that location an update yous can provide on this enhancement?
Not that I know of :(
Cool! Thanks for bringing this to their attending. I had searched earlier with no real results; I guess this time I entered in the right search words. I went in and updated the resolution, for now, it works.
+ii
Well, yous tin modify the resolution in the UEFI-BIOS but as presently every bit you power off the VM the old resolution of 1280x1024 is back.
Good luck!
Howdy is there a gear up for this yet? Information technology seems to exist the same with a windows 2019 datacenter server with UEFI-BIOS.
Cheers
Source: https://next.nutanix.com/server-virtualization-27/display-resolution-in-windows-server-2016-ahv-vm-stuck-to-1280x1024-37546
Posted by: willinghammandked81.blogspot.com
0 Response to "How To Change Screen Resolution In Windows Server 2016"
Post a Comment