question about Hyper-V resource management?
-
-
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
Hey a plumber has a different wrench for different jobs, why should Microsoft be any different?
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
-
-
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
That's the last thing you want. If you wanted easy, KVM is the answer.
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
IF that't he goal, then that makes sense. Hyper-V is good, it's just that the management of it is crappy.
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though. -
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
You will find tons of guides here on ML.
-
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
You will find tons of guides here on ML.
I think this has become my favorite forum. Much nicer than reddit, less BS than Spiceworks.. everyone is nice and thorough and we have SAM ruling with an iron fist
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
You will find tons of guides here on ML.
I think this has become my favorite forum. Much nicer than reddit, less BS than Spiceworks.. everyone is nice and thorough and we have SAM ruling with an iron fist
Can't up this enough.
-
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
You will find tons of guides here on ML.
I think this has become my favorite forum. Much nicer than reddit, less BS than Spiceworks.. everyone is nice and thorough and we have SAM ruling with an iron fist
I'm not actually in charge. I just oversee the tags.
-
I mean, I rule the tags with an iron fist!
-
I call my system....
GUTEN TAG!
-
@dave247 said in question about Hyper-V resource management?:
I'm new to Hyper-V Server 2016 and I'll try not to ask basic questions for every little thing.. but I'm kind of confused about this one..
I've set up a single Hyper-V Server 2016 and configured the basic settings and everything and I"m basically to the point where I can start setting up virtual machines. I just realized that I don't even see a way that I can look at the amount of memory or storage space on my Hyper-V server. I mean, I know how much I have because I configured the server's hardware, but beyond that, I can't see how to monitor how much is left, neither in sconfig or in the Hyper-V Manager in Windows 10.
What am I missing?
Just an FYI, you can Remote Desktop into your Hyper-V server, then in the command prompt, enter:
msinfo32.exeThat will open up System Info in a GUI.
-
Most basic tools do run in GUI mode in Hyper-V Server...
For example, the above and also:
iscsicpl.exe -
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
You will find tons of guides here on ML.
I think this has become my favorite forum. Much nicer than reddit, less BS than Spiceworks.. everyone is nice and thorough and we have SAM ruling with an iron fist
Interesting, yet still you post on both....
-
@dbeato said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@dave247 said in question about Hyper-V resource management?:
@dashrender said in question about Hyper-V resource management?:
@nerdydad said in question about Hyper-V resource management?:
Computer Management -> Action -> Connect to another computer... -> Your Hyper-V host
Exactly - what he's not telling you is that Computer Management is a completely different tool. It's the Windows tool.
If you came from ESXi or even XS, you're in for some surprises. Unlike ESXi and XS, there is no single pane of glass to see all of the things related to Hyper-V. Instead you have to manage all the components the exact same way you would a normal server. Computer Management handles a lot of them, but not all. For example, you can't look at Device Manager that way anymore - MS removed remote access a bit ago.
OOOOOOOOOOOOOOOOOH... yes. Shit. LOL
yeah - this is why I #$#%^@ hate Hyper-V
ugh.. I wish I knew this before.. Maybe I'll just use the free version of ESXi instead..
no - you shouldn't do that. If you bail on Hyper-V, you should look at KVM instead, so you aren't leaving often needed/desired feature that are free in KVM and Hyper-V and cost a ton in ESXi.
well I do want to gain some experience with Hyper-V so maybe I'll stick it out.. I just need to find a centralized guide on this or something.. The way to do things so far has been murky and illusive.. Part of the problem may be that I'm so used to VMware with ESXi and vSphere.
I have a thread.
https://mangolassi.it/topic/15767/building-a-hyper-v-2016-host-take-2it covers all the things to get all the pieces working.
It assumes an Active Directory though.Oh nice! I will comb thru this. And I do have AD running here. Thanks!
You will find tons of guides here on ML.
I think this has become my favorite forum. Much nicer than reddit, less BS than Spiceworks.. everyone is nice and thorough and we have SAM ruling with an iron fist
Interesting, yet still you post on both....
Many of us do, don't judge
-
I connect to my hyper-V server and use taskmgr to pop up task manager. This shows a quick glance of everything except drives.
I connect to my hyper-v server and use get-psdrive to check disks.
