Building a Hyper-V 2016 host Take 2

Dashrender

https://mangolassi.it/topic/15712/hyper-v-nic-tool

This thread has a solution in case you find one or more of you NICs bound to a team or vSwitch because you did your own thing.

Obsolesce

Something to add here, as I just had to re-do a Hyper-V host... Pagefile.sys

I installed Hyper-V Server 2016, and it decided to put the pagefile on the MD1000. I wanted it on the drive. It took me a while to figure out how to do it via PowerShell, but I got it. Here's the PowerShell I used to fix it:

Set-WMIInstance -Class Win32_PageFileSetting -Arguments @{name="C:\pagefile.sys";InitialSize = 4096; MaximumSize = 12288}

Run that line and reboot.
I chose my page file size as such because the drive is small, and I don't care about page file. But MS recommends to use use as automatically managed, so there we go... a mid-way compromise.

You can check the status by running this:

Get-WmiObject Win32_PageFileusage

dave247

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: 0_1513799750741_bf43bce0-3521-4cc8-80cb-75ef8234d764-image.png

I've been googling for a while now trying to fix it. No dice.

Also, NICE WRITE-UP!!

Dashrender

@dave247 said in Building a Hyper-V 2016 host Take 2:

Also, NICE WRITE-UP!!

Thanks.

Dashrender

@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”

dave247

@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

BRRABill

@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

Yeah has to be done on both sides. A gotcha for sure, that as you found out is not easily Google-able.

dave247

@brrabill 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

Yeah has to be done on both sides. A gotcha for sure, that as you found out is not easily Google-able.

Today I learned...

Dashrender

@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?

BRRABill

@dashrender said

Do I need to change something in my instructions to make that specifically stand out more?

I would think ... yes?

dave247

@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"

BRRABill

@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"

Dashrender

https://i.imgur.com/DqGo6tP.png

Updated.

BRRABill

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!

Emad R

@dashrender

Wow thats more difficult than setting up Linux KVM..
To the point that why would you want to do this.

Dashrender

@emad-r said in Building a Hyper-V 2016 host Take 2:

@dashrender

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.

Obsolesce

@dashrender said in Building a Hyper-V 2016 host Take 2:

@emad-r said in Building a Hyper-V 2016 host Take 2:

@dashrender

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.

BRRABill

It looks a lot harder than it really is.

Dashrender

@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!

BRRABill

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.