#WINDOWS REMOTE DESKTOP MANAGER VMWARE WINDOWS#

This results in the following error seen in the 'Robotic Playback Availability Events' view or 'Component Events':īWMGW0162E Rational Robot script failure, reason Unknown - Window was found but Rational Robot cannot make it active. If you do, the playback fails because it does not have control of the desktop. The session is temporary and can be terminated at anytime without disturbing Robotic playbacks.įor Remote Desktop sessions started with '/admin'ĭo not minimize the Remote Desktop screen. You can not see playbacks running or task manager activity as seen in the actual VM.

This session allows you to review various aspects of the RRT TEMA including logs and data file activity. If this session is terminated, Robotic scripts continue to be launched but fail as described above.

#WINDOWS REMOTE DESKTOP MANAGER VMWARE WINDOWS#

The method of starting the Remote Desktop session (mstsc.exe) is influenced by the type of access needed and the version of Windows being used. The procedure for starting the VM is influenced by the type of Remote Desktop access needed:ĭo not login (Manual login using Remote Desktop) If you do not login, the RRT TEMA is visible to the TEMS and playbacks are launched but they fail with 'BWMGW0153E Agent Screen is Locked' error being seen in the 'Robotic Playback Availability Events' view or 'Component Events' in TEP GUI console. This would mean starting the VM and logging in to ensure the RRT TEMA is communicating with the Management Server or the TEMS and the Rational Robot GUI playbacks are running. To access the RRT Agent or the RRT TEMA VM using Remote Desktop, the image must first be running on the VM host. If it is not possible to do this, you need to be aware of the following information and limitations when using Remote Desktop to access a machine running on a VM directly if that machine is being used to playback Rational Robot GUI scripts. The simplest method of using Remote Desktop is to access the host machine running the VMs and access the individual VM from there using the VM console.

Occasional access for the purpose of troubleshooting and/or maintenance.

Secure single remote access point (Permanently connected).

There are 2 possible reasons for using Remote Desktop to access a Virtual Machine (VM) running Robotic playbacks using Rational Robot GUI scripts: The first thing to remember about playing back Rational Robot GUI scripts in ITCAMfT is that Rational Robot must be able to access an unlocked desktop at all times and must have access to the active desktop running on the console.

Windows remote desktop manager vmware