Since Windows10, on some computers, but not all, the user is required to "run as administrator" on the ATE icon, if their profile is setup to use SSH to connect. otherwise you get an error message:

ATE SSH Transport Error
ATE failed to open SSH connection

Has anyone out there seen this problem ?

No one has reported this.

BUT: I've just managed to reproduce it. (It seems to happen only for all-users profiles that are launched from a normal user context.)

The immediate workaround is to create a new version of your configuration that is for the current user only.

But hopefully I'll have a better answer for the all-users case after studying it...

As always, you are correct. If I change my "all users" to "current user" my problems go away.

including the email thing.

thank you so much.

I've also found the real problem, which has to do with the accessing the SSH fingerprint in the registry (which is a necessary step in validating the connection). In the case where the fingerprint is new, typically the user is prompted to authorize it (unless you checked the Auto Accept Fingerprint option in the ATE config) and then the new fingerprint is written to the registry. But in the case where you have an all-users configuration, the normal user doesn't have write privileges. I'm going to modify it to not ask for write privileges, which won't solve every problem, but should allow you to get by if the fingerprint matches (or if you have the auto accept option set).

But, if I'm going to update the ashnet2.dll module for this, I might as well do a complete pass through all the related sub-modules (openssl, zlib, etc.) That may take a day or so. And, probably the new ashnet2.dll will only make it into 6.3/6.4 (although it could probably be manually copied into the 6.2 bin directory.)

I'll follow up when that's ready...

BTW, there should be an ashnet2.log file in your ATE directory which would presumably contains something like the following...

AshNet2 Ver 206 SSH connect to 192.168.253.134:22 login=jack, cfg=VMware-CentOS 7 (ssh all)
Unable to access registry key SOFTWARE\MicroSabio\JBCT\ATE\Hosts\VMware-CentOS 7 (ssh all)

Here's an updated version of the ashnet2.dll that should allow a normal user to make the SSH connection using an all-users configuration without being administrator. You can just replace the existing ashnet2.dll with it...

ashnet2-2.3.207.zip