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

    Trying to set up Hyper-V Server 2016, ripping my hair out

    IT Discussion
    11
    95
    11.0k
    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.
    • black3dynamiteB
      black3dynamite @dave247
      last edited by

      @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

      @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

      @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

      @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

      @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

      So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

      Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

      See this is why I am so confused.

      1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
      2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

      If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

      Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

      Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

      I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

      Option 1: Windows Server w/ Desktop Experience and then install Hyper-V role.

      Option 2: Windows Server w/ Core and Hyper-V role.

      Option 3: Hyper-V Server (The best option)

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

        @black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:

        @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

        @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

        @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

        @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

        @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

        So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

        Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

        See this is why I am so confused.

        1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
        2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

        If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

        Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

        Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

        I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

        Option 1: Windows Server w/ Desktop Experience and then install Hyper-V role.

        Option 2: Windows Server w/ Core and Hyper-V role.

        Option 3: Hyper-V Server (The best option)

        You are not understanding here. We all know all of that... That is not what he is stating.

        1 Reply Last reply Reply Quote 1
        • dave247D
          dave247 @JaredBusch
          last edited by

          @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

          @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

          @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

          @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

          @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

          @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

          So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

          Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

          See this is why I am so confused.

          1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
          2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

          If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

          Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

          Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

          I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

          I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

          Also, this thread is what I did on a defualt AD domain.

          https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

          about halfway down I posted the firewall rules I enabled and such.

          I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

          • Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
          • New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

          Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

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

            This is a different ISO than the one I used in January.
            14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

            0_1511565143212_93f4f52b-ba1c-464e-a0bb-2637e71a19d2-image.png

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

              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

              So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

              Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

              See this is why I am so confused.

              1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
              2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

              If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

              Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

              Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

              I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

              I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

              Also, this thread is what I did on a defualt AD domain.

              https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

              about halfway down I posted the firewall rules I enabled and such.

              I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

              • Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
              • New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

              Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

              You are a total idiot based on THAT post.

              The first is Server. The second is Hyper-V Server

              dave247D 1 Reply Last reply Reply Quote 1
              • dave247D
                dave247 @JaredBusch
                last edited by

                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

                Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

                See this is why I am so confused.

                1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
                2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

                If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

                Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

                Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

                I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

                I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

                Also, this thread is what I did on a defualt AD domain.

                https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

                about halfway down I posted the firewall rules I enabled and such.

                I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

                • Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
                • New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

                Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

                You are a total idiot based on THAT post.

                The first is Server. The second is Hyper-V Server

                pfffffhahahahahahahahah... WHAT THE FUCK.

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • dave247D
                  dave247
                  last edited by

                  Ok I swear I thought I downloaded the correct ISO. It was directly after I had a conversation with Scott over the phone about my VoIP debacle, and we got into servers and he told me about Hyper-V being completely free and blew my little fucking mind. SO I rushed out to Microsoft and downloaded it, and I know I KNOW I went to the right spot because I was specifically careful to download the file under "Microsoft Hyper-V Server 2016" and not the one for regular Server 2016.

                  If this was my problem all along then I'm going to owe you all an apology and a beer.

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

                    There is Windows Server 2016, and HyperV Server 2016. One you do not use as a hypervisor (even though you can), the other you do.

                    Don't confuse the two.

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

                      @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                      @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                      @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                      So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

                      Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

                      See this is why I am so confused.

                      1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
                      2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

                      If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want to rope you into having to pay them money??

                      Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

                      If that is a thing, it is so new that I've never seen it. It wasn't in the initial 2016 release.

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

                        @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                        Ok I swear I thought I downloaded the correct ISO. It was directly after I had a conversation with Scott over the phone about my VoIP debacle, and we got into servers and he told me about Hyper-V being completely free and blew my little fucking mind. SO I rushed out to Microsoft and downloaded it, and I know I KNOW I went to the right spot because I was specifically careful to download the file under "Microsoft Hyper-V Server 2016" and not the one for regular Server 2016.

                        If this was my problem all along then I'm going to owe you all an apology and a beer.

                        Oh, might you have been installing Windows instead of Hyper-V? LOL, that would do it šŸ™‚

                        1 Reply Last reply Reply Quote 1
                        • dave247D
                          dave247 @Obsolesce
                          last edited by

                          @tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                          There is Windows Server 2016, and HyperV Server 2016. One you do not use as a hypervisor (even though you can), the other you do.

                          Don't confuse the two.

                          Yes see but I already know this!!!!!!!!!!! I swear I thought I downloaded the correct ISO. I WAS CAREFUL TO DOWNLOAD THE RIGHT ISO!!

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

                            @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                            So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

                            Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

                            See this is why I am so confused.

                            1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
                            2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

                            If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

                            Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

                            Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

                            I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

                            I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

                            Also, this thread is what I did on a defualt AD domain.

                            https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

                            about halfway down I posted the firewall rules I enabled and such.

                            I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

                            • Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
                            • New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

                            Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

                            You are a total idiot based on THAT post.

                            The first is Server. The second is Hyper-V Server

                            pfffffhahahahahahahahah... WHAT THE FUCK.

                            Blame MS for making it confusing as fuck in the name of licensing dollars.

                            No one will hold it against you.

                            scottalanmillerS dave247D 2 Replies Last reply Reply Quote 4
                            • scottalanmillerS
                              scottalanmiller @JaredBusch
                              last edited by

                              @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                              So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

                              Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

                              See this is why I am so confused.

                              1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
                              2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

                              If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

                              Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

                              Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

                              I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

                              I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

                              Also, this thread is what I did on a defualt AD domain.

                              https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

                              about halfway down I posted the firewall rules I enabled and such.

                              I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

                              • Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
                              • New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

                              Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

                              You are a total idiot based on THAT post.

                              The first is Server. The second is Hyper-V Server

                              pfffffhahahahahahahahah... WHAT THE FUCK.

                              Blame MS for making it confusing as fuck in the name of licensing dollars.

                              No one will hold it against you.

                              Half the time looking at an ISO name I can't even figure out what it even is from them!

                              1 Reply Last reply Reply Quote 2
                              • dave247D
                                dave247 @JaredBusch
                                last edited by

                                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

                                Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

                                See this is why I am so confused.

                                1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
                                2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

                                If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

                                Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

                                Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

                                I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

                                I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

                                Also, this thread is what I did on a defualt AD domain.

                                https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

                                about halfway down I posted the firewall rules I enabled and such.

                                I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

                                • Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
                                • New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

                                Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

                                You are a total idiot based on THAT post.

                                The first is Server. The second is Hyper-V Server

                                pfffffhahahahahahahahah... WHAT THE FUCK.

                                Blame MS for making it confusing as fuck in the name of licensing dollars.

                                No one will hold it against you.

                                Yeah this time during installation it didn't give me any install options. Just installing straight Hyper-V... sigh

                                I never cease to amaze myself at my own ability to constantly screw up due to not paying attention.

                                Sorry guys and thanks for your help. Thanks for dealing with me.

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

                                  @dave247 This post is what I had to set for firewall on the Hyper-V Server after joining the domain.

                                  https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10

                                  After that I posted some images of what I did to setup teaming and such.

                                  dave247D 1 Reply Last reply Reply Quote 2
                                  • dave247D
                                    dave247 @JaredBusch
                                    last edited by

                                    @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                    @dave247 This post is what I had to set for firewall on the Hyper-V Server after joining the domain.

                                    https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10

                                    After that I posted some images of what I did to setup teaming and such.

                                    Great, thanks. I will get on that once the install is finished. I've been working on this for about 3 days now. Unreal.

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

                                      @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                      @jaredbusch said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                      @dave247 This post is what I had to set for firewall on the Hyper-V Server after joining the domain.

                                      https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10

                                      After that I posted some images of what I did to setup teaming and such.

                                      Great, thanks. I will get on that once the install is finished. I've been working on this for about 3 days now. Unreal.

                                      Yeah I have a HyperV firewall rule in a GPO. Your errors mentioned permissions. But that one said something else I think.

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

                                        I’m guessing the error the OP had waS because there was no Hyper-V to attach to.... now that we know it was the wrong ISO.

                                        1 Reply Last reply Reply Quote 2
                                        • dave247D
                                          dave247
                                          last edited by dave247

                                          Finally, after all that.. I still had trouble connecting from the Windows 10 computer through Hyper-V Manager. After another hour of pounding my head, I finally got connected.

                                          I had to:

                                          1. Run Hyper-V Manager as administrator and use the account that was a local admin on Hyper-V.
                                          2. Connect to server: hv01 - and do nothing with the "connect as other user" option

                                          Prior to this, I was just running Hyper-V Manager not as admin (my regular domain user account) and then I would choose "connect as other user" and put in the credentials of the domain account which was local admin on the Hyper-V server. That always lead to the permissions error.

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

                                            @dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

                                            Finally, after all that.. I still had trouble connecting from the Windows 10 computer through Hyper-V Manager. After another hour of pounding my head, I finally got connected.

                                            I had to:

                                            1. Run Hyper-V Manager as administrator and use the account that was a local admin on Hyper-V.
                                            2. Connect to server: hv01 - and do nothing with the "connect as other user" option

                                            Prior to this, I was just running Hyper-V Manager not as admin (my regular domain user account) and then I would choose "connect as other user" and put in the credentials of the domain account which was local admin on the Hyper-V server. That always lead to the permissions error.

                                            I thought you were using a user that was a member of the "Domain Admins" group?

                                            dave247D 1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 5 / 5
                                            • First post
                                              Last post