4.2.2 Notes on Windows log-on function
The Windows log-on function might not work properly depending on several conditions such as the machine settings, machine state, and log-on users. We therefore recommend that you keep the following precautions in mind when operating the Windows log-on function:
-
Execute the Windows log-on action while the Windows log-on window is displayed.
-
For example, suppose that you execute an action flow that involves the use of Windows event monitoring to monitor for log-off events followed by the execution of a Windows log-on action. In this case, a time lag between a log-off event and the subsequent display of the Windows log-on window can cause the subsequent Windows log-on action to end with an error. To prevent this from happening, you can insert a sleep# or other similar process before the execution of the Windows log-on action.
- #
-
Time from log-off to the display of the Windows log-on window varies with each environment. You must therefore first verify that inserting a sleep does not cause any problems.
-
Because screensaver is a state different from screen lock, you cannot cancel screensaver by using the unlock screen functionality.
-
If Interactive logon: Do not require CTRL+ALT+DEL (the option you can access by opening the Local Security Policy console of Windows 10 and selecting Local Policies, and then Security Options) is set to Disabled (which, by default, is set to Not Defined), the Windows log-on function does not work. If you want to change this setting, you have to first check the security policy of the system you are using.
-
If the log-on account for the job execution service is changed to an account other than the local system account, the Windows log-on action ends abnormally.