Microsoft does not support removing IPv6 from Exchange servers, Exchange 2010 or Exchange 2013.
From: [email protected] [mailto:[email protected]] On Behalf Of Richard Stovall Sent: Friday, October 25, 2013 8:17 PM To: [email protected] Subject: Re: [Exchange] Removing IPv6 from Exchange 201 CAS/HUB servers I'm pretty sure I remember reading (here, I think) that removing IPv6 from Exchange 2010 results in a configuration that is officially unsupported by Microsoft. I don't know about Exchange 201. :p The following Exchange link makes it seem like it might be OK to disable IPv6 on Exchange 2010 http://technet.microsoft.com/library/gg144561(v=exchg.141).aspx#DisEna. However, that page links to this http://technet.microsoft.com/en-us/network/cc987595.aspx, which has the following to say on the matter of disabling IPv6 in Windows (not specifically Exchange). ----- Q. What are Microsoft's recommendations about disabling IPv6? A. 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. ----- On Fri, Oct 25, 2013 at 3:14 PM, Todd Lemmiksoo <[email protected]<mailto:[email protected]>> wrote: I have an EMC support person asking me to remove IPv6 from our CAS servers. Is this safe to do. This in regards to GLR restores not working with Avamar GLR client. -- T. Todd Lemmiksoo
