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

    Building a Hyper-V 2016 host Take 2

    IT Discussion
    hyper-v 2016 dashrender install
    10
    58
    8.7k
    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.
    • BRRABillB
      BRRABill @JaredBusch
      last edited by

      @jaredbusch said in Building a Hyper-V 2016 host Take 2:

      @brrabill said in Building a Hyper-V 2016 host Take 2:

      @jaredbusch said in Building a Hyper-V 2016 host Take 2:

      @brrabill said in Building a Hyper-V 2016 host Take 2:

      QUESTION:

      Let's say you have 3 NICs in the server, and you give them static addresses of 10.0.0.1 10.0.0.2 and 10.0.0.3

      When you team them, the multiplexor adapter is created.

      This then gets its own static IP address?

      I keep losing connection here at this step, and I can fix it, but might be worth a small discussion on...

      No, when you team them the static addressing is lost. The best thing to do is have everything DHCP and then team. The team will pull an IP and then you can make it static.

      Just to confirm ... if you set them all, it means nothing?

      AKA, those static addresses all disappear?

      Yes. When you make a team hat has static ip on the original interfaces it tells you that that static config will be lost. But stupidly, it does not set it to dhcp either.

      Actually, I think it does now. Because I ended up going to the physical console, and it had pulled a new address. Maybe that is new.

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @BRRABill
        last edited by

        @brrabill said in Building a Hyper-V 2016 host Take 2:

        @jaredbusch said in Building a Hyper-V 2016 host Take 2:

        @brrabill said in Building a Hyper-V 2016 host Take 2:

        @jaredbusch said in Building a Hyper-V 2016 host Take 2:

        @brrabill said in Building a Hyper-V 2016 host Take 2:

        QUESTION:

        Let's say you have 3 NICs in the server, and you give them static addresses of 10.0.0.1 10.0.0.2 and 10.0.0.3

        When you team them, the multiplexor adapter is created.

        This then gets its own static IP address?

        I keep losing connection here at this step, and I can fix it, but might be worth a small discussion on...

        No, when you team them the static addressing is lost. The best thing to do is have everything DHCP and then team. The team will pull an IP and then you can make it static.

        Just to confirm ... if you set them all, it means nothing?

        AKA, those static addresses all disappear?

        Yes. When you make a team hat has static ip on the original interfaces it tells you that that static config will be lost. But stupidly, it does not set it to dhcp either.

        Actually, I think it does now. Because I ended up going to the physical console, and it had pulled a new address. Maybe that is new.

        Well, 2012 R2 did not do that. Haven't deployed a new 2016 to test that theory.

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

          @jaredbusch said in Building a Hyper-V 2016 host Take 2:

          @brrabill said in Building a Hyper-V 2016 host Take 2:

          @jaredbusch said in Building a Hyper-V 2016 host Take 2:

          @brrabill said in Building a Hyper-V 2016 host Take 2:

          @jaredbusch said in Building a Hyper-V 2016 host Take 2:

          @brrabill said in Building a Hyper-V 2016 host Take 2:

          QUESTION:

          Let's say you have 3 NICs in the server, and you give them static addresses of 10.0.0.1 10.0.0.2 and 10.0.0.3

          When you team them, the multiplexor adapter is created.

          This then gets its own static IP address?

          I keep losing connection here at this step, and I can fix it, but might be worth a small discussion on...

          No, when you team them the static addressing is lost. The best thing to do is have everything DHCP and then team. The team will pull an IP and then you can make it static.

          Just to confirm ... if you set them all, it means nothing?

          AKA, those static addresses all disappear?

          Yes. When you make a team hat has static ip on the original interfaces it tells you that that static config will be lost. But stupidly, it does not set it to dhcp either.

          Actually, I think it does now. Because I ended up going to the physical console, and it had pulled a new address. Maybe that is new.

          Well, 2012 R2 did not do that. Haven't deployed a new 2016 to test that theory.

          Confirmed with 2012 R2, that's exactly how it worked.

          Static IPs on NICs, turn them into a team, gone.

          All my Hyper-V hypervisors are now on 2016, and they use teams, but there is no sense in giving two NICs statically assigned IPs if you turn them into a team, so I have had no reason to try it on 2016.

          As JB said, make everything DHCP... then after you team them, then you can make a DHCP reservation if you want a specific IP... I rarely do static assignments, usually reservations unless it's a DC or something like that.

          JaredBuschJ 1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @Obsolesce
            last edited by

            @obsolesce said in Building a Hyper-V 2016 host Take 2:

            @jaredbusch said in Building a Hyper-V 2016 host Take 2:

            @brrabill said in Building a Hyper-V 2016 host Take 2:

            @jaredbusch said in Building a Hyper-V 2016 host Take 2:

            @brrabill said in Building a Hyper-V 2016 host Take 2:

            @jaredbusch said in Building a Hyper-V 2016 host Take 2:

            @brrabill said in Building a Hyper-V 2016 host Take 2:

            QUESTION:

            Let's say you have 3 NICs in the server, and you give them static addresses of 10.0.0.1 10.0.0.2 and 10.0.0.3

            When you team them, the multiplexor adapter is created.

            This then gets its own static IP address?

            I keep losing connection here at this step, and I can fix it, but might be worth a small discussion on...

            No, when you team them the static addressing is lost. The best thing to do is have everything DHCP and then team. The team will pull an IP and then you can make it static.

            Just to confirm ... if you set them all, it means nothing?

            AKA, those static addresses all disappear?

            Yes. When you make a team hat has static ip on the original interfaces it tells you that that static config will be lost. But stupidly, it does not set it to dhcp either.

            Actually, I think it does now. Because I ended up going to the physical console, and it had pulled a new address. Maybe that is new.

            Well, 2012 R2 did not do that. Haven't deployed a new 2016 to test that theory.

            Confirmed with 2012 R2, that's exactly how it worked.

            Static IPs on NICs, turn them into a team, gone.

            All my Hyper-V hypervisors are now on 2016, and they use teams, but there is no sense in giving two NICs statically assigned IPs if you turn them into a team, so I have had no reason to try it on 2016.

            As JB said, make everything DHCP... then after you team them, then you can make a DHCP reservation if you want a specific IP... I rarely do static assignments, usually reservations unless it's a DC or something like that.

            You can do this if you know 100% that the DHCP server does not exist on a VM running on that host.

            The Hypervisor hosts are one of the few things I set a static on. But not until it is all teamed and such.

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

              @jaredbusch said in Building a Hyper-V 2016 host Take 2:

              You can do this if you know 100% that the DHCP server does not exist on a VM running on that host.

              Yeah, if it is, you:

              1. Set static IP on your hyper-v host
              2. Set static IP on your DHCP VM on above host
              3. Set static IP on your DC on above host
              4. Set DHCP VM to start up first when you boot up the host

              @jaredbusch said in Building a Hyper-V 2016 host Take 2:

              The Hypervisor hosts are one of the few things I set a static on. But not until it is all teamed and such.

              Right

              1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender
                last edited by

                A reminder to myself

                https://i.imgur.com/JkQNtPZ.png

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

                  @Dashrender whoa, back from the dead.

                  JaredBuschJ 1 Reply Last reply Reply Quote 0
                  • JaredBuschJ
                    JaredBusch @scottalanmiller
                    last edited by

                    @scottalanmiller said in Building a Hyper-V 2016 host Take 2:

                    @Dashrender whoa, back from the dead.

                    Look who is talking....

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

                      @JaredBusch said in Building a Hyper-V 2016 host Take 2:

                      @scottalanmiller said in Building a Hyper-V 2016 host Take 2:

                      @Dashrender whoa, back from the dead.

                      Look who is talking....

                      Hey, takes a zombie to know a zombie 😉

                      DustinB3403D 1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403 @scottalanmiller
                        last edited by

                        @scottalanmiller said in Building a Hyper-V 2016 host Take 2:

                        @JaredBusch said in Building a Hyper-V 2016 host Take 2:

                        @scottalanmiller said in Building a Hyper-V 2016 host Take 2:

                        @Dashrender whoa, back from the dead.

                        Look who is talking....

                        Hey, takes a zombie necromancer to know a zombie necromancer 😉

                        I've FTFY

                        1 Reply Last reply Reply Quote 2
                        • DashrenderD
                          Dashrender
                          last edited by Dashrender

                          FYI - Hyper-v 2019 currently is broken. The March 2019 update supposedly fixes the RDP issue.

                          Though you still can't run

                           Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled true
                          
                          scottalanmillerS JaredBuschJ 2 Replies Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @Dashrender
                            last edited by

                            @Dashrender said in Building a Hyper-V 2016 host Take 2:

                            FYI - Hyper-v 2019 currently is broken. The March 2019 update supposedly fixes the RDP issue.

                            Though you still can't run

                             Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled true
                            

                            What about PowerShell Remoting, that still working?

                            1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch @Dashrender
                              last edited by JaredBusch

                              @Dashrender said in Building a Hyper-V 2016 host Take 2:

                              FYI - Hyper-v 2019 currently is broken. The March 2019 update supposedly fixes the RDP issue.

                              Though you still can't run

                               Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled true
                              

                              List things form the local console.

                              Get-NetFirewallRule | fl Name,DisplayGroup
                              

                              Edit better solution (on Hyper-V Server 2012R2):

                              Get-NetFirewallRule | Group-Object -Property DisplayGroup | Format-Table -Property Count,Name
                              

                              a702ea0a-a5b5-4eed-b06b-7d88de83d5f8-image.png

                              1 Reply Last reply Reply Quote 0
                              • DashrenderD
                                Dashrender
                                last edited by

                                Looks like they might have renamed it
                                838d7e9a-3c83-4662-9021-1339ccaac995-image.png

                                JaredBuschJ 1 Reply Last reply Reply Quote 0
                                • JaredBuschJ
                                  JaredBusch @Dashrender
                                  last edited by

                                  @Dashrender said in Building a Hyper-V 2016 host Take 2:

                                  Looks like they might have renamed it
                                  838d7e9a-3c83-4662-9021-1339ccaac995-image.png

                                  See my edit.

                                  1 Reply Last reply Reply Quote 0
                                  • DashrenderD
                                    Dashrender
                                    last edited by

                                    New command for firewall remote management

                                     Set-NetFirewallRule -DisplayGroup 'Windows Defender Firewall Remote Management' -Enable true
                                    
                                    1 Reply Last reply Reply Quote 0
                                    • DashrenderD
                                      Dashrender
                                      last edited by

                                      just to show the list

                                      e303b5fa-cba0-42e4-8bef-a5c506c94017-image.png

                                      1 Reply Last reply Reply Quote 0
                                      • DashrenderD
                                        Dashrender
                                        last edited by

                                        I can confirm that RDP works again.

                                        1 Reply Last reply Reply Quote 0
                                        • 1
                                        • 2
                                        • 3
                                        • 3 / 3
                                        • First post
                                          Last post