Building a Hyper-V 2016 host Take 2
-
@dave247 said in Building a Hyper-V 2016 host Take 2:
@dashrender said in Building a Hyper-V 2016 host Take 2:
@dave247 said in Building a Hyper-V 2016 host Take 2:
I've successfully added Windows Server Management to my Windows 10 system and am now able to connect to my Hyper-V 2016 server. However, I am having trouble viewing server info such as hard disk space. I get this error when trying to go to disk management:
did you run this command as noted above
Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”Yes, I ran that on the server but not my pc. I just ran it on my Windows 10 pc too and now it works.
THANKS
Do I need to change something in my instructions to make that specifically stand out more?
-
@dashrender said
Do I need to change something in my instructions to make that specifically stand out more?
I would think ... yes?
-
@dashrender said in Building a Hyper-V 2016 host Take 2:
@dave247 said in Building a Hyper-V 2016 host Take 2:
@dashrender said in Building a Hyper-V 2016 host Take 2:
@dave247 said in Building a Hyper-V 2016 host Take 2:
I've successfully added Windows Server Management to my Windows 10 system and am now able to connect to my Hyper-V 2016 server. However, I am having trouble viewing server info such as hard disk space. I get this error when trying to go to disk management:
did you run this command as noted above
Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”Yes, I ran that on the server but not my pc. I just ran it on my Windows 10 pc too and now it works.
THANKS
Do I need to change something in my instructions to make that specifically stand out more?
Maybe, "Run these commands on both server and management workstation"
-
@dave247 said in Building a Hyper-V 2016 host Take 2:
@dashrender said in Building a Hyper-V 2016 host Take 2:
@dave247 said in Building a Hyper-V 2016 host Take 2:
@dashrender said in Building a Hyper-V 2016 host Take 2:
@dave247 said in Building a Hyper-V 2016 host Take 2:
I've successfully added Windows Server Management to my Windows 10 system and am now able to connect to my Hyper-V 2016 server. However, I am having trouble viewing server info such as hard disk space. I get this error when trying to go to disk management:
did you run this command as noted above
Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”Yes, I ran that on the server but not my pc. I just ran it on my Windows 10 pc too and now it works.
THANKS
Do I need to change something in my instructions to make that specifically stand out more?
Maybe, "Run these commands on both server and management workstation"
He does say that. I just think it needs to be highlighted or something because in that block it's easy to miss.
"Remote access needs to be enabled on the machine you're remoting from as well as the one you're remoting too"
-
https://i.imgur.com/DqGo6tP.png
Updated.
-
Just wanted to throw in here that the updates window can lose focus, so if it's been a while ... you might need to hit a key in it.
@JaredBusch said this has been around forever, but this is the only time I have seen it personally, and it just got me again today!
-
Wow thats more difficult than setting up Linux KVM..
To the point that why would you want to do this. -
@emad-r said in Building a Hyper-V 2016 host Take 2:
Wow thats more difficult than setting up Linux KVM..
To the point that why would you want to do this.If you are an All Windows Shop, why would you want to have another technology tossed in?
I'm not saying you're wrong, there are just places that prefer to stick to one vendor/tech tree.
-
@dashrender said in Building a Hyper-V 2016 host Take 2:
@emad-r said in Building a Hyper-V 2016 host Take 2:
Wow thats more difficult than setting up Linux KVM..
To the point that why would you want to do this.If you are an All Windows Shop, why would you want to have another technology tossed in?
I'm not saying you're wrong, there are just places that prefer to stick to one vendor/tech tree.
Yeah it's pretty simple if you're already using a MS AD domain and have GP set up to pretty much make it all plug-n-play, then you don't have to worry about any of this stuff.
-
It looks a lot harder than it really is.
-
@brrabill said in Building a Hyper-V 2016 host Take 2:
It looks a lot harder than it really is.
Agreed - this is a pretty shitty setup. ESXi is super damned easy compared to this convoluted BS!
-
With my little XS adventure earlier this week, it reminded me how truly simple XS/XC/XO is.
Hyper-V really does need such a thing. Such a free thing.
-
@brrabill said in Building a Hyper-V 2016 host Take 2:
With my little XS adventure earlier this week, it reminded me how truly simple XS/XC/XO is.
Hyper-V really does need such a thing. Such a free thing.
I'm thinking once SSH is fully built into Windows, it will be much easier.
As of now, I'm able to use PowerShell Core to do
Enter-PSSessionfrom Linux TO Windows. Which helps when I'm writing PowerShell scripts in VSCode on Linux, and need to do real tests on a Windows machine... being able to do that is huge time saver.I don't think it's far off until it's part of all Windows and Hyper-V as well.
-
@brrabill said in Building a Hyper-V 2016 host Take 2:
With my little XS adventure earlier this week, it reminded me how truly simple XS/XC/XO is.
Hyper-V really does need such a thing. Such a free thing.
Do doubt!
ESXi and XS both have a web interface to manage them that is super simple and GUI enabled and crazy easy to understand (at least the basics - disk, RAM, etc) Hyper-V is anything but. You have to manage it with at least two different panes of glass (Hyper-V manager and Computer Manager) if not more.
Of course Scott will say you can manage it 100% with PS, which is likely true, but in a 1-3 host environment, that's rarely worth learning, other than learning for learning sake.
-
@dashrender said in Building a Hyper-V 2016 host Take 2:
Hyper-V is anything but. You have to manage it with at least two different panes of glass (Hyper-V manager and Computer Manager) if not more.
Eh? Have you seen WAC yet? That's insanely functional for managing Hyper-V infrastructure...
-
Setting up a hyper v server outside of a domain is just as much fun, completely redicolous really. ESXI and XS are a lot quicker to get up and going with.
-
@stuartjordan said in Building a Hyper-V 2016 host Take 2:
Setting up a hyper v server outside of a domain is just as much fun, completely redicolous really. ESXI and XS are a lot quicker to get up and going with.
Yes, a lot more steps need to take place on Hyper-V (all relating to remotely accessing and managing it)... due to using Kerberos and all that for authentication and access... versus everything else that just simply uses SSH. But looks like MS is moving in that direction.
-
@dashrender said in Building a Hyper-V 2016 host Take 2:
@brrabill said in Building a Hyper-V 2016 host Take 2:
With my little XS adventure earlier this week, it reminded me how truly simple XS/XC/XO is.
Hyper-V really does need such a thing. Such a free thing.
Do doubt!
ESXi and XS both have a web interface to manage them that is super simple and GUI enabled and crazy easy to understand (at least the basics - disk, RAM, etc) Hyper-V is anything but. You have to manage it with at least two different panes of glass (Hyper-V manager and Computer Manager) if not more.
Of course Scott will say you can manage it 100% with PS, which is likely true, but in a 1-3 host environment, that's rarely worth learning, other than learning for learning sake.
Web Interlace for XS or XCP-NG isn’t available ready to go after install complete compare to ESXi.
Windows Admin Center can manage Hyper-V.
Plus it’s a lot easier to setup Hyper-V 2016 in a workgroup environment compare to Hyper-V 2012 R2.
-
@dashrender said in Building a Hyper-V 2016 host Take 2:
@emad-r said in Building a Hyper-V 2016 host Take 2:
Wow thats more difficult than setting up Linux KVM..
To the point that why would you want to do this.If you are an All Windows Shop, why would you want to have another technology tossed in?
Hyper-V isn't Windows. Hyper-V might come from MS, but that isn't at all the same as not being another technology. In Hyper-V or KVM's case, you are equally adding "another technology", even if you are a 100% Windows shop. So the logic of KVM is simpler remains more important there, as you need another tech regardless.
-
@dashrender said in Building a Hyper-V 2016 host Take 2:
I'm not saying you're wrong, there are just places that prefer to stick to one vendor/tech tree.
That's not a reason. Preferring to stick to one vendor is not something that should affect a business (and ergo IT.) Evaluating sticking to a vendor to see if it is beneficial, yes. Just "liking having fewer vendors" is emotions and our job to protect against. Given the lack of integration, the lack of crossover skills, the higher learning curves, and the lower support options, Hyper-V is pretty difficult to justify here. There are reasons, for sure, but they realistically can't be legitimate reasons when presented as "single vendor" or "all MS." Those aren't valid business concerns.
Our staff already knows Hyper-V, MS through in free Hyper-V support, we see value in a third party plug in that works with Hyper-V... these are reasons to consider it. All valid reasons lead to bottom line improvements in business (and therefore IT.)
