Remote Hyper-V Manager Woes
-
Based on a comment in another thread I decided to take a look at MS Hyper-V Server 2016.
Simple to install. I LOVE the feel of it at the console and through RDP. It takes me back to my Dos and Unix days.
Plus, It's almost identical to ScreenConnect Backstage, which is my new favorite place to work.
However........ After a whole week, I still cannot mange it from my workstation.
I have everything except one piece set properly, based on hours and hours of reading and trying.
Is it even possible to manage a workgroup Hyper-V Server from a Domain PC through Hyper-V Manager?
I am getting this error:
An error occurred while attempting to connect to server. "R510-Hyperv". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server. The operation is not supported.That's cool, look what a bunch of hyphens did!
Virtual Machine Management services is running.
I can successfully map a drive to it with Net Use, I can successfully RDP to it, I can ping it by name...... I just can't get Hyper-V Manager to connect to it.
Any ideas? Anyone been here before?
-
I assume you don't want the Hyper-V server connected to the domain for some reason.
There is a guide here by Timothy Gruber which appears to do what you want.
-
@DustinB3403 said in Remote Hyper-V Manager Woes:
I assume you don't want the Hyper-V server connected to the domain for some reason.
There is a guide here by Timothy Gruber which appears to do what you want.
It's just a test box, and honestly, I like to get servers built as far as I can before we deliver them. So joining the domain is something I would prefer to do at a later time; once the server has been delivered on site.
-
@DustinB3403 said in Remote Hyper-V Manager Woes:
There is a guide here by Timothy Gruber which appears to do what you want.
This is the guide that got me past all of the misinformation, and had all the important info left out by MS. This is by far the best write-up out there for a domain connected PC to manage a workgroup Hyper-V Server
-
I'm curious - why are you deploying/testing 2016 instead of Hyper-V 2019?
-
@Dashrender said in Remote Hyper-V Manager Woes:
I'm curious - why are you deploying/testing 2016 instead of Hyper-V 2019?
Good question.
-
@DustinB3403 said in Remote Hyper-V Manager Woes:
@Dashrender said in Remote Hyper-V Manager Woes:
I'm curious - why are you deploying/testing 2016 instead of Hyper-V 2019?
Good question.
But I don't have a good answer....
-
@JasGot said in Remote Hyper-V Manager Woes:
@DustinB3403 said in Remote Hyper-V Manager Woes:
@Dashrender said in Remote Hyper-V Manager Woes:
I'm curious - why are you deploying/testing 2016 instead of Hyper-V 2019?
Good question.
But I don't have a good answer....
Well - it doesn't solve your issue, but it would be worth starting over with the most recent version.
-
Yeah, given that you are not in production yet. More stable, faster, more modern.
-
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
-
@JasGot said in Remote Hyper-V Manager Woes:
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
In Volume License Center? We have it in production, so it is definitely available.
-
@scottalanmiller said in Remote Hyper-V Manager Woes:
@JasGot said in Remote Hyper-V Manager Woes:
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
In Volume License Center? We have it in production, so it is definitely available.
MS has been breaking links lately. VLSC has been up and down.
-
@JaredBusch said in Remote Hyper-V Manager Woes:
@scottalanmiller said in Remote Hyper-V Manager Woes:
@JasGot said in Remote Hyper-V Manager Woes:
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
In Volume License Center? We have it in production, so it is definitely available.
MS has been breaking links lately. VLSC has been up and down.
Ugh. VLSC is such a mess in general.
-
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
In Volume License Center? We have it in production, so it is definitely available.
Eval Center. I'll try VLC now.
-
-
@JasGot said in Remote Hyper-V Manager Woes:
This link works:
https://software-download.microsoft.com/download/pr/17763.1.180914-1434.rs5_release_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISOThanks - Downloaded and installing now.
I have a spare box at the moment - I'm going to so see if I can shuffle some VMs off a 2016 Hyper-V box onto this new soon to be 2019 box.
-
It can be done but requires anonymous access to be enabled on the Hyper-V server (HVRemote is the step-by-step).
We don't do that for obvious reasons.
PowerShell is the best way to manage the server.
Enter-PSSession -ComputerName R510-HyperV -Credential R510-HyperV\Administrator -
@JasGot said in Remote Hyper-V Manager Woes:
@DustinB3403 said in Remote Hyper-V Manager Woes:
I assume you don't want the Hyper-V server connected to the domain for some reason.
There is a guide here by Timothy Gruber which appears to do what you want.
It's just a test box, and honestly, I like to get servers built as far as I can before we deliver them. So joining the domain is something I would prefer to do at a later time; once the server has been delivered on site.
We don't join standalone Hyper-V hosts to any guest domain. That's just asking for trouble on so many fronts.
-
Always an option to make a dedicated domain for Hyper-V, too. Not sure if I'd ever want that. But it works.
-
@scottalanmiller said in Remote Hyper-V Manager Woes:
Always an option to make a dedicated domain for Hyper-V, too. Not sure if I'd ever want that. But it works.
We've been deploying two for a while now in high exposure settings or high risk settings.
For a standalone Hyper-V server though that's a 12lb sledge for a 3" spike. Just a tad.
If running in a standard user session then right click Hyper-V manager and Run As Admin and use the Hyper-V's local administrator for credentials. That may work though I can't remember if it does since we manage everything via local console (RDP) or PowerShell Remote.
