Poor performance 4 users using shared eap file

[Geert Bellekens]

Personally I always recommend the path of least resistance, which means the first choice is to use the infrastructure that's already in place -- buying a new software package carries a cost, and adding a new thing that the users aren't used to in their daily routine is a drain on productivity.

Many organisations these days expect all apps to be cloud based or 3 tiers (n = 3 right) applications.  When you want to put in a full client (let's not fat shame here) application, it doesn't fit their standard deployment models (What do you mean the end user needs direct access to the database server?).

I recently had exactly the same experience. Standard installation of EA fat client with a direct connection to the database was out of the question (against security policies).
The acceptable workaround for the security requirements was to install EA as a Remote App because then it was a "server" connecting to the database, and no longer a client machine.

Must say that it got a bit hot at the time when we discovered this security policy It almost blew up the whole deal.

Geert

[Glassboy]

Must say that it got a bit hot at the time when we discovered this security policy It almost blew up the whole deal.

Some security policies are actually brain damaged.  You can end up removing all reference to the logged in user from all log files, and there for the data flowing into your SIEM is of no use for incident response.