ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Managing Hyper-V

    IT Discussion
    24
    328
    59.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      BRRABill @JaredBusch
      last edited by

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

      1 Reply Last reply Reply Quote 0
      • O
        Oksana
        last edited by

        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

        D 1 Reply Last reply Reply Quote 6
        • D
          Dashrender @Oksana
          last edited by

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

          1 Reply Last reply Reply Quote 4
          • M
            matteo nunziati @Obsolesce
            last edited by

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

            O 2 Replies Last reply Reply Quote 0
            • O
              Obsolesce @matteo nunziati
              last edited by Obsolesce

              @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

              M 1 Reply Last reply Reply Quote 2
              • O
                Obsolesce @matteo nunziati
                last edited by

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

                M 1 Reply Last reply Reply Quote 0
                • M
                  matteo nunziati @Obsolesce
                  last edited by matteo nunziati

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

                  S 1 Reply Last reply Reply Quote 0
                  • M
                    matteo nunziati @Obsolesce
                    last edited by

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

                    1 Reply Last reply Reply Quote 0
                    • S
                      scottalanmiller @matteo nunziati
                      last edited by

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

                      M D 2 Replies Last reply Reply Quote 0
                      • M
                        matteo nunziati @scottalanmiller
                        last edited by

                        @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

                        S 1 Reply Last reply Reply Quote 0
                        • D
                          Dashrender @scottalanmiller
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • S
                            scottalanmiller @matteo nunziati
                            last edited by

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

                            M 2 Replies Last reply Reply Quote 0
                            • M
                              matteo nunziati @scottalanmiller
                              last edited by

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

                              1 Reply Last reply Reply Quote 1
                              • M
                                matteo nunziati @scottalanmiller
                                last edited by matteo nunziati

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

                                1 Reply Last reply Reply Quote 0
                                • S
                                  scottalanmiller
                                  last edited by

                                  So sad that they felt that they had to do it that way.

                                  1 Reply Last reply Reply Quote 2
                                  • JaredBuschJ
                                    JaredBusch
                                    last edited by

                                    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?

                                    KellyK 1 Reply Last reply Reply Quote 2
                                    • KellyK
                                      Kelly @JaredBusch
                                      last edited by

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

                                      alt text

                                      1 Reply Last reply Reply Quote 3
                                      • triple9T
                                        triple9 @scottalanmiller
                                        last edited by

                                        @scottalanmiller said in Managing Hyper-V:

                                        @DustinB3403 said in Managing Hyper-V:

                                        I'm in the camp of not joining your hypervisors to the domain.

                                        If you get locked (because of domain controls) out of your hypervisors then you're SOL, along with the domain functions.

                                        We all had 5Nine for free till a few days ago.

                                        has anyone tried this product? https://www.probus-it.com/prohvm-hyper-v-manager/
                                        It has free version and pro is not that expensive (€59.00).
                                        I don't have access to Hyper-V server at the moment to try by myself how it works.

                                        dafyreD NashBrydgesN 2 Replies Last reply Reply Quote 0
                                        • dafyreD
                                          dafyre @triple9
                                          last edited by dafyre

                                          @triple9 Looks interesting.

                                          I did a quick test of it, and it let me connect from a non-domain joined Win10 client to a Domain-Joined Hyper-V 2012 R2 server with just entering my credentials and what-not.

                                          It DOES provide VM Console access, and it doesn't seem terribly slow either, so after my 5 minutes with it, I rate it as not bad based on the free version. Might be worth buying licenses for folks that manage several Hyper-V servers.

                                          1 Reply Last reply Reply Quote 1
                                          • NashBrydgesN
                                            NashBrydges @triple9
                                            last edited by

                                            @triple9 It's not as pretty as 5Nine but seems to perform the same functions as the free version of 5Nine provided. A little slower but it works.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 6
                                            • 7
                                            • 8
                                            • 9
                                            • 10
                                            • 16
                                            • 17
                                            • 8 / 17
                                            • First post
                                              Last post