![]() And of course disabling EAV Outlook integration which stopped the crash but leaves Outlook vulnerable.Disabling dnsclient and telephony service (could not get it to crash but dnsclient is needed on our network).Disabling telephony service (still crashed when left on overnight).In the Using ESET Endpoint Antivirus by itself section you can find help topics divided into several chapters and subchapters to provide orientation and context, including Download, Installation and Activation. Removing C:\Windows\System32\*.* from Realtime file protection (could not get it to crash but may have been a fluke) ESET Endpoint Antivirus 9 is primarily designed for use on workstations in a small business environment.Removing Outlook TSP integration using Xarios installer. ![]() Removing Xarios phone manager from realtime file protection.Our award-winning Anti-Phishing engine protects sensitive company information, such as usernames and passwords, against fake websites. Provides robust Antivirus and Antispyware protection, whether your endpoints run Windows or macOS. Tried remote install and local install of EAV For network security choose ESET, the pioneer of antivirus for 25 years.Uninstalling EAV, cleaning installation, reinstalling.We would like to use the TAPI integration in the future so will need to get the driver back in at some point, so this is only a temporary solution. EAV Outlook Integration is now ok to use.The only way to recover from this lock is to kill the svchost.exe process that spawned these services.Īs we do not use the TAPI funstionality in any software yet it is an ok workaround to remove the TAPI driver. This process also hosts DNSClient (problem pinging addresses via DNS name and Endpoint Security unable to connect to update server), Workstation (SMB weirdness) and some others. We use Xarios Phone Manager which links to our phone system and when coupled with EAV Outlook integration cause the process that hosts the Telephony (TapiSrv) service to 'lock'. I managed to get the issue to repeat fairly consistently by opening and closing Outlook many times, which would eventually cause the problem. I have since been able to re-visit the problem. As this issue was happening to many users I had to implement a workaround of disabling EAV Outlook integration which stopped the issue completely. I had a major issue with the domain just after I posted this so could not focus on this issue. Removing TAPI driver temporary workaround. Tl dr - TAPI driver and Endpoint Outlook integration do not play well together.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |