Recommended Posts

Hello folks,

I've noticed that my Microsoft Volume Licensing portal shows Server 2012 Standard and Datacenter versions, but no Enterprise.

Can anyone point me to information that will either explain this or suggest that an Enterprise version will eventually show up?

Thanks!

Edit: I should add that this is for my workplace account. We have had access to Enterprise versions of every server OS so far.

Link to comment
https://www.neowin.net/forum/topic/1118481-server-2012-enterprise/
Share on other sites

With the new licensing model in Server 2012, Standard is the new Enterprise. What features are you looking for that you need from Enterprise?

If you're looking for a full comparison, check out this Wikipedia page for a full list of features (http://en.wikipedia.org/wiki/Windows_Server_2012#Editions)

  • 5 weeks later...

With the new licensing model in Server 2012, Standard is the new Enterprise. What features are you looking for that you need from Enterprise?

If you're looking for a full comparison, check out this Wikipedia page for a full list of features (http://en.wikipedia....r_2012#Editions)

That's pretty square-on - Datacenter Server replaces both Enterprise Server and (understandably) HPC Server, while Standard replaces everything else (and, based on what it includes, *should* have replaced Windows Home Server, as Standard includes the useful-from-the-get-go Hyper-V support that Server Essentials lacks).

The pain in the rear with Standard is that if you use it as a Home Server replacement, you're going to wind up with a multirole server, as it pretty much forces you into the domain model for a standalone server; once you go down THAT road, you might as well make it a *server of servers* (multiple virtual servers hosted via Hyper-V). With multiple VMs (even if just servers), the CPU won't be the bog-down point (unless you're running multiple virtual SQL Server databases) as Hyper-V is surprisingly thrifty when it comes to CPU cycles, but memory may be; good thing DDR3 (standard unbuffered) is silly-cheap.

For the server build itself, for a home or other non-production server (including a test lab), my motherboard recommendation is, weirdly enough, identical to that for a gaming PC - i5 and a Z-series chipset (LGA1155). However, because this *is* a server, it need not be either a K-series (unlocked) or even Ivy Bridge CPU - a Sandy Bridge i5 is just fine. For the GPU side of the server, AMD's HD7750 makes all too much sense (no aux power needed *and* it can be leveraged by RemoteFX, which further de-leverages the CPU)

I got a Server 2012 setup here.

I got an i5 3570K and 16GB RAM on an Asrock z77 pro3 mobo.... now for remoteFX you will need to install desktop services roles and it's a lot of stuff to install... this is in order to use the GPU features.... if you don't install this you end up with standard graphics.

Sorry for not getting back to this after my original question. Thanks for the replies.

I wasn't really looking for any additional features... just wondering what had changed in their licensing model. It seems like a pretty big change to go from thousands of businesses using Enterprise versions to using the Standard version in 2012. Seems to me that it would have been a good idea for MS to provide a ton of information about this change beforehand.

I got a Server 2012 setup here.

I got an i5 3570K and 16GB RAM on an Asrock z77 pro3 mobo.... now for remoteFX you will need to install desktop services roles and it's a lot of stuff to install... this is in order to use the GPU features.... if you don't install this you end up with standard graphics.

Am I correct in assuming that you mean the Remote Desktop Services role?

I got a Server 2012 setup here.

I got an i5 3570K and 16GB RAM on an Asrock z77 pro3 mobo.... now for remoteFX you will need to install desktop services roles and it's a lot of stuff to install... this is in order to use the GPU features.... if you don't install this you end up with standard graphics.

Got a Server2012 Install, was looking at the RemoteFX, but i think ill wait till i get a better video card.

With the new licensing model in Server 2012, Standard is the new Enterprise. What features are you looking for that you need from Enterprise?

If you're looking for a full comparison, check out this Wikipedia page for a full list of features (http://en.wikipedia....r_2012#Editions)

So where does Cluster Failover Manager come in? It used to be an Enterprise feature but I don't see it in the list.

Correct

So, i just went through the process of getting the Desktop Experience installed on my Server 2012 VM. It's actually not necessary to install the Remote Desktop Services role at all. If you go to the Select Features screen in the Add Roles & Features Wizard, you'll see User Interfaces and Infrastructure. This includes Graphical Management Tools, Desktop Experience, and Server Graphical Shell. Install these, reboot, and your server looks much like a Windows 8 desktop. You could also just run "this dism /online /enable-feature /all /featurename:desktopExperience"

Here's a good link on the topic: http://www.win2012workstation.com/desktop-experience/

And Server 2012 Standard (with all the Enterprise goodness) is on DreamSpark! :woot: :woot:

It is on Website Spark as well (a new-for-2012 subset of DreamSpark - thanks to remixedcat for telling me about that); I'm dual-booting 8 and Server 2012 Standard; unlike 8, Server 2012 does *not* require SLAT/EPT unless you install RemoteFX (which works with any GPU that supports DX11 or greater - do you typically see big honking GPUs in a server?). For that reason, I find Server 2012 quite usable in the Hyper-V role.

There are only three paid versions of Windows Server 2012 - Essentials (replaces Small Business Server and Home Server), Standard (which also replaces Enterprise) and Datacenter (which also replaces Multipoint and HPC Server).

Still available (and free) is Hyper-V Server (semi-bare-metal virtualization server that targets Xen and other free hypervisors - in addition to being remotable via PowerShell, it also includes a hyperminimal GUI).

Sorry for not getting back to this after my original question. Thanks for the replies.

I wasn't really looking for any additional features... just wondering what had changed in their licensing model. It seems like a pretty big change to go from thousands of businesses using Enterprise versions to using the Standard version in 2012. Seems to me that it would have been a good idea for MS to provide a ton of information about this change beforehand.

Sorry, I don't have my vendor's PDF's on hand right now, but I'll list what I know. I'm assuming you have SA. If you check through your 2012 license counts, conversion should be as follows:

Every license of Server 2008 R2 Enterprise you owned has become 2 licenses of Server 2012 Standard.

Every license of Server 2008 R2 Enterprise you owned "may" have also become 1 license of System Center 2012 Standard. I am not 100% positive on this, however in reading my vendors 2012 product change guides, it indicates that any ?Enterprise? license becomes 1 System Center Standard license, and I did gain a number of "phantom" System Center Standard licenses that are equal in number to my Windows Enterprise licenses.

For every 2 single processor licenses of Server 2008 R2 Datacenter owned, you gain 1 Server 2012 Datacenter license that covers two processors.

For every 2 single processor licenses of SMSD owned, you gain 1 System Center 2012 Datacenter license that covers two processors.

Every individual license you had of a prior System Center product with SA has become 1 System Center 2012 Standard license. If you had 2 SCCM licenses, 2 SCOM licenses, 1 SCVMM license, you gained a total of 5 System Center 2012 Standard licenses.

For sake of licensing and processor counts, you are now always supposed to round up to an even number. If your server has one processor, licensing requires you count it as two.

If your server is running Server 2012 Standard and is running 1-2 Server 2012 Standard VM, its consuming 1 license. If it?s running 3-4 Server 2012 Standard VM?s, it?s consuming 2 Server 2012 Standard licenses.

There are additional conversions I'm not entirely recalling because I didn't own any.

So, i just went through the process of getting the Desktop Experience installed on my Server 2012 VM. It's actually not necessary to install the Remote Desktop Services role at all. If you go to the Select Features screen in the Add Roles & Features Wizard, you'll see User Interfaces and Infrastructure. This includes Graphical Management Tools, Desktop Experience, and Server Graphical Shell. Install these, reboot, and your server looks much like a Windows 8 desktop. You could also just run "this dism /online /enable-feature /all /featurename:desktopExperience"

Here's a good link on the topic: http://www.win2012wo...top-experience/

I meant that for remoteFX for Hyper-V VMs.

and Server 2012 FTW!!!

I meant that for remoteFX for Hyper-V VMs.

Whoops... totally missed that. I don't know much about RemoteFX yet, but am reading up on it now. I doubt the GeForce 8600GT in my "server" box is enough to utilize it.

and Server 2012 FTW!!!

Yeah, it's pretty slick for the most part. Can't say I like them mirroring the Windows 8 interface for a server OS in production environments, but it does have some great features.

  • 2 weeks later...
It seems like a pretty big change to go from thousands of businesses using Enterprise versions to using the Standard version in 2012. Seems to me that it would have been a good idea for MS to provide a ton of information about this change beforehand.

For what it's worth, back in July 2012 they did roll out stuff like this:

http://www.microsoft.com/en-us/server-cloud/windows-server/buy.aspx

http://download.microsoft.com/download/4/D/B/4DB352D1-C610-466A-9AAF-EEF4F4CFFF27/WS2012_Licensing-Pricing_FAQ.pdf

http://download.microsoft.com/download/C/1/6/C1667DE0-EAC8-4DE7-BC47-E27DAE5B38D6/WS%202012%20Data%20Sheet_All%20Up%20Product%20Overview.pdf

Also, the betas and release candidates all had only Standard and Datacenter installation options, so any organization that was keeping up would have figured out by July of 2012 that this was intentional, and why. While migrating licenses from Server 2008/2008R2 to 2012 can be a bit of bookkeeping work, the Server 2012 licensing seems easier to deal with as there are fewer options, and those are really more targeted at usage scenarios than simply editions to unlock features at higher costs (for example, the only real difference between Datacenter and Standard is cost and virtualization rights - they can both perform the same roles and features).

Is there anyway to get RemoteFX working with non-Quadro/FireGL cards? I have an Nvidia GTX 650 1GB but I haven't had any luck so far getting RemoteFX working properly.

same here :( I got a 650Ti

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!