Hi everyone, Our company is in the throws of planning a covertion of our WAN network to native IPv6. Currently, we have Exchange 2010 deployed in our enviroment with: 2 MBX, 2 CAS/HUB, and 2 EDGE/TMG servers with a Brocade NLB. I'm aware that TMG does not support IPV6, and that Microsoft is in fact abandoning the product entirely (rolling features from TMG into "other" products supposedly), so I need to find a new service publishing method. For one: if our LAN is staying IPv4 (address translation will occur at our Juniper firewall), what configuration do I need to do with Exchange to fully function, if anything? Secondly, what other products are available for publishing Exchange services and site externally (i.e. OWA, ECP, EAS, Autodiscovery, etc) beyong TMG? If there is any other tips or advice anyone can provide, it would be greatly appreciated! Thanks.

At present Exchange is not supported in a pure IPv6 environment. Therefore as long as you are in a dual stack platform there is little more that needs to be done. I have my own home network available on both IPv4 and IPv6 and it works fine. I just set static IP addresses on to each server. The Exchange server has the same IPv6 address internally and externally (no NAT involved) and if I am in one of the rare locations where IPv6 works over the Internet then I can connect. Although in the time since I implemented IPv6 for my Exchange server I have received a grand total of six emails on the IPv6 interface, all of which were marketing. I can't help with the publishing question, as I think all deployments of Exchange I have done have either been direct or used TMG. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

At present Exchange is not supported in a pure IPv6 environment. Therefore as long as you are in a dual stack platform there is little more that needs to be done. I have my own home network available on both IPv4 and IPv6 and it works fine. I just set static IP addresses on to each server. The Exchange server has the same IPv6 address internally and externally (no NAT involved) and if I am in one of the rare locations where IPv6 works over the Internet then I can connect. Although in the time since I implemented IPv6 for my Exchange server I have received a grand total of six emails on the IPv6 interface, all of which were marketing. I can't help with the publishing question, as I think all deployments of Exchange I have done have either been direct or used TMG. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

In Microsoft Exchange Server 2010, IPv6 is supported only when IPv4 is also used; a pure IPv6 environment isn't supported. Refer to: http://technet.microsoft.com/en-us/library/gg144561.aspx Regarding the publishing, you might need to contact your reseller for more information. Hope it is helpful.Fiona Liao TechNet Community Support

If no more question on this thread, we may mark it as answered. Thanks.Fiona Liao TechNet Community Support