make mathematica recognize CCompiler and compile CUDA code on remote Windows machine

I have set up a Mathematica remote kernel on a Windows 7 64 bit machine, which has Microsoft Visual Studio 2010 installed. When I start Mathematica on the windows machine Mathematica recognizes the C-Compiler without any problems and I can compile code using Compile as expected. But when I connect to the same machine via remote kernel, Mathematica does not find any C-Compiler, i.e.

Needs["CCompilerDriver`"]; CCompilers[]

yields only an empty list {}. When using Mathematica on the same machine locally the MS C-Compiler is listed when using CCompilers[]. How can I make Mathematica recognize my local C-Compilers when connecting via remote kernel connection?

Furthermore how can I compile CUDA-Code via the remote kernel connection, see below for the errors I get, when the MS C-Compiler is working?

Additional Information: I do connect to the windows machine from a Mac using Wolfram-SSH. I am running Cygwin OpenSSH on the remote windows machine. The setup seems to work fine otherwise. I tested remote connections to computers running Mac OS and Ubuntu Linux and I did not have any trouble with C-Compilers there.

Update (CCompiler working, still no luck with compiling CUDA code):

I have been able to get the MS C-Compiler working by explicitly setting

$CCompiler = {"Name" -> "Visual Studio", 
  "Compiler" -> 
   CCompilerDriver`VisualStudioCompiler`VisualStudioCompiler, 
  "CompilerInstallation" -> 
   "C:\\Program Files (x86)\\Microsoft Visual Studio 10.0", 
  "CompilerName" -> Automatic}

But my next step is to get the NVCC compiler to work in order to be able to compile CUDA code using CUDAFuncitonLoad. Unfortunately my intended target Windows-x86-64, which corresponds to my $SystemID is not recognized as a valid target option any more (it is though when running any nvcc compilation locally on the remote machine). This can be seen by executing the following example code:

cudaString = "__global__ void addTwo(mint * A, mint length) {
    int index = threadIdx.x + blockIdx.x*blockDim.x;
    if (index < length)
        A[index] += 2;
}"

res = CreateExecutable[cudaString, "addTwo", "Compiler" -> NVCCCompiler, 
  "CreatePTX" -> True, "CompileOptions" -> "-v", 
  "ShellCommandFunction" -> Print, "TargetDirectory" -> "C:\\temp", 
  "WorkingDirectory" -> "C:\\temp\\Working", 
  "Defines" -> {"mint" -> "int"}]
(*CreateExecutable::target: Target system specification "TargetSystemID" -> Windows-x86-64 is not available for NVIDIA CUDA Compiler installation "C:\Users\Wizard\AppData\ Roaming\Mathematica\Paclets\Repository\CUDAResources-Win64-9.0.2.0\CUDAToolkit\bin\*)

Manually adjusting the compiler paths does not help in this case, the following command gives me the same error as mentioned above:

res = CreateExecutable[cudaString, "addTwo", "Compiler" -> NVCCCompiler, 
  "CreatePTX" -> True, "CompileOptions" -> "-v", 
  "ShellCommandFunction" -> Print, "TargetDirectory" -> "C:\\temp", 
  "WorkingDirectory" -> "C:\\temp\\Working", 
  "Defines" -> {"mint" -> "int"}, 
  "CompilerInstallation" -> 
   "C:\\Users\\Wizard\\AppData\\Roaming\\Mathematica\\Paclets\\\
Repository\\CUDAResources-Win64-9.0.2.0\\CUDAToolkit\\bin\\", 
  "XCompilerInstallation" -> 
   "C:\\Program Files (x86)\\Microsoft Visual Studio 10.0", 
  "TargetSystemID" -> $SystemID]

Update 2 (Changing "TargetSystemID"): As you can see in the code snippet above "ShellCommandFunction" -> Print has been set, but I did not get any output except the error I mentioned above, i.e.

CreateExecutable::target: Target system specification "TargetSystemID" -> Windows-x86-64 is not available for NVIDIA CUDA Compiler installation "C:\Users\Wizard\AppData\ Roaming\Mathematica\Paclets\Repository\CUDAResources-Win64-9.0.2.0\CUDAToolkit\bin\

When setting the "TargetSystemID"->"Windows" (which is the wrong target) in the CreateExecutable-call above, mathematica asks for a correct "XCompilerInstallation"-path, which is a good sign. When I manually supply the path (as you can see in the call to CreateExecutable below) I get more information from the "ShellCommandFunction", which I currently cannot make sense of (except that nvcc seems to be called in the right way):

cudaString = "__global__ void addTwo(mint * A, mint length) {
        int index = threadIdx.x + blockIdx.x*blockDim.x;
        if (index < length)
            A[index] += 2;
    }";

res = CreateExecutable[cudaString, "addTwo", "Compiler" -> NVCCCompiler, 
  "CreatePTX" -> True, "CompileOptions" -> "-v", 
  "ShellCommandFunction" -> Print, "TargetDirectory" -> "C:\\temp", 
  "WorkingDirectory" -> "C:\\temp\\Working", 
  "Defines" -> {"mint" -> "int"}, 
  "CompilerInstallation" -> 
   "C:\\Users\\Wizard\\AppData\\Roaming\\Mathematica\\Paclets\\\
Repository\\CUDAResources-Win64-9.0.2.0\\CUDAToolkit\\bin\\", 
  "XCompilerInstallation" -> 
   "C:\\Program Files (x86)\\Microsoft Visual Studio 10.0", 
  "TargetSystemID" -> "Windows"]

Which gives me the output from the "ShellCommandFunction":

call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86

"C:\Users\Wizard\AppData\Roaming\Mathematica\Paclets\Repository\CUDAResources-Win64-9.0.2.0\CUDAToolkit\bin\nvcc.exe" -ptx -m32 --compiler-bindir "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin" -arch=sm_10 -O3 -v -Dmint=int -o "C:\temp\Working\addTwo.ptx" "C:\temp\Working\addTwo.cu"

But also the following error messages (which I find confusing, because the path mathematica complains it cannot open is never created):

OpenWrite::noopen: "Cannot open !(\"C:\\Windows\\m-1937a361-0128-49fa-8ead-8640028d2166\")." General::stream: $Failed is not a string, InputStream[ ], or OutputStream[ ]. ... and more errors that follow from the initial one