Please try following these steps:
Check if entered account has administrator privileges. Check if the domain administrator’s name is listed in the local machine’s “Administrators” folder under “Local Users and Groups”
Check if firewall is disabled on remote computer. Check if you can telnet to server_name port 9901 and/or server_IP port 9901 from the target to the server.
Go to services → right click on COMODO ESM Server → Properties → Go to the Log On Tab → Select “This account” → and input the domain administrator information → Click apply → stop and restart the service.
2-> Error on Telnet : “could not open connection to the host, on port 9901: Connect failed”
3-> Changed the log on services of ESM Server to the Domain Admin, but can’t restart it, i tried both :
3a → From Windows Services : i got this error The COMODO ESM Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
3b-> From Comodo Console, i can’t start it either, due to errors : got an access right issue on the local SQL mdf database. I put the local admin on read/write on the mdf, but still another error appear. I guess the domain admin do not have rights properties inside the DB.
I can deploy manually the Offline Agent on the Deestination Server, but there’s no “Offline Comodo Security Client” ?? (It was possible before on the version 2.1). I gave up this version 2.1 for some reasons, but Comodo 3.0 looks really promising, so i’m trying harder.
It’s really kind of crazzy It still not working to deploy it
. I have installed SQL Express 2012 just for the purpose = OK
. Telnet on port = OK
. Comodo ESM Server Running under Domain Admin = OK
. Firewall = OFF
. Comodo Agent Running under Domain Admin = OK
. Command “winrm quickconfig” on the Destination server = OK
Then step of deployment :
Executing update script…
Uploading Package … 83%
→ Fatal error during installation
Well, don’t know what to do now. It would have been helpful to get an Offline Client Installer, at least.
If someone come back with any help, i’ll be greatful.
You can replicate the ESM problems by right-clicking on “Manage” in your Server 2008 R2 menu. Wait for the roles to populate then right click on your server at the top of the tree-view in the left hand panel. Select “Connect to another computer” and supply a name or IP address of the target. You will get an error message about not being able to connect to the target.
If you need more help with enabling WinRM on the host server please let me know.
I had this problem and I found it was because the service “Windows Remote Management” was stopped and set to manual startup type on the destination machine. If you have the same problem as I had, here is how I fixed it:
On the destination machine type services.msc into the search bar on the start menu.
Find Windows Remote Management (WS-Management) in the list of services, start the service.
Re-try the deployment.
If it succeeds, consider enabling the service through group policy.
Select Startup: Automatic
Service Name: WinRM
Service Action: Start Service
You know (or can search for) how to apply the policy etc.
** When viewing the Group Policy Object Settings in Group Policy Management you will NOT see the correct settings that you applied, but they DO exist and they are what you set them to. This is a documented Microsoft glitch with a hotfix available.