>>Since you have been running into this net-wall for a few days now, instead on trying to break all bricks in this wall, try another approach: get # of errors with exe on share.
>>Either provide a local install manually or give it half a day to get a loader or launcher fitted to your install.
>>Compare # of errors after a week. If local install incurs markedly less errors, use a loader on all "difficult" sites.
>>Show any admin not happy with each user having same exe in his "local" files the reduction of errors and ask him if he wants to start straightening out all the errors you sidestepped.
>>Ooops - you have cached ALL the exe-internal network accesses to your local disk ;-))
>
>Installing application locally or storing anything locally, so far, is out of the question. This installation of my application is in Europe (small country). They are very keen on their security.

As today is May 1st, to honour all working those keen security stiffs: (－‸ლ) (－‸ლ) (－‸ლ) (－‸ლ) (－‸ლ)
From a "permission threat" it makes no difference at all if you run from a share on server or local install.
As soon as there is a process ID on client, it could spell trouble.
Running the exe from share might marginally offer better tracking with less effort - perhaps Al can offer opinion.

> They don't trust "outsiders", especially from the USA :).

Whisper to them on the phone you are Russian ex-pat (and hope NSA does not heighten your threat score)

> And as far as they are concerned, they view Americans as people who either shoot each other or watch football (the American football, of course) :)

Every nation has special kinks - although me neither carrying a gun nor enjoying talking to death is hard to place.
Esp. as I might watch a boxing or MMA fight, but won't look at groups of people pummeling small objects, be it soccer or football