Windows 8

First of all, a GINORMOUS “THANK YOU!” to Mary Jo Foley for bringing to my attention and piquing my interest in regards to Microsoft’s recent announcement that Windows 7 Server is (and always has been, apparently) synonymous with Windows Server 2008 R2. If not for her, I probably would’ve simply forgotten about the following information for much longer than I already have. lol. Anyway, thanks, MJ! You da (wo)MAN! =)

First thing’s first: If you haven’t heard, Microsoft managed to thoroughly confuse the crap out of much of the community by dropping one of their infamous ambiguity bombs: Windows Server 2008 R2 (slated for a 2010 release) = Windows 7 Server.

Derrrrr, HUH!?

Allllrighty, then! So, those of us who have been adhering closely to Microsoft’s release cycle up to this point by assuming (comfortably, I might add) Windows Server 2008 R2 would come well-before Windows 7 Server were basically dropped off in the land of “wtfville”. Interesting place, this “wtfville!” What’s there to potentially learn here in “wtfville?” Let’s find out, shall we? Yes, we shall.

For your reference, here is a slide dated November, 2007 that I’ve had for way too long to not have done anything with it by now, but perhaps that’s best since it may provide some sort of clarity to Microsoft’s recent statement. This does make Microsoft’s seemingly odd statement mesh (Full resolution image at the click of a mouse!):

Interesting slides here in “wtfville.” Let’s recap:

Windows Server “7”: 2011
Windows Server “8”: 2013
Windows Server “9”: 2015


If Windows 7 Server really is Windows Server 2008 R2, then does that roadmap imply the following?

Windows Server “7” = Windows Server 2008 R2
Windows Server “8” = Windows Server 2013
Windows Server “9” = Windows Server 2013 R2

I assume they’re just going to treat every minor and major update for the next 7 years or so not as they have up to this point, but rather in their newly-adorned numerical codename format. The question from there is how does Microsoft then plan on publicly referencing those server releases? By their ambiguous numerical codenames or as is assumed by me above… or better yet, in some kind of top-secret ninja format where one must DIE if they ever found out! (Any takers that Sinofsky would go for the extreme latter if he could? hehehe)

Let’s make this even MORE confusing by tweaking that roadmap to fit their latest projected year of release for Windows 7 Server (aka Windows Server 2008 R2, mind you) in the following January 2008 server roadmap (Confucious say: “Clicky-clicky for full resolution image.” Long Zheng say: “I don’t talk like that, Stephen. Prepare to die, Stephen.”):

Windows Server “7”: 2010
Windows Server “8”: 2012
Windows Server “9”: 2014

Then, we would have:

Windows Server “7” = Windows Server 2008 R2
Windows Server “8” = Windows Server 2012
Windows Server “9” = Windows Server 2014 R2

Actually, let’s get even MORE wacky in “wtfville” by referencing the following slide out of a February 2008 presentation which tentatively places Windows Server 2008 R2 in a 2009 release slot (You know what to do for a full resolution image… I hope):

Hmm, “Windows 2012 Server” DOES have a nice ring to it, now that I think about it! Anyway, Microsoft’s release cycle of 2 years between minor releases and 4 years between major releases still seems to apply regardless of which slide we reference above. Don’t forget that the exact date of release may fall on what appears to be the 1st, 3rd or even 5th year due to a number of factors, such as whether they go by the calendar year, their fiscal year, etc. Basically, what I’m taking away from this is that Microsoft has decided to go with a numerically sequential codename standard. Man, if Microsoft was superstitious, imagine the confusion and mass chaos to ensue when they got to Windows 2013 Server or Windows Server “13”! …oh yeah, I forgot… they ARE superstitious. *cough, cough* OFFICE 14 *cough, cough*

Well, “wtfville,” it’s been real and it’s been fun but it hasn’t been real fun, if you know what I mean! And now, let’s see what MJ’s take on all of this is. GO!


PS – Yes, I realize I used “Windows Server ‘7’” and “Windows 7 Server” interchangeably, but so does Microsoft, so, PUH! =)

Oh, and Rafael Rivera Jr. say:

UPDATE: Supposedly, this really was all just a matter of Windows 7 Server being the internal codename for what will be Windows Server 2008 R2 but MJ doesn’t buy it.

Leave a reply