Hi,
> Test Complete requires Screen to be unlocked to identify the test objects.
This is not TestComplete's requirement, but the generic behavior of Windows OS - the OS just does not provide the application with the desktop where application's UI can be drawn if workstation is locked. Otherwise, if the interaction with UI is not required, TestComplete runs fine and executes script code without any problem on the locked workstation (e.g. if script code operates with command line utilities and/or COM objects only).
Gennadiy is correct - Windows OS does not provide means to unlock locked workstation by some automation code, thus you must not lock the workstation. If it is a security policy enforcement, you may consider dedicated test box without the display (or, better, virtual machine) accessed via remote desktop (RDP). Using RDP you will provide active user session where your tests will be started via scheduler and switch then this session to desktop (https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html). This will result in active user session while keeping workstation's desktop not easily accessible to others.
.RebootAndContinue() method exists if you need to reboot test box from test (https://support.smartbear.com/testcomplete/docs/testing-with/running/rebooting-computer.html).
