ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Windows & Network Issues >> General Windows & Network Issues >> Procedure to setup EVO via TS or Citrix
http://www.istechforum.com/YaBB.pl?num=1195147651

Message started by stew on 11/15/07 at 10:27:31

Title: Procedure to setup EVO via TS or Citrix
Post by stew on 11/15/07 at 10:27:31

Anyone have any recommended best practices for deploying EVO via Citrix or Terminal server? I am struggling with some overall design questions and a few nagging problems and would appreciate any input or links to info regarding how to "BEST" deploy EVO via Citrix or Terminal Server.

I have already completed these steps:

Setup SD-Q setting for the Alternate Drive in all companies (M)
Set all users to map a specific "Terminal Services Home Folder" (Drive M)
Created one empty directory on c:\ists on the terminal server and locked it down so no one can modify it.
Installed EVO to one users (my) "Terminal Services Home Folder"
Copied my EVO installation folder to all my users "Terminal Services Home Folder (M)
Published the App via Citrix using M:\ISTS\EVOERP.EXE M:\ISTS

This seems to be a real pain. Is there a better way to do this via Terminal Server?

One would think you could install EVO to one folder .........oh I don't know maybe C:\ISTS and then point the application to use the TASPRO7ini or any other files from the user profile location.

Anyone care to share their overall setup? My concern is that using the setup I detail out above would an admin need to update every users application every time there was an update to the EVO app correct?

I am struggling with EVO "updating to a newer runtime" every time I just copy over a known good ISTS folder for a new user. Makes me concerned that everytime there is an update I will have issues.

Any help or documents on using EVO via Terminal server / citrix would be fantastic.

Title: Re: Procedure to setup EVO via TS or Citrix
Post by timgolds on 12/06/07 at 13:13:56

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.

Title: Re: Procedure to setup EVO via TS or Citrix
Post by NovaZyg on 12/06/07 at 14:42:50

%USERPROFILE% will work for Evo Only programs and users, but we still have to live with the Classic system, and it does not know what %USERPROFILE% is. So as not to have to maintain multi versions of code we have to write to the lowest common system, TAS5...

Title: Re: Procedure to setup EVO via TS or Citrix
Post by kkmfg on 12/07/07 at 06:36:51

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!

Title: Re: Procedure to setup EVO via TS or Citrix
Post by GasGiant on 12/07/07 at 07:17:32

Aw, c'mon. Classic runs great on my 486's! Try that with Evo :P

But seriously, "Evo, and only bug fixes to Classic" was the highest vote-getter in our less-than-scientific poll last March, so I hope the future plans of ISTech do include a branch at some point. Even understanding users will wander off after awhile. Seems like the sticking point for DBA holdouts has been due to the slowness of the new Evo versions of programs. Now that we have some real improvement in that arena it should be easier to get companies to move up to Evo in the near future.

Title: Re: Procedure to setup EVO via TS or Citrix
Post by kkmfg on 12/07/07 at 09:08:48

;-) 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.

Title: Re: Procedure to setup EVO via TS or Citrix
Post by Tim Goldstein on 12/13/07 at 10:24:04

It's my understanding that the space shuttle will only run on a 386 processor. Even though the 486 processor was in production at the time, NASA could get the code to the 386 since it was obsoleted by Intel!

So they can't update the software or firmware but they can update the O-Rings and the Tiles!

Just a little bit of useless information!

Tim

Title: Re: Procedure to setup EVO via TS or Citrix
Post by kkmfg on 12/13/07 at 11:45:11

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.