Via Toshiba EID;
The department code is stored in registry, and it is encrypted and in Binary for security purposes.
This setting is saved in the Registry under
“HKEY_CURRENT_USER → Printers → DevModePerUser → [NameOfPrinter]”. In key Private Print is Binary Value starts at – 08E0, In key Department Code starts at – 0A48.
Now that we have the location where the department code is stored it has helped in tracking down a possible cause of the problem. Things are not totally resolved but I think we have a direction of investigation.
What I have found out so far;
1.) In Registry:
A direct IP based printer queue will create a record in both
“HKEY_CURRENT_USER > Printers > DevModePerUser > [NameOfPrinter]”
“HKEY_CURRENT_USER > Printers > DevModes2 > [NameOfPrinter]”
The Windows Print server based queues only have a listing in
“HKEY_CURRENT_USER > Printers > DevModes2 > [NameOfPrinter]”.
The DevModePerUser record is absent.
2.) Testing our e-Studio 3540c:
* Using the direct IP based printer queue with the driver as delivered for the device via Windows Print server (Toshiba e-STUDIO4520CSeries Driver version 18.104.22.168) I cannot assign the department code to a saved custom printer profile. As the department code is saved in a single location per device this suggests that the driver as supplied is the issue – for some reason it doesn’t refer to the saved departmental code even though it is stored in the registry.
* Using the direct IP based printer queue with an updated driver from Toshiba (TOSHIBA Universal Printer 2 version 7.49.1733.0) the departmental code is saved against custom printer profiles allowing full access to these features without impacting the printing.
This suggests that the fault is with the current driver; either due to
a.) The driver itself having a fault
b.) The method of driver delivery via Windows Print server produces the fault, or driver permissions due to the server delivery cause the issue.
Is it possible to update the driver for our test printer on the Windows Print server to the TOSHIBA Universal Printer 2 version 7.49.1733.0 to see if this problem is resolved?