"At least one network connection on the Enterprise Vault server is IPv6-enabled"

[worldzfree]

I have read the other topics about this message that is presented after running the Enterprise Vault Deployment Scanner and I understand that IPv6 is not yet supported.  My question is that if IPv6 is enabled on the NIC (default 2008 R2 setting) will this actually harm anything?  What I am saying is that is enabled but it has never been touched.  Will just the fact that it is enabled cause issue?

[JesusWept3]

Bjorn B on this forum earlier identified an issue where the Vault Admin Console was resolving the name to the IPV6 address and then it failed to read the status of any of the tasks or services on that machine.

Also there are issues regarding OWA and it failing to work correctly if the EV Server has IPV6 enabled also

[jim_leggett]

I have seen are when the EV server is Pure IPV6. I have not found any issues leaving the default of IPV4 & IPV6 enabled.

[JesusWept3 · Accepted solution]

my suggestion would be, based on the deployment scanner warning you about it, and issues that you might not see(but possibly could) to deselect it, that way if you call in to support it won't be the first thing that they ask you to do

I mean, where as there is no harm in disabling it, theres possible issues that could arise from leaving it enabled

[GertjanA]

If I recall correctly, it also interferes with OWA functionality of the extentions.

The pdf for Deployment Scanner shows:

Checks networks and servers and warns if any are configured to use IPv6, which can prevent Enterprise Vault from working correctly with OWA.  

See https://www-secure.symantec.com/connect/forums/deployment-scanner-90-ipv6-test-why