Video Screencast Help
Welcome to Symantec Connect
Solve problems, Share knowledge, Earn rewards.

Connect communities are where Symantec business customers, partners, and employees find solutions, share technical knowledge, and submit product ideas.

Join the conversation with over 411,097 registered members.

Your Community

Content is grouped by products and topics:


Earn rewards points whenever you participate on Connect.

New People

Network with people near and far.

Connect ActivityRSS

discussion comment 31 Jul 2015
Steven05 commented on: Logs BPBKAR
new discussion 31 Jul 2015
Am running Backup Exec 2012 (SP4 + hotfix 217347) small business edition on Windows Small Business Server 2011 Standard. When attempting a full SDR backup to a 3TB HDD on a LS220D480 NAS it is getting to about 16.2GB and apparently whilst still working on the exchange information store mailbox database.  It then just starts creating two 2KB files every minute whilst the backup ...
new discussion 31 Jul 2015
Hi, We have some problems with purge on our LUA server (download and distribute don't intersect with purge schedule), here some logs from server: 2015-07-31 07:30:08,220 [pool-2-thread-5] INFO  cleanCLU.PurgeCluThread  - Server: Default Production Distribution Center -- Not Deleting file as isCZ is false : 1438227827jtun_irev150723007.7z 2015-07-31 07:30:08,220 [pool-2-thread-5] ...
new discussion 31 Jul 2015
Just raising awareness of these known vulnerabilities in all previous releases of the 12.1 Symantec Endpoint Protection Manager (SEPM) and SEP client: Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Multiple Issues ...
new discussion 31 Jul 2015
Hey guys, I''ve been looking around the Symantec Encryption Management Server, and I can't find the license count. Anyone here know this? Thank you,
new discussion 31 Jul 2015
I got a strange problem: I am using PGP Command Line 10.3.2 build 12281 and I want to encrypt a file for multiple recipients. The public keys of them are imported and signed, and they work fine when used individually ("user1" and "user2" are just placeholders for the real key names): $ pgp --encrypt test.dat -r "user1" test.dat:encrypt (0:output file test.dat.pgp) $ pgp ...