Join this episode for more Stories from the EUC Road as Sean Donahue (Nutanix) and Al Solorzano (E360) tackle this all too familiar question. But does it have to an \u201cOR\u201d statement? Can you have an \u201cAND\u201d statement instead? Tune in to learn more about performance in EUC, happy employees and how you might sleep better at night in the age of Malware and Ransomware.<\/p><\/oembed>

Resources<\/p>

Hyper-V 2016

A
徽章 +7
Hyper-V 2016何时兼容？
该主题已关闭以供评论

43个答复

d
徽章 +1
同样在这里。对支持完全失望。
A
徽章 +2
任何更新？



看起来MS现在说的是服务器核心是托管Hyper-V的最佳选择。因此，我希望工程时间不会浪费在试图使纳米工作的过程中浪费。



https://blogs.technet.microsoft.com/hybridcloud/2017/06/15/delivering-continous-innovation-novation-with-windows-server/?mc = officeo365&mc = secsect = secsys＆mc = secys＆mc = iot＆mc = iot c = iot 2 opc = mmc = mmc = mmc = Winserververververerver




  • 从这些更改中，客户现在将看到纳米服务器图像的尺寸缩小超过50％，进一步减少了启动时间并提高了容器密度。作为关注容器的这一努力的一部分，我们将删除与基础设施相关的角色的功能。我们建议部署服务器核心安装选项，而不是使用Nano Server，而是包括您需要的所有角色和功能。
  • 向前迈进，服务器核心将是托管虚拟机和容器的推荐选择 - 可以运行纳米服务器容器映像，服务器核心容器映像，甚至是Linux容器图像。
  • 服务器核心也是我们推荐的基础架构工作负载选项。许多客户没有意识到服务器核心是运行Azure和Azure堆栈的基本图像。

\n

\nLooks like MS are now saying Server Core is the best option for hosting Hyper-V. So I hope engineering time has not be wasted on trying to make Nano work...

\n

\nhttps:\/\/blogs.technet.microsoft.com\/hybridcloud\/2017\/06\/15\/delivering-continuous-innovation-with-windows-server\/?MC=OfficeO365&MC=SecSys&MC=IoT&MC=MSAzure&MC=WinServer

\n

\n

    \n
  • From these changes, customers will now see the Nano Server images shrink in size by more than 50 percent, further decreasing startup times and improving container density. As part of this effort to focus on containers, we will be removing the functionality for infrastructure-related roles. Instead of using Nano Server for these scenarios, we recommend deploying the Server Core installation option, which includes all the roles and features you would need.
    \n
  • Moving forward, Server Core will be the recommended choice for hosting your virtual machines as well as your containers \u2013 which can be running a Nano Server container image, a Server Core container image, or even Linux container images.
    \n
  • Server Core is also our recommended option for infrastructure workloads. Many customers don\u2019t realize that Server Core is the base image that runs Azure and Azure Stack.<\/ul>","quoteUsername":"AndrewUpson","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
d
徽章 +3
我们也是。仍在等待有关HyperV 2016支持的一些消息。
s
徽章
+1。Q2现在已经结束了，在近5个月内没有更新。这是怎么回事？我认为我们都知道，这是微软的重大升级，具有许多插入性。但是至少，某种形式的沟通会很好。我相信我并不是唯一一个由Nutanix支持到2016年的主要基础设施项目的人，因此，任何形式的现实ETA都将受到赞赏。
w
徽章 +5
对此的任何更新将不胜感激。我今年没有参加。



问候，韦恩

\n

\nRegards, Wayne","quoteUsername":"wlansdowne","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
A
徽章 +2
我也没有参加..但是我听说/看到2016年全部走了。ga aug/sep。这是宣布的会议：



Nutanix Enterprise Cloud，具有Hyper-V和Windows Server 2016Nutanix以成为主管不可知论而感到自豪，并以我们的Windows Server 2016对Hyper-V的支持继续这一传统。Windows Server 2016的Hyper-V引入了许多新的关键功能，包括离散设备分配，变更块跟踪和开关嵌入式组件以命名。本届会议将探索使用Nutanix的Hyper-V支持，包括有关我们与Windows Server 2016及其产品生态系统集成的技术细节。在Nutanix上了解Windows Server 2012 R2和Windows Server 2016之间的关键差异。使用Nutanix部署基于Windows Server 2016的Hyper-V解决方案时，获得最佳实践和注意事项。了解与系统中心套件和Azure Pack在内的Hyper-V生态系统的集成点。

