In addition to facilitating testing of today's modern Web applications on the protocol level (HTTP), Silk Performer can also use real Web browsers (Internet Explorer). However, because Windows Internet Explorer behaves differently under the system account, TEA Agent must run as a process for Web Browser-Driven (AJAX) projects. This is known limitation.
When a TEA agent is running as a process, a session must be kept alive at all times. This means user must not log off from the remote session (however they can disconnect).

To run a synthetic TEA Agent as a process, follow this link:
https://docs.bmc.com/docs/display/TSPS101/Starting+and+stopping+a+synthetic+TEA+Agent+as+a+process

Things that have to be taken into consideration:
- When running TEA agent as a process, “Internet Explorer Enhanced Security” must be disabled.
- TEA Agents running as a process consume more resources so they can handle a fewer number of monitors.
To avoid unnecessary memory consumption of a browser-driven monitor, it is good scripting practice to call the BrowserStop function at the end of the monitor transaction. This forces the Windows Internet Explorer control to close and all associated memory is freed (thus problems that have been reported with Internet Explorer memory leaks can be avoided). At the beginning of the next monitor execution a new Windows Internet Explorer instance is created.
-Scripts that run on a TEA Agent running as a process will require access to the mouse to be able to preform the clicking actions needed to progress through the script.  For this reason, TEA Agents running as a process should be run in a dedicated account.  This account should have limited user activity to prevent the mouse from being used by a user.  If there is a chance that a user is using the the mouse while a script is running, then the script may not be able to complete its clicking actions and will trigger false failures.

If the server (on which TEA agent is running) is restarted, customer has to ensure that the login account (under which the scripts are running) can login automatically. BMC cannot endorse any application or tool over another for autologon functionality. Many customers reported that they are successfully using the Sysinternals - Autologon application (Microsoft Free Utility).

FAQ: A common problem with Autologon is putting the shortcut to start_agent.bat in the wrong place. It must go into a Startup directory and that Startup directory must be the Startup directory of the user name that Autologon is configured for.  Most Windows computer have more than one Startup directory so please make a note of this.

Perhaps the shortcut is here:
%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup 

But perhaps it actually needs to also go here:
C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Or maybe here:

C:\Users\MyTestUser\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

If  the TEA Agent is not automatically starting after a reboot please verify this.