Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SEP 11.0.5002.333 client and Sage Ver 11.01

Created: 10 Mar 2010 | 15 comments
MWL Systems's picture
0 0 Votes
Login to vote

The SEP 11.0.5002.333 client is installed on a new SBS 2008 server and all of the clients on the domain. They use Sage Ver 11.01 on several PCs and the data is stored on a shared folder on the server. Sage runs unacceptably slowly unless I disable the SEP Client on the server. It makes no difference whether or not the SEP client is activated or even installed on the individual PCs. I have tried excluding all of the Sage folders from the virus check. Oplocks are enabled and SMB signing is disabled. Is this a problem with SEP 11.0.5002.333 client? IT was never this bad with previous versions.

 

Comments

Rafeeq's picture
10
Mar
2010
0 Votes 0
Login to vote

hi

Have you enabled Network threat protection on your client machines? 

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

Prachand's picture
10
Mar
2010
0 Votes 0
Login to vote

What are the component od SEP

What are the component od SEP is installed?

If NTP is installed, don't disable it  first uninstall it from add remove program and then see if that helps.

Also does sage use any ports for commuincation?

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

MWL Systems's picture
10
Mar
2010
0 Votes 0
Login to vote

SEP 11.0.5002.33

Only anti virus and anti spyware are enabled on the client machines.

Sage does not use any specific ports for communication. It simply connects to a shared folder structure through a mapped drive.

Rafeeq's picture
10
Mar
2010
0 Votes 0
Login to vote

hi

Can you uncheck autoprotect and check the progress?
 

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

MWL Systems's picture
10
Mar
2010
0 Votes 0
Login to vote

If Auto Protect is off on the

If Auto Protect is off on the server it works fine. Makes no difference whether it's on or off on the PCs.

Rafeeq's picture
10
Mar
2010
0 Votes 0
Login to vote

hi

are your clients installed as managed or unmanaged ?
Do you have SEPM installed? 

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

Vikram Kumar-SAV to SEP's picture
10
Mar
2010
0 Votes 0
Login to vote

Create Centralized exception

Create Centralized exception for your Sage software.in SEP

MWL Systems's picture
11
Mar
2010
0 Votes 0
Login to vote

I've already created a

I've already created a centralized excetion; has no effect.

MWL Systems's picture
11
Mar
2010
0 Votes 0
Login to vote

SEPM is installed on the

SEPM is installed on the server. All clients are managed.

Aniket Amdekar's picture
11
Mar
2010
0 Votes 0
Login to vote

 Hi, Go to SEPM->Policies->

 Hi,

Go to SEPM->Policies-> Antivirus & Antispyware Policy-> File System Autoprotect-> Advanced Scanning and Monitoring -> Click on the radio button "Scan a file when it is modified".

Let us know if you see a performance improvement after this.

Aniket

MWL Systems's picture
11
Mar
2010
0 Votes 0
Login to vote

Scan a file only when modified

Already tried this. Once again - no difference to performance.

Also tried turning on Network Scanning and trusting the machine at the other end. Nothing has any effect other than disabling the SEPM client on the server. To simply click on a record to display it takes in excess of 10 seconds when the SEPM Client is running on the server; otherwise it's instant.

BKTECH's picture
27
May
2010
0 Votes 0
Login to vote

Same issue here with Symantec SEP Small Business edition

We have exactly the same issue and are running sep sbe antivirus. With auto protect off sage runs fine with it on sage grinds to a halt. Exceptions setup as per sage support and standard sage installs and whether managed or unmanaged client installed on server it makes no difference.
Loads of forum postings list de-select network scanning but this is not an option on the unmanaged client on the server. We have just switched to symantec due to NOD Eset freezing the server .

We need help too. Leaving autoprotect off is not a solution.
Thanks
Leo

MWL Systems's picture
28
Jun
2010
0 Votes 0
Login to vote

It's also happening with SEP

It's also happening with SEP version 11.0.6005.562 on another user's system. Does anyone at Symantec hav a solution for this?

Leo S's picture
30
Aug
2010
0 Votes 0
Login to vote

It's even happening with SEP

It's even happening with SEP version 11.0.6100.645... Still no solution?

Sean_Ali's picture
03
Sep
2010
0 Votes 0
Login to vote

My client having the same

My client having the same issue but only when running reports on Sage
SEP Version 11.0.5002.0 and 11.0.6100.645
Server OS: Windows server 2008 Std SP2 64bit
All the client are managed through SEPM
Centralized Exception list been done and Scan on Modify only

We need fix please..

Sean