Jump to content

Recommended Posts

Posted

A member of staff has brought something to my attention and that is the colour options on the toshiba driver that are used for our Toshiba MFDs around school.

 

So, on windows LTSB2016 the colour option within the driver defaults to AUTO even though the default options on the server are set to Black & White,

 

On windows LTSB2015, the settings are replicated from the server as expected.

 

I've already got an issue with the toshiba driver that no one wants to own up to, could this be another issue and a nail in the coffin for the toshiba drivers on our network.

 

Getting staff to change the setting to black & white each time they want to print is not acceptable as we want BW set as default with the option to change to colour. Having this option set as AUTO means jobs are going to be printed in colour if no one checks the settings.

 

Those of you who are using Toshiba MFDs around your school with windows 10, please check to see if you get the same. We are running the latest version of the PS3 driver on the network.

 

Thanks

Posted
We had this problem with our Toshiba machines. It stopped happening when we upgraded our print server to Server 2016 from Server 2012.
  • Thanks 1
Posted
We had this problem with our Toshiba machines. It stopped happening when we upgraded our print server to Server 2016 from Server 2012.

 

Ah - that would make sense.

Posted
We had this problem with our Toshiba machines. It stopped happening when we upgraded our print server to Server 2016 from Server 2012.

 

Can i do an inplace upgrade from server 2012r2 to 2016 or should i start with a new server? Would the inplace upgrade trash the server?

Posted
Can i do an inplace upgrade from server 2012r2 to 2016 or should i start with a new server? Would the inplace upgrade trash the server?

 

I have never done an in-place upgrade. I start a fresh and migrate when I do it.

 

Thanks

Posted

Thanks, so i did an inplace upgrade on one of our non inuse 2012r2 VMs and everything went well. Tested the toshoba mfd driver and yep, the river replicates to the client machines without any issues.

 

Now to think about moving the papercut server to 2016.

  • 2 weeks later...
Posted

Now running on Server 2016 (the migration was very very simple) however the issue still remained but was able to solve the issue so i'm not entirely sure upgrading to 2016 has actually cured the issue.

 

Once papercut was working on the new server, i tested the driver issue on my workstation and found the print preferences settings (colour: auto) within the driver weren't been applied correctly (should have been colour: black and white) that were set in the Server's Print Management.

 

Instead, the default print preferences for drivers on the print server had to be set at Control Panel > Devices and Printers > {printer queue} rather than in the print management. I wonder if this is how it should have been set on Server 2012R2 rather than setting the default print preferences in the print management.

 

I tried both advanced and general settings - both via control panel > devices and printers and via print management on the FollowMe queue and the only way that worked was via control panel, setting this via print management didn't have any affect on the issue.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...