My experiences with Hyper-V Server 2016



  • Just installed it. Took some cell phone pics that I will upload later of the stuff prior to having ScreenConnect installed.

    0_1485483918307_Screen Shot 2017-01-26 at 8.22.19 PM.png



  • It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f



  • No iDrac or whatever remote hardware option?



  • @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    I never understood this - is there something inherent to Windows that makes it require windowing like that? why not just terminal text on a screen like Linux/Unix?



  • @Dashrender said in My experiences with Hyper-V Server 2016:

    No iDrac or whatever remote hardware option?

    Dell iDrac requires Java for console. Such a horrible scenario.

    Basically I quit buying iDrac Enterprise (required for console) because of the uselessness of it. Other than base OS or Hypervisor install everything else can generally be dealt with from the basic iDrac, or the Dell OMSA.

    Specific to this server though, I won it from @xByteSean 2 years ago, it did not come with an Enterprise iDrac card, and I did not feel like buying one for the reason stated above. I did buy a number of HDD and some memory from him for it though.



  • @JaredBusch said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    No iDrac or whatever remote hardware option?

    Dell iDrac requires Java for console. Such a horrible scenario.

    Basically I quit buying iDrac Enterprise (required for console) because of the uselessness of it. Other than base OS or Hypervisor install everything else can generally be dealt with from the basic iDrac, or the Dell OMSA.

    Specific to this server though, I won it from @xByteSean 2 years ago, it did not come with an Enterprise iDrac card, and I did not feel like buying one for the reason stated above. I did buy a number of HDD and some memory from him for it though.

    awesome..
    is this yours or your company's?



  • Changing users is a stupid feeling process.

    Press the ESC key? WTF?
    Related note: The ESC key on the keyboard on the crashcart in the colo did not work, heh. I had to connect via ScreenConnect and hit ESC on my laptop keyboard.

    0_1485489550393_upload-bd23faa1-f7c8-4cac-8fc7-b19869e2cbb4

    So I press ESC once...
    What options? Is this some hint that cert based logins are possible?
    0_1485489589061_upload-d609170f-2582-4075-9fe2-ea139bb68116

    Press ESC again...
    Okay, at least this is understandable.
    0_1485489672974_upload-afb0651f-3499-4a48-ac07-d54e9fa85656

    Selected Other User
    Oh look! We can hit ESC again...
    0_1485489722958_upload-cc87dd7c-0292-4dea-9b20-7fe39937ede5

    I did so, and found the super secret method to logon locally/another domain that I am sure the How do I thing would have told me on the prior screen.
    But wait! I can hit ESC again!
    0_1485489831542_upload-6b0c8fc9-dbd3-4f4c-bc14-e343fa195f86

    Yeah, back to the select a user!
    0_1485489920950_upload-39eb7ad6-69a1-4d77-877e-5cdab524694d

    Just seriously WTF? Login does not need to be this complicated...



  • @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    No iDrac or whatever remote hardware option?

    Dell iDrac requires Java for console. Such a horrible scenario.

    Basically I quit buying iDrac Enterprise (required for console) because of the uselessness of it. Other than base OS or Hypervisor install everything else can generally be dealt with from the basic iDrac, or the Dell OMSA.

    Specific to this server though, I won it from @xByteSean 2 years ago, it did not come with an Enterprise iDrac card, and I did not feel like buying one for the reason stated above. I did buy a number of HDD and some memory from him for it though.

    awesome..
    is this yours or your company's?

    Well the RAM and HDD belong to the company. The server is mine, but I did not want it running at home, and we have a prodction server in this colo space already. We have never used this server for anything production wise, because it was running Server 2012 R2 Datacenter on the hardware from our Partner licensing. That cannot be used for anything but internal. It was a good test space the last couple years. But now I can use it in production if I want. Also, the license is no longer available to us when our renew hits next month, so I had to change soon because of that anyway.



  • @JaredBusch said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    No iDrac or whatever remote hardware option?

    Dell iDrac requires Java for console. Such a horrible scenario.

    Basically I quit buying iDrac Enterprise (required for console) because of the uselessness of it. Other than base OS or Hypervisor install everything else can generally be dealt with from the basic iDrac, or the Dell OMSA.

    Specific to this server though, I won it from @xByteSean 2 years ago, it did not come with an Enterprise iDrac card, and I did not feel like buying one for the reason stated above. I did buy a number of HDD and some memory from him for it though.

    awesome..
    is this yours or your company's?

    Well the RAM and HDD belong to the company. The server is mine, but I did not want it running at home, and we have a prodction server in this colo space already. We have never used this server for anything production wise, because it was running Server 2012 R2 Datacenter on the hardware from our Partner licensing. That cannot be used for anything but internal. It was a good test space the last couple years. But now I can use it in production if I want. Also, the license is no longer available to us when our renew hits next month, so I had to change soon because of that anyway.

    lucky you having a nice playground box.



  • Server 2016 core is supposed to be easier to manage out of the box than Server 2012 R2 was.

    It is true that there is no longer an option in the sconfig menu to enable remote access. But the firewall rules are still not enabled by default.

    I go through and enable these on initial setup. I only enable file and printer sharing, so I can easily copy files to the admin share during setup. I turn that back off later.

    Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true
    Set-NetFirewallRule -DisplayGroup 'Remote Event Log Management' -Enabled true
    Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled true
    Set-NetFirewallRule -DisplayGroup 'File and Printer Sharing' -Enabled true
    Set-NetFirewallRule -DisplayGroup 'Remote Service Management' -Enabled true
    

    Side note: One of these days I need to write a tighter set of rules to create instead of simply enabling the default rules.



  • Hmm, I'm not getting what the issues are. I have been using hyperv server 2016 full force in production environments and I haven't noticed less manageability at all.

    Are you domain joining them? That can help simplify setup. But even without. Maybe im just too tired right now and not reading correctly.



  • @Tim_G said in My experiences with Hyper-V Server 2016:

    Hmm, I'm not getting what the issues are. I have been using hyperv server 2016 full force in production environments and I haven't noticed less manageability at all.

    Are you domain joining them? That can help simplify setup. But even without. Maybe im just too tired right now and not reading correctly.

    This is not the first time I have dealt with this (That was a different site and domain though).
    I fully expected and was prepared for this.
    Yes, this is a domain joined instance.
    All of my Windows stuff in this facility is on the domain ad.bundystl.com
    It is the first time I have had time to deploy 2016.
    Do you have a GPO pushing these firewall policies?
    I know for a fact that I do not. This is a default AD environment.



  • @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    Nice.



  • @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    I never understood this - is there something inherent to Windows that makes it require windowing like that? why not just terminal text on a screen like Linux/Unix?

    Yes. There is no TTY display on Windows currently. They'd have to fundamentally change how things work to switch that. Could they? Of course. But it would change a lot of the underpinnings that I'm guessing they do not want to change. I've yet to hear of a Windows Admin complaining that they can't hook up a serial cable to work on their Windows box, so until they do, I doubt MS sees a reason to move to such a setup.



  • @scottalanmiller said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    I never understood this - is there something inherent to Windows that makes it require windowing like that? why not just terminal text on a screen like Linux/Unix?

    Yes. There is no TTY display on Windows currently. They'd have to fundamentally change how things work to switch that. Could they? Of course. But it would change a lot of the underpinnings that I'm guessing they do not want to change. I've yet to hear of a Windows Admin complaining that they can't hook up a serial cable to work on their Windows box, so until they do, I doubt MS sees a reason to move to such a setup.

    Plus ... marketing! 🙂



  • @scottalanmiller said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    I never understood this - is there something inherent to Windows that makes it require windowing like that? why not just terminal text on a screen like Linux/Unix?

    Yes. There is no TTY display on Windows currently. They'd have to fundamentally change how things work to switch that. Could they? Of course. But it would change a lot of the underpinnings that I'm guessing they do not want to change. I've yet to hear of a Windows Admin complaining that they can't hook up a serial cable to work on their Windows box, so until they do, I doubt MS sees a reason to move to such a setup.

    I'm not talking about a serial cable. I don't hook a serial cable up to machines running linux, I connect a monitor to my VGA adapter and get a full screen terminal, not a windowed screen like JB shows above.



  • @Dashrender said in My experiences with Hyper-V Server 2016:

    @scottalanmiller said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    I never understood this - is there something inherent to Windows that makes it require windowing like that? why not just terminal text on a screen like Linux/Unix?

    Yes. There is no TTY display on Windows currently. They'd have to fundamentally change how things work to switch that. Could they? Of course. But it would change a lot of the underpinnings that I'm guessing they do not want to change. I've yet to hear of a Windows Admin complaining that they can't hook up a serial cable to work on their Windows box, so until they do, I doubt MS sees a reason to move to such a setup.

    I'm not talking about a serial cable. I don't hook a serial cable up to machines running linux, I connect a monitor to my VGA adapter and get a full screen terminal, not a windowed screen like JB shows above.

    You are though, you just don't realize it. That's why Linux, Solaris, AIX, HP-UX, BSD all look alike, that's a TTY redirect to the screen. Windows doesn't have the serial cable TTY, so doesn't have that redirect.



  • @scottalanmiller said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    @scottalanmiller said in My experiences with Hyper-V Server 2016:

    @Dashrender said in My experiences with Hyper-V Server 2016:

    @JaredBusch said in My experiences with Hyper-V Server 2016:

    It is all up enough for me to get out of the colo, so I am.

    But here is an interesting change. They removed even more GUI. Hyper-V Server 2012 R2 still had the normal Server 2012 R2 locked screen after boot.

    Not Hyper-V 2016.

    0_1485485125544_upload-cb24a55b-94c3-4648-ad56-7aa00683013f

    I never understood this - is there something inherent to Windows that makes it require windowing like that? why not just terminal text on a screen like Linux/Unix?

    Yes. There is no TTY display on Windows currently. They'd have to fundamentally change how things work to switch that. Could they? Of course. But it would change a lot of the underpinnings that I'm guessing they do not want to change. I've yet to hear of a Windows Admin complaining that they can't hook up a serial cable to work on their Windows box, so until they do, I doubt MS sees a reason to move to such a setup.

    I'm not talking about a serial cable. I don't hook a serial cable up to machines running linux, I connect a monitor to my VGA adapter and get a full screen terminal, not a windowed screen like JB shows above.

    You are though, you just don't realize it. That's why Linux, Solaris, AIX, HP-UX, BSD all look alike, that's a TTY redirect to the screen. Windows doesn't have the serial cable TTY, so doesn't have that redirect.

    OIC.



  • It's really a combination of Windows being from the 1990s and UNIX being from the 1970s and UNIX using RISC hardware most of the time (back then) and Windows using commodity hardware most of the time. Commodity hardware always has graphical output, but non-commodity big iron basically never does, it just has the serial connection. This is what caused the underlying different. Could Microsoft make their system LOOK LIKE how Linux presents their TTY? Of course they can, but why? Could Linux make theirs appear like how Windows looks? Actually no, they can't, not without adding a Windowing layer. But that's because it uses a base character generator and Windows has a graphical layer. But under the hood, it makes sense. One isn't better or worse, it's just different heritages led to different ways of presenting a basic screen. I prefer the Linux way only because it gives me a nostalgic feeling for the old days. Back when I started on UNIX, we didn't have Windowing environments at all, so character generators was all that there was. I miss the clicky IBM keyboards, too.



  • You know you can still buy those.



  • @Dashrender said in My experiences with Hyper-V Server 2016:

    You know you can still buy those.

    Buy what, servers?



  • @scottalanmiller You can still buy the IBM clicky keyboards www.pckeyboard.com



  • @jt1001001 said in My experiences with Hyper-V Server 2016:

    @scottalanmiller You can still buy the IBM clicky keyboards www.pckeyboard.com

    Oh!! Lol



  • 8_1485566487165_IMG_5651.JPG 7_1485566487165_IMG_5650.JPG 6_1485566487165_IMG_5649.JPG 5_1485566487165_IMG_5648.JPG 4_1485566487164_IMG_5647.JPG 3_1485566487164_IMG_5646.JPG 2_1485566487164_IMG_5645.JPG 1_1485566487164_IMG_5644.JPG 0_1485566487163_IMG_5643.JPG



  • @jt1001001 yeah, I got one of those unicomp 7 years ago… it works great, still my main keyboard. Big import taxes US -> Italy, but great feelings!



  • Old thread but I just found this out after wasting a few hours last evening trying to get Hyper-V 2016 on my Dell 2950 lab server. Processors need to support SLAT
    http://www.nodefinity.net/post/hyper-v-on-poweredge-2900-2950-the-end-of-the-road-is-windows-server-2012-r2