Managing Hyper-V
-
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@Tim_G yes but @scottalanmiller was discussing the binding caused by mmc: new hypeev? New windows workstation...
I'm gonna have to go back and read all 95 posts.
Nope! 95% is @scottalanmiller just read the last one
-
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@Dashrender said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
I don't understand what the issue is here. Install and configure a Hyper-V Host... then connect to it via Hyper-V Manager, FCM, or PowerShell. None of the Windows GUI tools do anything that you cannot do with PowerShell. In fact it's the other way around. You can do way more to Hyper-V with PowerShell than from any tool. Just learn the commands and move on. They are so easy.
That allows you to manage the hypervisor.. what about getting console access to the VMs?
Hyper-V Manager gives you console access to the VMs.
Is that a PowerShell tool? How do you get the console via PowerShell?
Maybe I missed some posts and am not on track of what was meant by "console access to the VMs".
Can you clarify what is meant by that? For example, console access to a Windows Server 2016 VM running on Hyper-V Server 2016?
How do you see the VM's console. The output that on Windows by default goes to the VGA adapter. The ability to see the system boot up before services come online or to connect before there is networking within the VM. Not the ability to see hyper-v, no one needs that. but to see the VMs at the console, not RDP, level.
In Hyper-V Manager... right-click -> connect? Or double-click on the VM, I think that brings up the console too.
Right, we are asking how to do this WITHOUT those tools. No Windows workstation, no Windows 10. Just assume a non-domain Windows 8 box without anything on it. What can you do to connect to an arbitrary Hyper-V machine and get to a VM's console?
-
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@Dashrender said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
I don't understand what the issue is here. Install and configure a Hyper-V Host... then connect to it via Hyper-V Manager, FCM, or PowerShell. None of the Windows GUI tools do anything that you cannot do with PowerShell. In fact it's the other way around. You can do way more to Hyper-V with PowerShell than from any tool. Just learn the commands and move on. They are so easy.
That allows you to manage the hypervisor.. what about getting console access to the VMs?
Hyper-V Manager gives you console access to the VMs.
Is that a PowerShell tool? How do you get the console via PowerShell?
Maybe I missed some posts and am not on track of what was meant by "console access to the VMs".
Can you clarify what is meant by that? For example, console access to a Windows Server 2016 VM running on Hyper-V Server 2016?
How do you see the VM's console. The output that on Windows by default goes to the VGA adapter. The ability to see the system boot up before services come online or to connect before there is networking within the VM. Not the ability to see hyper-v, no one needs that. but to see the VMs at the console, not RDP, level.
In Hyper-V Manager... right-click -> connect? Or double-click on the VM, I think that brings up the console too.
Didn't we determine both that this needs to be Windows 10 AND domain joined? Was it just one or the other? Ideally I think an answer with no Windows at all is sought, but freedom of Windows choices is at least better.
-
@scottalanmiller You need a Windows 8.1 or Windows 10 computer, and like I said on my post before you can go to the c$ of that HyperV enter the username and password and then connect using the Hyperv console.
-
@dbeato said in Managing Hyper-V:
@scottalanmiller You need a Windows 8.1 or Windows 10 computer, and like I said on my post before you can go to the c$ of that HyperV enter the username and password and then connect using the Hyperv console.
Okay, having him try that. What about if you are not on a LAN and not willing to expose SMB over the WAN?
-
@dbeato said in Managing Hyper-V:
@scottalanmiller You need a Windows 8.1 or Windows 10 computer, and like I said on my post before you can go to the c$ of that HyperV enter the username and password and then connect using the Hyperv console.
WHAT?!
-
@scottalanmiller Then it will be in the same domain.
-
The third part talks about how to connect to non domain joined HyperV.
-
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@Dashrender said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
I don't understand what the issue is here. Install and configure a Hyper-V Host... then connect to it via Hyper-V Manager, FCM, or PowerShell. None of the Windows GUI tools do anything that you cannot do with PowerShell. In fact it's the other way around. You can do way more to Hyper-V with PowerShell than from any tool. Just learn the commands and move on. They are so easy.
That allows you to manage the hypervisor.. what about getting console access to the VMs?
Hyper-V Manager gives you console access to the VMs.
Is that a PowerShell tool? How do you get the console via PowerShell?
Maybe I missed some posts and am not on track of what was meant by "console access to the VMs".
Can you clarify what is meant by that? For example, console access to a Windows Server 2016 VM running on Hyper-V Server 2016?
How do you see the VM's console. The output that on Windows by default goes to the VGA adapter. The ability to see the system boot up before services come online or to connect before there is networking within the VM. Not the ability to see hyper-v, no one needs that. but to see the VMs at the console, not RDP, level.
In Hyper-V Manager... right-click -> connect? Or double-click on the VM, I think that brings up the console too.
Right, we are asking how to do this WITHOUT those tools. No Windows workstation, no Windows 10. Just assume a non-domain Windows 8 box without anything on it. What can you do to connect to an arbitrary Hyper-V machine and get to a VM's console?
Ahh, I see.
You'd use the tools that are built to do that, just like with any hypervisor.
For Hyper-V, if you want to manage a VM via the console, you'd use Hyper-V Manager. You can get it from RSAT, or you can use the built-in one on Win10.
If it's off domain, you have to perform a couple quick extra steps that can be put into a script.
-
@Tim_G said in Managing Hyper-V:
For Hyper-V, if you want to manage a VM via the console, you'd use Hyper-V Manager. You can get it from RSAT, or you can use the built-in one on Win10.
the thing that we like about other platforms is that this is so much more robust. My Scale, for example, is a secure web interface that I can use from anywhere on any machine. No need for special operating systems set up to work. Hyper-V just doesn't have that kind of flexibility here I guess.
-
@Tim_G said in Managing Hyper-V:
If it's off domain, you have to perform a couple quick extra steps that can be put into a script.
I've never tried to use RSAT over a WAN, seems like a bad idea
-
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
If it's off domain, you have to perform a couple quick extra steps that can be put into a script.
I've never tried to use RSAT over a WAN, seems like a bad idea
I use it over a vpn to our office in OKC... it works a little slow, but it works.
-
@scottalanmiller Agreed, is like opening VMware or Xenserver over WAN....
-
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
If it's off domain, you have to perform a couple quick extra steps that can be put into a script.
I've never tried to use RSAT over a WAN, seems like a bad idea
I'm using it from Sweden to San Diego, but I VPN first.
-
@dbeato said in Managing Hyper-V:
@scottalanmiller Agreed, is like opening VMware or Xenserver over WAN....
Is it? I don't think that it is. Do you feel as confident about RSAT over the WAN as you do about XAPI?
-
@brianlittlejohn said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
If it's off domain, you have to perform a couple quick extra steps that can be put into a script.
I've never tried to use RSAT over a WAN, seems like a bad idea
I use it over a vpn to our office in OKC... it works a little slow, but it works.
VPN is just another term for the LAN, just a slow portion of it. That's still LAN security as a model, which we don't do here.
-
And I believe the intended OP can't either, it's for multiple client locations, I think.
-
@scottalanmiller Not in any way!! I meant like opening the ports so you could use Vsphere or XenCenter over WAN...
-
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
For Hyper-V, if you want to manage a VM via the console, you'd use Hyper-V Manager. You can get it from RSAT, or you can use the built-in one on Win10.
the thing that we like about other platforms is that this is so much more robust. My Scale, for example, is a secure web interface that I can use from anywhere on any machine. No need for special operating systems set up to work. Hyper-V just doesn't have that kind of flexibility here I guess.
Yeah, I don't know why. I guess either it can't be done, or what is already available is sufficient enough to not interest anyone enough to build something else.
-
@Tim_G said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
For Hyper-V, if you want to manage a VM via the console, you'd use Hyper-V Manager. You can get it from RSAT, or you can use the built-in one on Win10.
the thing that we like about other platforms is that this is so much more robust. My Scale, for example, is a secure web interface that I can use from anywhere on any machine. No need for special operating systems set up to work. Hyper-V just doesn't have that kind of flexibility here I guess.
Yeah, I don't know why. I guess either it can't be done, or what is already available is sufficient enough to not interest anyone enough to build something else.
Or maybe people just are so used to accepting the limitations that they don't think about the power and flexibility that some other platforms have. We are putting Hyper-V into the datacenter right now and it's severely crippled in usability compared to the Scale/KVM sitting in the rack with it. Dramatically so.
