Hello
I am installing Sophos Enterprise Console 551 on a Windows 2016 Server (Standard Edition).
There is another installation on a 2008 R2 server (SEC v550) on the same network. The R2 server is going to be decommissioned. I am unable to 'move' the installation across because there is not enough hard drive space left to take a backup of the Sophos databases on the 2008 server. Both servers are domain controllers and are the only servers this charity has.
My intention was to install SEC on the 2016 server, configure it, then uninstall the SEC installation from the 2008 server and re-protect the clients so they picked up the new SEC.
I have created a single new user account (SophosTitan) that has been specified for both the database access and for the Update Manager's credentials.
When I start the SEC a dialog appears with the title Initializing. Checking configuration... Waiting for Sophos Update Manager to register... After a short time a notification with the title Sophos Enterprise Console appears stating: Sophos Update Manager has not yet registered with the ystem. Do you want to continue waiting for it?
I have followed the instructions given here: https://community.sophos.com/kb/en-us/65025 but the notification continues to be displayed. I have restarted the services (which were running) and looked at the agent log but don't understand what the contents mean:
******************************************************************************
05.12.2018 11:42:09 176C I SOF: C:\ProgramData/Sophos/Remote Management System/3/Agent/Logs/Agent-20181205-114209.log
05.12.2018 11:42:09 176C I Sophos Management Agent 4.1.1.127 starting...
05.12.2018 11:42:09 176C I Starting AdapterManager ...
05.12.2018 11:42:09 0688 I Starting AdapterMonitor thread ...
05.12.2018 11:42:09 0688 I Loading new adapters: 0 registered adapters; 0 loaded adapters.
05.12.2018 11:42:10 176C I InitialiseClientLibraryLocal Agent, SOFTWARE\Sophos\Remote Management System\ManagementAgent\Private, , 1, ...
05.12.2018 11:42:11 0CCC W MSClient::Connect: failed to get router's IOR from supplied address and port.
05.12.2018 11:42:11 0CCC W NoRouterIORException: Caught MSClient::Connect: failed to get router's IOR from supplied address and port.
ClientConnection::Reconnect()
05.12.2018 11:42:17 0CCC W MSClient::Connect: failed to get router's IOR from supplied address and port.
05.12.2018 11:42:17 0CCC W NoRouterIORException: Caught MSClient::Connect: failed to get router's IOR from supplied address and port.
ClientConnection::Reconnect()
05.12.2018 11:42:22 0CCC I Initializing ...
05.12.2018 11:42:22 0CCC I Running certificate verification...
05.12.2018 11:42:22 0CCC I Compliant certificate hashing algorithm.
05.12.2018 11:42:22 0CCC E CORBA::Exception: Caught CORBA user exception, ID 'IDL:SophosMessaging/Rejected:1.0' ClientConnection::Reconnect()
05.12.2018 11:42:27 0CCC I Initializing ...
05.12.2018 11:42:27 0CCC I Running certificate verification...
05.12.2018 11:42:27 0CCC I Compliant certificate hashing algorithm.
05.12.2018 11:42:27 0CCC E CORBA::Exception: Caught CORBA user exception, ID 'IDL:SophosMessaging/Rejected:1.0' ClientConnection::Reconnect()
05.12.2018 11:42:32 0CCC I Initializing ...
05.12.2018 11:42:32 0CCC I Running certificate verification...
05.12.2018 11:42:33 0CCC I Compliant certificate hashing algorithm.
05.12.2018 11:42:33 0CCC E CORBA::Exception: Caught CORBA user exception, ID 'IDL:SophosMessaging/Rejected:1.0' ClientConnection::Reconnect()
05.12.2018 11:42:37 176C I Shutting down...
05.12.2018 11:42:37 176C I Stopping AdapterManager ...
05.12.2018 11:42:38 0CCC I Initializing ...
05.12.2018 11:42:38 0CCC I Running certificate verification...
05.12.2018 11:42:38 0CCC I Compliant certificate hashing algorithm.
05.12.2018 11:42:38 0CCC E CORBA::Exception: Caught CORBA user exception, ID 'IDL:SophosMessaging/Rejected:1.0' ClientConnection::Reconnect()
05.12.2018 11:42:39 0688 I Terminating the AdapterMonitor thread ...
******************************************************************************
I have checked the Windows Firewall and can see that ports 8192 to 8194 have been opened both inbound and outbound under the 'Domain' profile.
I have not proceeded with configuration of the new installation.
I was wondering if I needed to uninstall the old v550 installation before proceeding with the new v551 installation. If so, can anyone recommend a best practice to completely remove all traces of the old (and the new) installations so that I can start again? Or, perhaps someone can help me decipher the log so that I can understand what is happening and resolve this issue.
Many thanks!
Mark
This thread was automatically locked due to age.