I have a couple of users who like to logout of their Lync 2010 client. They apparently think that they are being watched through this program. This is a bit of a hassle since we use this program to see if users are sitting at their desk.
I am trying to write a .bat file to automatically kill the communicator process and then restart the program on the remote machine. I am having nothing but success with killing the communicator process using pskill. When attempting to start the client using psexec, however, it will not work.
It will start a new communicator.exe process on the remote computer just fine. It doesn't seem to actually start the program though. There is no icon in the taskbar showing the program is running and communication with the user does not work as it still shows them offline.
On the local machine (the one I am running from), I just use a bat file that calls another .bat file on the remote machine. The .bat file on the remote machine kills all communicator.exe processes using pskill -t. It then attempts to start a new communicator session using "start communicator /fromrunkey" This will start a new communicator.exe process on the remote computer without any problems. That's all it will do though.
Anybody have any suggestions on what I can do to make it actually launch the client on the remote computer? I have exhausted all options I can come up with. I would like to get this working so the users in question finally figure out that if they logout of Lync it is going to just start back up on them. Hopefully after time they will catch on and stop logging out of the program.