I would like to know if the server that runs Uniprint requires a GUI interface or can it be the core OS and everything is managed remotely? We are looking at building a new server and wondering if Windows Server 2019 Core would be supported?
Uniprint is not supported on the "Core" versions of Windows Server. We've never tested that and have (till now) not had a request to support it. If the demand to do so increases, we will consider it. I'd be interested in hearing from customers. I'd also like to know why Core is preferred over the GUI versions of Windows server (security?, cost?, server resources?, etc..).
-Jeff Herald - Pharos Systems
Uniprint does require the a GUI interface to get through the installers.
More specifically, the installer will start, but will fail the pre-requisite checks because mmc.exe is not available on Server Core. There is no current plan to move away from this requirement.
Microsoft has indicated that they are evolving Windows Server to reduce dependence on the traditional GUI in favor of remote management using tools such as Windows Admin Center and PowerShell. This is a more efficient and secure model that the industry in general has adopted, especially since IaaS and PaaS continue to supplant traditional on-premises infrastructure.
Yep. I follow the Microsoft motions very carefully. However, there is still a host of "here's what's not supported" in Core that Uniprint requires, which leaves us (Pharos) with choices:
1. Do we wait for Core to catch up with our needs? or
2. Do we drop some supported functions in favor of developing for Core? or
3. Do we develop around Core, but still keep the feature set?
Choice #1 extends our Time to Market once the feature set in Core is available, but allows Uniprint to basically stay "as is" no matter what Windows Server installation option is used.
Choice #2 is likely to be wildly unpopular with anyone.
Choice #3 means that new functions/supported platforms are basically frozen in time while the entire operation of Uniprint is recoded to work with what is available. It's expensive in many ways and restricts, short term, our ability to react to any other dynamics that pop in.
But, we continue to track what's available and real trends in the marketplace. So things may change, or we may stay the course and see what Microsoft does about bringing more features to Core.
My sense after the Pharos Uniprint Roadmap webinar is that Pharos intends to modernize the Uniprint product and sustain a more innovative development approach going forward.
If that is indeed the vision, I think that the answer lies somewhere between choices 2 and 3. However, the decision to drop supported functions because they are not compatible in their current state is different than committing to redevelop those functions in a modern and compatible way.
For example, legacy functionality currently found in the Microsoft Management Console could be migrated to a native web-based application as we are already seeing, redeveloped to support Windows Admin Center and PowerShell, or even further, available to customers programmatically through a REST API.
I would very much appreciate the extensibility and flexibility of REST API endpoints for Uniprint management. This could also help Pharos develop the platform by providing third parties with the ability to extend the solution and provide tools to the greater community.
Choice 1 seems to imply that Core may not currently support what Pharos requires, but I think it is important to differentiate between the potential immaturity of Core as opposed to the legacy architecture of Uniprint.
Looking forward to your feedback!
From a server administrator and security perspective, the less people that have to log directly into servers the better. Core is the direction Microsoft is pushing. The default install for Server 2019 is Core. The size of core is smaller, so patching is smaller/quicker. It does support .Net Core, but I don't know if that would cover what is required by Pharos. I appreciate the quick responses by all.
Retrieving data ...