Help with my first Hyper-V setup
-
There's things you need to do like allow remote access to the Plug and Play interface, open up some firewall rules, allow remote server management through WinRM, automatic startup of Plug and Play service and Windows Remote Management (WS-Management) service, etc.
-
Also, run
winrm qcon both. -
Isn't it a PITA if you're not accustomed to it all?
This is why KVM is so nice.
-
@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. -
@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 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.
-
@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) -
@lj said in Help with my first Hyper-V setup:
How do I allow remote access to Plug and Play interface?
Open up mmc on your desktop, and add the Group Policy Object Editor, connecting to your Hyper-V host.
Browse to:
Computer Configuration/Administrative Templates/System/Device Installationthen enableAllow remote access to the Plug and Play interface.But is that the error you get when trying to access Disk Management of your Hyper-V host remotely?
Are you connecting as a user that has permissions on the Hyper-V host?
There are also some firewall rules that need to be opened for remote Disk Management (on your Hyper-V host).
Remote Volume Management - Virtual Disk Service (RPC)
Remote Volume Management - Virtual Disk Service Loader (RPC)
Remote Volume Management (RPC-EPMAP)Enable-NetFirewallRule -name RVM-RPCSS-In-TCP,RVM-VDSLDR-In-TCP,RVM-VDS-In-TCP -
@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?
-
@lj said in Help with my first Hyper-V setup:
@obsolesce The Win10 is and the HyperV host is not.
Why not? This does nothing but over complicate your set. You already have an AD environment. why are you not leveraging it?
-
@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.
-
@lj said in Help with my first Hyper-V setup:
@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.
It is not like to are adding an AD server or anything. You are just adding another member to the domain. No different than adding a desktop.
-
@jaredbusch OK. I just glanced at Windows Admin Center and Hyper-V manager. How and where do I add the host to a domain? on the AD? command line on the host?
-
@lj said in Help with my first Hyper-V setup:
@jaredbusch OK. I just glanced at Windows Admin Center and Hyper-V manager. How and where do I add the host to a domain? on the AD? command line on the host?
Yes on the host. same as anything else.
You don't add a new desktop form WAC.
-
@jaredbusch OK. I figured it out. Option 1 on sconfig menu. Now I am typing correctly the name of the domain, then trying domain\admin and admin only for the user. After typing the password I get "The specified domain either does not exist or could not be contacted". I am guessing the host needs the equivalent of Network browsing, network neighborhood or something turned on.
-
@lj Never mind. It was the DNS server not set to domain. restarting Host now.
-
@lj I went to Windows Admin Center-Users and Groups. deleted my user. Added my user with full domain name and password. Added that user to the HOST's local administrators. Still don't have permission.
-
I closed Windows Admin Center. re-opened and selected host then manage as and checked use my Windows account. Do I have to log off my Win10 machine or reboot the Host or anything?
-
@lj said in Help with my first Hyper-V setup:
Now instead of You do not have access rights to Logical Disk Manager on..I am getting "unable to connect to virtual disk service"
-
@obsolesce I read the MS thread. VDS was running and set to manual but I restarted it anyway. Still don't have permission. I went back to Groups and added myself to Remote Management Users.
