I am experiencing an issue with a company written program and printing on Citrix. Basically the program prompts the user to select a printer when they want to print a label and it saves that printer name on an .ini file. Everything works fine until the users logs out and then attempts to log back in to use the application. They try to print the lable and the program will not prompt for a printer because it has already saved the printer that user will be using and then it crashes. The problem is that Citrix renames the printers Printername in Wi....... from session ...
Well they server they connect to and the session change from time to time and the application can't find the printer name preciously saved crashing the entire application.
I have read something about Legacy printer names being a possible solution but after reading some more on it I am not sure I understand the concept.
Would that feature really help? if so, any good resources on implementing it?
What I really need is for the printer names to remain unchanged.
I am using PS4.5 on Windows server 2003 with remote users over a WAN.
Any ideas or comments leading to a solution would be very much appreciated.
Thanks
You would need to do a combination of legacy printer names, and telling Web Interface to not use dynamic client names. That should keep the printer name the same.
It's also the session number that's the biggest problem... not the client name itself. If you can set this printer up as a network printer instead of a client printer, that would take care of it, too.
Why is it called "Common Sense"? It doesn't seem all that common!
I agree, it is the session ID that is a problem. I configured the Legacy Printer Name policy and being the first time I do anything with Citrix Policies I am not sure if this is something I have done wrong but after applying the policy, I connected to Citrix and the server mapped my printers, however when I send a print job to it nothing happens.
Any ideas on this?
I do agree, network printers would eliminate 90% of my headaches but this is being run over a WAN so I am not sure how it would work... I will test this possibility as well.
Thanks for all your replies and good ideas.
We have a similar setup - a legacy app that writes an .INI file to the Windows folder. I use a vbcript at logon, it checks for the existence of a Win32_Printer, with a certain beginning portion of a name (in our case, the script looks at: left(objPrinter.Name,8) = "DYMO Lab"), then the script re-creates the .INI file, pumps the correct entries to it. It can also load registry entries for settings. Seems to work flawlessly - it doesn't matter what server, or session name - it finds the session mane of the printer and puts that into the file.
I can post this, if you want. Can also help with the modifications you may need for your environment. This has been working for Citrix 4.0 and XenApps 4.5