Overview 💥
Microsoft officially ended support for Windows Server 2012 and Windows Server 2012 R2 on October 10, 2023, discontinuing security updates, bug fixes, technical support, and online content updates. Reference : Microsoft's official documentation
As a result, Liongard ended support for agent versions 4.2.4 and greater on Windows Server 2012 starting June 1, 2024. Partners are strongly recommended to upgrade to Windows Server 2016 or later to maintain platform compatibility, security, and performance.
Impact on Liongard Agents and Node.js 🤔
Liongard agents 4.2.4+ leverage Node.js v18, which no longer supports Windows Server 2012/2012 R2. This affects:
Agent installation
Agent auto-updates
Inspectors running on affected servers
Platform functionality reliant on Node.js
Agent Version | Node.js Version | Compatibility with Windows Server 2012 |
4.2.3 | 14.21.3 | Supported (EOM) |
4.2.4+ | 18.x | Not compatible |
❗ Node.js 14.21.3 (used by 4.2.3) is EOS/EOL, currently has no known CVEs, but running EOS software introduces potential security risk.
Liongard Support Stance 🦁
Agents 4.2.4 and higher:
Not compatible with Windows Server 2012/2012 R2
Installation will fail on these OS versions
Auto-update to 4.2.4+ is unsupported on Windows Server 2012
Agent 4.2.3:
Last version supported on Windows Server 2012
End of Maintenance (EOM): Active
End of Life (EOL): May 31, 2025
Partners must disable auto-update to prevent upgrading to unsupported 4.2.4+
Use only if partners accept the risk of EOS/EOL Node.js
Recommended Actions for Partners 🚀
1️⃣ Upgrade the Operating System
Liongard strongly recommends upgrading to Windows Server 2016 or later. This ensures:
Full compatibility with the latest Liongard Agent (4.2.4+)
Security patches and Node.js v18 support
Stable inspections across all endpoints
2️⃣ Pin Agent 4.2.3 (If Upgrade Is Not Possible)
For systems that cannot be upgraded immediately:
Download agent 4.2.3: Liongard Agent 4.2.3 Documentation
Install the agent on Windows Server 2012
Disable auto-updates to prevent accidental upgrade to 4.2.4+
Accept risk associated with running EOS/EOL software
Node.js 14.21.3 is EOS/EOL
No future patches or security updates will be provided
Monitor inspections for any potential compatibility issues
⚠️ This is a short-term, risk-accepted workaround, not a long-term supported configuration.
Checking Agent Versions and Auto-Update Status 👀
Navigate to Admin > Agents in Liongard
Verify the agent version running on the Windows Server 2012 node
Ensure auto-update is disabled for agents pinned to 4.2.3
Confirm that no newer agent versions are automatically applied
Key Considerations 🚨
Topic | Guidance |
Installation of 4.2.4+ | Will fail on Windows Server 2012 due to OS requirements |
Security Risk | Running agent 4.2.3 on EOS/EOL Node.js introduces potential vulnerabilities |
Support | Liongard cannot provide patches for future Node.js vulnerabilities on 4.2.3 |
Inspection Reliability | Some inspections may fail if agent is not updated; consider short-term mitigations |
Recommended Action | Upgrade OS → Install latest Liongard agent (4.2.4+) |
Frequently Asked Questions (FAQ) 🙋♂️
Can I install agent 4.2.4+ on Windows Server 2012?
➡️: No. Versions 4.2.4+ are not compatible and will fail to install. Auto-update to 4.2.4+ is blocked on these systems.What if I can’t upgrade from Windows Server 2012 immediately?
➡️: You may continue using agent 4.2.3 with auto-update disabled. This is a temporary, risk-accepted solution. 4.2.3 EOL is May 31, 2025.Are inspections still reliable on 4.2.3?
➡️: Most inspections will function. However, compatibility issues may occur. Monitor inspection results closely.What are the risks of using agent 4.2.3 on 2012?
➡️: Node.js 14.21.3 is EOS/EOL. No security patches or updates will be provided. Liongard is not responsible for vulnerabilities or inspection failures.Can I auto-update 4.2.3 on Windows Server 2012?
➡️: No. Auto-update must be disabled to prevent accidental upgrade to 4.2.4+, which would break support.Is there a long-term supported solution for Windows Server 2012?
➡️: No. Liongard recommends upgrading to Windows Server 2016 or later. Using 4.2.3 on Windows Server 2012 is short-term, risk-accepted only.What if my agent auto-updated accidentally to 4.2.4+ on 2012?
➡️: This is treated as a defect. Rollback is not officially supported. Reinstalling agent 4.2.3 may restore compatibility temporarily.
When to Contact Support 👨💻
Contact Liongard Support if you experience:
Installation failures on Windows Server 2012/2012 R2
Inspectors failing unexpectedly on 2012 systems
Issues confirming agent version or auto-update settings
Agent logs indicating Node.js or service errors
📝 What to Include When Opening a Support Ticket
To help us resolve your issue efficiently, please provide:
Server OS version (e.g., Windows Server 2012 R2)
Agent version installed
Auto-update status (enabled/disabled)
Inspector IDs affected
Error messages or logs
Steps already attempted to fix the issue
✅ Providing detailed information helps our team troubleshoot faster and provide accurate guidance.
Summary 🤩
Microsoft ended support for Windows Server 2012/2012 R2: Oct 10, 2023
Liongard ended support for agent 4.2.4+ on Windows Server 2012: June 1, 2024
Agents 4.2.4+ will not install on Windows Server 2012
Agent 4.2.3 is last supported version for Windows Server 2012:
EOM: Active
EOL: May 31, 2025
Auto-update must be disabled
Partners assume security risk running EOS/EOL Node.js
✅ Recommended solution: Upgrade to Windows Server 2016 or later and install the latest Liongard Agent for full support, security, and inspection reliability.