Windows Terminal Server Sessions

jleask · Post by **jleask** » Tue Sep 20, 2005 9:16 am

We have RoboTask installed on our Windows Terminal Server - and when we log into the machine with multiple sessions and each session has robotask open - the problem we end up with is that changes made in one session are not carried over to the other.
How can we avoid this? Please advise (or ask if you need further clarification).

Post by **Oleg** » Wed Sep 21, 2005 7:03 am

Are you using the same folder of tasks for all sessions? RoboTask is not adapted for sharing of tasks, therefore only final changes has effect.
By default the tasks folder is placed to local profile of each user.

jleask · Post by **jleask** » Wed Sep 21, 2005 7:07 am

Yeah - we realized that they shared the folders but did not update the other sessions using the same folders. The problem is we log in with a standard network name, not individual accounts.
Unless you have a better suggestion it looks like we're just going to have to make concious decisions to develop on 1 box, impliment on another, and make sure the program is only open in 1 session.

Post by **Oleg** » Wed Sep 21, 2005 7:26 am

What impede your users to logon under individual accounts? It's not difficult and your users will not disturb each other.

jleask · Post by **jleask** » Wed Sep 21, 2005 7:37 am

Theoretically it's not a problem but our IT team has it setup that way for years and it'd be more of a hassle to have that changed then to just make sure only one session has robotask open.
Thanks for the help Oleg - greatly appreciated!