Give us your feedback! Help us improve the product!

[Guest]

[Melih]

Disk Encryption will be incorporated as the next stage..

[Little Mac]

EDIT: I removed SQL 2008 Express and installed SQL 2005 Express Adv and the installation worked.  So apparently, this software "REQUIRES" 2005 only.  I did use the SP3 version of 2005.

Good point!

Also note that if you're installing on an XP SP3 box, you will likely run into issues with MSXML6.

Reason is that XP SP3 includes a newer version than what comes w/MS SQL Server 2005 Express SP3.  Apparently MS SQL can't tell a newer version already exists and not install that part, so the whole thing gets hosed.

If so, use MSICUU2 to remove the XP SP3 version of MSXML6, then reinstall MS SQL Server 2005 Express.  Not the cleanest way, but until XP and SQL coders can work together it may be all you can do...

LM

[LHammonds]

What exactly gets hosed up?  Everything seems to be working OK.  I have 2 machines managed with the CIS product remotely installed.

I had the following installed PRIOR to install WinXP SP3:

 - MSXML 4.0 SP2 (KB954430)
 - MSXML 4.0 SP2 Parser and SDK
 - MSXML 6.0 Parser

Here are the version details of my system as it currently stands:

 - Comodo CESM Agent - Version 1.0.0.0
 - Comodo Endpoint Security Manager - Version 1.1.1813.31
 - Comodo Internet Security - Version 3.8.6595.1477
 - MSXML 4.0 SP2 (KB954430) - Version 4.20.9870.0
 - MSXML 4.0 SP2 Parser and SDK - Version 4.20.9818.0
 - MSXML 6.0 Parser - Version 6.10.1129.0
 - Microsoft .NET Framework 1.1
 - Microsoft .NET Framework 1.1 Hotfix (KB928366)
 - Microsoft .NET Framework 2.0 Service Pack 2 - Version 2.2.30729
 - Microsoft .NET Framework 3.0 Service Pack 2 - Version 3.2.30729
 - Microsoft .NET Framework 3.5 SP1
 - Microsoft SQL Server 2005 Express Edition with Advanced Services SP3 - Version 9.00.4035
 - Windows Installer 4.5
 - Windows Internet Explorer 7 - Version 7.0.5730.11
 - Windows PowerShell(TM) 1.0 - Version 2
 - Windows XP Service Pack 3

LHammonds

[Little Mac]

If you had MSXML6 prior to update from XP SP2 to SP3, you might be fine.  The SP3 installer might be "smart" enough see XML already there and not overwrite the install.

Here's the way it tends to happen, though:

XP SP3 installs MSXML6.

MSSQL Server 2005 Express comes with MSXML6 as well.  Their installer can't tell (or doesn't "care") that XML is already installed.  Rather than skip it, it reinstalls over (but doesn't uninstall the existing one first).  However, it can't complete the install because a newer version (from SP3) is already installed, so it errors out. 

Thus, MSSQL can't complete it's install because of a problem w/VSS Writer (MSXML6 issue).  Existing MSXML6 is at that point non-functional; it cannot be repaired, nor uninstalled, because there is an incomplete installation pending, and MSSQL still "wants" to install its version of MSXML in order to finish installing.

The work-around then is to install MSICUU2 to remove the now-corrupt MSXML6, then reinstall MSSQL. 

The issue is well-documented online (although not so much by MS...).

LM

[wlovins]

After testing the software, I have a few comments that would make it easier to use/administer for our environment. It is possible I missed a few of these things in the documentation. If I have, please point me to the right places.

For information:
Client machines - All Windows XP (x86) with all of the latest patches/service packs.
Server - Windows 2003 Server (x86) with SQL Server 2k5 Express

1: Ability to enable/disable portions of the software during install or from the admin console.
Specifically, we'd like to implement the virus scanner now on all machines, but not enable the firewall. I don't see any convenient way to do this. If I need to use the import/export configuration piece (under tools I think), either give an easier way to find documentation or just implement a basic configuration manager for setting certain components for certain groups of users. I guess what I'd eventually like to see is service classes for different machines.

2: The ability to allow virus scanning to be initiated on the client machines. I installed the remote management version of the Comodo software and noticed a few things weren't working properly (or at least it didn't appear to be).
   a: Real-time scanning didn't look to be enabled by default.
   b: There wasn't any way to have the end-user right-click on a file/directory and scan something immediately.
   c: The user couldn't initiate a scan of the entire disk/machine from the comodo interface on the client machine. Everything popped up that it was disabled in the Remote Administration Mode.

