So here's the issue,
We use Windows Remote Assistance for remote controlling employee's computers when troubleshooting issues.
Almost all of our employees use virtual desktops through VMware, running Windows 7 32bit with some machines running 64bit.
Remote Assistance is enabled on all of our machines.
Some of our technicians are experiencing a weird problem. Sometimes, seemingly randomly, when they send an employee a Windows Remote Assistance request and the user tries to accept the request, the end-user's machine will suddenly shutdown and reboot. This of course delays our technician from being able to troubleshoot the issue and can sometimes lead to lost work for the end-user.
I've done some Google searching as well as searching within this forum but so far I haven't come across anyone else who's ran into this issue before. I've never seen it happen before and we aren't finding anything terribly significant in Windows logs so far.
So I am looking to see if anyone in the community has ran into this issue before and could possibly shed some light on what might be going on.
This problem doesn't happen all the time, and certainly is not following any discernible pattern. This makes it incredibly difficult to troubleshoot or otherwise look into.
We use Windows Remote Assistance for remote controlling employee's computers when troubleshooting issues.
Almost all of our employees use virtual desktops through VMware, running Windows 7 32bit with some machines running 64bit.
Remote Assistance is enabled on all of our machines.
Some of our technicians are experiencing a weird problem. Sometimes, seemingly randomly, when they send an employee a Windows Remote Assistance request and the user tries to accept the request, the end-user's machine will suddenly shutdown and reboot. This of course delays our technician from being able to troubleshoot the issue and can sometimes lead to lost work for the end-user.
I've done some Google searching as well as searching within this forum but so far I haven't come across anyone else who's ran into this issue before. I've never seen it happen before and we aren't finding anything terribly significant in Windows logs so far.
So I am looking to see if anyone in the community has ran into this issue before and could possibly shed some light on what might be going on.
This problem doesn't happen all the time, and certainly is not following any discernible pattern. This makes it incredibly difficult to troubleshoot or otherwise look into.