David; In MSP 3.3, the device MUST be contactable from the Workstation PC that is going to control it. Due to the nature of ActiveSync itself, depending on the OS, it MAY be possible to contact the device from the PC to which it is ActiveSync'ed or it may not.  But ActiveSync NEVER allows the device to be contactable from some other Workstation PC on the network (a different PC from the one the device is ActiveSync'ed to).  So, with MSP 3.3, you MAY be able to Remote Control the device from the Workstation PC to which it is ActiveSync'ed, or you may not, depending on the OS of the device (WM5 and up usually will work, CE universally will not work).  But you will NOT be able to Remote Control the device from any other Workstation PC when it is ActiveSynch'ed to a different PC.  This is a limitation of ActiveSync that is unavoidable due to the fact that Remote Control in MSP 3.3 relies on having the Workstation PC contact the device. In MSP 3.3.1 (to be released this month), there is a new Tunnel Service available,  If you install the Tunnel Service on a managed Windows PC (which could be the PC the device is ActiveSync'ed to or any Windows PC between there and the Workstation PC that will be Remote Controlling the device), and if you configure the device to connect to that Tunnel Service, then any Workstation PC that can contact that Tunnel Service can Remote Control that device via that Tunnel Service.  Since this relies on a connection established by the device to the Tunnel Service, it allows Remote Control of devices that only support outgoing connections, such as ActiveSync and many WWAN carriers. Allan