Hi Guys,

For 1 year after migration from exchange 2007 to exchange 2013, there is no problem with it.

In past few days, suddenly our outlook client disconnect from server.

I just restart the exchange server but it took a long time(1 hour) for connecting in client outlook.

same with the day, we have a problem with paging file error message in exchange server.

is it related ?

Thanks,

Hilda

I dont think its related to pagefile error, was there any Windows update or Exchange related updates applied on the same same day, What did eventvwr had to say during the 1 hour connection delay.

EXBPA ?? what does it report, DC + GC were they also rebooted during this time??

Hi Hilda,

It is not sure whether the issue related to page file error.

When the page file error had been solved, was there the same issue for connecting client outlook?

As the above suggestion mentioned, you should check if there was any event error logs when the issue occurred, it could give us some hints and help us to troubleshoot the issue.

Best regards,

Hi Niko,

After admitting for a month, the problem is still going.

Outlook client disconnect for 5 - 10 minutes then connected again. It happens 2-3 times a week.

In event viewer, i saw this error : " Active Directory configuration lookup failed with error: Could not find server '  ' in Active Directory.

I installed symantec antivirus in exchange server dan DC .. can be it caused by symantec, something like firewall ?

Thank u guys,

Hilda

Hi,

I am Chetan Savade from Symantec Technical Support Team.

I don't think SEP will be causing this issue, if SEP would have blocked traffic then it would have blocked permanently.

If Microsoft Exchange servers are installed on a computer with Symantec Endpoint Protection client, the client software automatically detects the presence of Exchange. When the client software detects a Microsoft Exchange server, it creates the appropriate file and folder exclusions for File System Auto-Protect and all other scans. Microsoft Exchange servers can include clustered servers. The client software checks for changes in the location of the appropriate Exchange files and folders at regular intervals. If Exchange is installed on a computer where the client software is already installed, the exclusions are created when the client checks for changes. The client excludes both files and folders; if a single file is moved from an excluded folder, the file remains excluded.

The latest available release of the Symantec Endpoint Protection client software creates file and folder scan exclusions for the following Microsoft Exchange server versions:

• Exchange 5.5
• Exchange 2000
• Exchange 2003
• Exchange 2007
• Exchange 2010 (introduced with SEP 11 RU6 MP1)
• Exchange 2013 (introduced with SEP 12.1 RU3)

Symantec recommends that the Exchange server's OS always be protected by the latest available release of SEP.  The Exchange server's message flow and Information Store must be protected by a dedicated mail security product, such as Symantec Mail Security for Microsoft Exchange.

Automatic exclusions for an Exchange 2013 server were introduced with  SEP 12.1 RU3. Releases of SEP prior to 12.1 RU3 do not automatically set exclusions, so scan exclusions for Exchange 2013 needs to be added manually per Microsoft's recommendations. Please follow the instructions contained in the article "File-Level Antivirus Scanning File-Level Anti-Malware Scanning on Exchange Servers 

Best Regards,

Chetan

• Edited by Chetan Savade 17 hours 27 minutes ago

Hi,

I am Chetan Savade from Symantec Technical Support Team.

I don't think SEP will be causing this issue, if SEP would have blocked traffic then it would have blocked permanently.

If Microsoft Exchange servers are installed on a computer with Symantec Endpoint Protection client, the client software automatically detects the presence of Exchange. When the client software detects a Microsoft Exchange server, it creates the appropriate file and folder exclusions for File System Auto-Protect and all other scans. Microsoft Exchange servers can include clustered servers. The client software checks for changes in the location of the appropriate Exchange files and folders at regular intervals. If Exchange is installed on a computer where the client software is already installed, the exclusions are created when the client checks for changes. The client excludes both files and folders; if a single file is moved from an excluded folder, the file remains excluded.

The latest available release of the Symantec Endpoint Protection client software creates file and folder scan exclusions for the following Microsoft Exchange server versions:

• Exchange 5.5
• Exchange 2000
• Exchange 2003
• Exchange 2007
• Exchange 2010 (introduced with SEP 11 RU6 MP1)
• Exchange 2013 (introduced with SEP 12.1 RU3)

Symantec recommends that the Exchange server's OS always be protected by the latest available release of SEP.  The Exchange server's message flow and Information Store must be protected by a dedicated mail security product, such as Symantec Mail Security for Microsoft Exchange.

Automatic exclusions for an Exchange 2013 server were introduced with  SEP 12.1 RU3. Releases of SEP prior to 12.1 RU3 do not automatically set exclusions, so scan exclusions for Exchange 2013 needs to be added manually per Microsoft's recommendations. Please follow the instructions contained in the article "File-Level Antivirus Scanning File-Level Anti-Malware Scanning on Exchange Servers 

Best Regards,

Chetan

• Edited by Chetan Savade Wednesday, May 13, 2015 1:59 PM

Hi Chetan,

How should the customer have SEP configured if mount points are in use?  I.E. LUNS are on a SAN, and presented to Windows and are accessible through

C:\Mounts\SANDisk1\

C:\Mounts\SANDisk2\

C:\Mounts\SANDisk3\

etc.

What configuraiton do they need to leverage?

Cheers,

Rhoderick

Hi,

For many reasons, including the typical large (terabytes) capacity of NAS, the Symantec Protection Engine is the right product to secure these machines.
The use of the Symantec AntiVirus or Symantec Endpoint client to scan drives on a NAS device is not recommended and is not supported.

Reference:http://www.symantec.com/docs/TECH123099

Best Regards,

Chetan