Hi @Anoushka 5074 ,

Check the KBs below

https://apeople.automationanywhere.com/s/article/A2019-Simulate-keystroke-command-not-working-when-VM-is-disconnected/

Navigate to CR - > Manage - > Device - > Depoyment
Change the device type from "Regular" to "RDP".

https://apeople.automationanywhere.com/s/article/A2019-Simulate-keystroke-command-not-working-when-VM-is-disconnected/

HTH

Regards

Hi @Raul Jaimes ,

I am not able to access these articles due to some unknown issue. Can you please give the solution in text format in the reply.

Thank you in advance.

Basically is:

KB1.-

Disable start menu at startup or at the time of reconnect.
or
Right click on start menu and select Shut down or sign out--> Disconnect.
or
Add Simulate keystroke command with Esc button to close start menu at the beginning of task execution.
or 
Please use batch file to disconnect the VM .

https://apeople.automationanywhere.com/s/article/Batch-file-to-lock-and-disconnect

KB2:

Navigate to CR - > Manage - > Device - > Depoyment
Change the device type from "Regular" to "RDP".

HTH

Regards

Dear @Anoushka 5074,

Regarding your question, keystrokes work independent of deployment type, however you must remember that they only operate on the element that is designed to work if that element is focused.

To bring the window to the foreground, you may attempt Window: Activate Action, however Object Cloning/Capture Action is far more reliable than keystrokes. Is there anything that prevents you from using the former? If so, please elaborate so that we can assist you.

Regards,

Hi @Anoushka 5074 ,

You can try adding a Window Screen capture just before and after this Keystroke action. If you are getting black screen there, then we can confirm that the last RDP session logout was not proper or someone else might be having an active session on that runner machine during the BOT execution. If that’s the case, use either of the following methods.

• Use the enclosed .bat file to properly logout from the machine

or

• Use the Run→ sign-out action