\n

\nNUTANIX ENTERPRISE CLOUD WITH HYPER-V AND WINDOWS SERVER 2016<\/b>Nutanix takes pride in being hypervisor agnostic and continues that tradition with our Windows Server 2016 support for Hyper-V. Hyper-V with Windows Server 2016 has introduced a number of new key features including discrete device assignment, change block tracking and switch embedded teaming to name a few. This session will explore Hyper-V support with Nutanix including the technical details around our integration with Windows Server 2016 and its ecosystem of products. Learn the key differences between Windows Server 2012 R2 and Windows Server 2016 on Nutanix. Obtain best practices and considerations when deploying a Windows Server 2016 based Hyper-V solution with Nutanix. Understand the integration points with the Hyper-V ecosystem of products including the System Center suite and Azure Pack.","quoteUsername":"AndrewUpson","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
j
徽章 +4
看着发行说明在AOS 5.1.1.3中，我的印象是Hyper-V 2016仍然不是GA。



Hyper-V


  • 不支持ENG-87078 SCVMM 2016和Windows Server 2016版本。
release notes<\/a> of AOS 5.1.1.3, I get the impression that Hyper-V 2016 is still not GA.

\n

\nHyper-V

\n

    \n
  • ENG-87078 SCVMM 2016 and Windows Server 2016 versions are not supported.<\/ul>","quoteUsername":"jhed","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
A
徽章 +2
AOS 5.5是2016年支持的人。现在不能遥远...戴尔已经在此上有技术预览文档：



http://en.community.dell.com/techcenter/extras/m/white_papers/20444598



http://en.community.dell.com/techcenter/extras/m/white_papers/20444596



https://blog.dellemc.com/en-us/hyper-converged-infrastructure--help-you-taste-the-sweet-life/
d
徽章
嗨，乔恩，



自Windows Server 2016发布以来，对Hyper-V 2016的支持的任何更新都将接近一年。



谢谢

dhiraj

\n

\nAny update on the support for Hyper-V 2016, it's close to a year since the release of Windows server 2016.

\n

\nThanks

\nDhiraj","quoteUsername":"DhirajBakare","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
r
徽章
5.5？哇，直到再3-6个月，我才想到这一点，对发行的发展进行了努力。
Mikasa
徽章 +1
来吧，至少给我们一些东西吗？我们是否需要启动一个新线程，因为您将其标记为已解决的原因，当然不是。
s
徽章
我在5.5上获得的最新更新是它已经延迟了。最初的发布应该是9月，但是已被推迟。它是“预计在（日历）年底之前”。
s
徽章
我同意，在这个线程上，Nutanix的完全沉默有点荒谬。
mmcghee
秩
UserLevel 3
徽章 +17
嘿大家。对Windows Server 2016和Hyper-V的支持将带有5.5版本，该版本即将到期。几周前，我们与Ignite结合了一些公告，您可以在此处找到更多详细信息：https://next.nutanix.com/t5/nutanix-connect-blog/nutanix-set-to-deliver-support-for-windows-server-2016-microsoft/ba-p/23662 雷蒙
https:\/\/next.nutanix.com\/t5\/Nutanix-Connect-Blog\/Nutanix-Set-to-Deliver-Support-for-Windows-Server-2016-Microsoft\/ba-p\/23662<\/a> Raymon<\/a>","quoteUsername":"mmcghee","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
乔恩
秩
UserLevel 6
徽章 +29
嘿伙计，

对不起，极度延迟。在这一点上，我意识到它的边界愚蠢，并代表工程学（包括我自己）的每个人，感谢您的耐心。



这是交易。2016年对我们来说发生了很大变化（这是一件好事），这花了我们一段时间来适应我们可以轻松地将现有的2012年客户提升到2016年，并提供踢脚产品对于Net-New Hyper-V安装也是如此。



为了保持直接和关注点，我不会消除每个细节，而是简单地说我们已经解决了所有这些挑战，并且预计将以AOS 5.5启动2016年的支持。



