
- #FORTINET SUPPORT PHONE NO HOW TO#
- #FORTINET SUPPORT PHONE NO UPDATE#
- #FORTINET SUPPORT PHONE NO DRIVER#
- #FORTINET SUPPORT PHONE NO UPGRADE#
- #FORTINET SUPPORT PHONE NO SERIES#
#FORTINET SUPPORT PHONE NO SERIES#
#FORTINET SUPPORT PHONE NO DRIVER#

Mike400 what problems do you have with Dell that requires support so often? We've only had a few Dell laptops for general use but they seem to be pretty solid. I'm very very very intrigued by Defender, I'll put it that way. they have a bit more capability than a standalone AV could offer. I know that'd be laughable in years past but they really have built that platform up and with intune, Azure AD, etc. Honestly, I'm kind of considering Microsoft Defender. so now we have a handful of PC's which no longer have Cylance installed. I've tried to get it figured out with their support team but nobody can seem to figure it out. but if you uninstall Cylance from the endpoint, the app works like a champ. For whatever reason, there are some apps that don't work but Cylance does NOT generate any sort of log for it and doesn't show it as being blocked anywhere. My current whitelists are massive and I still can't get some things to work correctly. It didn't like Windows Updates (I don't blame it, I hate them too), Office products, ANYTHING which included remote capabilies like or Teamviewer, and it absolutely hated our internal ERP system.

The changes made it much MUCH more aggressive and the day it changed, just about everything had issues.
#FORTINET SUPPORT PHONE NO UPGRADE#
The latest was an upgrade on their end which tweaked the big algorithm that the whole product is known for and built upon.

They've made some pretty questionable decisions with the product too. They're OK nowĭell - I don't care what anybody says, I've only ever had great support from Dell. Trusted Tech Team - I don't know that support can get much better than TTTĬheckpoint - They can be slow to get back to you but they're usually alright once you get somebodyĬylance - used to be great, then Blackberry came in. Meraki - Some of the worst support I've ever experienced If you decide to move I'll dig through our notes from our POC's for Sentinel One, Sophos Intercept-X and Crowdstrike Falcon. The contrast with Sentinel One is stark, REGULAR updates and refinements. I don't know where the product development has gone in the last 8 months, but it was disturbingly slowed in the prior twelve months. It pained me to move off of CylancePROTECT and OPTICS, but the trajectory after the BlackBerry acquisition was as bad as I feared. How do you feel about your security stack vendors and their support? When support sucks, you tend not to want to use it - prior experience is why we switched to Fortinet! Sentinel One support has been great as well. Using support during product evaluation is a necessary step, but that doesn't make it a familiar process.
#FORTINET SUPPORT PHONE NO HOW TO#
The follow-up email with a description of the issue and resolution was better than expected, with some useful suggestions (like don't freaking turn off ICMP echo, OK?) and links to how to use support better (see documentation). I haven't used Veeam support in ages, they're critical, I'll need to work on that list and dole out the tasks.Īnyway, it was a solidly reassuring and good support experience, despite I was on the phone for 45 minutes yesterday evening.

#FORTINET SUPPORT PHONE NO UPDATE#
We're going to start a new documentation stack to update support processes for critical vendors. I hate that feeling of not being able to figure it out, especially an important infrastructure piece, but that's what support is for. A random coincidence of a phishing URL getting blocked and rule 0 intercepting and blocking all traffic led to a support call for the first time in a WHILE to Fortinet.
