I tried location based printing in our view 5 enviroment, but it doesn't seem to work.
I have two printers, first is locally attached USB printer which is then redirected into VM via thinprint and second one is network printer mapped directly into VM as shared printer.
By default the thinprint priter gets marked as default printer and I want to change this that the my Xerox 3300 would be default printer.
Here are my settings but they doesn't work. We are using Win7 and 2008r2 for AD server.
After I login, I see both printers and the default one is Xerox 3300, but after 20 or 30s, the default printer is changed to the one added via thinprint.
Should I add both printers into this setings or what I'm doing wrong ?
Also where I could fint this ADM files ?
Nobody uses location based printing ?
Does nobody use location based printing or nobody have any problems with it ? Or is my question simply stupid ?
I don't think your question is stupid. I think would probably happened is that it just got bumped from the front page and no one saw it. You should get some hits this time around.
The ThinPrint functionality in View leaves a lot to be desired.
That being said, the only way I know of to get a printer to map using TP is the way you showed, IP_x.x.x.x and using the GP. That setting will not pick up true TP printers that start with TP_. Now I don't think that's your issue. I just think that unfortunately View has to find and attach your printer every time someone logs on to the VM. The nature of Windows is to make this your default printer.
A simple work around is to just create a script that runs after log in and forces the default printer to the one you choose. I know this isn't pretty, but I do this at every customer now because I can guarantee the results this way. I can't guarantee them the way you are doing it.
Gunnar
How about this pdf document ?
http://www.vmware.com/files/pdf/VMware-View-ThinPrintGPOConfig-IG-EN.pdf
It mentions "thin print" all the time and I thought that I could manage thin print printers via this GPO extension. Well I gues I was wrong.
You can "manage" ThinPrint all you want. But you don't actually own all the functionality of the full ThinPrint. VMware has OEM'd a small portion of it. I know this because I called TP up once for support and they didn't take that call too kindly.
This is what we used to fix the default printer changing to the thinprint printer. We have tested this and it works.
We have auto usb connection enabled and we install the printer driver in the image. This works way better then the thinprint because
with thinprint it is a hit or miss. Also we didn`t want to turn off thinprint in the image because we had users connecting from
home wanting to use their home printers. This way thinprint still works but it won`t change your network default printer.