Printer Problem -

[TDJB3]

I am testing View 5 and have Persona running.  The parent image is Windows 7.

Here's the problem, we add a printer (printer188), run a test, and maybe create a document and print it.  All's fine.  We log off and return to that machine or go to a machine that is in a different pool and the printer/s show up differently and we can't send a print job to them.  The printer name goes from printer188 to printer@#$%#188.  If I have more than one printer, all the printers will have the problem.  I right click on the default printer and I get a menu ( no menus for the other printers.  When I select a menu item such as Printer Properties, I get a listing of all the machines.

Has anyone seen this problem before?

[gunnarb]

Local or network printer?

[TDJB3]

I forgot to mention that these are network printers.

[gunnarb]

Do you get the same problem when you log in (assuming you are a local admin)?

[TDJB3]

Yes, I do have the same issue as well when I log onto a virtual machine.

[mittim12]

Is the print driver installed in the base image?   If you want your printer to roam I would expect this driver would need to beinstalled so that it's available from whatever desktop you connect to. 

[psplnalin123]

For printer problem as the process you are following for the Physical Desktop follow the same on the virtual desktop. Let the users to be add the printer as you configure the Persona management then next time the user login he will get the same profile with printers he installed.

Secondly. you could use the ThinPrint to manage the printers using GPO or local GPO.

https://docs.google.com/viewer?a=v&q=cache:sCAvtcxeIDIJ:www.vmware.com/files/pdf/VMware-View-ThinPri...

[TDJB3]

Psplnalin123

How do I set up ThinPrint without AD?  I read the document and speaks to using AD.

[TDJB3]

I really don't know the answer to this, but do you need to be an administrator on your cloned machine for ThinPrint to work?  Following the logic that is laid down with VMware, it doesn't seem that that would be the case.  I just want to make sure.

[mittim12]

ThinPrint doesn't require administrative privileges to function properly. 

[TDJB3]

Thank you for the response.

[TDJB3]

To resolve this problem, I had to stop the Virtual Printing portion of the agent.  This cleared up the problem.