Re: Windows Server Hyper-v 2012

0 views

Skip to first unread message

Message has been deleted

Melva Simons

unread,

Jul 12, 2024, 8:03:59 AM7/12/24

to gueknifinper

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?

windows server hyper-v 2012

Descargar https://vbooc.com/2yOzbx

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.

When adding hyper-v host server sensor I get an error "Microsoft Windows Server 2019 Datacenter" does not support BytesPersec (Field). This host have another sensors (CPU, Memory, Diskspace) which work fine. Additionally I have another server with Windows Server 2019 Datacenter on it and haven't same problem like this.

I have windows servers 2019 datacenter edition running Hyper-V on and add "Hyper-V Host Server" type sensor. On one of them I get this error ("Microsoft Windows Server 2019 Datacenter" does not support BytesPersec (Field)). Remote Registry Windows service started and runs. Also I have 4 another Hyper-V servers, but have not same issue with them.

File and printing share is active and authorized in windows firewall in the hyper-v 2019 host. i can open the folder \\hyper-v 2019 host\c$ successfully on the virtual machine in which veeam B&R11 is installed.

Yes it is similar account and it is a domain adminitrator account dedicated for veeam installation. i add the account in the local administrator group in the hyper-v 2016 host, the hyper-v 2019 host, Virtual Machine in which veeam is installed. Veeam is installed under the same account.

Well, I assumed what you did was install Windows Server 2019 on a physical host then enabled Hyper-V. Then after, you created a Windows Server 2019 VM and installed Veeam v11 on it and are trying to add the physical Hyper-V host to test with and/or backup VMs on it?

Nothing you shared you're trying to do seems out of sorts. Should work. Not sure what else you can try. At this point, about the only other thing I can suggest is contact Veeam support to check the logs.

Hi @akd79 , as @MicoolPaul already mentioned, perhaps a DNS-issue. Try to use always at first FQDN, verify if a A-record and PTR-records exists in DNS with the correct ip-address. If that is not working, try with IP-Address.

I did notice that to resolve these issues, both servers must be 100% patched and upto date, dont try any other changes, until both physical servers that have the Hyper V Role installed, have been patched and are upto date with the same patches applied, Reboot both severs twice - bingo, should all be working.

while Installing Veeam i get Failed to connect to host
Access denied or timeout expired.
Check if you have local administrator privileges on computer .
Possible reasons:Invalid credentials.

If you are still experiencing the same issue, I suggest checking the HyperV event log. Although this issue can be tricky to resolve, taking a look at the event log will help you save time. Additionally, I found three similar issues related to this problem not been resolved so far. Therefore, I will create a post and link to all three issues for your reference.