Almost there!  First, none of the terminal users can see C:\ISTS or Evo will try to use it!  Remove it and remove write remissions from the root!
 
Next, Each user must have complete access to their M drive.  That means the share and security!  if not they can't update the runtimes when there is an update.  
 
Next,  Install the Evo client on session.  Make sure Evo is using M:\ISTS then copy that ISTS directory to each user directory.  Next move EvoERP Local shortcut in that users desktop to all users/desktop.
 
Each user will now have everything ready to go except email.  Have ach user login and set their email settings.
 
Since Evo is a client server application is has to do a lot of work reading and writing data and applications to/from the server.  to help speed things up,  Evo stores temp information and settings in the local ISTS directory.  these files are unique for each session but that isn't a problem on a PC.  It's only when you get to terminal services that it beocmes a problem so every user needs their own ISTS directory.
 
(For Allen) I would be really nice if Evo created the ISTS directory under %userprofile%/Application Data/ISTS Then this wouldn't be a problem as that directory is unique to each user and each user has full rights to their profile directory.
 
Hope it helps.

You see... some people don't appreciate the fact that Evo is being held back by people who refuse to upgrade. This is like coding windows so it'll run on a 286 because some old geezers won't spend 400 bucks on a new machine. Past a certain point you have to quit punishing the users who actually realize which century it is. It's things like this that make other systems seem tempting.
 
Of course, my views on this have long been known: DUMP CLASSIC! It's crap, it always was, it always will be, and we need to move on!

Running evo on a machine more powerful than an etch-a-sketch does help though.
 
But, yes, please cut bait on Classic and fork off the code base for Evo so that we can get nice features and/or bug/annoyance fixes that Tas5 doesn't support.

Actually, I had heard that one of the big reasons it uses a 386 and will probably not be updated is that faster processors are more prone to EM interference because of their smaller gate size. In space there is too much background radiation and it's much safer to use old hardware with large gate sizes.