Error
  • JUser::_load: Unable to load user with id: 67

Featured Articles

IHS teardown reveals Galaxy S5 BOM

IHS teardown reveals Galaxy S5 BOM

Research firm IHS got hold of Samsung’s new flagship smartphone and took it apart to the last bolt to figure out…

More...
Galaxy S5, HTC One M8 available selling well

Galaxy S5, HTC One M8 available selling well

Samsung’s Galaxy S5 has finally gone on sale and it can be yours for €699, which is quite a lot of…

More...
Intel lists Haswell refresh parts

Intel lists Haswell refresh parts

Intel has added a load of Haswell refresh parts to its official price list and there really aren’t any surprises to…

More...
Respawn confirms Titanfall DLC for May

Respawn confirms Titanfall DLC for May

During his appearance at PAX East panel and confirmed on Twitter, Titanfall developer Respawn confirmed that the first DLC pack for…

More...
KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 gained a lot of overclocking experience with the GTX 780 Hall of Fame (HOF), which we had a chance to…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Tuesday, 20 March 2007 15:26

Microsoft admits that OneCare is flawed

Written by
Image

Working on a fix


Microsoft is admitting that its OneCare security suite has "a problem" with the underlying antivirus code.

 
Speaking to ZDNet UK at the CeBIT show in Hanover, a senior manager admitted that its consumer security product is far from perfect and that pieces are actually "missing".

 
Arno Edelmann, Microsoft's European business security product manager, told ZDNet UK that although OneCare was not a bad product bits and pieces were missing.

 
He said that its main problem lies with a core technology of OneCare, the GeCAD antivirus code, and how it interacts with Microsoft mail servers.

 
This means that Microsoft updates and mail server infrastructure do not harmonise. Mail received from a server running Exchange 2007, works well, but if mail is received from servers running Exchange 2000 or 2003, the likelihood of quarantining is too high.

 
Edelmann said that the software should never have been rolled out when it was, but they're fixing the problems now," said.

 

More here.

Last modified on Tuesday, 20 March 2007 14:32

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

To be able to post comments please log-in with Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments