Naming discrepancies across Print Servers
-
Yes - ServerS
For some reason the Vendor has setup a number of (Azure) servers to address printing. Sadly, it would seem that Printer NAMING is not the same across them.
While I am trying what I am able to do to argue this down to one - OUR PRIMARY - print server; is there any functionally practical way to correct the naming of each printer across the print servers without having to 'match and correct' on each?
-
@gjacobse said in Naming discrepancies across Print Servers:
Yes - ServerS
For some reason the Vendor has setup a number of (Azure) servers to address printing. Sadly, it would seem that Printer NAMING is not the same across them.
While I am trying what I am able to do to argue this down to one - OUR PRIMARY - print server; is there any functionally practical way to correct the naming of each printer across the print servers without having to 'match and correct' on each?
FFS, good luck, that place sounds like a cluster
-
What? They have hosted servers in Azure that are acting as print servers? OMG - WHY?
Yeah, let's send this huge payload to Azure, then back to the local network for the printer - why not IP printing?
-
@gjacobse said in Naming discrepancies across Print Servers:
servers without
As a pratical way you would have centralized printing on a CLoud Service but with Windows Servers then you will have to manually match and correct or somehow script it.
