Notifications
Clear all
Topic starter
We are currently on EMR 9.8.4 and are experiencing an issue where default printer is picking local printer on the Citirx servers such us Biscom Fax or Microsoft XPS document writer. We have removed the image writer from the environments and this has help with some of the calls but we are now getting more reports of the the Biscom Fax being selected and we are unable to remove that from the citrix server due to it being the faxing solution. We have done some research with within forums and found some details around CPS 12 having similar issues (See Below) and trying to address with a configuration file change. Without GE making any change we are very hesitant to do any configuration file changes.
"In the emr.ini file: from: UseClientName=FALSE to: UseClientName=TRUE This changes how CPS stores the Printer Setup for the EMR side of the application. It stores based on the connecting client name (in our case the thin client) vs server name. The issue in our environment was one user would set a default printer for Prescriptions or handouts in EMR printer setup and it would change it for everyone else on that server. This only seems to affect the EMR side"
Posted : March 10, 2015 8:50 am
Not exactly sure what your specific issues are but EMR9.8.4 has an issue with service provider through the order module not going to the correct location when you have them setup to go somewhere other that your selected default printer. We have been having this issue since sept 2014 when we upgraded to 9.8.4. We have since upgraded to 9.8.7 and still experiencing the same issue. The config change will not fix this problem. Call GE and have them add you to SPR 59601. Talk with them and verify that this is the same issue just to be sure. Last I heard a fix for this issue is slated for 9.9 but I wish it would come sooner.
Posted : March 10, 2015 9:23 am
Hi,
The piece you found and quoted is what fixed this issue for us, we had major problems with it when we upgraded to 9.8 the first time. It turns out when we loaded 9.5 back in the day it was also a problem but the server team director found that out and fixed the file - he had since left when we upgrade to 9.8 and it turns out the file is overwritten during an update so it had to be reset - wish we didn't run around in circles for 3 weeks before realizing it...
Since we made the change over the summer we have not seen the issue again.
Thanks
Mike
Posted : March 10, 2015 10:09 am
The UseClientName will fix the issue you are describing. If you are in a citrix environment and you do not have it set, every time a new users logs into citrix on the same server and changes a printer setting, they will change it for everyone on that server from then on that uses the same session number. UseClientName setting stores the users client PC or terminal name in the database for printer settings instead of storing the Citrix server and session number. This means that printer settings will be tied to the PC logging into the server and any change will be tied to that PC instead of the citrix server.
The only other thing that UseClientName changes is that it disables jobs.txt from running. In a Citrix environment you do not want the jobs.txt to be run by a standard user anyway because most likely they do not have permission to write to the Centricity installation folder. This means that when you push out jobs.txt changes you either need to manually apply them to citrix servers or do it after hours and disable UseClientName, login as an administrator to EMR and so that the updates happen, then switch UseClientName back.
Posted : March 12, 2015 5:02 am
