This relates to installing an Office Jet with hplip for uses on a print server. A good Linux server can operate for weeks, months, and even longer without reboots. hp-setup -i configures the printer. This may not work over pure SSH console-only. It will work with X over SSH via Xming by launching gnome-terminal and then running hp-setup -i in that terminal. The Cups web administration panel works via cupsctl –remote-admin. The firewall needs to allow traffic on port 631 via firewall-cmd –zone=public –add-port=631/tcp –permanent, and then firewall-cmd –reload. Command firewall-cmd –list-all shows the active ruleset. Cups administration website works at http://10.10.10.10:631, replacing the IP address with the one for the Linux server. Windows uses the print via network printer with address of the form http://10.10.10.10:631/printers/Officejet-4630-series, where the IP address is the machine with Cups remote access, and where the printer name is the actual one on the server. The printer name appears in the Cups administration website.
Other notes: Best Practices for the Linux and Application Admins – Great article with mistakes and the lessons learned, Running a program as root on startup [creating a service for use with systemd] – excellent discussion on creating services. Keeping SSH access secure – Basic analysis on dealing with SSH worms that try many username and password combinations. This page on Microsoft’s DevOps for bots has a lot of useful resources such as telemetry, testing, dashboards, and source examples related to bots and smart agents.