When Windows Server 2012 is configured for DirectAccess or client-based remote access Virtual Private Networking (VPN), a memory leak may occur in the Remote Access Management service when remote clients access the Internet using the DirectAccess or VPN connection. Microsoft knowledgebase article KB2895930 describes the issue in detail and includes a link to the hotfix to resolve this issue.
Posted by Richard M. Hicks on March 25, 2014
https://directaccess.richardhicks.com/2014/03/25/windows-server-2012-remote-access-management-service-memory-leak/
Active Directory ADC Always On VPN AOVPN application delivery controller authentication Azure book bug CA certificate certificates Certification Authority cloud configuration device tunnel DirectAccess DNS EAP education encryption endpoint manager enterprise mobility error F5 firewall Forefront Forefront UAG GPO group policy high availability hotfix IKEv2 Important Links InTune IP-HTTPS IPsec IPv6 IPv6 transition technology Kemp learning load balancer load balancing LoadMaster management Manage Out MDM MEM Microsoft Microsoft Endpoint Manager Microsoft Intune Mobility multisite NetMotion NetMotion Mobility Networking network location server network policy server NLB NLS NPS NRPT OTP performance PKI PowerShell ProfileXML public cloud RADIUS RasClient redundancy Remote Access routing routing and remote access service RRAS scalability SCCM security SSL SSTP System Center Configuration Manager TLS training troubleshooting UAG update user tunnel VPN Windows Windows 7 Windows 8 Windows 10 Windows 11 Windows Server Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows Server 2022 XML
Subscribe now to keep reading and get access to the full archive.
marc
/ September 8, 2014we installed the hotfix, but we still have mem leak issues, we are split tunneling, is there anything else we should look at? We have a case open with M/S but nothing has come from it yet.
Richard Hicks
/ September 15, 2014It’s always possible that the leak could be something other than the remote access management service. Detailed investigation and troubleshooting should identify the source of the leak. I’m sure MS will locate something soon.
victor bassey
/ April 6, 2020Is this and issue with RRAS on server 2016 also? I’m having to reboot the RRAS servers almost every 5 days as RAM usage does seem to be release even when most users are disconnected.
Richard M. Hicks
/ April 6, 2020No. There was another issue in Windows Server 2016 having to do with high memory consumption. It was fixed in KB4534307.