Re:Just in time for us to migrate to Symantec
on
A Bad Week for Symantec
·
· Score: 2, Interesting
As a former Symantec Corp customer, I'll disagree with that. The uninstaller for 8 was horrible, and the push install of 9 flat out didn't work for about half of my network (frequently caused by issues with 8). Nothing special about the network either, it just didn't work. In fact, about 1 in 20 network installs didn't work at all for some reason and I had to go install by hand. 9->10 seemed like it was going better until I had several systems start randomly screwing up and causing our EE and ME CAD applications to crash. I was getting sick of all the issues with security between the server and the clients as well as a multitude of other things.
I moved to NOD32, and couldn't be happier. Uses less than half the resources Symantec Corp did, and does a better job. I've had systems come out cleaner using a 3 month old set of definitions with NOD than Symantec Corp. I've got a central management interface that hasn't needed updated in over 6 months because there's been no security holes. Updates happen according to my policies by dropping them in the correct directory if I don't want it to auto-download, although I do just use auto-downloading. I can have one central server per location, then have the server upload it's logs to my central server a few times a day to keep traffic on my VPN links down. It works better and has caused fewer issues. Plain and simple, it's been a better product. Cheaper too!
Granted it was ages ago and I believe with either version 3 or 4, but without a Dragon recommended sound card or headset headset I could easly speak in a normal manner (after about 2-3 weeks worth of training and doing corrections) in any window and get maybe one or two errors per page in a document. Had more problems with chatting on IRC and ICQ, but not too many. Did a few multi-page papers at that time, and actually would say it didn't hurt me any. A mute switch on the mic was a godsend though. Kept it in one hand, and reached for the mouse as needed. Main thing is, make sure you do your corrections through the software and it'll catch on. It improved over time. Note this was in a dorm room for the most part so I was greatly pleased.
Slashdot Mirror
As a former Symantec Corp customer, I'll disagree with that. The uninstaller for 8 was horrible, and the push install of 9 flat out didn't work for about half of my network (frequently caused by issues with 8). Nothing special about the network either, it just didn't work. In fact, about 1 in 20 network installs didn't work at all for some reason and I had to go install by hand. 9->10 seemed like it was going better until I had several systems start randomly screwing up and causing our EE and ME CAD applications to crash. I was getting sick of all the issues with security between the server and the clients as well as a multitude of other things.
I moved to NOD32, and couldn't be happier. Uses less than half the resources Symantec Corp did, and does a better job. I've had systems come out cleaner using a 3 month old set of definitions with NOD than Symantec Corp. I've got a central management interface that hasn't needed updated in over 6 months because there's been no security holes. Updates happen according to my policies by dropping them in the correct directory if I don't want it to auto-download, although I do just use auto-downloading. I can have one central server per location, then have the server upload it's logs to my central server a few times a day to keep traffic on my VPN links down. It works better and has caused fewer issues. Plain and simple, it's been a better product. Cheaper too!
Granted it was ages ago and I believe with either version 3 or 4, but without a Dragon recommended sound card or headset headset I could easly speak in a normal manner (after about 2-3 weeks worth of training and doing corrections) in any window and get maybe one or two errors per page in a document. Had more problems with chatting on IRC and ICQ, but not too many. Did a few multi-page papers at that time, and actually would say it didn't hurt me any. A mute switch on the mic was a godsend though. Kept it in one hand, and reached for the mouse as needed. Main thing is, make sure you do your corrections through the software and it'll catch on. It improved over time. Note this was in a dorm room for the most part so I was greatly pleased.