I've been dealing with onboarding our servers into Defender, and it's been such a hassle! Sometimes it works like a charm, but other times it's just a mess. Servers randomly stop checking in, certain components fail, and I've even tried scripting the process, but the various issues make it unreliable. I'm curious if other people are facing the same challenges or if it's just us.
7 Answers
We onboarded hundreds of servers and only had about a 2% failure rate. The few that failed were tricky to fix, often due to corrupt assembly errors that needed some weird fixes from Microsoft support. Overall, onboarding itself was smooth, though.
For the servers that aren’t registering, a simple solution is to run the Defender offboarding script, restart the server, and then try onboarding again. That usually does the trick!
I only encountered a few odd cases, mainly with older 2016 servers that were missing components. Other than that, it’s been generally smooth for everything else!
I've worked with multiple antivirus solutions like McAfee and Crowdstrike, and I find Defender for Business to be the most solid and easy to use. It’s been flawless for me.
All I faced was an initial hiccup getting started. I just had to toggle the policy off and back on to get it going. After that, it was pretty smooth sailing!
Honestly, I didn't have any major issues. The onboarding process has been rather straightforward for me, no complaints!
When I was at a managed services provider, the main issues we had were with older operating systems missing prerequisites. If any other antivirus products weren’t completely uninstalled, you'd see incomplete data in reports too.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures