Hello,
I'm having an issue with location based printing and the app that use the default printer. We are running View 5.1, Windows Sever 2008 R2 Print server, I have 2000 users, 800 View desktops, 500 Zero clients and about 15 to 20 different locations on one single campus. We have about 15 printers setup in the thinprint GPO and the policy just basically states that if the Base Device (Zero Client, Thin Client, Desktop, Laptop) hostname starts with the location code (MAIN***) then you get this printer. Well after a lot of trial an error we got the printers show load when a user logged in and we they changed locations, for example if user Jane is at device "Main123" she got printer "Printer1", then when she switched locations and her Floating Desktop followed her to computer "Unit456" she got printer "Printer2". So that part works, most of the time. We still get calls about printers not showing up, and we can just start the TPautoconnect service and the correct printer will show up in a few seconds.
The part I'm having trouble with is when a user switches locations and in their Desktop Session they leave an application open. The new default printer will change in Windows - Devices and Printers, but the app won't pick up the new printer change. And it is not one inparticular app, it is all apps the use the default printer when you select print. I have ran all my tests in Word 2007, I will login at one location, get a printer, open Word 2007, type random letters, select print and the page will print out on the default printer. BUT if I leave Word up and I change locations, I will get a new printer in Devices and Printers, but in Word the printer shows up as the previous default printer, and if I select print in Word it will not printer to the new default printer, it will print to the previous default printer that isn't even loaded in Devices and Printers anymore.
The temporary fix is for the user to just close out of the app before they switch locations or after they switch. Sorry for the long back story, but my quesion is, Has anyone ran into this same issue? And if so, What work around's did anyone come up with? Or if no one has seen this before, Do you have any ideas?