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

Printer Dialog/List extremly slow after reconnect to session


Patrick Schindler

Question

Hello,

we are working with Windows Server 2016 and XenApp 7.15 LTSR CU2.

We use only autcreated client printers with citrix universal printer driver.

 

Our problem is that after disconnect and reconnect to a user session accessing printers is extremly slow.

E.g. when reconnecting to session and trying to print from outlook, word, adobe... the print dialog takes about 10-30 seconds until

all printers are listed. Office says "connecting to printer"...

When completly logging off user session and logging on to new session everything is fine.

 

Any ideas? Do we have something misconfigured?

 

Kind regards,

 

Link to comment

11 answers to this question

Recommended Posts

  • 0

We have about 100 users and lots of individual printers. Therefore we do not want vendor specific drivers on citrix servers.

The problem is not printer specific, which means it happens for users with local epson printer only, and also for users with 5 local other printers...

The only thing they have together is that after reconnect to session the slow printer listing...

After complete logoff and logon everything is fine. Therefore there must be a problem with mapping printers after reconnect or universal printer driver.

 

Link to comment
  • 0

HI!

 

we have the same issue on W2k12R2 with 7.15.2.

We opend a supportcase and did some traces but Citrix is not able to figure out the reason.

We exchanged the cpsv.exe (to 7.15.0.10009 yes its newer than 7.15.2.x).

Also tried the EMF Driver, that mitigated our issue to ~ 8 Sec.  BUT EMF has some bugs, incompleet printign! So we revertet to XPS.

 

At the moment we try to use Native Drivers on VDA for some test Users ( HP PCL6 Universal 6.6.0, with Version 6.6.5 we saw the same problem)

This seems to be the best choice at the moment.

 

 

 

 

Citrix saw errors in our traces when calling CtxPrnGetPortNameFromHandle:

CpUpdLib,clientPCaps.c,2043,UpdIsBoundPrinter,9,Error,"UpdIsBoundPrinter: CtxPrnGetPortNameFromHandle()

its dooing this for about 30 Sec (our delay) then they see this:

CtxPrnGetPortNameFromHandle,15,Information,"CtxPrnGetPortNameFromHandle found port

 

 

 

 

Citrix asked us to try 7.15.3 but there we see the same problem with Citrix universal Drivers!

 

 

no Idea by now, already invested > 200hours

 

Anyone? we gonna pay a beer :)

 

 

 

Link to comment
  • 0

Hello everyone,

 

We are using Citrix Virtual Apps and Desktops 7 1912 LTSR CU2 - Virtual Delivery Agent 1912.0.2000.2345 with server 2019.

 

As a profile backup , we use VMWARE Dynamic Environment Manager to save Network printers.

 

Once the user start the new session, there are no any network printers available. However, after 2 3 minutes, they seems to appear there.

 

This is creating a real problem for many users. Everytime, default printer is changed to "Microsoft print to PDF".

 

Can someone, explain me what is going on here ?

 

PS : We are using lexmark printers in our print server and no any print drivers are installed locally in a VDA Server.  Do we need to install any drivers locally to remove this problem ?

 

Thanks everyone.

Link to comment
  • 0

 

On 5/25/2021 at 3:05 PM, Anup Chhetri1709161910 said:

Hello everyone,

 

We are using Citrix Virtual Apps and Desktops 7 1912 LTSR CU2 - Virtual Delivery Agent 1912.0.2000.2345 with server 2019.

 

As a profile backup , we use VMWARE Dynamic Environment Manager to save Network printers.

 

Once the user start the new session, there are no any network printers available. However, after 2 3 minutes, they seems to appear there.

 

This is creating a real problem for many users. Everytime, default printer is changed to "Microsoft print to PDF".

 

Can someone, explain me what is going on here ?

 

PS : We are using lexmark printers in our print server and no any print drivers are installed locally in a VDA Server.  Do we need to install any drivers locally to remove this problem ?

 

Thanks everyone.

 

We are facing the same issue you describe. 1912 LTSR CU1  with server 2019.

Did you ever get this fixed ?

 

Link to comment

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...