鉴于我们是一家上市公司，我不能在5.5上放置前瞻性日期；但是，我将从工程学的角度说，我们已经将所有人都掌握了关闭此版本，这意味着最终的质量保证和启动准备。我们现在已经在2016年的Hyper-V中在现场拥有Alpha和Beta客户，并将其反馈塑造为产品。



总的来说，这是 *整个 *客户群，如果您觉得自己处于黑暗状态，请随时通过您的业务电子邮件直接发送电子邮件给我jon@nutanix.com，我很高兴聊天详细介绍了我们的工作。对于2016年Hyper-V具体问题，我也很乐意在PM中循环以了解该功能，我们可以讨论更多。我们为在Nutanix的一本漂亮的书籍而感到自豪，因此我的“数字门”总是开放的。



我再次表示歉意，我们没有随着进度更新此线程，但是我希望这足以满足我们需要在5.5启动之前（共同）（共同）进行的最后一点点等待。
乔恩·科勒（Jon Kohler）|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！

\nSorry for the extreme delay. I realize its borderline silly at this point, and on behalf of everyone in engineering (including myself), I appreciate your patience.

\n

\nHere's the deal. 2016 changed quite a bit for us (which is a net-good thing), and that took us quite a while to adapt in a way that we could uplift our existing 2012 customers to 2016 in an easy manner, and provide a kick butt product for net-new hyper-v installs as well.

\n

\nI won't rattle off each detail, for the sake of keeping this direct and to the point, but rather simply say we've worked through all of those challenges, and are projecting to launch 2016 support with AOS 5.5.

\n

\nGiven we're a public company, I can't put a forward-looking date on 5.5; however, I will say from the engineering perspective, we've got all hands on deck working on closing down this release, which means final QA and launch prep. We've already got alpha and beta customers on 2016 Hyper-V in the field right now, and have molded their feedback into the product.

\n

\nIn general, and this goes for the *ENTIRE* customer base, if you ever feel you're in the dark on something, please feel free to email me directly jon@nutanix.com from your business emails and I'm happy to chat in detail about what we're up to. For 2016 Hyper-V specific issues, I'm happy to loop in the PM for that feature as well, and we can discuss even more. We pride ourselves on being a pretty open book here at Nutanix, so my \"digital door\" is always open.

\n

\nMy apologies again that we didn't update this thread with our progress, but I'm hoping this will suffice for the last little bit of waiting we need to do (collectively) before 5.5 launches.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
r
徽章
你好乔恩，



与Hyper-V 2016发布兼容性花了一年的时间，Nutanix计划如何跟上Microsoft更快的Windows Server＆System Center的发行速度，因为它们将每六个月发布新版本？

参考 -

https://cloudblogs.microsoft.com/hybridcloud/2017/06/15/delivering-continouul-innovation-with-with-windows-server/

https://cloudblogs.microsoft.com/hybridcloud/2017/06/15/frequent-continuul-releases-coming-for-system-center/



谢谢。
乔恩
秩
UserLevel 6
徽章 +29
这是个好问题Rohanfargade。我所说的“结构性”工作花了很多时间，因为我们必须重新编码大部分Hyper-V支持，并将代码扩展到两个方向工作（支持滚动升级和类似）。一项艰巨的任务，肯定比我们想象的要大。



现在完成结构性工作，支持那些更快的释放候选者（敲打木材）应该变得容易得多。不过，这一切都是最好的，尤其是在支持DDA的情况下，它极大地简化了我们做事的方式，因此降低了引擎盖下的整体复杂性。



无论如何，着眼于未来，我们已经在研究那些增量的“快速火车”发行。立即在1803年释放前工作
乔恩·科勒（Jon Kohler）|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
rohanfargade<\/a>. A lot of the time spent getting Hyper-V 2016 working was what I'd call \"structural\" work, as we had to both recode an extremely large portion of our Hyper-V support as well as extend the code to work in both directions (to support rolling upgrades and the sort). Quite a large task, and certainly larger than we thought it would be.

\n

\nNow that the structural work is done, supporting those faster release candidates (knock on wood) should be a heck of a lot easier. Its all for the best though, especially with support for DDA, it greatly simplifies the way we do things, so the overall complexity under the hood has been reduced.

\n

\nAnyhow, looking to the future, we're already looking at those incremental \"fast train\" releases. Working on the pre-release 1803 code right now","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu