Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2227
  • Last Modified:

XenDesktop 5 - Printer Drivers

Hello Everyone,

I am currently working with XenDesktop 5 and am having an issue with my printer drivers on Windows 7.  I am using the Citrix Profile Management 3.2.2 and have configured policies for the XenDesktop environment.

The issue is that when a user logs into their virtual desktop they can install the printer.  First time around it asks them to install the printer driver, which is expected and all goes well.  Driver is installed, printer is set, they can set options, and print as if they were still on a regular desktop.  When they logoff and log back on later, the printers are still there, the printer preferences are still there, but the printer drivers are not.  So when you go to print to it, you need to install the printer drivers again.  Drivers install and all is good again.  

Any thoughts on what I need to do to save these drivers?

Regards,

Jason
0
TIDIProducts
Asked:
TIDIProducts
  • 4
  • 3
1 Solution
 
amichaellCommented:
Sounds like the following:

1. You are using pooled images.  A pooled image isn't persistent, so when the user logs off all modifications to the desktop (in this case installed print drivers) are lost.

2. The printer is being saved in the user's profile, which is normal.

If you want the drivers to be present at every login without the need to install upon the user connecting to the printer then the drivers will need to be included in the Windows 7 image.
0
 
TIDIProductsAuthor Commented:
How will that work for the user then?  Right now, you are correct I am using a streamed image in this case, the printer saves in the profile as expected.  So if I install the print driver as part of the image, when the user adds the printer it'll keep that, then when they login again, is it automatically going to install the drivers or know the right drivers exist for it?  

I had done that for one printer, as long as I defined the printer as a local printer it didn't seem to be an issue.  But when I added a printer as a network printer, using the same driver, it still seems to not know where the driver is at.  Does that make sense?
0
 
amichaellCommented:
Are these shared printers?  Or are you trying to do local printing (e.g. local IP)?

If you are connecting to shared printers and the drive you install is the same driver the share is using you should be in good shape.  You can look at the Windows event logs if the printer isn't connecting.  Might give an indication that Windows is trying to use a different driver.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
TIDIProductsAuthor Commented:
Yes these are shared printers.  I have a 2003 server setup as a print server.  That does have the latest drivers on it for the printer in question.  Specifically updated it to make sure it was compatible with Windows 7.

If I define the printer like you are suggesting, as a local printer using a standard TCP/IP port I encounter the same issue, unless I make it part of the image by default.  Then it stays without a problem.  Since I'm streaming the image, this could be a possible solution, although I would prefer to let user define their own printers, or use Citrix Policies to define what printers a person gets depending on where they connect from.  That's another thing that hasn't worked for me yet, but I'll save that for another time.

I'll check event viewer and see what's hiding out in there.  
0
 
amichaellCommented:
Yep, take a look at the Event Logs.  So long as the required driver is included with the image the user shouldn't have to download any drivers.
0
 
TIDIProductsAuthor Commented:
The message that I'm coming up with in Event Viewer is Event ID 1106.  Source MetaFrameEvents, Task Category Printer Management.  Client printer Auto-creation failed.  Driver could not be installed.  Driver possibly not in the list of drivers on the server.  Driver cannot be located.  Driver has not been mapped.  Then it references the client name (endpoint device) and the printer that it's trying to connect to on the server.  

The printer in this case isn't a client printer though because I have not defined any printers on the Wyse Xenith device that this error message is refering to.  I'm still doing some digging on my side into the error.  I'll let you know if I find anything more.  Let me know if you've run into this.
0
 
TIDIProductsAuthor Commented:
Apparently it is pretty picky and since I didn't put the driver in, as the shared printer, it wouldn't detect it properly.  Now that I added the network printer and saved it as part of the image, now the driver maps without a problem.

Thanks for the assistance!  That also cleared up the client printer auto-creation errors in the event log.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now