SPM seems perpetually outdated. The last time I looked the latest was almost 1 year old. The Datacenter question has come up a few times with most of our tech folks not noting any issues. 

That being said I don't become embroiled in configuring and supporting server environments because there is a multitude of ways they can be configured. I typically point people to the SPM, advise that I don't believe they will run into issues but if they do they will need to discuss with Sage and not us because we don't provide  extra support  for configurations not on SPM.

TL;DR: If you use something, not on SPM, and call Sage support and they refuse to support it then we don't act as the fall guy.

Thanks Wayne,

I greatly appreciate the response, although I was also hoping to hear from perhaps an IT person or two as well as someone from Sage Engineering. There must be some reason the Datacenter Server O/S keeps reappearing on the SPM.

According to this TechNet Blog it seems like the only real difference is that the Datacenter allows unlimited Virtual Servers as Guest O/S.

We have a development environment running Sage 1016 on a Windows Datacenter 2012 server.

Configured as follows. We have 6 VM's on the data center server all configured in a terminal server farm.

One of the VM's hosts Sage 2016, while the other VM's are terminal server hosts for Admin/Sales/Remote clients respectively (all connecting to the Sage 2016 VM).

Haven't had any issues, but not live for another month or so.

I recently saw some System not supported notation for Contractor version. Also on Server 2012 in a Terminal server environment. Seems to be running fine. I had the same reaction/concern you're feeling.

Hey Cullen - Prior to Server 2008 (if memory serves), Datacenter edition was essentially a different enough o/s from Standard, Enterprise, and other editions and that is why it was not supported. However, since then Microsoft changed the o/s to be identical to Enterprise with the exception of licensing. That is where we are today. There are clients that run Sage 100 on it successfully today and it should run just fine for you as well. I don't see any reason you should change that, especially for your test system. This also means the SPM is just un-updated (still un-updated) on this point.