By using this website, you agree to our Terms of Use (click here)
Device Hub documentation seems a little murky to me leaving me with 2 questions
1) when I am an on premise install....why do i need device hub when the server and my devices are on the same wan albeit different lans
2) assuming it is needed, should it be on the same server as acumatica or is it best run on a dedicated workstation on the same lan as, for example, the warehouse and printer
I haven't used it personally, but my understanding is:
1. Acumatica is running as a IIS web service. Maybe they could have found a way for IIS to talk to printers directly, but I'm not sure if that's even possible. Also, since most Acumatica customers are SaaS, it wouldn't do any good since the IIS server in the cloud wouldn't have their printers installed. Printing from the web browser is limited because of the security in a web browser. So DeviceHub gives Acumatica a more reliable path to your printers.
2. I would think dedicated workstation would be better to keep the Acumatica server as lean as possible. I don't see why the LAN would matter, as long as it can hit the Acumatica HTTPS URL. Also, in some cases like a Zebra printer connected locally to a workstation on the Warehouse, installing DeviceHub on the workstation would be required.
Online Members
