User Profile
stopnik
Copper Contributor
Joined May 22, 2020
User Widgets
Recent Discussions
Re: Exchange Server Mail Stuck on Queue due to Microsoft Bug 01/01/2022
It’s one or the other, not both - I personally recommend bypassing instead of full disable so you’re still receiving updates. Your malware scanning will stay on bypass for each exchange server until you set it back to disabled and restart the transport services again. But it’s entirely up to you on what you do… I can’t believe Microsoft support hasn’t released anything official about this at this point.11KViews1like6CommentsRe: Exchange Server Mail Stuck on Queue due to Microsoft Bug 01/01/2022
SABBIRRUBAYAT - just a note that it's not a cyber attack, it's an int32 conversion issue with the date code of the 2022 signatures that Microsoft still hasn't fixed. I had also originally disabled malware scanning using the disable scripts last night to get things working, but the problem with this is that the malware definitions/engines are never updated for the FIP-FS service when you do that...it's better to set all your servers to bypass scanning instead. I had tried this last night before the internet blew up (this is for 2013 but same thing for 2016/2019 - https://docs.microsoft.com/en-us/exchange/disable-or-bypass-anti-malware-scanning-exchange-2013-help). The problem with that article is it doesn't say to restart the transport service after running the bypass command - but you have to do that for it to take effect. If you do it this way, mailflow will work and your definitions will continue to be updated so that hopefully when Microsoft fixes this your servers will be updated so that when you remove the bypass things continue to work (rather than re-enabling scanning, then waiting for the engines to update which takes a long time/breaks your mail flow again).12KViews1like11CommentsRe: 2012r2 Direct Access non-paged memory leak
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.2.4KViews0likes1CommentRe: 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!2.4KViews0likes3CommentsRe: 2012r2 Direct Access non-paged memory leak
mattsutton1295 - this doesn't help you, but I have the exact same issue. I have a set of 2012 R2 DA servers that are load balanced, and they started having a major memory leak during the transition to a new 2019 RDS farm that utilizes UDP (old farm did not, and I had this DA farm up for years without issue). I now have both servers set to a ridiculous 32gb of RAM each so that they continue to function with only doing a weekly reboot - if you find anything, let me know!2.9KViews0likes6Comments
Recent Blog Articles
No content to show