Posted by Richard Neer on August 08, 2012 at 21:02:54:
Just migrated a large, multi-location client from using C2004.
Having problems with the Terminal Server used by multiple locations and running CA within each user profile. User cosw.ini has entries for multiple local IP's so that users at a specific branch get routed to a specific machine on the local side that only serves partitions used by that branch. Each TS user profile previously had its own cosw.ini copy placed in the \windows directory of the specific profile. This allowed users at any branch to have a default (once used) IP to select from the list, as well as any screen/font changes they desired.
Now, there appears to be only a single cosw.ini manipulated in the \all users\app data\\signature systems folder, which means that as eash user selects the IP they want from the drop-down list, the next TS user, regardless of location, gets that IP as the saved default. This is causing havoc since they are used to having the same IP they last used already filled in. We use different host machines with unique node names to determine default programs settings for the remote users, like printers and data directories. Many users are so used to the default IP being correct they are not paying attention to it when running CA. And, any settings they may make that impact the cosw.ini, i.e. screen colors, position, etc., are overwritten by the next user connecting to the TS since all users are accessing the same cosw.ini.
How do I specify a unique cosw.ini location for each user profile on TS? I assume that with this, all users are also using the same CATEMP location, which previously was not an issue with each profile having its own, specified in their own respective cosw.ini.
Each user is launching CA with "\\server\directory\comet.exe" parameters.
I must have this resolved tonight for open of business in the morning. There is no turning back now.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.