Centralize Print Server With Seagull With Stock Setup Folgen
We have a centralize print server that we want to use to manage our 100+ Zebra Printers to go along with 3500+ end user Windows Workstations. We have elected to go with the Seagull drivers instead of the native Zebra since we have been informed that it works a lot better and prints better labels. We discover a really strange problem and unsure if this is a configuration issue or is a design/architectural issue.
We have installed one printer queue on the centralize print server using the seagull driver and we modified the stock for the queue. By default, there was 5 stock size to choose from, we only need one or two due to our requirements, and not all zebra printers will have the same stock size as well. We made the modification to the stock size and everything seems to work. Now the bizarre thing that occurs is when we add another zebra printer queue on the centralize print server, it undid all our changes on the first queue and revert back to the default number of stock sizes. What makes matter worst if we make a change to one print queue on the print server (add a custom stock) it automatically changes the other printer queues that uses the seagull driver. Not sure if this was done be designed. It appears that the Seagull print drivers uses some sort of "shared" dll or registery key that each printer queue reads in to determine the number for stock sizes, which begs the question if it was meant to be used in a centralize enterprise print server.
The reason why we wanted to control the stock sizes at the print server level, is because I do not want to modify 3500+ workstations with login scripts, registry scripts, etc. to modify the stock sizes for each driver. Is there a work-around or perhaps a commerical product that Seagull offers that can fix this issue?
Any insight or help would be appreciated.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.