As the folks at IS Tech know, we have our Evo~ERP users networked and pretty mobile (some work over Terminal Services most or all of the time) and have chosen to Evo from a mapped, personal share. This makes our installs a little different than your common dance.
 
This past weekend I ran the update from home via Terminal Services and it went very well, except that the user piece, the runtime, did not update properly and threw errors. One of the warnings mentioned running evoerp.exe on the server (mapped drive L: for us), which we wound up having to do for every user. All we had to do was login as the user, Start>Run: "L:\evoerp.exe L:\", but we had to do that for about forty user names, which meant looking up forty passwords and logging in and out of forty terminal services sessions.  
 
Obviously, we would like to see the runtime update work for each user without a hitch, but at least it worked a lot better on this update than on the last (when we had to delete the contents of the ISTS folder for each user, copy in the default directory contents from the server, and then launch Evo). And, yes, I am whining a bit, but I do understand that we are in a tiny minority of users who do things this way. So, why did I write this? Firstly, to have something in the forum archives about this situation, but also to keep the discussion on this subject in view.

I could tell you, but then I'd have to rip out your eyes and cut off your fingertips.