![]() ![]() No matter which account I use (local "Administrator" or other user with Administrator rights). Check if you have local administrator privileges on computer XXX. ![]() I'm trying to add physical machine (with Hyper-V role and many VMs) to Veeam Managed Servers, and it fails with error: many other Windows & Linux VMs running on Hyper-V VM (MSSQL 2016) - Windows 2019 Standard, standalone (non-domain) - for DBs, also for Veeam's DB VM (Hyper-V) - Windows 2019 Standard, standalone (non-domain) - for Veeam Community, latest version physical machine - Windows 2019 Standard, standalone (non-domain), for Hyper-V Virtualization with Hyper-V role installed ![]() I don't have to install a Veeam agent on the Hyper-V host do i? Side note at 1 time there was a hyper-V management or something like that in the programs/features on the Host which I uninstalled hoping maybe that was the issue and it would just re-add it. I've tried turning off the windows firewall but still get the same message. After I open VBR go to backup infrastructure > add server > Microsoft Hyper-V > Hyper-V then It ask for the DNS name or IP which I input the LANIP > Choose Microsoft Hyper-V server (Standalone) > added the administrator credentials for the Hyper-V Host 2012R2 (i've tried both servername\administrator and just administrator) but i get the error above. I have VM setup with Server 2016 Standard that I've installed Veeam Backup and Replication Community Edition. The scenario I have is a Windows Server 2012R2 Standard running Hyper-V (not attached to a domain). I'm getting failed to connect to host LANIP Access Denied or timeout expired.Ĭheck if you have local administrator privileges on computer LANIP.Ģ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |