sara2000
asked on
DHCP and Windows 2012 R2
We are planing to install Windows 2012 R2 and DHCP. The IP v6 is enabled in Windows.
Is there any issue of leaving it on or disabling ?
Is there any issue of leaving it on or disabling ?
just leave it alone. Unless you run into issues but the default (on) is just fine.
Hi,
As long as the IPV6 network is not in one of the DHCP pools, this has no impact on your configuration. But good practice is that you disable your server's IPV6 network because unused features and roles should be disabled.
Christian K.
As long as the IPV6 network is not in one of the DHCP pools, this has no impact on your configuration. But good practice is that you disable your server's IPV6 network because unused features and roles should be disabled.
Christian K.
Microsoft has officially said on several occasions that disabling IPv6 is *NOT. best practice. I must respectfully disagree with the comment above suggesting that it is.
ASKER
We are debating on it. One of our tech told me that they had an isdue with dhcp and dns and suggested us to disable it.
I am reluctant to do that.
I am looking for MS recommendation , Cliff, would you happen to have the link so I can forward to my collegue to read it in his tea break.
I am reluctant to do that.
I am looking for MS recommendation , Cliff, would you happen to have the link so I can forward to my collegue to read it in his tea break.
https://www.microsoftpressstore.com/articles/article.aspx?p=2224359&seqNum=5
From the link:
Although you cannot uninstall IPv6 on Windows platforms, you can disable it if desired. However, Microsoft does not recommend disabling IPv6 for the following reasons:
During the development of Windows platforms by Microsoft, services and applications were tested only with IPv6 enabled. As a result, Microsoft cannot predict what might be the consequences of disabling IPv6 on Windows.
Some Windows features will not function if IPv6 is disabled. Examples of such features include DirectAccess and Remote Assistance.
From the link:
Although you cannot uninstall IPv6 on Windows platforms, you can disable it if desired. However, Microsoft does not recommend disabling IPv6 for the following reasons:
During the development of Windows platforms by Microsoft, services and applications were tested only with IPv6 enabled. As a result, Microsoft cannot predict what might be the consequences of disabling IPv6 on Windows.
Some Windows features will not function if IPv6 is disabled. Examples of such features include DirectAccess and Remote Assistance.
It's been mentioned in several TechNet networking docs, blog posts, and in just about every MCSA exam guide that has been approved by Microsoft for the last 10 years. Plenty of good sources out there for this info. I'm mobile so I don't have a specific link offhand, but I see someone just posted it. A quick google search will probably pull up plenty more.
The *only* time I've seen IPv6 cause an issue is when it was misconfigured *or* when an ISP router was falsely advertising a site-local address that windows was (properly) picking up. And this is with extensive experience in actively deploying IPv6 for the last decade.
The *only* time I've seen IPv6 cause an issue is when it was misconfigured *or* when an ISP router was falsely advertising a site-local address that windows was (properly) picking up. And this is with extensive experience in actively deploying IPv6 for the last decade.
Here is one of those links
“It is unfortunate that some organizations disable IPv6 on their computers running Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft’s perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.”
http://technet.microsoft.com/en-us/network/cc987595.aspx
“It is unfortunate that some organizations disable IPv6 on their computers running Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft’s perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.”
http://technet.microsoft.com/en-us/network/cc987595.aspx
ASKER
We have decided to unbound. But not sure whether it is the best solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
IPv6 should be left on unless there is a specific reason to disable it for app compatibility reasons, and even then needs to be done carefully with planning.