System resources alerting (check under System Settings in your Policies)
Support of Windows 7 Embedded (Standard)
Management of AV scan scheduling as a policy item (check under Antivirus in your Policies)
VNC to remote (WAN-connected) endpoints
Push-deployment capability for Linux/Mac endpoints
CES 6.4
Big thanks to Dmitry, Alex , Sergey and their teams, Slava and his team, Radu and his team, Georgiana, Egemen and, of course, the big boss Melih for continuing to believe
Were you logged on with the same credentials you used when you installed 60913?
Are you using the LocalDB database or an external SQL(Express) database?
yes. i use the same account that user for 60913.
I use MS SQL Server 2012 Express LocalDB that was by default in ESM 2 … because i made an directly upgrade from ESM 2 to ESM 60913 a few weeks ago.
The error causing the upgrade to fail is: Database connection test failed: System.InvalidOperationException: Cannot check whether database exists. Error: Login failed for user ‘NT AUTHORITY\SYSTEM’. —> System.Data.SqlClient.SqlException: Login failed for user ‘NT AUTHORITY\SYSTEM’.
This is an SQL related issue and it either means NT AUTHORITY\SYSTEM is not listed as a SQL user or it does not have DbCreator rights.
In order to fix this:
1.Download MIcrosoft SQL Server Management Studio 2008 http://www.microsoft.com/en-us/download/details.aspx?id=7593
or
Download MIcrosoft SQL Server Management Studio 2012 http://www.microsoft.com/en-us/download/details.aspx?id=29062
2.Install it and connect to the local Db. It should be (localDb)\v11.0, using Windows Authentication
3.Expand Security, Expand Logins
4.If NT AUTHORITY\SYSTEM exists in that list, double click on it, skip to step 6
5.If NT AUTHORITY\SYSTEM is not listed, right click Logins, choose New Login, Search for System. It will add it as NT AUTHORITY\SYSTEM
6.Click on Server Roles, and make sure you add a check mark for “dbcreator”
7.Click Ok
8.Try installing ESM again.
CES 6.4 which is deployed through Comodo ESM wasn’t yet fully tested with win 8.1 , but we have received feedback of users that have installed it even if it’s not yet in the ESM windows supported list. ( First uninstalling ESM Agent+CES from endpoint with win 8 installed, upgrade it to win 8.1 , do the deployment of ESM agent and CES 6.4).
The feedback was good (CES functioning properly) but with the steps described in the previous post( First uninstalling ESM Agent+CES from endpoint with win 8 installed, upgrade it to win 8.1 , do again the deployment of ESM agent and CES 6.4). CES 6.4 deployed through Comodo ESM wasn’t yet fully tested with win 8.1 .