Posted by Marc Shevick on December 15, 2005 at 09:53:00:
The following is a citrix issue and the problems that we experienced and resolved (so far). My understanding on the creating of the cosw.ini file is that comet checks to see if there is a cosw.ini in the d&s\all users\app...\signature... folder. If there is not, it checks to see if there is one in the d&s\username\windows folder. If found, all is great. If not, a new fresh one with no settings is created in the d&s\allusers\app...\signature... folder. What appears to have happened is that additional citrix sessions were created by the administrator on Monday creating a new user name, etc. When launching comet, all of the existing scenarios failed and a brand new fresh cosw.ini is put in the all users folder. From that point on, all of the other users are screwed. It looks like cosp refreshes it printing settings from the cosw.ini every time it prints. Therefore, once the new cosw.ini if created, all printing settings go away. When you have some time, would like to discuss options so that client does not have to remember to copy a cosw.ini into a user's folder every time a new citrix session is created.