Hi, thanks for posting.

You've set things up correctly for grid only mode. It's worth noting that turning off the local node in the distributed processing window is by itself enough (the changing of the max processing threads is optional).

When in grid only node, the CPU affinity settings for NCrunch are still applied to the local machine. There is still value of having a dedicated CPU core for the NCrunch engine, as even though the tests are running remotely, the engine still needs to do work to coordinate test runs and merge coverage data.

I would recommend adjusting your CPU core assignments so that NCrunch has a single CPU core and VS has all the rest. If you notice the 'core utilisation' in the corner spinner popup seems to be constantly in the red, you can maybe try giving it two cores.

EDIT: Given complications with the core assignments with VSCSCompiler.exe, I'm changing my recommendation here. You are better to do away with core assignments and simply assign ALL cores to both VS and NCrunch when working in grid-only mode. In this way, the O/S can balance the load and we don't end up cornering the VS build system by accident.