Tip of the Day: Windows Server 2016 and IPv6…


Today's tip...

Question of the Day:

Question:

My customer has a question about the use of IPv6. Microsoft guidance for the past few releases of Windows Server is to leave IPv6 enabled even if you’re only using an IPv4-enabled network. Has that guidance changed at all for Windows Server 2016? Does that guidance differ if Windows Server is running in a virtual machine or in Azure?

Answer:

Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. This recommendation has been consistent going back to Windows Server 2008 R2 and remains true with Windows Server 2016 whether running on a physical system, in a virtual machine or in Azure IaaS. By leaving IPv6 enabled, you ensure that IPv6 applications and services and hosts can take advantage of IPv6-enhanced connectivity when available. Finally, it’s important to note that IPv6 is a core technology of Windows/Windows Server and is thus included in application and OS testing and validation. Microsoft does not test any scenarios with IPv6 services disabled.

For more information about IPv6 see: https://technet.microsoft.com/library/hh831730.aspx

Comments (0)

Skip to main content