Forum Discussion
2012r2 Direct Access non-paged memory leak
david0n unfortunately there's no fix as far as I'm aware of with Direct Access running on 2012 R2, it's fixed in 2016 and 2019. I am not in the position to upgrade ours right now, so I have my 2 servers on an automatic reboot schedule at 2am once a week (staggered as I have an HA pair), this has managed the leak so that the servers don't fail. It's not ideal, but it works for now until I can move all of our clients over to a newer version.
Good luck!
We ended up retiring our 2012r2 Direct Access environment and moved to 2019 Always on VPN. We were rebooting every night for a while. We finally just bit the bullet and migrated over to AOVPN.
Good Luck!!
- stopnikNov 18, 2020Copper Contributor
mattsutton1295- that's good to hear! Unrelated to this post I realize, but how did you handle transitioning over your clients? Were you able to get away with delivering the new certs & GPO settings/etc over the old DA connection or did you have to bring all the clients back into the corporate office to get reconfigured? That's the main reason I haven't done our upgrade - with this pandemic, having everybody bring in or ship their devices back to our office isn't feasible.
- mattsutton1295Nov 18, 2020Copper Contributor
We had employees bring devices back to the closest office to their residence to get them on the corporate network. Not ideal, but I think it worked out that they scheduled the time vs something go wrong and then making them come in because their device can no longer connect.