Closed betullam closed 2 years ago
What is the status on this? Have you already done anything?
We are still investigating running the Alma Print Daemon as a Windows Service.
Any news on this?
Great news, thank you!
Please note that general release of 1.3 will come first. The version that can run both as a service, and in its current form, will most likely be numbered version 2.0.
Alma Print Daemon 2.0-beta is available with this new feature.
https://github.com/ExLibrisGroup/alma-print-daemon/releases/tag/v2.0.0-beta
Has anyone been running the 2.0 beta as a service? Any feedback?
@mgobat: Yes we are running it as a service and as far as I know it works without any bigger problems. But to be able to give you a correct answer I should ask the person in our IT department who installed it on our printer server. I will get back to you as soon as I have an answer.
@betullam, thank you for your response. We look forward to any additional feedback from your IT department.
@mgobat The person from our IT department told me that it is running without problems as a Task, but that it fails when he tries to run it as a Service. I hope this helps!
@betullam, could you please ask your IT person to send me some details on the task vs service experience? I'm at mark.gobat@exlibrisgroup.com. Thank you.
Available in release 2.0.0. Please open new issues if you are having problems running the application as a service.
Our Goal: We would like to run the Alma Print Daemon as a service on a server that manages our printers. It is a Windows Server 2016. We already tried installation and printing - that worked great.
The Problem: After logging off from the server the Alma Print Daemon is closed. Thus printing is not possible anymore. Due to our security policy every staff member that logs on to the server and does some work on it has to log off after he/she finished and therefore the Alma Print Daemon is closed also.
Our Feature Request: It would be great if the Alma Print Daemon could be run as a service that starts up when the Windows Server starts, without the need that a user logs in and starts the app manually. It would also be necessary that the app starts un-paused (see issue #1)