Deployed V4 driver Locked printissue

[tinalt]

I have a customer who has the V4 universal driver installed on a 2019 server. The clients use a Enhanced Point and Print driver, as they should. The problem is they cannot used the locked print function. They error out at the copier. Does anyone have any info on how to get this working with Ricoh drivers? We also have Canon onsite and we don't have any issues with them.

[slimslob]

Re: Deployed V4 driver Locked printissue

Try using the standard PCL6 driver and throw the "Universal Driver" in the ash heap where it belongs. They very seldom support all the features that the standard PCL6 drivers support.

[KenB]

Re: Deployed V4 driver Locked printissue

Are you using the PCL6 Universal version 4.xx (I think the latest is 4.32 or 4.33), or the Type 4 Universal driver? Both are available on the Ricoh site.

They are quite different.

I know that the Type 4 driver has all kinds of limitations.

[rthonpm]

Re: Deployed V4 driver Locked printissue

I have a customer who has the V4 universal driver installed on a 2019 server. The clients use a Enhanced Point and Print driver, as they should. The problem is they cannot used the locked print function. They error out at the copier. Does anyone have any info on how to get this working with Ricoh drivers? We also have Canon onsite and we don't have any issues with them.

The enhanced point and print driver is the substitute used by a connection to a shared printer using a v4 driver if the actual v4 driver isn't on the client system. Unlike a v3 shared print queue, when using a v4 driver the client doesn't download the driver from the server.

To use all of the features of the machine you'll need to manually install the v4 driver on client machines before connecting to the print queue.

It's a hassle to do that so the better option would be to just find the model specific v3 driver and replace the v4 driver with it.

Another fun fact: if you have a mixed OS environment where non-Windows systems also use the same print queue they won't be able to use any queue set up to use a v4 driver.

Sent from my BlackBerry using Tapatalk

[tinalt]

Re: Deployed V4 driver Locked printissue

The enhanced point and print driver is the substitute used by a connection to a shared printer using a v4 driver if the actual v4 driver isn't on the client system. Unlike a v3 shared print queue, when using a v4 driver the client doesn't download the driver from the server.

To use all of the features of the machine you'll need to manually install the v4 driver on client machines before connecting to the print queue.

It's a hassle to do that so the better option would be to just find the model specific v3 driver and replace the v4 driver with it.

This is what I would normally do, however, this requires administrator rights on the clients and in the current environment of my customer that is not available to the end users. Does anyone know why Canon has this figures out and working, and if Ricoh has any plans to address this?

I actually expect this to become more prevalent in the future and will probably only cause more headaches until Ricoh does something about it.

[tinalt]

Re: Deployed V4 driver Locked printissue

Try using the standard PCL6 driver and throw the "Universal Driver" in the ash heap where it belongs. They very seldom support all the features that the standard PCL6 drivers support.

Amusingly this is the exact opposite of what I have experienced in the field. Several times I have removed the machine specific to use the universal to get access to functions that were not working, or not even available on the machine specific.

[rthonpm]

Re: Deployed V4 driver Locked printissue

V4 drivers are still considered fairly niche and only supported in Windows. Traditional version 3 drivers aren't going anywhere anytime soon. With lots of mixed OS environments I've stayed away from v4 drivers, as v3 queues create the proper hooks to support CUPS based hosts to connect to the queue.

Unless there's a real need to use a v4 driver (and there really isn't), I'd always steer all customers to using the traditional driver model.

Sent from my BlackBerry using Tapatalk

[rthonpm]

Re: Deployed V4 driver Locked printissue

Amusingly this is the exact opposite of what I have experienced in the field. Several times I have removed the machine specific to use the universal to get access to functions that were not working, or not even available on the machine specific.

In model specific drivers, you often still have to manually add the additional features like finishers or extra trays. Many universal drivers can query the device to see what features are installed.

The only manufacturer I've seen with the query function in their model specific drivers has been Sharp.

Sent from my BlackBerry using Tapatalk

[KenB]

Re: Deployed V4 driver Locked printissue

One big drawback to the V4 drivers is the port type limitation. Only standard ports are supported.

This precludes them from being used in print controlling apps, such as Equitrac, PaperCut, or Streamline.

[slimslob]

Re: Deployed V4 driver Locked printissue

Amusingly this is the exact opposite of what I have experienced in the field. Several times I have removed the machine specific to use the universal to get access to functions that were not working, or not even available on the machine specific.

According to the information that Ricoh used to put on their driver download page, universal drivers, before Microsoft started messing around with printing, were only for use with pooled printers. Pooling printers required that all printers in a pool used the same driver regardless of make or model. Universal drivers filled that requirement. Of course it also meant that only those features that were available on all the printers could be used.

[tinalt]

Re: Deployed V4 driver Locked printissue

V4 drivers are still considered fairly niche and only supported in Windows. Traditional version 3 drivers aren't going anywhere anytime soon. With lots of mixed OS environments I've stayed away from v4 drivers, as v3 queues create the proper hooks to support CUPS based hosts to connect to the queue.

Unless there's a real need to use a v4 driver (and there really isn't), I'd always steer all customers to using the traditional driver model.

Sent from my BlackBerry using Tapatalk

To mitigate the Print Nightmare vulnerability you need admin rights on workstations to install print drivers, per

KB5005010: Restricting installation of new printer drivers after applying the July 6, 2021 updates

In deployed environments this creates more work for IT departments. Shockingly, they want to use the V4 and the point and print deployments.

I will tell my customer that Canon has there act together and he should look at getting some Canons.

[slimslob]

Re: Deployed V4 driver Locked printissue

To mitigate the Print Nightmare vulnerability you need admin rights on workstations to install print drivers, per

KB5005010: Restricting installation of new printer drivers after applying the July 6, 2021 updates

In deployed environments this creates more work for IT departments. Shockingly, they want to use the V4 and the point and print deployments.

I will tell my customer that Canon has there act together and he should look at getting some Canons.

In other words, you don't even want to try. You think that you can make more money by selling your customers new equipment they don't really need. It is going to bite you in the ass eventually and your customers are going to go to someone like rthonpm who knows what to do.

[tinalt]

Re: Deployed V4 driver Locked printissue

In other words, you don't even want to try. You think that you can make more money by selling your customers new equipment they don't really need. It is going to bite you in the ass eventually and your customers are going to go to someone like rthonpm who knows what to do.

I feel like you are seeing some option that was presented that I am not. I can,
1. Deploy drivers to the workstations using admin credentials(which the customer does not want)
2. Do nothing and leave it broken
3. Move them to a manufacture that has figured out how to use V4 drivers

What are you seeing as an option that I am not?

[slimslob]

Re: Deployed V4 driver Locked printissue

I feel like you are seeing some option that was presented that I am not. I can,
1. Deploy drivers to the workstations using admin credentials(which the customer does not want)
2. Do nothing and leave it broken
3. Move them to a manufacture that has figured out how to use V4 drivers

What are you seeing as an option that I am not?

You can do what rthonpm suggested and have them install the V3 driver that actually has fewer problems than the V4 version regardless of the printer manufacturer.

[tinalt]

Re: Deployed V4 driver Locked printissue

You can do what rthonpm suggested and have them install the V3 driver that actually has fewer problems than the V4 version regardless of the printer manufacturer.

As per my last post that requires admin rights to install on the clients, hence a non option per the customer