Microsoft: Windows Server 2012 R2 goes gold

Microsoft: Windows Server 2012 R2 goes gold

Summary: Microsoft has RTM'd its 'Blue' version of Windows Server, a k a Windows Server 2012 R2, according to company officials.


Not too surprisingly, given the two teams work in lockstep, Microsoft has released to manufacturing Windows Server 2012 R2, alongside Windows 8.1 client.


Windows Server 2012 R2 is the "Blue" update to Windows Server 2012. Microsoft officials announced in a blog post on August 27 that the R2 release has RTM'd. (I'd bet it probably did on Friday, August 23, the same day that Windows 8.1 did.)

Microsoft execs also acknowledged today that Windows 8.1 has RTM'd and is being handed off to OEMs starting today, August 27.

The Server team announced a couple of weeks ago that they would be withholding availability of the RTM bits until October 18, which is launch day for Windows 8.1 and Windows Server 2012 R2. The team acknowledged that no volume licensees, no MSDN/TechNet subscribers will be getting the gold bits until that date. Only the OEM partners are getting early access to the RTM bits.

The reasoning on the server side seems to be the same as on the client side: Microsoft plans to continue to update the RTM bits right up until the time of launch.

In today's blog post, officials also reiterated that the next version of Windows Intune (Wave E?) will also be availble as of October 18. Microsoft is still on track to delvier System Center 2012 R2 on October 18, according to today's post. (The post does not mention whether System Center 2012 R2 "RTM'd" yet or not.)

I asked whether Microsoft also released to manufacturing Visual Studio 2013 today and was told this has not yet happened. Microsoft released a preview test build of Visual Studio 2013 in late June. Officials have said VS2013 should be commercially available before the end of calendar 2013.

Update: Also, for those asking, here's all we know so far about Windows Server 2012 R2 pricing and licensing.

Topics: Windows Server, Microsoft, Software Development, Windows 8


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • How about Hyper-V Server 2012R2 ?

    Is there still a 2012 R2 version of the *free* Hyper-V Server?
  • Is this Windows Server 2012 R2 for Phones and Tablets?

    I try the Windows Server 2012 trial and see the children's touch interface with colour squares. Trying to understand and use Windows Server 2012 during a month is really frustrating and return to Windows Server 2008 R2.

    I don´t understand why Server OS has a touch OS. Never see a server with a touch screen!!!!

    Has Windows Server 2012 R2 solved this removing this ugly UI? Is the main bug i found in this version.
    • Don't use it if you don't like it

      There's no need to use the new UI.
      Srever 2012 boots stright to the desktop.
      Add your favorites either to the desktop or to the task bar and foret the new UI.
      Arguing that the new UI is a sufficient reason to discard the OS is humm. I'd prefer not to say waht I'm thinking to.
      • UI

        Hmm, not choosing server OS due to a UI, and only based on features and performance...let me guess your choise OS is Linux or Solaris.
    • it is not only Ugly...

      ...but it is also idiotic. Each time I need to logoff (Sign Out they call it now) from a server I need to move my mouse all along the 28" diagonal of my screen from bottom left to top right. How ill concieved is that ?
      (Please dont argue CTRL+F4, I use lots of RDP windows at a time and I can never be sure where focus is)
    • Silly

      This is silly, why you don't install the server core and use it by the PowerShell.
  • 2013

    Quit being goofy with version names; just call it Server 2013.
    • I agree. We need to focus on the important things.

      I agree @Glonq. We need to focus on the important things like what the name of the version is rather than trivial things such as the functionality offered by the product
  • Dear Microsoft: It's 2013

    Or: why using year numbers for version numbers makes your products look old.