e2e_appmon Windows 10

[Generali Servicemonitoring]

​Hello everyone.

Does anyone known if the user which login to the robot need a special right unter Windows 10 with the e2e_appmon probe?

Currently we want to switch from Windows 7 to Windows 10 and the login doesn´t work.

We also have an other Windows 10 Maschine working, which is not limited by thousands of policies. So I am pretty sure that our problem is a right/ policy topic?!

Kind Regards
Jessi

[Britta Hoffner]

Hello Jessi,

there might be one issue that e2e_appmon scripts that open a cmd.exe shell then attempt to execute Windows binaries that required
administrator rights (like the dfsutil utility) fail on Windows 10 systems even if the script is being
executed by a user who is a member of the administrator group. Errors similar to the following will
appear in the cmd.exe shell when the script is executed:

dfsutil is not recognized as an internal or external command,
operable program or batch file.

It appears that the additional security features of Windows 10 prevents the e2e_appmon probe
from staring the cdm.exe shell in administrator mode, even if the script is executed from a
user account that is a member of the administrator group.

This is a Windows OS restriction. Unless there is a way to force the Windows 10 OS to
always open the cmd.exe shell in administrator mode, it will not be possible to execute Windows
10 binaries that require administrator rights to be executed

Kind regards,
Britta

[Generali Servicemonitoring]

Hello Britta,

The e2e_appmon probe does not ​not sign-on automatically. The logon window (see Logonwindow.jpg) shows the username defined in the e2e_appmon.cfg.
When we make a vnc-connection to this robot, choose to sign-on with a different user but use the same user-credentials anyway, the logon is succesful and the probe is running.

Does the robot-user need certain policies to sucesfully logon via the e2e-probe on a windows10 robot? We have another windows10 robot running in another domain where this problem does not occur.

Kind regards, Jan

[Britta Hoffner]

Hello Jan,

can you please verify if this might be the difference between your working and non working environments ?

There could be an environmental issue which prevented the e2e_appmon probe to login after a reboot until the Domain user configured in the e2e_appmon probe physically logged on to the system after a reboot.

In this case, the issue could have been resolved by reimaging the Windows 10 VM, then reinstalling VNC, the UIM robot, and the e2e_appmon probe.

Kind regards,
Britta