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.
Awards
Pluralsight
Consulting
Newsletter
- My Tweets
- 6to4
- AADJ
- Absolute
- Absolute Secure Access
- Absolute Software
- Active Directory
- ADC
- administration
- Always On VPN
- Always On VPN Book
- Always On VPN DPC
- AMA
- Amazon EC2
- Amazon Web Services
- AOVPN
- AOVPN Book
- AovpnDPC
- application delivery controller
- Application Filter
- authentication
- AWS
- Azure
- Azure Active Directory
- Azure AD
- Azure AD Join
- Azure Application Gateway
- Azure Conditional Access
- Azure Load Balancer
- Azure MF
- Azure MFA
- Azure Traffic Manager
- Azure Virtual WAN
- Azure VPN
- Azure VPN Gateway
- BIG-IP
- certificates
- Cisco
- Cisco Umbrella
- Cisco Umbrella Roaming Client
- Citrix ADC
- cloud
- Cloudflare
- Compliance
- Conditional Access
- Consulting Services
- Cryptography
- Deployment
- Device Management
- device tunnel
- DirectAccess
- DirectAccess Book
- DirectAccess Deprecated
- DirectAccess End of Life
- DirectAccess EOL
- DNS
- DNS Policies
- DPC
- Dynamic Profile Configurator
- EAP
- EC2
- ECC
- education
- Elliptic Curve Cryptography
- encapsulation
- Encryption
- end of life
- Endpoint Manager
- Enterprise
- enterprise mobility
- EOL
- extensible authentication protocol
- F5
- force tunnel
- force tunneling
- Forefront TMG 2010
- Forefront UAG 2010
- General
- Geographic Redundnacy
- GitHub
- Group Policy
- HAADJ
- High Availability
- Hotfix
- Hybrid Azure AD Join
- IKEv2
- iManage
- Important Links
- Infrastructure
- InTune
- Intune Certificate Connector
- Intune PFX Connector
- IP-HTTPS
- IPv6
- IPv6 Transition
- ISATAP
- Kemp
- learning
- Load Balancing
- LoadMaster
- local traffic manager
- LTM
- Manage Out
- MDM
- MEM
- MEMCM
- MFA
- Microsoft
- Microsoft Endpoint Manager
- Microsoft Intune
- Mobile Device Management
- Mobility
- Multifactor Authentiction
- multisite
- MVP
- NAC
- Name Resolution
- name resolution policy table
- NAP
- NCA
- NCSI
- NDES
- NetMotion
- NetMotion Mobility
- NetMotion Software
- Netscaler
- Network Access Control
- network connectivity assistant
- network connectivity status indicator
- Network Device Enrollment Service
- Network Device Enrollment Services
- network policy server
- nmap
- NPS
- NRPT
- Offline Domain Join
- OMA-DM
- OpenDNS
- OpenSSL
- OpenVPN
- Operational Support
- OTP
- PEAP
- PFX Connector
- PKI
- Pluralsight
- PointSharp
- PowerShell
- Professional Services
- ProfileXML
- Protected EAP
- Proxy
- Proxy Server
- public cloud
- public key infrastructure
- Quad9
- Recommended Reading
- Remote Access
- reporting
- routing
- routing and remote access service
- RRAS
- SCCM
- SCEP
- Secure Socket Tunneling Protocol
- Security
- Simple Certificate Enrollment Protocol
- Split DNS
- split tunnel
- split tunneling
- SSL
- SSL and TLS
- SSTP
- Surface Pro
- Surface Pro 4
- System Center 2012
- System Center Configuration Manager
- systems management
- Teredo
- TLS
- TLS 1.3
- TPM
- Traffic Filter
- Training
- transition technology
- Transport Layer Security
- troubleshooting
- Trusted Platform Module
- Uncategorized
- Update
- user tunnel
- video
- Visual Studio
- Visual Studio Code
- VPN
- VPN Proxy
- VS Code
- Vulnerability
- Web Application Proxy
- Web Proxy
- Web Proxy Server
- webinar
- Windows 10
- Windows 11
- Windows 7
- Windows 8
- Windows 8.1
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
- Workshop
- WorkSite
- XML
- Zero Trust
- Zero Trust Network Access
- Zscaler
- ZTNA
Windows Server 2012 Remote Access Management Service Memory Leak
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/
Microsoft DirectAccess Client Troubleshooting Tool
Always On VPN Book
DirectAccess Book
Always On VPN DPC
-
Recent Posts
Always On VPN Resources
DirectAccess Resources
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 enterprise mobility error F5 firewall Forefront Forefront UAG Forefront UAG 2010 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 RasClient redundancy Remote Access routing routing and remote access service RRAS scalability SCCM security Server 2012 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
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.