It is not possible to simulate user activity and control user interfaces when Windows is logged out, and since Vista was introduced "interactive services" are no longer supported. To run interactive automation tasks, Windows must be logged in. But leaving a computer unlocked is a security risk and therefore not desirable.
To solve this, Macro Scheduler's unique AutoLogon technology allows you to schedule tasks to take place even when Windows is locked or logged out. Windows AutoLogon allows you to specify the correct credentials, so that at the required time, the macro will log back into Windows, perform the task and then log out again.
Usernames and password are stored in an encrypted form and only used when AutoLogon is enabled and Windows is logged out/locked at the time the macro is fired on a schedule.
Other tools, such as Sysinternals AutoLogon, simply set the AutoLogon registry entry with the username and password in the registry. All this really does is bypass Windows log on - Windows is then always logged in as that user as soon as it is started no matter who starts it, which is why registry autologon is not a secure option. Corporate policy often requires that PCs are logged out or locked when left unattended.
In contrast our AutoLogon solution stores the username and password in encrypted form, while allowing Windows to be locked or logged off as normal. Once locked or logged out, a user will still need to enter a username and password in order to log into Windows. But if a macro that has had AutoLogon enabled with a valid username and password is activated by a schedule while Windows is locked or logged out, Macro Scheduler's AutoLogon component will automatically log the user in, perform the macro, then return the workstation to a locked or logged out state.
*AutoLogon has been tested in the above operating system versions using clean default Windows installations with no third party security add-ons while connected physically to the machines. Due to infinite system/security config possibilities we are unable to guarantee successful operation for your own environment and do not support use of AutoLogon in terminal server/RDP environments. Therefore please test with the demo version before buying.