@jaredbusch I guess I just thought that since this was a trial I shouldn't mess up my existing domain.
I will add the host to the domain.
@jaredbusch I guess I just thought that since this was a trial I shouldn't mess up my existing domain.
I will add the host to the domain.
@obsolesce I think I'm getting closer. I updated the local group policy and on the desktop and ran your commands on the host. Now instead of You do not have access rights to Logical Disk Manager on..I am getting "unable to connect to virtual disk service"
Are you connecting as a user that has permissions on the Hyper-V host? Not sure. I am logged into my domain user on the desktop and created a user with same name and password on host. that may not be enough. Is there a run as option for opening computer management?
@obsolesce Windows Remote Management was already set to automatic. Plug and Play was running but wasn't set to automatic.
How do I allow remote access to Plug and Play interface?
(BTW I plan to archive this whole thread for reference)
@obsolesce I have considered KVM but for now am trying Hyper-V. I still plan to load KVM on an old desktop when I get a chance.
@lj Just ran winrm qc on both. Each one said "WinRM
service is already running on this machine. WinRm is already setup for remote management on this computer"
@obsolesce Thanks. I've done a lot of those but actually can't remember all of them right this second. I think most of those were required for Hyper-V manager, Windows Admin Center and the parts of Computer mangement that do work.
I'll start through your list and try to see what I've missed.
@obsolesce The Win10 is and the HyperV host is not.
@lj The message when attempting Disk Management is "You do not have access rights to Logical Disk Manager on...
@obsolesce That is the one thing I haven't been able to get working. computer management will allow some of the functions like users and groups but the disk management won't work and I've tried a lot of googled solutions. Most of them are Powershell commands to run on both machines. None of them have worked.
Starting over may be good experience anyway. I will backup my VMs with Altaro and also with Hyper-V manager if I figure out how. If I lose the VMs I still wouldn't be in too bad a shape.
Thanks for everyone for everything I've learned so far. Here is my next problem. I decided to expand my volume the Hyper-V OS is on. I was able to use Diskpart to shrink the other volume but was unable to extend the OS volume. They must not be adjacent but without Disk Management I don't have a visual. I tried booting Gparted and Partition Wizard mini tool. Neither would boot. They may be a few years old. How can I extend the volume?
@black3dynamite I like it so far. I can't remember why I tried it instead of Veeam but to seems to work fine. I haven't tried a restore from it yet.
@dustinb3403 Any reason you would prefer UrBackup over Altaro Free or Veeam free?
@brrabill Thanks. I haven't got there yet but I assume there is a way to change the size of all the drives without starting over.
@dustinb3403 I'm not familiar with UrBackupPC. I'll read about it. We should be getting way faster broadband in the next year and by then I hope to have the old server with Hyper-V installed and have it in a branch that has a locked room available. My current thoughts are to install a Guest OS there and have a scheduled backup of some kind from the new server to the remote one. I have a Dell Rd1000 removable HD built in the new server and Altaro seems to use it ok.
@dustinb3403 Yes, Microsoft Hyper-v Server 2016, not Windows server
@dustinb3403 Thanks. Dom0 is the Host, right?
Our setup: public library system- 5 staff at HQ-currently using WinServer 2088R2 with AD
Primary use is file storage
We have purchased new hardware and Windows Server 2016 licenses and CALs
new hardware: dell T330, 16 GB ram, 2 TB hard drive, Intel(R) Xeon(R) CPU E3-1220 v5 @ 3.00GH
Hyper- V server 2016 installed, 5nine manager installed ,Altaro backup installed
Hyper-V manager connecting remotely from Win10Pro desktop
Windows Admin Center connecting remotely from Win10Pro desktop
2 VMS running Windows Server 2016 not activated yet or in use. I can blow this away and rebuild if necessary
My starter questions:
RAm allocation. For instance if each VM got 6B does that leave 4 for the hypervisor? Is there any good rule of thumb?
Hard drive. I have 30GB on C:\ where the Hypervisor OS is installed and most of the rest on F:\ where the virtual disks for the VMs are. Is the 30 too small, too large, about right for Hyper-V OS?
Do checkpoints recover all files or just OS files (kind of like System Restore in desktops)?
I welcome any feedback I am just starting in Virtualization. More questions to follow.Some days my replies will be slow.
The rd1000 with a disk in the slot shows up as D:. When I tried to use diskpart to set it offline it says "Virtual disk service error: the operation is not supported on removable media".
I don't think Hyper-V manager is going to let the VMs attached to it unless it is offline. Catch 22.
I think the RDXutility is the only way I will get this going. Thanks to everyone for your help so far.
@lj Got ahead of myself. It did install without .net. It just won't run. I cd to the directory and type RDXutility.exe but nothing happens.