posting this since I just read it last week. http://blogs.technet.com/b/askpfeplat/archive/2013/06/17/ipv6-for-the-windows-administrator-why-you-need-to-care-about-ipv6.aspx and this since it seems topical http://blogs.technet.com/b/askpfeplat/archive/2013/06/24/ipv6-for-the-windows-administrator-ipv6-fundamentals.aspx oh, and got rid of WINs a few years ago. While I am pretty sure it was because we didn't need it anymore, inconveniencing our in-house devs would probably have gotten it ripped out sooner :) Steven Peck http://www.blkmtn.org
> Date: Mon, 1 Jul 2013 06:47:34 -0700 > Subject: Re: [NTSysADM] A very good article to read : Features Removed or > Deprecated in Windows Server 2012 R2 Preview > From: [email protected] > To: [email protected] > > That article doesn't address a very compelling argument for leaving > IPv6 running - it's the newer/better network stack, and while IPv4 > will be around well past *my* retirement, and possibly past the > retirement of my 3yo child, government and business mandates are > already starting to favor IPv6. > > Oh - and Understanding IPv6 is now in its 3rd edition, and worth it. > > Kurt > > On Mon, Jul 1, 2013 at 6:30 AM, David Lum <[email protected]> wrote: > > Along the lines of " one more service running that (theoretically) isn't > > needed", > > http://blogs.technet.com/b/jlosey/archive/2011/02/02/why-you-should-leave-ipv6-alone.aspx > > David Lum > > Sr. Systems Engineer // NWEATM > > Office 503.548.5229 // Cell (voice/text) 503.267.9764 > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > On Behalf Of Kurt Buff > > Sent: Sunday, June 30, 2013 5:35 PM > > To: [email protected] > > Subject: Re: [NTSysADM] A very good article to read : Features Removed or > > Deprecated in Windows Server 2012 R2 Preview > > > > I'm not a developer, so can't comment on that, but will take your word for > > it. > > > > However, as a sysadmin and user, I am puzzled by the fact that MSFT seems > > unable to bring out products for business use that work well with DDNS and > > FQDNs. as opposed to NetBIOS names. > > > > Also, from both an aesthetic and a security policy point of view, I think it > > would make sense to get rid of it - it's just one more service running that > > (theoretically) isn't needed. > > > > However, WINS hasn't given me problems since at least NT4, and I'm still > > running it under Win2k8 R2, so I don't really care much one way or the other > > - as I said, it's more amusing than anything else. > > > > Kurt > > > > On Sun, Jun 30, 2013 at 2:39 PM, Michael B. Smith <[email protected]> > > wrote: > >> WINS just makes life so much easier as a developer. Seriously. > >> > >> Each product they try to remove WINS dependencies from, it breaks stuff > >> and adds more complexity. > >> > >> For example, you can run Exchange without WINS (and I'm referring to a > >> complex Exchange deployment - multiple domains, discontiguous namespaces, > >> etc.etc.) - but the complexity of configuration Is Just Not Worth It. > >> > >> It's a heck of a lot cheaper to run WINS - and less likely to break. > >> > >> To paraphrase Brian's comments - if you have an IT organization that > >> thinks getting rid of WINS is their top priority - then they are > >> wrong. :) > >> > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Kurt Buff > >> Sent: Sunday, June 30, 2013 2:51 PM > >> To: [email protected] > >> Subject: Re: [NTSysADM] A very good article to read : Features Removed > >> or Deprecated in Windows Server 2012 R2 Preview > >> > >> Didn't say I don't like it - MSFT has in the past threatened to remove it, > >> and it's amusing to note that they've never followed through. > >> > >> Kurt > >> > >> On Sun, Jun 30, 2013 at 10:51 AM, Jonathan Link <[email protected]> > >> wrote: > >>> Well, be that as it may, Kurt still doesn't like it. > >>> > >>> > >>> On Sun, Jun 30, 2013 at 1:43 PM, Brian Desmond > >>> <[email protected]> > >>> wrote: > >>>> > >>>> +1 > >>>> > >>>> I tell most customers who think removing WINS from their environment > >>>> is a good use of their time to find a more worthwhile project to > >>>> invest in. WINS is dead simple, solves a problem, has practically no > >>>> infrastructure overhead, and requires nearly no maintenance. > >>>> > >>>> Thanks, > >>>> Brian Desmond > >>>> [email protected] > >>>> > >>>> w – 312.625.1438 | c – 312.731.3132 > >>>> > >>>> -----Original Message----- > >>>> From: [email protected] > >>>> [mailto:[email protected]] On Behalf Of Michael B. > >>>> Smith > >>>> Sent: Friday, June 28, 2013 10:53 PM > >>>> To: [email protected] > >>>> Subject: RE: [NTSysADM] A very good article to read : Features > >>>> Removed or Deprecated in Windows Server 2012 R2 Preview > >>>> > >>>> Pffft. > >>>> > >>>> That isn't going anywhere, anytime soon. > >>>> > >>>> I expect it to be around after I retire. > >>>> > >>>> -----Original Message----- > >>>> From: [email protected] > >>>> [mailto:[email protected]] On Behalf Of Kurt Buff > >>>> Sent: Friday, June 28, 2013 11:10 PM > >>>> To: [email protected] > >>>> Subject: Re: [NTSysADM] A very good article to read : Features > >>>> Removed or Deprecated in Windows Server 2012 R2 Preview > >>>> > >>>> I see WINS isn't on that list. :) > >>>> > >>>> On Fri, Jun 28, 2013 at 5:08 PM, Michael B. Smith > >>>> <[email protected]> > >>>> wrote: > >>>> > Features Removed or Deprecated in Windows Server 2012 R2 Preview > >>>> > > >>>> > http://technet.microsoft.com/en-us/library/dn303411.aspx > >>>> > > >>>> > > >>>> > >>>> > >>> > >> > >> > > > > > > > >
