Windows Hyper-v Server Iso
Chara Fiebig
Seems like there is a lot of confusion here, windows Hyper-V Server is based on a stripped-down version of windows server 2019 or whatever the main LTS server channel is at the time.
When you download the ISO it will install just like windows server 2019 but will have the Hyper-V kernel running by default, but with standard and Datacenter this does not occur until the Hyper-V role is enabled on standard or Datacenter the OS becomes what is called the root partition. SIde not Microsoft did a push to the Linux kernel for Hyper-V that would allow the root partition to be Linux instead of windows.
Other features that would normally be available in a windows server 2019 standard or datacenter will be missing such as AD, Storage Spaces Direct on Windows Hyper-V Server. However standard storage spaces will be available as well as Failover Clustering. The thing with the Windows Hyper-V server is that the guest OSs are not licensed. With the server 2019 standard you get two Guest licenses and the data center edition, grants you an unlimited number of guest licenses. If you plan to not run a VDI solution IE win10 or Linux on top of it the cost of licensing each VM becomes cost-prohibitive vs just obtaining a standard or Datacenter License.
Should I set up a DC and File Server running together on the bare metal, or should I use the virtualisation licences that come with Windows Server 2016 Standard to run just Windows Server + Hyper-V on the bare metal and create a separate VM for each of the Domain Controller and the File Server?
I'm aware that 16 GB RAM is not a huge amount, and there's a fair bit of overhead with running 3 copies of Windows vs just one - more RAM is fairly easily sourced though if this is the only limitation. I would reserve 2-4 GB for Hyper-V, 2-4 GB for the DC and 8-12 GB for the File Server.
There are a pair of 1 TB disks mirrored for the boot drive, were I to go the virtualisation route then I would create another partition on the boot drive formatted as ReFS to hold the C: drives for each of the VMs.
I would lean towards virtualizing it since it afford you more flexibility. If the hardware gets marginal, or if there's an issue the manufacturer can't/won't resolve, then you can just do an online migration to another hyper-v server.
Do not use DFS-R. It's inability to replicate open files and awful switch-over logic (DFS-R doesn't know which server has the latest consistent data) can lead to very bad results, especially, in virtualized environments.
2) You can use Hyper-V as a file server but make sure you have it properly licensed, just using free Hyper-V will require you to at least buy CALs. I'd talk to your Microsoft sales rep with EULA in hands.
Actually, you could create Free SMB3 File Server on Hyper-V 2016.2016 Server has been specifically developed and created only for virtual machines. According to Microsoft EULA, it is not recommended to repeat the steps below, because this process is a violation of the license agreement. The reason why we can create SMB File Share on Hyper-V 2016 is simple: all Windows servers require SMB 1/2/3 to work, and Hyper-V 2016 is not an exception. But it does not mean you should create any unsupported Microsoft services on GUI-less Hyper-V 2016.
In your case, not using virtiualization seems like a waste of resources and also limits how much you can accomplish without needing to purchase additional hardware/servers. Also, DFS Replication requires Active Directory Domain Services so you'll need to create an AD domain.
Hello..We do a lot of Hyper-V installations with many Windows VM Guests and have started installing Sophos Advanced Server Advanced-X on the Windows VM's and all is well. However, I have been reading where Sophos Central Server Advanced is NOT supported on Hyper-V. Specifically a Hyper-V host such as 2012, 2016 or 2019 with the GUI installed and the Hyper-V Role installed. There is not support for that.
Now to me this is a huge vulnerability especially if the Hyper-V host is on the domain. Does Sophos have any solutions for this I am not seeing in their portfolio? Do we need to need to move those Hyper-V hosts into their own workgroup or possibly DMZ?
When you say Hyper-V host such as 2012, 2016 or 2019 with Hyper-V role means you have datacenter (or any other) edition and you have enabled Hyper-V role on that server. Am I right? Or do you mean standalone Hyper-V hypervisor?
Thank you for your response. Yes. You are correct. I am NOT referring to the stand alone hypervisor (core). I am referring to a windows server standard or datacenter version running the full GUI and have the hyper v role installed.
Microsoft offers the standalone Hyper-V server for free. I'm wondering if I can install roles other than the Hyper-V role on this? I know installing other roles alongside Hyper-V is a bad practice, but what I'm trying to ask is if the Hyper-V Server edition of Windows Server allows installation of other roles, like DNS server, File Server etc. Infact I'm not interested in running Hyper-V, just looking for a free windows server to install some roles on.
Hyper-V Server is a dedicated stand-alone product that contains the hypervisor, Windows Server driver model, virtualization capabilities, and supporting components such as failover clustering, but does not contain the robust set of features and roles as the Windows Server operating system.
The reason MS offers this functionality is to seriously compete with the likes of VMWare, Xen, etc. If MS allowed other services like Active Directory, File Sharing, etc to run as a part of Hyper-V standalone - what reason would anyone have to purchase licenses for Windows Server? I think Microsoft got into the enterprise VM market a bit late, but Hyper-V standalone is sure to give them a foothold to build from for the future. I personally use Hyper-V at work and could not imagine how I would manage the same number of machines if they were physical boxes.
I have setup a new server on our network. Connected to domain, network, hyper-v installed and I am unable to add this server to the Virtual Infrastructure > Microsoft Hyper-V > Standalone Hosts > (server). I have my Veeam server trying to contact our new server and there seems to be a road block. I am running Veeam V11a trying to setup a new 2019 windows server. During the hyper-v setup process I have added the name and/or IP address, I have selected the last option (standalone) which matches the description of the new server. My credentials do work because I ran a test to setup a VM running server 2019 and I was able to set that up right away. For some reason the physical server is blocking the Veeam connection. Is there a firewall exception I need to add? I did attempt to manually add the physical server to Veeam so the agent might create its own firewall exceptions. I was unsuccessful at that as well.
This may seem weird, but try something for me. The domain password you are using, type it into Notepad++ on the local host/server/hypervisor you are using, copy it, and then paste it into the credentials setup in Veeam on the backup server, and then save the credentials. Weirdly, sometimes copying and pasting is the best way to deal with passwords in VMs. Caps lock may be on, something weird may be happening behind the scenes. It is a best practice taught to me by an IT veteran. It sounds dumb, but give it a shot.
but there's no option to team NICs anywhere. I've also check with: Microsoft System Center, Virtual Machine Manager 2008 R2... Nothing. I need it for network redundancy, especially given the fact this server got 4 NICs
Yes, you need to install the Dell driver, if it is not already installed because Microsoft officially doesn't support teaming. You can do it on driver level and it will be transparent for Windows. I already did it on my PE2950 and on R710 should be the same.
If you already installed your Hyper-V, you cannot do the teaming without first removing the Hyper-V from the NICs, I think. After the teaming is done you will have to bind your Hyper-V to the team again.
Correction: I am sorry, I think, I misunderstood: are you asking about the free Microsoft Hyper-V Server or about the Windows Server 2008 with Hyper-V? Within Microsoft Hyper-V you cannot do teeming, you need a full OS to install the Dell Broadcom drivers.
nop, I'm using Windows Hyper-V server R2.. its a free version of windows 2008 r2, but with only hyper-v role, and with no GUI. similar to core versions, but only hyper-v role. I got it from technet or msdn. but by now, you can order a swerver with 2008 R2. its out already, in all channels, including retail, oem, eopen.
now few updates. Till now, I converted 10 machines into the hyper-v server. I tried many ways to use broadcom tool for the teaming. but even when I got the teamed NIC working, (yes, it's possible!) and after I assigned it to virtual machines, i had no net communication inside the virtual machines.
I spent many hours trying to solve it. My guess its not working, coz the hyper-v role was installed before the teaming. and of course, the problem is, the role comes build-in with this version of windows, and can't be re-installed, as far as i know.
Since than, I've installed Windows 2008 R2 enterprise server w/ HYPER-V role instead of what I had before. I did that because I had Blue Screen boots every 2-3 weeks on the host server. since than, I discovered that it didn't helped me with the boots, and I'm trying now this KB: -us (apparently there's an errata with Intel xeon 5500 cpu family. anyway, I'm now waiting to see if it solved the problem.)
Back to the teaming issue. On my first installment of windows hyper-v 2008 r2, I eventually succeeded to install broadcom BACS. Which didn't helped me. well, there was nic teaming, and I could create a virtual network on the hyper-v, and apply a virtual machine to it. But on the virtual machine, there was no communication working at all. tried latest version and different versions of BACS and the driver.
d3342ee215