Using the normal RDP you cant access any of your videocard specific functions. Try to use VNC.
Well I know for sure that OpenCL fails because the video card is technically "turned off" (at least the drivers) when RDP is being used. Thus poclm and other GPU miners do not work. So yeah in that case VNC is the way to go. I do not like VNC though cause I find it much slower than RDP.
In regard to RDP and video drivers..read this:
"Terminal Services both on Windows Server 2003 and Windows XP include a
driver that acts as the video driver within the TS user sessions. This
means that the local video hardware on the server is not used. All
graphical output created inside the TS user sessions is directed through
the RDP video driver, which converts the GDI calls into an RDP video
stream being forwarded to the network driver. As a result the quality of
video hardware on the Win2003-based or XP-based Terminal Server does not
directly affect graphics performance of TS user sessions"
@ Jaime Frontero
RDP takes over and masks the existing system video drivers, so you do not have access to video card functions normally handled by the drivers. Tools that access the video card at a low levels (ie bypassing the drivers) will still be able to read info from the card..ie tools like GPU-Z and such, temp monitors, etc.