Correct me if I'm wrong. When you have a policy that says not to install client printer drivers and a user connects isn't the Citrix generic printer driver suppose to take over and map the printer for the user? If thats the case what would cause this? _"Client printer auto-creation failed. The driver could not be installed. Possible reasons for the failure: The driver is not in the list of drivers on the server. The driver cannot be located. The driver has not been mapped. The driver is a V4 driver_" Is it somethign to due with the driver being a v4 and citrix cant map that with their generic driver?

Do you have it set to use the UPD in the policy as well?

i'm not sure how it works in later policies, but we used to do driver mapping like HP* to Citrix Universal

There's also the Mac client -> LaserJet driver tom foolery

yes we have it set to use upd in the policy. It appears to only have problems with this v4 version of the driver. May have to install the driver which i really dont want to do

Anytime you do a VDA upgrade/reinstall, make sure to reinstall the LaserJet PS driver

@Jon Bucud where do you get that driver from? Now that you said it I dont have that anymore

I ended up putting it in the sealing script back then, because it was so important.

So i can rule out v4 drivers as being any part of the issue? v4 work fine on client and vda?