As of January 10, 2023, Windows 8 reached its end of life, followed by Windows Server 2012 on October 10, 2023. Atera provides support only for operating systems actively supported by their vendors. Although these versions are no longer supported, this article outlines steps to ensure the Atera agent remains functional on these systems.
Important note: Since these Windows versions are no longer supported by Microsoft, Atera cannot guarantee resolution for all issues. However, we will assist to the best of our ability. In case you encounter issues with these Windows versions, please reach out to our support team.
TLS 1.2 Requirement
For the Atera agent to function on Windows 8 and Windows Server 2012, TLS 1.2 must be enabled on these devices. Without TLS 1.2, the agent will not operate as intended.
For detailed information about TLS 1.2, refer to the official Microsoft documentation:
Enable TLS 1.2 script
Download the Enable TLS 1.2 Script: To simplify enabling TLS 1.2, Atera has developed a script.
Steps to Enable TLS 1.2
Follow these steps to run the script and resolve TLS-related issues:
1. Install the required update: Install the file windows8-rt-kb3140245-x64_b589173ad4afdb12b18606b5f84861fcf20010d0.msu.
Note: The script automatically backs up all registry values in the folder where the batch files are run.
2. Run the basic script: Execute Enable_SSL12_Kb.bat and restart the machine.
3. If the issue persists: Run the "aggressive" script: Enable_SSL12_Aggressive.bat and restart the machine again.
Important note: Ensure a backup plan is in place to regain access to the server if remote access becomes unavailable after running the aggressive script.
Run scripts from Atera
If your Windows 8 or Server 2012 devices are capable of running scripts through Atera, you can execute the TLS script directly via the platform:
Important note: The file windows8-rt-kb3140245-x64_b589173ad4afdb12b18606b5f84861fcf20010d0.msu cannot be uploaded to Atera, this file will need to run locally on your machine.
1. Run scripts manually: Use the Run Scripts module to execute each script in the order outlined above.
2. Automate script execution: Create separate IT Automation profiles for each script and execute them sequentially.
Create IT Automation profiles
Before creating an IT Automation profile, make sure to upload the TLS scripts to your account, following the steps in this article:
To create the IT Automation profile.
1. Go to to Admin > Monitoring and Automation > Patch Management and IT Automation.
The Patch Management and IT Automation page appears.
2. Click the Add Profile button, enter the name of your profile, and click on Save.
3. On the new profile page, go to the script section and click the Add script button.
4. Click the Select button next to the TLS script, now the script will be attached to your profile.
Once the script has been assigned, click the Save, button, and you are done. The profile has been created. Make sure you follow the same steps for the aggressive script. As a form of best practice, we suggest you create a separate IT Automation profile.
Before running the profile, make sure you assign the profile to the desired devices, instructions can be found in this article:
To learn how to schedule an IT Automation profile, please visit this link:
Known Issues and Limitations
While enabling TLS 1.2 resolves most Atera agent functionality issues, some problems may persist due to the nature of unsupported Windows versions:
- Domain Controllers: Older Domain Controllers may experience compatibility issues when using TLS 1.2.
- Remote Desktop Protocol (RDP): RDP connections on these systems may encounter disruptions.
To troubleshoot further, consult Microsoft's documentation on TLS 1.2:
Contacting Atera Support
If you encounter issues despite following these steps, please contact Atera Support. While we cannot guarantee a solution for all problems on unsupported systems, we will do our best to assist you.
Important Reminder: We strongly recommend upgrading to supported operating systems to ensure optimal security and performance.
Legal Disclaimer
By using the provided script, you acknowledge and agree to the following terms: The script and TLS 1.2 are provided "as is" without any warranties or guarantees of any kind. The use of this script and TLS 1.2 is at your own risk. Atera does not guarantee that the script and TLS 1.2 will resolve the issue or that it will not cause unintended consequences. You are solely responsible for any changes made to your system's registry and for any potential impacts on other services running on your servers. Atera shall not be liable for any damages, including but not limited to, direct, indirect, incidental, or consequential damages, arising out of or in connection with the use of the script and/or TLS 1.2. This includes any loss of data, loss of business, or any other damages. You may not modify, distribute, or sell the script without our prior written consent. By proceeding with the use of the script, you confirm that you have read, understood, and agreed to the terms outlined in this disclaimer.
