The Network Suite functionality is deprecated. We don’t recommend using it for distributed testing. Consider using a CI/CD system for managing distributed tests. See Migrating Distributed Tests to CI/CD Systems for details. In case you need to run web tests on multiple environments in parallel, you can also try using your project’s Execution Plan.

The “Verification failed” error that occurs during distributed testing can be caused by incorrect user account settings and permissions. Go through this checklist to fix the issue:

Note:

For other possible causes and solutions to the “Verification failed” error, see Message - Verification failed.

Make sure the host is a remote computer. The master computer cannot be a host at the same time.
Make sure the project contains user account information for the remote computer (domain, user name and password) either in the Hosts editor or in the Network Suite Properties. Double-check the user account information is correct.

The domain must be the same as the one specified in Control Panel | User Accounts on Windows XP, or in Control Panel | User Accounts | Manage User Accounts on later Windows versions.
Make sure that the user account used to log in to the remote computer:
- Has a non-empty password.
- Belongs to the Remote Desktop Users group on the remote computer.
Make sure that the user account, under which TestComplete or TestExecute is running on the master computer, has permissions to share the Shared path folder on the master computer.
Make sure the following group policies are disabled on the remote computer:
- Always prompt client for password upon connection
- Prompt for credentials on the client computer
If the remote computer belongs to a domain, these policies must also be disabled on the domain controller.

For instructions, see Configure Group Policies.
If the remote computer runs Windows 10, Windows Server 2016 or Windows Server 2019, make sure that the Require use of specific security layer for remote (RDP) connections group policy is enabled on it and the security layer is set to Negotiate.

For instructions, see Configure Group Policies.
If the remote computer has other users logged in and it has a non-server edition of Windows, log off other users.
If the remote computer has a server edition of Windows:
- If you get the “There are several sessions running under the same user account on the remote computer” error:
  1. Enable the Restrict each user to one session option in Remote Desktop Session Host Configuration (formerly Terminal Services Configuration). For instructions, see Distributed Testing - Requirements.
  2. Log off other sessions of this user account on the remote computer.
- If you get the “There are too many users logged in” error, log off other users from the remote computer. For instructions, see Distributed Testing - Requirements.
Make sure that the Remote Desktop on the remote computer is not configured to use a zero port. To do this, check that the value of the following registry key is non-zero:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

We recommend that it should be set to its default value 3389.
Make sure that the remote computer does not show any additional messages or prompts after you log in to it manually. If it does, ask your system administrator to disable these messages.

To check whether user accounts on remote computers are configured correctly

Message - Verification failed. Problems With User Accounts.

See Also