![]() ![]() There have been occasional lockups of the VM on shutdown during updates, but "normal" reboots have always worked. Windows server updates, runs, participates in all domain activities just as a server running on physical box or VMware - I haven't seen any performance degradation, issues, or errorsġg. I set mine up joining an AD domain (AD version 2016) which worked fine. You'll need to VNC to complete the setup, install RDP and then you can RDP in. partition/format your drives and run through Windows setup as usual. Drives will appear from the virual disk(s) you selected in the initial VM setup. Pick setup option 2 "manual" for new Windows installation, then you'll have to load the drivers from the VirtIO disk. You have about 1-2 seconds before it times out and fails to bootġf. Press ENTER, then be ready to hit any key to boot from the Windows ISO CD. ![]() Once you see the UEFI boot menu, select Boot from device, pick the virtual CDROM with the Windows image loaded on it using arrow keys. It appears to be a try-it-until-it-works type of thing depending on your browser/screen setupġe. I had to go into the VNC details of the VM (from TN CORE main panel menu: Virtual Machines / Select VM / Devices / VNC / 3 dot menu on the right / Edit / Resolution) and change resolution to 640x480. The UEFI boot menu appeared scrambled and unreadable. Anything you type or press in there does nothing - just wait for the countdown, then type EXIT, press ENTER, and the UEFI boot menu apearsġd. On powerup, there is a text-mode boot menu where it counts down (the Windows setup doesn't appear). I had to download the VIRTIO-WIN from, version 0.1.240, create a 2nd virtual CD and mount the image before starting installġc. Disk driver was set to VirtIO, but Windows installer ISO contained no valid drivers. The VirtIO driver was never detected by the OSġb. NIC driver needs to be INTEL E1000 in order to work. (VNC still enabled from setup, but using RDP to get in now).ġa. Installed Win Server Standard from ISO (en-us, 16 core) as 1 vCPU/8core/2thread with 48GB RAM, 1TB vdisk partitioned as 3 user partitions (200/200/600 GB). I'm having a failure during installation of MS SQL Server 2022 (Developer free edition) on Windows Server Standard 2022 as a VM on TNAS CORE 13.0-U5.3.ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |