Solved

Symantec Corporate 10.1.7.7000 Auto-Protect disabled on user level account WinXP

Posted on 2009-04-02
7
1,261 Views
Last Modified: 2013-12-09
I have some workstations (XP SP-2) that are coming up with the Symantec client Auto-Protect disabled.  However, this is only happening on the user level logons.  When we go in with an administrator level account, the client initiates without issue.

I've been researching and some say that the definitions could be at issue (corruption or access rights).  If it were corruption, I don't think the admin level accounts would be ok.  And I've double checked the access to the definitions directories and user level accounts have full access.

Any ideas?  Thanks in advance for your response.

-Dik
0
Comment
Question by:ShuttleDIK
  • 5
  • 2
7 Comments
 
LVL 15

Expert Comment

by:xmachine
ID: 24056788
Hi,

Here's the solution to your problem:

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/962e1e4378ef0d4d882570bb0065726a?OpenDocument


A Symantec Certified Specialist @ your service
0
 

Author Comment

by:ShuttleDIK
ID: 24076207
Yep - I checked that one.  Unfortunately - 1) I don't have admin access to the Symantec controls (only to the Domain OU & local PCs - the Symantec installation sits higher up the Domain chain).  and 2)  Tamper Protection isn't enabled on the clients.

I did have some luck with rolling back the definition version.  So that might end up being the solution.  I need to see more examples of the failure before I can close this out.

Thanks for responding, though!!  Much appreciated.
0
 

Author Comment

by:ShuttleDIK
ID: 24087516
Well, "fixing" the definitions only works sometimes.  I still end up with User level accounts having the Auto-Protect disabled and the Admin accounts enabled on many machines.

XMachine, can you confirm in the attached jpg that the Tamper Protection is indeed off?  Thanks!
If the symptom is the same, perhaps there's a different but similar cause?

Thanks again for your help.  I'm upping the point value 'cause it's taking more work here than I expected.

-Dik
Tamper-Protection.JPG
0
Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

 
LVL 15

Assisted Solution

by:xmachine
xmachine earned 50 total points
ID: 24090555
Yes, it's off and locked.
0
 

Author Comment

by:ShuttleDIK
ID: 24091197
Right.  The Symantec servers sit above the OU which we manage and therefore we do not administer it.  But we do administer the workstations on which the client is running.  I think something is happening when a user is logged in and new virus defs are pushed down.  Many machines I'm able to copy over definitions from a working PC and the lil' red circle goes away.  However, I have a couple where that just doesn't fly.

Thanks again,
D
0
 

Author Comment

by:ShuttleDIK
ID: 24097636
Most all of the workstations now are Auto-Protecting properly now, with various re-implementations of the Virus Definitions.  I still have one lonely machine that will not Auto-Protect on a User Level account.

I did a fresh clean of the virus defs again(I'm doing this manually). And this time when I logged in as a user, the VPTray icon first yielded the yellow exclamation point for 20 second, the reverted back to the red circle.

Is there perhaps an ini, dat or cfg file in which I could confirm the Tamper Protection setting?  The screenshot posted before is from an admin log in to the workstation, the user level doesn't let you view the GUI configuration.

Thanks!
0
 

Accepted Solution

by:
ShuttleDIK earned 0 total points
ID: 24098219
Ok, after a re-build & compression of the registry on my last lingering faulty machine, the Auto-Protect is again working.

So the fix was to clean out the virus-defs & replace with known working copies.  Rebuild & compress the registry.  If this somehow addressed any active Tamper Protection issues, I wouldn't have confirmation about that.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Identifying virus/malware after an attack 8 110
remove chinese softwares 22 109
Zeus black pop up screen virus 7 62
do i need anti virus software with windows 10? 13 13
Some site administrators might be considering how to filter incoming traffic to a site by identifying the domains or networks of the traffic source, in the same way that a spam filter does on an email server, such as blocking all emails sent from th…
Have you ever tried to find someone you know on Facebook and searched to find more than one result with the same picture? Perhaps someone you know has told you that they have a 'facebook stalker' or someone who is 'posing as them' online and ta…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

914 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now