Microsoft comes clean on 'weird things' in Windows Server 2012 R2, Server 2003

Microsoft issues a warning on a Windows Server conflict that's a model of clarity and insight. Yes, that Microsoft

I hesitate to use the terms "Microsoft" and "clear" in the same sentence, but you should see this Technet post, even if you aren't having trouble getting Windows Server 2012 R2 and Server 2003 to run on the same domain.

It seems that many admins are complaining about Kerberos lock-outs that leave their users unable to log on. The lock-outs occur on domains with both Server 2003 and Server 2012 R2 running, typically in a situation where the admin is trying to migrate off the old server.

Instead of posting the usual official billowing pile of meaningless mumbo jumbo with denials or vague hints of solutions yet to come, 'Softie David Beach on the Directory Services team has precisely identified the problem, explained why it happens and what Microsoft is going to do about it, and given several straightforward workarounds -- not all of which work. And he admits that they don't always work.

Imagine how different life would've been if Microsoft had taken the same approach with the Windows 8.1 Update debacle or the ongoing Surface Pro 3 problems.

Here's a sample:

We realize that upgrading an enterprise environment is not easy, and much less so when your users start to have problem during your upgrade. So we're just going to come out and say it right up front: We are working on a hotfix for this issue, but it's going to take us some time to get it out to you. In the meantime, here are some details about the problem and what you can do right now.

Simple truth, plainly spoken -- Beach deserves a medal.

This story, "Microsoft comes clean on 'weird things' in Windows Server 2012 R2, Server 2003," was originally published at InfoWorld.com. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. For the latest developments in business technology news, follow InfoWorld.com on Twitter.

Recommended
Join the discussion
Be the first to comment on this article. Our Commenting Policies