Scott:
I am currently using RDP to access my SWRemote via a Desxcape. HB server is located on the same machine as the SWRemote, but accessed via different user accounts. I never launch an SWRemote from within the server account, only from within the desxcape account. However, I am having an SWRemote process show up in the server account and this process is not killed by exiting the SWRemote in the desxcape account (though the process is no longer visible from the desxcape account).
I am using command line parameters to start the SWRemote by name via the desxcape account.
Currently, the desxcape is the only SWRemote that is being used on the server via RDP.
If the process is running under the server account and I launch the SWRemote from the desxcape account it is causing connection issues.
Any help is appreciated. My skills are limited and the scope of the user accounts is unclear. If I kill the process using a script on the server account, will this kill the process in all user accounts? Is there a way to insure that all process related to an SWRemote are killed when it exits?
I would like to get this solved while the system is simple. I am getting ready to add 4 additional devices (Nokia 770's) via RDP which will increase the complexity considerably.
Thanks,
Osler
SWRemote Process
So you are saying that you start a SWRemote in a non-server login account and it starts not only the SWRemote you would expect to start, but a second in the server account? Can you see the SWRemote running in the server account?
I don't really know much about Desxcape and how it works to give any specific help related to it. However, the HB Server does not launch any SWRemotes on it's own, so if there is a SWRemote instance running on the server account it must have been stared by something else (RDP connection or even a script on the server??).
I don't really know much about Desxcape and how it works to give any specific help related to it. However, the HB Server does not launch any SWRemotes on it's own, so if there is a SWRemote instance running on the server account it must have been stared by something else (RDP connection or even a script on the server??).
Scott
Yes and no. The process is present but there is no associated application. Meaning that I can open task manager and see the process, but there is no SWRemote to speak of open on the server account (doesn't show up in applications...only processes).
Desxcape is just like an airpanel (SmartDisplay). It just RDP's into the server.
For example, if I go into the desxcape account and start the SWRemote, then go back to server I can see it connected under SWRemotes. Go back to desxcape and exit the remote then back to server and I still see the SWRemote is connected even though I "killed" it. Go back to desxcape and open task manager...no swremote application or process. Go into server and open task manager....no swremote application but a process exists. Its not until I kill the process that that swremote no longer shows up in the HB server (I am using the SWRemote no the local remote btw).
No scripts or batch files used for autostart of a swremote on either account.
Osler
Desxcape is just like an airpanel (SmartDisplay). It just RDP's into the server.
For example, if I go into the desxcape account and start the SWRemote, then go back to server I can see it connected under SWRemotes. Go back to desxcape and exit the remote then back to server and I still see the SWRemote is connected even though I "killed" it. Go back to desxcape and open task manager...no swremote application or process. Go into server and open task manager....no swremote application but a process exists. Its not until I kill the process that that swremote no longer shows up in the HB server (I am using the SWRemote no the local remote btw).
No scripts or batch files used for autostart of a swremote on either account.
Osler
Yes...the above was accomplished by simply switching back and forth between users. No smartdisplay involved.
This does not consistently happen and this hadn't been happening since I upgraded to V3 until an iTunes update a few days ago. Dunno if they're related or not (windows updates are turned off on this machine).
Osler
This does not consistently happen and this hadn't been happening since I upgraded to V3 until an iTunes update a few days ago. Dunno if they're related or not (windows updates are turned off on this machine).
Osler