The Evolution™ payroll service-bureau software, from iSystems, includes an Evolution Client (formerly known as EvoRemote) component used to provide a desktop application that phones home to the Evolution servers.

Though the vendor (Asure née iSystems) does not support the client software under terminal services, it's been made to work in the past; these notes discuss some considerations to smoothe the way a bit.

Installation steps

Evolution does not require administrative rights to run, but it does require them to install it. We've compiled these steps that we believe will help an IT administrator get Evoluition working for local users.

1. Log into the servers' physical console as Administrator

This can be done either by going to the physical keyboard/display attached to the server, or using terminal services with the /console switch to enable takeover of the physical console.

2. Put the server in "install" mode

This is done by getting to a command prompt (Start » Run » "cmd" + ENTER), then switching the mode:

C> change user /install

You'll be visiting this CMD window again shortly; just minimize it for now.

3. Install the software using the defaults

The EvoClient_version.MSI installer defaults to the \ISystems directory in the drive with the most free space; most users prefer to force this to install in C:\ISystems in case another drive is selected.

Evolution no longer installs into \Program Files\, so if your installer is defaulting here, please obtain a newer installer from your service bureau. Do not attempt to install Evolution to any version of Program Files.

4. Open the permissions on the installation directory

When Evolution is updated on the server — usually multiple times per month — the remote client automatically downloads newer .DLL and .EXE files; non-administrative users require write permissions to the iSystems directory.

Use Windows Explorer and navigate to My Computer, then C:\, then right-click on the \ISystems folder and select Properties. Select the Security tab and add Full Control for All Users.

Failure to open these permissions will prevent these routine updates from taking place.

5. Turn off installation mode

Returning to the CMD window that was opened earlier, change the terminal services mode back to /execute.

C> change user /execute

Special considerations

We have limited experience with Evolution under a terminal services environment, and will offer these notes (most of which related to multiple concurrent users).

When a user logs into to Evolution, it first checks to see if a code update is required from the server; if so, it starts the download process. Since this involves replacing the existing code, the update will fail of some other user on the same server is running Evolution: Windows cannot delete or replace any program components that are in use. In this case, it's necessary to get all users out of Evolution, then one user logs in to allow the update to complete. Once done, other users can logon as well.
It's possible that the reporting components used by Evolution may misbehave in the face of multiple concurrent users; we have not seen this fail and have no real way to investigate, but our suspicion is that it may be be problematic.

Users noting additional steps or considerations are encouraged to report them to your service bureau where they will find their way back to these notes.

This page is not published or supported by iSystems, the software vendor. Payroll end users should always contact their payroll provider's customer service staff for assistance.

First published: 2009/01/24
Updated: 2019/04/24

More Evo Tips

Does this site look plain?

Steve Friedl's Evolution Tech Tips

Terminal Services considerations for Evolution Clients

Installation steps

Special considerations