Each host needs to have dedicated hardware and a dedicated OS to connect to.  If Sun ray is a distributed computing solution where all the desktops run a thin terminal that then connects to a server running shared resorces this won't work.  

It would work if each client had dedicated OS and hardware or even a Unique environment for each client like how VMware or Hyper V does.   

The issue of a terminal session is that the pcAnywhere host connects to the root hardware if you will rather than in that session's information only.  This limits the host because there isn't a root session and if it did connect to the root session each individual session would also try to connect again to the root thus the error that it is already running or that it can't run because it can't connect to the root resources.

cheers.

I've been unable to reply for a while but in response Sunray is basically "VirtualBox" which is a VMware type of virtualisation. Each OS is a real entity. The hardware is shared as in VMWare also. I'm afraid i dont understand anything lower level than that.

This was in case anyone did know, I can now follow this up with a  call to Symantec support and if i find anything I will post it here.

If RDP is used to connect to this "Sunray" device, then the problem is likely the conflict described in the following KB article:

"pcAnywhere Host, RDP, Terminal Server and Citrix don't work at the same time" at http://www.symantec.com/docs/TECH137703. 

As a result of this conflict, if pcAnywhere is installed via Remote Desktop, then the Symantec pcAnywhere Host Service will probably fail to start.  A reboot should resolve that issue.  Once the pcAnywhere service starts and a host is running, a subsequent Remote Desktop connection will probably cause the pcAnywhere service to stop, or at least put it into a bad state again.  I usually recommend that customers choose either pcAnywhere or RDP, but not both.

But its not resolvable for us because in Sunray there will always be an RDP session from the user and when PCA tries to bind to the multiple sessions KVM it falls over. Disconnecting the user probably would work but this isn't an option for 1st line support since they need to interact with the remote user session.

In conclusion backline Symantec have stated to us via a support call that this will not work and there are currently no plans to get it to work (presumably since its a complete product rerwrite). It has become a bone of contention with us and we reverted to Carbon copy in the interim.

Hoping for that product rewrite to be honest.

Have you considered using VNC?  Is there a specific feature that pcA or Carbon Copy gives you that VNC can't do?

You could also try seting pcA to not run as a service but rather as a program.   Maybe put it in the start up list so that way it would be running at the user level instead of at the system leve.

cheers,