Managing Hyper-V
-
@John-Nicholson said in Managing Hyper-V:
@Dashrender said in Managing Hyper-V:
Now we come to my question.
Is there any reason to not put all the Hyper-V Hosts into a single domain to ease management?
For security and stability I've always seen at any real scale you run a Management domain. Also, given cases of Cyrtolocker hitting Hyper-V hosts I'd be damned careful with separate accounts/domains for Hyper-V hosts as someone encrypting your VM's can bypass a LOT of your protections.
This is always how I feel about it. Separate everything for platform.
-
@John-Nicholson said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@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?
Wouldn't you never put a hypervisor on the public internet directly on any port?
Depends on what you call directly. Any why not? We used to feel this way about servers in general, then cloud came along and now it's the standard. You want your platform pretty tight and locked down. But one way or another all systems need to be managed. Every enterprise cloud's platform management is directly on the Internet (Amazon, Azure, etc.) There is no getting around it. So yes, I would definitely put my platform management on the Internet.
-
@stacksofplates said in Managing Hyper-V:
@John-Nicholson said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
ecosystem
Also dropping Nano from being a supported path sucks for people who were hoping for it to be a true small secure embedded install (Core requires a 32GB DISK!)
Holy crap. I didn't realize it was that big.
Isn't that only the "role" install, not a proper one?
-
@JaredBusch said
Are you not paying any attention to what you are reading?? Remote access is not console access.
I rarely pay attention. Makes things too boring.
-
StarWind is currently working on the new product - a flexible and customizable web-based platform which will allow users get the full control over their IT infrastructures from a single HTML5 graphical interface including S2D, Failover Clustering and Hyper-V. More information to be found in a nearby thread: https://mangolassi.it/topic/14114/help-starwind-to-pick-the-name-for-the-upcoming-product
-
@Oksana said in Managing Hyper-V:
StarWind is currently working on the new product - a flexible and customizable web-based platform which will allow users get the full control over their IT infrastructures from a single HTML5 graphical interface including S2D, Failover Clustering and Hyper-V. More information to be found in a nearby thread: https://mangolassi.it/topic/14114/help-starwind-to-pick-the-name-for-the-upcoming-product
Very cool - but the big question - will it allow the launching of a console connection to a VM?
-
@Tim_G said in Managing Hyper-V:
Also dropping Nano from being a supported path sucks for people who were hoping for it to be a true small secure embedded install (Core requires a 32GB DISK!)
I think he means nano is available only for those with a datacenter licence. maybe he was hoping in an hyper-v server 2016 based on nano rather than on core.
anyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login. -
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
Also dropping Nano from being a supported path sucks for people who were hoping for it to be a true small secure embedded install (Core requires a 32GB DISK!)
I think he means nano is available only for those with a datacenter licence.
Well that makes perfect sense, because Hyper-V Server is free, and does just Hyper-V. Nano Server should not be free, because it can do a LOT of things, in addition to Hyper-V. The list is long, and continues to grow.
Also, there's two versions of Nano Server: Datacenter and Standard
-
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed. -
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed.no my point is: core is not guiless. it still run in a gui env. simply you do not have gui tools. but definitively it has a window manager, or you will land in a huge dos shell. period.
-
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
Also dropping Nano from being a supported path sucks for people who were hoping for it to be a true small secure embedded install (Core requires a 32GB DISK!)
I think he means nano is available only for those with a datacenter licence.
Well that makes perfect sense, because Hyper-V Server is free, and does just Hyper-V. Nano Server should not be free, because it can do a LOT of things, in addition to Hyper-V. The list is long, and continues to grow.
Also, there's two versions of Nano Server: Datacenter and Standard
so nano is available even to standard! nice! I was misinformed.
-
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed.no my point is: core is not guiless. it still run in a gui env. simply you do not have gui tools. but definitively it has a window manager, or you will land in a huge dos shell. period.
It's not considered a GUI, it's nothing but a way to handle the CMD shell (DOS shell disappeared decades ago and was never on Windows.) It does output to VGA, but there is no real GUI aspect. It's just not TTY.
-
@scottalanmiller said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed.no my point is: core is not guiless. it still run in a gui env. simply you do not have gui tools. but definitively it has a window manager, or you will land in a huge dos shell. period.
It's not considered a GUI, it's nothing but a way to handle the CMD shell (DOS shell disappeared decades ago and was never on Windows.) It does output to VGA, but there is no real GUI aspect. It's just not TTY.
still there is a window manager to handle multiple windows at a time. also you can run GUI tools (like firefox and so...).
it is not like a pure cmd line env a-la-linux
-
@scottalanmiller said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed.no my point is: core is not guiless. it still run in a gui env. simply you do not have gui tools. but definitively it has a window manager, or you will land in a huge dos shell. period.
It's not considered a GUI, it's nothing but a way to handle the CMD shell (DOS shell disappeared decades ago and was never on Windows.) It does output to VGA, but there is no real GUI aspect. It's just not TTY.
This is a weird concept to comprehend, but I do agree with it.
-
@matteo-nunziati said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed.no my point is: core is not guiless. it still run in a gui env. simply you do not have gui tools. but definitively it has a window manager, or you will land in a huge dos shell. period.
It's not considered a GUI, it's nothing but a way to handle the CMD shell (DOS shell disappeared decades ago and was never on Windows.) It does output to VGA, but there is no real GUI aspect. It's just not TTY.
still there is a window manager to handle multiple windows at a time. also you can run GUI tools (like firefox and so...).
it is not like a pure cmd line env a-la-linux
I've not tried that. You can fire up Firefox on it, really?
-
@scottalanmiller said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@scottalanmiller said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
@Tim_G said in Managing Hyper-V:
@matteo-nunziati said in Managing Hyper-V:
nyway MY core is just around 8GB, small enough. Also microsoft has some issues with "no-gui". you go from core, which is something like linux cmd line + xserver + fluxbox, to something with no local management at all! ASAP nano can be managed only by remote powershell. No local login.
They allowed the whole switching from GUI to Core and vice versa in Server 2012 R2. They removed that ability in 2016 for good reason, imo.
But even in 2016 core, you can install apps easily... even in Hyper-V Server if it's licensed.no my point is: core is not guiless. it still run in a gui env. simply you do not have gui tools. but definitively it has a window manager, or you will land in a huge dos shell. period.
It's not considered a GUI, it's nothing but a way to handle the CMD shell (DOS shell disappeared decades ago and was never on Windows.) It does output to VGA, but there is no real GUI aspect. It's just not TTY.
still there is a window manager to handle multiple windows at a time. also you can run GUI tools (like firefox and so...).
it is not like a pure cmd line env a-la-linux
I've not tried that. You can fire up Firefox on it, really?
DONE!
YEEEEEEEEAAAAAAHHHH
I've done something @scottalanmiller didn't!!!!!
-
@scottalanmiller seriously, yes this is just a window manager as anything else. think of hyper-v server 2016 as a basic linux install + xorg + xinit launching an xterm.
it simply spawns 2 cmds one with proper cmd line, another with the sconfig.bat script runing in it. but it is the windows' window manager, without explorer and so.
-
So sad that they felt that they had to do it that way.
-
It has been that was since Hyper-V Server 2012 was released.
How else do you think the normal install GUI screens pop up when you install stuff like the ScreenConnect MSI or Dell OMSA?
-
@JaredBusch said in Managing Hyper-V:
It has been that was since Hyper-V Server 2012 was released.
How else do you think the normal install GUI screens pop up when you install stuff like the ScreenConnect MSI or Dell OMSA?
