Understanding settings propagation from server to client (and vice versa ?)
Hello, I've been experimenting with the Seagull print driver in my test environment for a few days, and I'm having some trouble understanding the settings propagation
My goal is to set printing preferences and label stocks for the print queues on the print server. These settings should be deployed to all clients computers. Also, standard non-admin users on client computers shouldn't be able to change the settings.
Here is my setup: the print queues for our printers (mainly TEC EX4T1) have been configured on the print server with the latest version of the Seagull driver. Then, for each print queue:
- Bidirectional mode has been enabled in the "Port" tab, as well as the Tools / Driver Options / Network Settings menu, and is indicating "Available".
- In Tools / Driver Options / Network Settings, I've enabled "Configuration Sharing", "Share settings between Users" and "Share settings between all documents".
- Also in the same menu, "Users allowed to change options" / "Network Users allowed to change options" are both set to "Admin":
- Finally, I've set the printing preferences for each print queue: a few label stocks in Page Setup, and thermal settings in the "Support" tab.
On client computers, printing preferences are successfully inherited form the print server and evrything seems to match up correctly ! (preferences, label stocks,..). Great.
Now here's the issue: I've noticed a few times printing preferences on the server changing magically "by themselves" out of nowhere (for example thermal mode, and other prefences). Like if some incorrect setting on a client was propagated back to the print queue on the server (?)
Can you tell me if there are some mistakes in my setup that could cause such an effect ?
Thanks a lot
PS: additionaly, is a comprehensive and exhaustive manual detailing each parameter of the Seagull print driver available ? This would be a great help !
Please sign in to leave a comment.
Comments
0 comments