We have what is probably a short term problem - but it's a BIG problem.
We have a graphical application coded in AcuCobol (oops - Extend - showing my age there!). It launches automatically when the Windows system starts. This is important.
And the second critical requirement is, we need to be able to sign into the system remotely and interact with the program. We currently do this with Remote Desktop.
This is easy under Windows desktop (10 & 11) and in the past it was doable on Windows Server. But it's getting harder and harder to accomplish in later Windows Server versions, and in WS2019 it seems impossible. We have not been able to find a way to make the program (1) launch automatically when the server boots, (2) with a graphical UI, and (3) allow us to access & interact with it remotely.
Of course we could refactor the application to separate the UI and the rest of the program, but that is more work than we are willing to take on right now. And really the perfect solution would be to allow remote access via web browser, not RDP.
It seems like AcuToWeb almost does this: it allows a GUI AcuCobol program to run on one system, and access it from any other system via browser. That would be a perfect solution except the program does not start until one connects via AcuToWeb.
If we could get the program to launch from eg Task Manager, and then run within the AcuToWeb architecture so we could access it remotely, that would be perfect. And WS would allow it because it's not interacting with the desktop/console.
Is there a way?
(AFAIK it would not be possible to launch the web browser with the AcuToWeb URL on boot, because that accesses the Desktop, and thats the sort of thing WS2019 does not support)
Many thanks in advance for any answers, hints, or tips. Or even a definite "that cannot be done".