Community Chat

Hi all,

I have a schedule that runs every 5 mins ...so I have configured the schedule only with the main task no Login agent(login, Logout) is used. the main task completes less than 30 seconds...so after 3-4 schedule completion, the resource is getting into a logged-out state all of a sudden. is it because the resource gets locked out due to being idle for a long time (4 mins)? if yes is there an option to disable this? Also When I connect to that VM manually through RDP if the VM is idle for 2-3 mins it gets locked out. So is it same case with the schedule? Could use some help here. 

Thanks & Regards,

Vamsi M

Hi Vamsi,

In my cases, I kept Login logic within the automation flow, i.e., the process check whether the machine is logged in if not login in again, also in some case we logout the machine after the execution, the resource gets logged out when it reaches the idle timeout, and our security team didn't allow us to disable this feature. 

We can also use some utility automation to do mouse move, click ALT in a loop to keep the resource session alive. Please let me know if u need more help on that.

Hello Vasmi,
yes, the auto log-out can be disabled - ask your infrastructure admins to set a special policy for your VMs.
And yes the same setting applies for both login via RDP connection and via login agent (schedule). 

Hi Vamsi,<o:p></o:p>

<o:p> </o:p>

for example, you internal IT team is not willing to disabled the group policy. Try below solution.<o:p></o:p>

<o:p> </o:p>

Below script, copy and paste into note pad and save it as 'Numlock.vps' in the RDP machine desktop. Once the file has been created and select the file and do right click and open.<o:p></o:p>

<o:p> </o:p>

<o:p></o:p>

<o:p> </o:p>

Then below script will run automatically and make system as active,  later in the background it will keep on press num lock. So that machine won't be in idle state and it will not auto locked.<o:p></o:p>

<o:p> </o:p>

Note: because of this script no issue will happen to your automation script.<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p>

Code:<o:p></o:p>

<o:p> </o:p>

Set wshShell=wscript.CreateObject("WScript.Shell")<o:p></o:p>

do<o:p></o:p>

                wscript.sleep 4000<o:p></o:p>

                wshshell.sendkeys"{NUMLOCK}"<o:p></o:p>

                wscript.sleep 4000<o:p></o:p>

loop<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p>