Video Screencast Help

Error in logs "Cannot assign a client authentication token"

Created: 04 Aug 2011 | 6 comments

So after completing our upgrade to 12.1 SEPM & Clients and still working out minor issues. I decided to pull a report on all the errors we care getting from clients. The biggest one that i see happening all day long since the upgrade started for which i pulled the log from the starting date of the upgrade i'm getting this all over the place and not sure how to resolve the issue.

I did look thru the docs and forums but did not find anything or i'm missing it on how to resolve this issue.

 

 

Discussion Filed Under:

Comments 6 CommentsJump to latest comment

Mithun Sanghavi's picture

Hello,

Are you using a Authentication Token for Clients like RSA or Verisign?

I believe this is in reference to the Same.

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Swapnil khare's picture

This is caused due to the Pre Boot Authentication Begin Skipped while Creation of the Client Packages, either through the Autologon or through the Active Directory Policies

 

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

 

WelshPretender's picture

The last post seems to suggest the cause of the error but doesn't go as far as explaining how to resolve it, either from SEP Manager or the client itself.

Any ideas? I'm in the same scenario as the first post and want to fully understand why the errors are occuring and how to solve them.

Thanks

E Praveen's picture

SEP alone occupying 3 GB of space in root volume.

C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\12.1.671.4971.105\Data\Definitions\VirusDefs

C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Definitions\VirusDefs

 

using 2003 server R2...

 

Any ways to solve this...