I know this topic has been beat to death in this forum, but I'd still just not understanding how to get around the issue of running QTP on a remote machine after logging in to the machine with RPD.
Here's my situation, I using QTP on a desktop client/server VB.Net app. The app and QTP are installed on the remote machine. Due to company security policies, I am only allowed to use RDP to remote into the machine. As everyone knows, this will work fine until I either minimize the remote session or the screen saver on my console machine kicks in (screen savers can't be disabled, kick in every 10 minutes). even if I wrote or downloaded a utility that would send constant activity on the console to prevent the screen saver form kicking in, The automation I'm running typically runs for several hours to several days at a time.
Since my Colsole machine is a laptop that i take home with me every night, I eventually need to disconnect and shutdown the console. Once I do this, the remote machine is left at the "Locked" screen waiting for the logged in user (me) to press CTRL+ALT+DEL and then enter my credentials, thus causing the QTP script to fail since it can no longer manipulate AUT object since they are not visible on the GUI.
I know I can't be the only one facing this problem. If anyone has a solution or workaround to keep the scripts running on the remote machine after the remote session has been disconnected, I'd love to hear them.
Would PC Anywhere or a similar application work? I used to use SMS Remot and it worked beautifully, but corporate has 'upgraded' SMS and the Remote option is no longer available.
I appreciate any help and sorry about the long post!
Check this key: "Software\Policies\Microsoft\Windows\Control Panel\Desktop" and set the timeout to a large value. Even if your network admin has policies that set these values (i.e. screensaver settings are grayed out) if you are local admin on the box, you can modify these values and set the screensaver not to kick in.
I've read the post from the FAQ's and seen other suggestions. All are basically the same in attempting to disable the screen saver or simulate activity from the keyboard or mouse to prevent the screen saver from kicking in. This does not work in my situation due to the fact that I'm using a laptop to kick off all the remote sessions and eventually I need to shut it down and take it home. I'm running on up to 15 remote machines simultaneously as well.
Does anyone know if something like PC Anywhere would work?