Jump to content
Welcome to our new Citrix community!
  • 0

Xenapp 7.13 Auto created printers not creating


Mairi Raby

Question

We have Xenapp 7.13 running on Server 2016

I enabled extra logging on the Xenapp printer auto creation in the Policy and now it gives me an event viewer error, so at least my policy is working

 

Printer auto-creation failure. Reason: AddPrinter() failed with status 0x705. Client name: (WSMTP117) Printer name: (Citrix UNIVERSAL Printer (from WSMTP117) in session 29) Port name: (client:29) Driver name: (Citrix Universal Printer) Print processor: (Citrix Print Processor)

 

Printer auto-creation failure. Reason: AddPrinter() failed with status 0x709. Client name: (WSMTP117) Printer name: (Microsoft XPS Document Writer (from WSMTP117) in session 29) Port name: (Client:29:Microsoft XPS Document Writer) Driver name: (Microsoft XPS Document Writer v4) Print processor: (WINPRINT)

 

Printer auto-creation failure. Reason: AddPrinter() failed with status 0x709. Client name: (WSMTP117) Printer name: (Microsoft XPS Document Writer (from WSMTP117) in session 29) Port name: (Client:29:Microsoft XPS Document Writer) Driver name: (Microsoft XPS Document Writer v4) Print processor: (WINPRINT)

 

It does not auto create any printers at all, including the printers I have loaded from the Network.

Under xenapp 6.0 All printers were auto created.  I have set the Citrix Policy to autocreate all Client printers, Also Client Printer redirection is enabled.

What am i missing???

Link to comment

2 answers to this question

Recommended Posts

I fixed the issue.  I had Xenapp 6 previous and it always loaded all printers as the universal driver was turned on by default.

On 7.13 the default is for the universal driver to be not turned on.  Once I enabled that policy then it did exactly as i expected.

The auto creation errors above were misleading errors.

The redirected/autocreated Local printers are now working, with the Auto Create Client Printers and Auto Create Generic Universal Driver.

 

The way I discovered this was to load a driver foreign to the system onto my PC and the server and log on and the printer was auto created as a session printer.  

So then I enabled Auto-Create generic Universal Printer Policy and it all flowed, without the need for drivers to be loaded for each printer onto the Citrix VDA/Server

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...