On Thu, Apr 16, 2015 at 9:00 AM, Webster <[email protected]> wrote:
> Disabled or simply unchecked on the NIC’s properties? > Unchecked on the NIC properties. Not disabled with a registry key. I should have been more clear. > > > Thanks > > > > > > Webster > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Michael B. Smith > *Sent:* Wednesday, April 15, 2015 6:33 PM > *To:* [email protected] > *Subject:* RE: [NTSysADM] DFSDIAG warnings - IP with conflicting site > associations > > > > It is NOT SUPPORTED to disable IPv6 in modern Microsoft OSes. > > > > I personally consider it a bug that Microsoft still allows it to be > disabled. But I lost that bug-battle. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Ben Scott > *Sent:* Wednesday, April 15, 2015 3:56 PM > *To:* [email protected] > *Subject:* Re: [NTSysADM] DFSDIAG warnings - IP with conflicting site > associations > > > > On Apr 15, 2015 11:35 AM, "Michael Leone" <[email protected]> wrote: > >> You are doing yourself a large disfavor in turning off IPv6. > > > > Why? Especially in this isolated test domain. > > Microsoft and their code want IPv6, only support environments with it > enabled, and will use it when it is enabled. > > If you disable it in your production environment, things may (and likely > will) break in weird ways. Microsoft isn't known for handling corner cases > well. > > If you disable it only in your test environment, you're making your test > environment significantly different from your production environment. Why > bother testing if you're not testing what you're actually going to do? > > -- Ben >
