Due to some badwidth constraints, I would like to run MAS90 on a terminal service server.
Our main MAS90 install resides on a Novell server. I would like to install the client on the terminal service machine and allow others to access MAS90 via that. The problem I am running into is that MAS90 is creating some kind of locking file that indicates to other sessions that the MAS90 launcher is already running. Is there a way around this? I am not opposed to moving the MAS90 data to the server's harddrive if thats what it takes.
Oh, and to clairify, we are currently running Terminal Services on a 2K machine and we do not currently have Citrix Metaframe, but may consider purchasing that, if that will do the job.
Our main MAS90 install resides on a Novell server. I would like to install the client on the terminal service machine and allow others to access MAS90 via that. The problem I am running into is that MAS90 is creating some kind of locking file that indicates to other sessions that the MAS90 launcher is already running. Is there a way around this? I am not opposed to moving the MAS90 data to the server's harddrive if thats what it takes.
Oh, and to clairify, we are currently running Terminal Services on a 2K machine and we do not currently have Citrix Metaframe, but may consider purchasing that, if that will do the job.