Can I run the diagnostics on a CIS client from CESM console?
As I said before, I just killed my own CIS by manually deleting bases.cav in safe mode :P. It now says Antivirus engine is not initialised. I will run diagnostics or reinstall CIS again, not a problem. 8)
But, I just wanted to know if the same can be done from CESM console instead of client side installation. ;D
Edit: Can I uninstall CIS on a client from CESM console? (may be for a reinstallation)
(testing CESM to it’s peeks… >:-D)
Hi Siva,
Whenever I run a new program or application, after clicking the "do not isolate again" in the sandbox alert, the file is not getting in to the trusted files list. It gives the same alert everytime I try to open the file, no matter how many times I click the "do not isolate again" link. ???
This behaviour is really weird. After clicking the “do not isolate again” link a file should get the trusted files list no matter whether CIS is in local or remote administration mode. From the other hand the behaviour when CIS shows popus being in remote mode is wrong and this should be fixed in CIS.
For now I can think of the only reason why this is happening: the changes to the trusted files list you made by clicking the “do not isolate again” might be overwritten by ESM policy. I.e. you add a new file to the list and ESM overwrites the list and in that way restores its original state (without the added file). Do you think this is a possible reason for your case? If not, could you please export CIS configuration from that endpoint (go to “More->Manage My Configurations” and export the active configuration to a CIS xml configuration file) and send it to us? Also, what OS and CIS versions are installed on that endpoint?
Sincerely,
Alexander
Two things are still bothering me.
I could connect to CESM server from client interface in almost all the cases. The passwords were not wrong either. 88)
I tried it twice and thrice on different systems, it’s the same result.
However, I am very much happy that there is at least a beginning :-TU and surely we are going to overcome these minor issues in the upcoming releases. Awaiting a new and improved version… 
I could not wait longer so I tried to implement CESM on a trial basis in my office.
I installed CESM and CIS on one system and tried to deploy agent from CIS interface. It failed with a message saying “agent deployment failed”, no other information. What could be the cause ?
I installed CESM and CIS on another machine things worked fine here. I copied data on to it’s cache folder. I could successfully update CIS on the same system by setting the proxy :-TU (This system does not have Internet connectivity).
But, by setting this system and port as proxy to CIS on other systems, they do not seem to identify this at all. They are all giving “Check your internet connection” message ??? :o. (The system with CESM is accessible to all other systems, folder sharing, file backup and all other networking functions are working without any problem.) How do I know what could be the problem ???
One possible reason is connectivity issues. Try specifying IP addresses (not DNS names), and ensure no firewall rules block Agent connections.
But, by setting this system and port as proxy to CIS on other systems, they do not seem to identify this at all. They are all giving "Check your internet connection" message ??? :o. [i](The system with CESM is accessible to all other systems, folder sharing, file backup and all other networking functions are working without any problem.)[/i] How do I know what could be the problem ????Again, try specifying IP addresses for the proxy, and apply proxy settings via policy. If you're applying manually, and CIS fails to update, try cycling your LAN interface (disable/enable).
3. Can we use any [b] HTTP file server[/b] like [b]HFS[/b] http://www.rejetto.com/hfs/?f=intro instead of CESM ? or CESM is compulsory to distribute updates ???CESM is not designed to work in totally offline environment. You need to provide some kind of Internet connection at least for the CESM server machine, otherwise it won't function properly.
–
Best regards,
Denis.
The network is fine. I am able to ping the system with dns name, able to use shared folders using name, etc., Besides, using IP address also gave the same result.
As for firewall rules, there is no firewall at all. I disabled both windows and comodo firewalls, as I did not have any internet connection at all.
The network is fine. I am able to ping the system with dns name, able to use shared folders using name, etc., Besides, using IP address also gave the same result.
That’s exactly why I asked for the possibility of using 3rd party file server tools, so that I can simply avoid using CESM at the system where I do not have internet connectivity.
Here is my plan:
I use CESM on a system with connectivity and generate proxy cache.
I copy proxy to the system with no connectivity.
I use tools like HFS to distribute the proxy cache data over http
I specify this system as proxy address on CIS clients to download updates.
When I try to install CESM 2.1 Beta on WinXP (SP2) systems, I get “installation ended prematurely, please try again” error.
Does CESM require SP3 or is there any other reason ?
Hi, Siva.
The CESM server requires XP SP3.
CESM Central Service computer - the PC that will run the Endpoint Security Manager software 1. Operating system Microsoft® Windows™ Server family: • Windows 2003 Server (SP2 or higher) x86 and x64 editions • Windows 2003 Small Business Server • Windows 2003 Small Business Server R2 • Windows 2008 Server (SP2 or higher) x86 and x64 editions • Windows 2008 Small Business Server • Windows 2008 Server R2 - or - Microsoft® Windows™ client family: • Windows 7 x86 and x64 editions • Windows XP (SP3 or higher) x86 and x64 editions • Windows Vista (SP1 or higher) x86 and x64 editions
Thanks for the reply…
That indeed answered my question, but kept my problem alive
This way I can completely avoid installing CESM on all clients (quite unnecessary and weird in my opinion)
Any suggestions ?
I can’t give you advises on how to avoid installing CESM on your workplace But if you only need to distribute updates for CIS on your network, setup some proxy server able to serve requests from cache and you are done. CIS is already able to connect through proxy, for years, and CESM doesn’t deal with updates itself, anyway. The CachingProxy we added in 2.1 Beta was aimed primarily on saving traffic, for large networks, and to mitigate some (occasional) connectivity issues. You probably will need to find another proxy software, but the idea remains the same.
!ot! !ot! !ot!
I do not want to avoid CESM to save money ;). But, as I have explained in my previous posts, my primary goal is to update CIS on all offline systems and the proposed solutions such as installing CESM on one system and updating others from network did not work for me :'(.
I wanted to have a simpler solution so that I can use it on a per system basis, in this way I can also give updates to all my friends who do not have internet.
I could never get it to work, there is no single working tutorial or guide to achieve this in this forum. I myself posted one which is lengthy and does not always work for myself.
I do understand the idea behind it, but the process still remains unexplained, it never worked, for me at least :'(.
Can any of you please guide me in a step by step manner on using a suitable http/proxy server (please suggest one, a simple one) in a completely offline environment.
Hi Siva, thanks a lot for such detailed feedback.
Let’s look what we have with agent and CIS deployment. “The network name cannot be found” is a quite tricky error to reproduce so we need to go through some check steps if you don’t mind.
Even trying to deploy CIS on to the same system where CESM is installed is also giving the same error.
This likely means that problem is with the server machine.
4. About error suggestions I am totally agree, this is a subject to change in next releases. HKLM.…\forceguest=0 means that this key should be set to 0.
5. If deployment fails with error “bad username or password” and you are sure that login and password entered are correct then it likely you have not set forceguest and LocalAccountTokenFilterPolicy keys on the target machine, please check this.
Please let us know results. Thank you.
Thanks Tim for your concern.
Yes, I only have CIS installed. I disabled Comodo Firewall, that did not make any difference.
Yes, I am able to access that folder, it is opening “Windows” folder.
To be more exact, I am now just trying to deploy agent on to the same system where both CESM and CIS are installed. So, it itself is the server, it is the client.
The “forceguest” is already set to “0”. The second one I thought was unnecessary (as the current user is in administrators group), but I did create it to verify, it does not make any change too.
This system configuration is Win7 x64 with UAC disabled. CESM 2.1 and CIS 5.10 installed and running. (Although the same failure occured on XP clients too, I am just trying to solve this test case first, as this is the simplest thing for me to do)
I observed a strange behaviour with installing and uninstalling CIS, while it is a client to CESM.
This is what I did.
I installed CESM, installed CIS, deployed agent, uninstalled CIS (for some purpose)
Here is the surprise, the agent was still there running on the system, while CIS got uninstalled alone. It did not offer to uninstall the agent or warn about it’s presence.
When I installed CIS again and go to “Manage this endpoint”, it shows “agent was successfully deployed” without me doing anything., but it is not connected to CESM, CIS main interface also does not show any sign of it in it’s left corner.
When I try to reconnect it to CESM, it says “agent deployment failed”
May be this is some design issue, please look in to this.
Besides, please provide a way to uninstall CIS directly from CESM, this way we can have more control over it. In case of trying out a different version on a client also, this is very useful.
Besides, please provide a way to uninstall CIS directly from CESM, this way we can have more control over it.
Hi Siva,
We are planning to include this feature in one of next releases. The user will be able to decide whether he wants to uninstall CIS when removing a computer from the “View All Computers” screen.