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.
    • scottalanmillerS
      scottalanmiller @wirestyle22
      last edited by

      @wirestyle22 said in Managing Hyper-V:

      @matteo-nunziati said in Managing Hyper-V:

      @JaredBusch said in Managing Hyper-V:

      @matteo-nunziati said in Managing Hyper-V:

      ok comany is closing. after dinner will put notes here!

      it is just winrm, trusthosts and same user/password/workgroup setup. then you can fly!

      This is the answer for non domain joined systems.

      But most people have no need for this in the SMB as a MS AD deployment is almost always already in place.

      @Dashrender opened this thread with a poor hypothetical scenario.

      It is something that can apply to an ITSP or consultant, but it is completely not something that will apply to the vast majority of deployments.

      They asked for non ad joined management...

      Even so, Jared is right.

      There ARE cases where you need or want to avoid AD joining. But I think that I agree, normally AD joining will be best and probably should happen here.

      matteo nunziatiM 1 Reply Last reply Reply Quote 0
      • dbeatoD
        dbeato @DustinB3403
        last edited by

        @DustinB3403 That is what I do, there is no need to join to the domain. If you are on the Windows 8.1 or Windows 10 computer you can browse the \servername\c$ share enter your username and password and then you can manage Hyperv without any prompts too.

        1 Reply Last reply Reply Quote 0
        • dbeatoD
          dbeato @scottalanmiller
          last edited by

          @scottalanmiller 5nine has changed recently on this and no more free version...

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • dbeatoD
            dbeato
            last edited by

            There is also this, https://corefig.codeplex.com/

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

              @scottalanmiller said in Managing Hyper-V:

              @wirestyle22 said in Managing Hyper-V:

              @matteo-nunziati said in Managing Hyper-V:

              @JaredBusch said in Managing Hyper-V:

              @matteo-nunziati said in Managing Hyper-V:

              ok comany is closing. after dinner will put notes here!

              it is just winrm, trusthosts and same user/password/workgroup setup. then you can fly!

              This is the answer for non domain joined systems.

              But most people have no need for this in the SMB as a MS AD deployment is almost always already in place.

              @Dashrender opened this thread with a poor hypothetical scenario.

              It is something that can apply to an ITSP or consultant, but it is completely not something that will apply to the vast majority of deployments.

              They asked for non ad joined management...

              Even so, Jared is right.

              There ARE cases where you need or want to avoid AD joining. But I think that I agree, normally AD joining will be best and probably should happen here.

              Don't know. I miss ad for my company management. But honestly I see hypervisors as a building block like vlans and so. Something before services like the AD. Don't know if I would join the hv to the ad. Word this differently: it was xen would you put it under domain via samba in dom0?

              1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @dbeato
                last edited by

                @dbeato said in Managing Hyper-V:

                @scottalanmiller 5nine has changed recently on this and no more free version...

                Yes, we've been talking about that a lot 🙂

                dbeatoD 1 Reply Last reply Reply Quote 1
                • dbeatoD
                  dbeato @scottalanmiller
                  last edited by

                  @scottalanmiller I realized that after my post.. 😕

                  1 Reply Last reply Reply Quote 1
                  • ObsolesceO
                    Obsolesce @scottalanmiller
                    last edited by

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

                    matteo nunziatiM scottalanmillerS 3 Replies Last reply Reply Quote 0
                    • matteo nunziatiM
                      matteo nunziati @Obsolesce
                      last edited by

                      @Tim_G yes the virtual console

                      1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @dbeato
                        last edited by

                        @dbeato said in Managing Hyper-V:

                        There is also this, https://corefig.codeplex.com/

                        Only major feature being sought is the remote console redirect from the VMs. Otherwise PowerShell does everything.

                        1 Reply Last reply Reply Quote 1
                        • scottalanmillerS
                          scottalanmiller @Obsolesce
                          last edited by

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

                          ObsolesceO 1 Reply Last reply Reply Quote 1
                          • scottalanmillerS
                            scottalanmiller @Obsolesce
                            last edited by

                            @Tim_G said in Managing Hyper-V:

                            For example, console access to a Windows Server 2016 VM running on Hyper-V Server 2016?

                            Right, the console of the VM, not of the host. We know how to see the host, and how to manage Hyper-V from PowerShell. but if you pop in an ISO and fire it up to install, how do you interact with it as with Windows you need a GUI at this point and with Linux you need a TTY redirect.

                            1 Reply Last reply Reply Quote 0
                            • ObsolesceO
                              Obsolesce @scottalanmiller
                              last edited by Obsolesce

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

                              matteo nunziatiM scottalanmillerS 3 Replies Last reply Reply Quote 1
                              • matteo nunziatiM
                                matteo nunziati @Obsolesce
                                last edited by matteo nunziati

                                @Tim_G yes but @scottalanmiller was discussing the binding caused by mmc: new hyperv? New windows workstation...

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

                                  @scottalanmiller said in Managing Hyper-V:

                                  @matteo-nunziati said in Managing Hyper-V:

                                  ok comany is closing. after dinner will put notes here!

                                  For the weekend?

                                  Yep!

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

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

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

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

                                      1 Reply Last reply Reply Quote 2
                                      • scottalanmillerS
                                        scottalanmiller @Obsolesce
                                        last edited by

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

                                        ObsolesceO 1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller @Obsolesce
                                          last edited by

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

                                          dbeatoD 1 Reply Last reply Reply Quote 0
                                          • dbeatoD
                                            dbeato @scottalanmiller
                                            last edited by

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

                                            scottalanmillerS matteo nunziatiM 2 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 16
                                            • 17
                                            • 5 / 17
                                            • First post
                                              Last post