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

Featured Articles

Snapdragon 400 is Qualcomm’s SoC for watches, wearables

Snapdragon 400 is Qualcomm’s SoC for watches, wearables

We wanted to learn a bit more about Qualcomm's plans for wearables and it turns out that the company believes its…

More...
Qualcomm sampling 20nm Snapdragon 810

Qualcomm sampling 20nm Snapdragon 810

We had a chance to talk to Michelle Leyden-Li, Senior Director of Marketing, QCT at Qualcomm and get an update on…

More...
EVGA GTX 970 SC ACX 2.0 reviewed

EVGA GTX 970 SC ACX 2.0 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Nvidia GTX 980 reviewed

Nvidia GTX 980 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
PowerColor TurboDuo R9 285 reviewed

PowerColor TurboDuo R9 285 reviewed

Today we will take a look at the PowerColor TurboDuo Radeon R9 285. The card is based on AMD’s new…

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

 

Facebook activity

Latest Commented Articles

Recent Comments