Agree, even worse is that there’s more than on way to skin that cat and far too many examples on the interwebs that show people how to get into trouble.
Because they haven’t cooked out the ability and the internet is forever we’ll be having the same conversation repeatedly. We already have had it here how many times? From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Wednesday, April 15, 2015 4: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]> [mailto:[email protected]] On Behalf Of Ben Scott Sent: Wednesday, April 15, 2015 3:56 PM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] DFSDIAG warnings - IP with conflicting site associations On Apr 15, 2015 11:35 AM, "Michael Leone" <[email protected]<mailto:[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 PG&E is committed to protecting our customers' privacy. To learn more, please visit http://www.pge.com/about/company/privacy/customer/
