Jonathan Starr

Member
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jonathan Starr

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Regardless of the error message, just rebooting the machine 'fixed' the problem. Edit: That string, and variations on it, does not appear in any documentation I could find.
  2. I've just received the following error message and I think there may be some missing information or a typo/failed string replace? HostJob[Emsisoft Enterprise Console]: Some remote security settings are incorrect. Please consult 87 documentation. Can anyone help with this error message?
  3. Hi Raynor, we're also suffering from it too so you aren't alone. Like you we have a relatively simple setup and I believe I've eliminated the obvious potential issues such as network transport, time synchronisation, etc.. I have noticed it's a lot better than it used to be, it's only a few clients each time now instead of nearly all. And I've discovered I can rejoin the clients remotely using WMI remote process execution which saves wear and tear on my legs. Regards, Jonathan
  4. Hi Frank, Thank you very much for the reply. We don't (currently, anyway) have a local administrator account available on the machines, so I'm trying to work out a way to persuade psexec to run the script as local system. Invoking psexec from a domain administrator user context with the following options starts the script on the target under LOCAL SYSTEM: psexec \\MACHINE_IP_OR_HOSTNAME -s -i "C:\TEMP\Disconnect_EAM_from_EEC.bat" It's very interesting that on some machines the service gets removed just fine in a domain administrator context and on some it does not. I have a large stack of Process Monitor logs to look though now, the answers should be in there somewhere I guess. I have debug logs from machines that have become disconnected from EEC, would this be enough for your programmers to work out why our machines keep dropping off. Or would you need a diagnostic log that was started before a machine began having communication problems?
  5. Guess there's an edit timeout then. A little bit of work later and there is no difference between the manual command and the GUI button, CommService receives the exact same arguments. As EEC and PSEXEC cause the same broken behaviour but running the disconnect script as LOCAL SYSTEM on the target works (but RunAs [domain administrator] does not...) it looks like some interesting permissions/ACL issue.
  6. I know this was supposed to be fixed, but it's still happening. It seems to be triggered by major Windows 10 updates. After the Fall update I have a sea of red 'Not Protected!' in my EEC console, maybe 30% of the clients and it's not the same ones each time. The server log shows [CLIENT_IP]: Emsisoft Anti-Malware client connection failed. Code: 32000. Description: Could not establish connection. The client SQLITE log has the following in it: SERVER_HOSTNAME~8082~1~276: Server certificate verification failed. Connection aborted.~~0 Running Disconnect_EAM_from_EEC.bat and then a full or lite deploy package does not solve the issue. Clicking the Disconnect button in the client GUI and then running a lite deploy package does solve the problem. What does the Disconnect GUI button do differently to the Disconnect_EAM_from_EEC.bat script? I need to be able to script a fix for this rather than running round to each machine. Edit: The script line C:\Program Files\Emsisoft Anti-Malware\CommService.exe" /uninstall /silent EmsiCommService does not uninstall the service on the problematic machines. I'll investigate why not while I wait to hear anything. Edit2: I keep accidentally fixing it, which is slowing things down. The problem seems to be an EOSError exception which the Delphi documentation says is an 'operating system error', very helpful!
  7. I can't replicate the same issue currently but I have managed to reliably create what may possibly be a related issue, it seems to be highly timing related: Description: This will create a group at the same level as the special group 'Organisation', it will also have a different name between the 'Policies' and the 'Clients' screen. Steps: Clone 'Organisation' to a new group (New group 1). Clone 'New group 1', this will create a new child group (New group 2). Rename 'New group 2' to 'aaaaaa'. Drag 'aaaaaa' to the 'Organisation' group to change its level. Add a computer to 'aaaaaa'. Rename 'New group 2' to 'bbbbbb'. Notes: Steps 2, 3 and 4 must be completed quickly. Results: 'bbbbbb' will now be on the same level as 'Organisation' not a child of it as is normal, it will also have two different names depending on the screen you are on. If you try to delete 'bbbbbb' you may also get: The given DataRow is not in the current DataRowCollection. at System.Data.DataRowCollection.Remove(DataRow row) at A2EGui.Screens.ClientSettings.ComputerGroupsScreen.RemoveSubTree(ComputerGroup computerGroup, List`1 computerGroups) at A2EGui.Screens.ClientSettings.ComputerGroupsScreen.DeleteGroup() at A2EGui.Screens.ClientSettings.ComputerGroupsScreen.bDelete_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at DevExpress.XtraEditors.BaseButton.OnClick(EventArgs e) at DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m) at DevExpress.XtraEditors.BaseControl.WndProc(Message& msg) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Edit: I have also managed to create two 'New group 1' groups after doing this, one as a child of the other. And after deleting the groups I get an error that 'aaaaaa' or 'bbbbbb' already exists as a name now.
  8. Understood, I won't be touching anything else in there. I think the only other solution to this would be have been a fresh install though, it doesn't seem possible to rename the group root from the GUI and some of the new groups I cloned were also defective until I adjusted things. Have I provided enough information for you to log this with the developers as a issue? I have a copy of the broken db if you would like. Many thanks for your assistance.
  9. I'm not sure, I can't replicate it when I try now. I can't guarantee I'm remembering correctly but I am fairly sure that's what I did. (Edit: I think) I've fixed my issue by rejiggling the database and it seems to be working properly now. Adding new groups by cloning existing ones has produced working groups so far.
  10. Ok, restarting the service again after trying some more things has caused 'Organisation' to now be named 'Production'. The ComputerGroups table in the ae2System db does not look correct (attached). I'm going to have a go at fixing ComputerGroups and the linked ids in the other tables manually and see if I can get things straightened out.
  11. Thanks for the quick reply Frank H. I dragged the computer responsible for the top 'New Group 2' in my screenshot to 'Development'. The Client screen showed it was now in 'Development'. I then dragged it back to 'Production' and the Client screen showed it was back as 'New Group 2' again. So the issue follows the groups not the machines by the look of it. Regards, Jonathan
  12. Emsisoft Enterprise Console version 2017.12.0.3282 I'm having an issue with the policy names on some policies. I created them by cloning the 'New Computers' policy and renaming them, then dragging them up one level to be under 'Organisation'. In the Policies screen they show the correct names. In the Clients screen two of them are called 'New Group [x]'. I deleted one and recreated it and it was still called 'New Group' in the Clients screen. Am I doing something incorrectly when making these?