Problem With Ms Outlook *.pst File After Installing Eset Endpoint Security

[kenny.hoh 1]

Having some trouble when installing ESET Endpoint Security to computers that previously installed with Symantec Endpoint. After complete the installations, the Outlook failed to download the email. After a few test run, apparently the *.ost file is corrupted. 

 

Install EES in a Windows 7 with Ms Office 2010 without Web Control and Personal Firewall.

User subscribe to Office365.

After installed EES, user unable to receive email from Outlook 2010. The outlook status failed to download email. suspect *.ost file acting weird and corrupted after that. Install over 10 computers and out of the 10, 2 have the similar problem. This is bad when we are prepare to install over 500 computers

Backup outlook data file *.ost
Delete email profile and recreate a new profile.

Restore the *ost file.
Resync the email, all other folders back to working condition, except inbox. Inbox download email progress bar remained as "downloading" for a very long time.
Uninstall ESET, restart outlook and recreate profile, using back the same *ost file, still the same.

Last try, delete profile, recreate the profile, recreate the *.ost file and can only download email in normal.

Reinstall EES then everything back normal.

 

Is that mean EES is messing with the *.ost file? Have you guys have any problem with it? 
 

Edited October 1, 2014 by kenny.hoh

[Marcos 5,070]

ESET products don't touch ost files at all. Does disabling integration with MS Outlook in the email protection setup make a difference?

[Arakasi 549]

When you say User subscribe to Office365....

If you are migrating mailboxes from a local mail server or different hosting to office 365, you will need to create new mail profiles anyway. This has nothing to do with ESET.

Your original ost is gonna get burned, and you need to move your pst's into the new mail profiles after setting up office 365.

[bbahes 29]

@Marcos It has everything to do with ESET Products.

@kenny.hoh Try changing "Disable checking upon inbox content change" option.

I've had so many problems with large .pst files and ESE Endpoint Antivirus in my Company. Finally I found that changing this option helps.

Edited October 7, 2014 by bbahes

[kenny.hoh 1]

Thanks for all the reply. Appreciate it. 

 

The trouble is the case happen randomly and we are having hard time to determine if the computer is potentially with the problem. 

 

 

ESET products don't touch ost files at all. Does disabling integration with MS Outlook in the email protection setup make a difference?

 

@marcos, further investigation, we found disabling integration with MS Outlook could work. We have tried new installation and disable the integration with Outlook. We also discovered they are using Symantec Enterprise Vault. Not sure if this could be the problem. What is the disadvantages disabling the integration with outlook?

 

When you say User subscribe to Office365....

If you are migrating mailboxes from a local mail server or different hosting to office 365, you will need to create new mail profiles anyway. This has nothing to do with ESET.

Your original ost is gonna get burned, and you need to move your pst's into the new mail profiles after setting up office 365.

 

@arakasi, they have completed the migration more than a year ago while on Symantec Endpoint. 

 

@Marcos It has everything to do with ESET Products.

@kenny.hoh Try changing "Disable checking upon inbox content change" option.

I've had so many problems with large .pst files and ESE Endpoint Antivirus in my Company. Finally I found that changing this option helps.

 

@bbahes, i probably want to try out changing "Disable checking upon inbox content change" option. 

 

 

[bbahes 29]

@kenny.hoh Are you using Linux mail server? Dovecot?

Edited October 13, 2014 by bbahes

[kenny.hoh 1]

@kenny.hoh Are you using Linux mail server? Dovecot?

 

The customer host their email with Office365, and using Symantec Enterprise Vault to journal and archive their emails. We install with ESET Endpoint Security 5.0.2229.1

Edited October 14, 2014 by kenny.hoh

[kenny.hoh 1]

we have tried disabled the "Disable checking upon inbox content change" and apparently things went well. We manage to deploy to hundreds of computers with no sweat. 3 computers came back with problem - unable to sync with Outlook when ESET is up and running. User ran the diagnose and discover that having problem with port 443. It went on corrupting the inbox again. They have to set up and re-sync the email, that wasted about 24 hours. 

 

Once they disable ESET Endpoint Security, the problem didn't occur. 

 

Please help. 

[bbahes 29]

After a extensive diagnostics on client and gateway side I can say that PST corruption did not occur due to ESET product.

Turn's out that our corporate gateway IPS policy (Intrusion Prevention Security Policy) was blocking specific incomming e-mail messages.

Due to nature of POP3 protocol PST files got corrupted.

 

But in your case since you are using 443 protocol it could be that ESET is scanning HTTPS traffic and blocking connection. It has to be turned off in several places. You should try running extensive diagnostics in Outlook and ESET. The both provide option to log activity.

Edited March 17, 2015 by bbahes

[kenny.hoh 1]

Thanks for the response. It turn out the client's computers was infested with Trojans and viruses before installing ESET. We are now more convinced that their internal settings and infestation causes the entire episodes. For the Port 443, could it be used as backdoor which is commonly used to bypass the corporate firewall. I will call this a close case. Thanks for your help.