Sage 100

We have a customer that moved everybody to terminal server for using Sage 100 Advanced. Now they have latency problems. We thought things were marginal there before the change, so their IT increased disk IOPS -- but it's still having problems. We ran performance tests, running a full rebuild of Sales Order files. In all 3 tests we ran the rebuild from a Sage Advanced client. In 2 tests the client and database were on the same machine (but we tested on 2 different servers), and the performance was consistently good. However the acid test was running the rebuild from the client on the TS, with the db on the ERP server. So, the client is on a different machine on the network from the server. In this case it takes roughly 2.5x longer to complete. My question is this: in this thin-client architecture, what in the world is processed on the client during a SO rebuild? It seems to me there shouldn't be anything. If I can determine what processing is occurring, we can help their IT determine what resources on this virtual image they need to enhance. Any ideas?

Does the Spawn Tasks user preference make any difference? What is the OS of each server?

The OS is Windows server 2008 R2. I haven't messed with Spawn Tasks, but I'll pass it on the IT group. I'm really interested in understanding what sort of processing is occuring on the Advanced client, since I expected there to be not much. @AlnoorCassim - can you shed any light on this?