AutoPrep Machine Configuration Guide
1. Overview
In Unattended Desktop Automation (a form of Process Automation or UI automation running without a human present), the automation machine must remain continuously accessible, logged in, and stable.
Many Windows security, power, and session features can interrupt this flow if they are not configured appropriately.
These configurations ensure that the automation machine remains compatible with the HuLoop Human-Supervised Automation Service used to execute unattended automations:
- Continuously logged in
- Accessible to the automation platform
- Stable and operational
- Free from interruptions
This allows unattended automations to execute reliably without requiring manual intervention.
2. Machine Configuration Requirements
The following machine configurations are required to support unattended desktop automation.
| Machine Configuration | Purpose | Reason for Change |
|---|---|---|
| Enable Auto Login | Automatically logs a predefined Windows user account into the system after reboot without requiring manual password entry. | In unattended automation, there is no user physically present to enter credentials. Auto-login ensures the automation environment starts automatically after a system restart or patch update. Without it, automation processes cannot launch because the desktop session is not active. |
| Set Password Never Expires | Prevents the Windows account password from expiring according to domain or local security policies. | If the password expires, Windows forces a password change at next login. This stops auto-login and interrupts unattended automation because the system waits for user interaction. Setting it to never expire ensures automation continues to run without interruption. |
| Enable RDP (Remote Desktop) | Allows remote access to the machine through Remote Desktop Protocol. | Unattended automation machines are usually located on servers or virtual machines without direct physical access. RDP allows administrators or support teams to monitor automation runs, troubleshoot failures, deploy scripts, or perform maintenance remotely. |
| Disable Sleep & Hibernate | Prevents the system from entering low-power states such as sleep or hibernate after inactivity. | Automation requires the system to remain fully operational. If the machine enters sleep or hibernate mode, automation processes stop and scheduled jobs fail. |
| Disable Screen Timeout | Prevents the display from turning off after a period of inactivity. | Many UI automation tools interact with the active desktop session. If the screen turns off or the session becomes inactive, UI rendering may stop and automation tools may fail to locate elements or perform actions. |
| Disable Lock Screen | Prevents Windows from automatically locking the session after inactivity. | When a session is locked, most UI automation frameworks cannot interact with the desktop because the UI is hidden behind the lock screen. |
| Disable Screen Saver | Prevents the screen saver from activating after idle time. | Screen savers overlay the desktop UI and block automation from interacting with application elements, which can interrupt automation workflows. |
| Disable RDP Timeouts | Prevents Remote Desktop sessions from disconnecting or logging off automatically after inactivity. | Many unattended automation environments operate inside an RDP session. If the session disconnects or times out, automation may lose access to the active desktop context. |
| Disable UAC Settings | Disables or reduces User Account Control prompts that ask for administrator approval before executing privileged operations. | Automation scripts cannot interact with secure desktop prompts like UAC. If these prompts appear, the automation workflow may stop and wait for manual confirmation. |
| Prevent Auto-Restart with Logged-On Users | Prevents Windows from automatically restarting the system after updates while a user session is active. | If Windows restarts during automation execution, running processes terminate abruptly and may lead to incomplete transactions or inconsistent states. |
3. Administrator Privilege Requirements
Some machine configurations require administrator privileges because they modify system-level settings such as the Windows registry, local policies, or security controls.
| Machine Configuration | Requires Administrator Privileges | Reason |
|---|---|---|
| Enable Auto Login | Yes | Requires modifying Windows registry settings used for automatic login. |
| Set Password Never Expires | Yes | Changing account password policies or user account properties requires administrator rights, especially in domain environments. |
| Enable RDP (Remote Desktop) | Yes | Enabling Remote Desktop modifies system settings and firewall rules. |
| Disable Sleep & Hibernate | Yes | System-level power plan changes require administrator privileges to apply consistently across the machine. |
| Disable Screen Timeout | Sometimes (usually yes in enterprise environments) | If applied through system power policies or registry changes, administrator rights are required. |
| Disable Lock Screen | Yes | Requires modifying local group policy or registry settings that control Windows session behavior. |
| Disable Screen Saver | Sometimes | If configured per user it may not require administrator privileges, but system-level enforcement may require admin access. |
| Disable RDP Timeouts | Yes | Requires modifying Local Group Policy or registry settings controlling Remote Desktop session limits. |
| Disable UAC Settings | Yes | UAC is a system-level security control that can only be modified by an administrator. |
| Prevent Auto-Restart with Logged-On Users | Yes | Requires modification of Windows Update policies or registry settings. |
4. User Account and Auto Login Requirements
For unattended automation to function reliably, the machine and user account configured with HuLoop AutoPrep must remain stable and properly configured.
The following requirements and considerations apply:
- The user account configured for AutoPrep must have Local Administrator privileges on the VM or machine where the automation will run.
- The automation machine should only be accessed using the same Windows user account configured during AutoPrep setup.
- During configuration, AutoPrep automatically enables Windows Auto Login for the selected user account.
- If any changes are made to the configured user account, AutoPrep must be configured again.
- Examples include:
- Password change · Removal of Local Administrator privileges · Reassignment of Local Administrator privileges · Changes to user permissions or security policies · Any other modification affecting the configured user account
- After account-related changes are made, Windows Auto Login must be configured again before unattended automation can resume normally.
- Existing scheduled tasks associated with the configured account should also be deleted and recreated.
- This is required because the Windows user token associated with the scheduled task may become invalid after account or permission changes.
5. Risks and Environment Considerations
5.1 Organizational Policy Overrides
Machine configurations applied by HuLoop AutoPrep may be overridden by organizational policies such as:
- Active Directory Group Policies (GPO)
- Enterprise security policies
- Compliance enforcement policies
These policies may automatically revert configuration settings.
5.2 Automation Environment Instability
If required settings such as Auto Login, RDP configuration, power settings, or UAC settings are reverted by organizational policies, the environment required for unattended automation may no longer remain valid.
5.3 Automation Failures or Interruptions
Changes to these configurations may result in:
- Automation jobs failing
- Automation stopping unexpectedly
- Inability to interact with the desktop session
5.4 Inconsistent Machine State
Policy updates may be applied automatically during:
- System refresh cycles
- Patch updates
- Domain policy updates
As a result, machine configurations may change without prior notification.
5.5 Operational Impact
If required settings are modified or reverted, scheduled unattended automations may stop functioning until the required configurations are restored.
6. Disclaimer
6.1 Configuration Dependency
Unattended automation functionality depends on the machine configurations set by HuLoop AutoPrep. Any modification to these settings through external policies, manual changes, or IT security enforcement may impact automation execution.
6.2 Verification as a Troubleshooting Step
If unattended automation stops working on a machine, the first troubleshooting step should be to verify that all required system configurations applied by HuLoop AutoPrep are still intact.
6.3 Policy Control Outside Tool Scope
HuLoop AutoPrep cannot prevent changes enforced by organization-level policies such as:
- Domain Group Policies
- Security compliance updates
6.4 Restoration Requirement
If any configuration is found to be reverted, the setting must be restored before unattended automation can resume normal operation.
6.5 Environmental Responsibility
Ensuring that automation machines remain compliant with the required configuration is the responsibility of the system administrators managing the environment.