3: There were a few minor issues with the software removal portion capability. Specifically, it was the list of installed software wasn't 100% accurate. When I went into Add/Remove programs, Hamachi was installed. In the list of installed software that I had Comodo pull, Hamachi wasn't in the list. So.. in this case, there is a disparity between the installed software lists.

I would like to be able to easily unlock some of that functionality for some users. I know I can install the normal free version on client machines... but that removes the ability for me for force a scan across the entire network. 

It looks like you're off to a great start. I will enjoy seeing it evolve as time goes on. 

[napsterz]

After testing the software, I have a few comments that would make it easier to use/administer for our environment. It is possible I missed a few of these things in the documentation. If I have, please point me to the right places.

For information:
Client machines - All Windows XP (x86) with all of the latest patches/service packs.
Server - Windows 2003 Server (x86) with SQL Server 2k5 Express

1: Ability to enable/disable portions of the software during install or from the admin console.
Specifically, we'd like to implement the virus scanner now on all machines, but not enable the firewall. I don't see any convenient way to do this. If I need to use the import/export configuration piece (under tools I think), either give an easier way to find documentation or just implement a basic configuration manager for setting certain components for certain groups of users. I guess what I'd eventually like to see is service classes for different machines.

2: The ability to allow virus scanning to be initiated on the client machines. I installed the remote management version of the Comodo software and noticed a few things weren't working properly (or at least it didn't appear to be).
   a: Real-time scanning didn't look to be enabled by default.
   b: There wasn't any way to have the end-user right-click on a file/directory and scan something immediately.
   c: The user couldn't initiate a scan of the entire disk/machine from the comodo interface on the client machine. Everything popped up that it was disabled in the Remote Administration Mode.

3: There were a few minor issues with the software removal portion capability. Specifically, it was the list of installed software wasn't 100% accurate. When I went into Add/Remove programs, Hamachi was installed. In the list of installed software that I had Comodo pull, Hamachi wasn't in the list. So.. in this case, there is a disparity between the installed software lists.

I would like to be able to easily unlock some of that functionality for some users. I know I can install the normal free version on client machines... but that removes the ability for me for force a scan across the entire network. 

It looks like you're off to a great start. I will enjoy seeing it evolve as time goes on. 

Adding To The Above Points Mentioned By Wlovins, I Would Also Like To Mention That  An Option Should Be Added Where The Client PC's Can Fetch The Vir. Def. Updates Which Is Been Already Downloaded To A Centralised Server. Since We Don't Have This Option In The Versions Released So Far, All My Client PC's Has To Connect To The Internet Individually To Update The Vir. Definitions Which Eat's The Bandwith. Moreover Its Been Something Like Making Mandatory That The Client PC's Should Have An Internet Connection.

[dlehman]

I agree with Wlovins and napsterz.  The three main functions I would like to see are user initiated scanning, delete computers, and move computers. 
Currently I only have the 5 free licenses but I will have the full product soon, so this may not be an issue.  But if a user thinks they have a virus I go look at their PC and run scans, even logged in as admin to their box I cannot run a manual scan.  However, getting CIS deployed throughout the network should stop the virus from getting in, in the first place. 
I am in a network where the AD changes quite frequently.  I am in process of cleaning it up and that involves deleting old computers and renaming current computers and putting them in the appropriate OU. 
Comodo will import the AD structures just fine and when I rename a computer in AD doing another import will update the CESM database.  However, it will not delete computers or move the renamed ones to the new OU. 
I understand not deleting a computer to preserve the integrity of the database and history of alerts and logs.  But I have 375 computers and only 5 are managed at this time.  If a computer has never been managed, you should be able to delete it.  Also I don’t think changing its place in the computer tree will affect the integrity of the database. 

Thank you,
dlehman

[ratz]

Hello!

I just want to comment some of you post to give you updated information about COMODO products.

wlovins

1: Ability to enable/disable portions of the software during install or from the admin console.
Specifically, we'd like to i....

CIS 3.11 support partial installation. You can select components to install - Defence+ and Firewall or Defence+ and Antivirus.

napsterz
Comodo Offline updater can be used to update antivirus, so for now computers can have no internet connection. Just connection to Comodo Offline updater.

dlehman
You cannot delete computer, but can hide them, which actually equivalent of deleting.

[Tags:]