We're having trouble getting our clients to reconnect after upgrading from Enterprise Console 4.0 to 5.1.
Granted, a straight upgrade didn't work, so I had to run the stored procs in the various versions of the console to get the database from SOPHOS4 up to SOPHOS51, and the database is now located locally on the same box as the management server.
After changing the connection string, I can open up the Enterprise Console and see all of the devices, but hte only one connected is the server itself as the Update Manager.
Things I've already checked:
(1) The box now only has one NIC on it, so thats not an issue. the mrinit.conf files also show this single IP
(2) I've checked the router logs, other than a bunch of "cannot verify peer's ssl certificate, unknown ca", things seem fine - I see these after I try and push a policy:
16.10.2012 17:29:37 113C I Logged on Agent as a client
16.10.2012 17:29:37 0A9C I Routing to Agent: id=007DDFD1, origin=Router$sophos, dest=Router$sophos.Agent, type=EM-ClientLogon
16.10.2012 17:29:37 0A7C I Sent message (id=027DDEEC) to Agent
16.10.2012 17:29:37 0A7C I Sent message (id=007DDEEF) to Agent
16.10.2012 17:29:37 0A7C I Sent message (id=007DDFD1) to Agent
16.10.2012 17:29:57 0A9C I Routing to EM: id=007DDFE5, origin=Router$sophos.Agent, dest=EM, type=EM-GetStatus-Reply
16.10.2012 17:29:57 06F4 I Sent message (id=007DDFE5) to EM
(3) For a test client, I've verified that I can ping the IP address that Sophos lists for that device from the Sophos enterprise console machine.
(4) The DNS is properly set up to go to the new machine, which has the necessary files within a folder in IIS that mirrors the old server's setup. This "should" get around the primary update policy location IP address changing as it was listed under an http address that is a DNS name we can change.
Any pointers would be fantastic right now.
This thread was automatically locked due to age.
