Windows Server Core is not certified by Progress for any OpenEdge version. If you require that Windows Server Core are certified for OpenEdge server-side components, an enhancement to the product can be requested through the Progress Community via an Ideas submission, refer to Article 000010839, How to submit an idea for a Progress product enhancement
If this is a critical certification, please contact your Progress Customer's Sales Account Manager to discuss this further.
OpenEdge Windows certification are performed on standard full (Server with Desktop
) Windows installations.
A Server Core
installation does not include the following GUI shell packages:
While maintaining the capabilities required to support traditional business applications and role-based workloads, Server Core does not have a traditional desktop interface. Instead, Server Core is designed to be managed remotely through the command line, PowerShell, or a GUI tool (like RSAT or the Project Honolulu management portal). In other words, there is no local desktop in Server Core, by definition.
User interface elements that are not included in Server Core:
- The Windows Explorer desktop shell (Explorer.exe) and any supporting features such as Themes
- All MMC consoles. MMC tools for managing a Server Core installation need to be run from a different machine running a Full Windows Server install. While enabling the rule groups for Event Viewer, Services, or Shared Folders will allow most other snap-ins to connect, some MMC snap-ins do not have a corresponding rule group that allows them to connect through the firewall and require further configuration before they can connect.
- All Control Panel utilities, except Regional And Language Options (Intl.cpl) and Date And Time (Timedate.cpl)
- All Hypertext Markup Language (HTML) rendering engines, including Internet Explorer and HTML Help
- Most Windows accessories such as Paint, Calculator, and Wordpad, it does have Notepad
- The .NET Framework is also not present in Server Core, which means there's no support for running managed code on a Server Core installation. Only native code, written using Windows application programming interfaces (APIs), can run on Server Core.
While it is possible to install OpenEdge Server components on a Windows Server Core machine, this Windows configuration has never been tested and is therefore not Certified. For example since Windows Server 2012, an administrator can convert from Full Server to Server Core with GUI Management to Server Core. In order to provide support
, any issues encountered would first need to be reproduced on a Full Server
Windows install. Any GUI applications that depend on either the .NET Framework or on the Explorer.exe shell for example, will not run on Server Core.