>>First, there is no issue. This is a installation that does not yet exists. No, the user does not connect using RDP. The user is on the network and the server is mapped to the PC or they use UNC. I was looking for some range of numbers, as far as latency and the bandwidth, to give the IT. So that they spin the VM in the "correct" location.
>
>If each client pulls out the EXE from a remote server, then, that would be an infrastructure where you will need as much bandwidth as you need. We use to run application like this while ago. During these days, it is becoming very rare. At least, if you could have each user to have the EXE and simply pull the data from the backend, that would help. But, then again, if the application is not client/server, and you would do a browser, for example, it would become very slow as this queries an enormous amount of data at any given time.
>
>In that infrastructure, more bandwidth might help, more CPU power from the server and memory.

The application is client/server (with SQL Server database). If I place all executable and meta data on each PC, I will have to design a way to update each client on each update. I know it can be done but I have to think about it.
So far, all other customers use the approach of EXE on the server and the client pulls it at start and goes to the server for meta data when necessary.