Skip to main content

How to solve if your Sophos Enterprise Console is not updated?

If your Sophos Enterprise Console is not updated, what will you do to resolve it?

It's simple and easy to resolve.

Check your Sophos Update Source URL are properly connected with your network or not first.

Go to Update Manager and check Username and Password for Source is correct or not. If all are correct, follow below steps.

Open a web browser and enter the following three addresses into the address box.

If the connection fails the most like cause is a firewall (including Windows 2008 server's software firewall) or a proxy blocking the connection or EnterpriseConsole.exe

To resolve the connection issue, allow connections on the above addresses (or for simplicity: * and * on port 80 for your Sophos Management server (and any other Sophos Update Manager servers) and add EnterpriseConsole.exe.

 If a successful connection is made you will see the message "it works - authed" or "it works", then you need to check your SEC.

1)Close your SEC
2)Select Start | Run | type: services.msc
3)Scroll down to the Sophos services (by default the list is in alphabetical order)
4)Stop the following services in this order:

Sophos Message Router
Sophos Agent
Sophos Update Manager
Sophos Management service (if present)

5)Ensure that any processes named 'SophosUpdateMgr.exe' are no longer running.

6) In Windows Explorer browse to:

- XP/2003: C:\Documents and Settings\All Users\Application Data\Sophos\Update Manager\Update Manager
- Windows 7/2008: C:\ProgramData\Sophos\Update Manager\Update Manager

You will see two folders Warehouse and CIDS.

Rename that two folder as Warehouse.old and CIDS.old. Then create Warehouse and CIDS folders again.

7) Start the following services in this order again:

Sophos Message Router
Sophos Agent
Sophos Update Manager
Sophos Management service (if present)

8) In Enterprise Console, download the files again by right-clicking the parent update manager and selecting 'Update now'.
9) Once the parent update manager has downloaded its data, right-click the child update manager and select 'Update now'.

Wait about 30 minutes and then you will see your SEC is updated.

If you want, you can copy and paste files from Warehouse.old and CIDS.old to Warehouse and CIDS back.

OK. You resolve your SEC updating issue.

May you all be happy.
(Be knowledgeable, pass it on then)


  1. Your blog is really good. This information is really useful for those who have searched for this and you have great knowledge about this. I’m really impressed with your post. 3PL Warehouse Management Systems

  2. This comment has been removed by the author.

  3. Thanks for your post. It's very helpful post for us. You can also visit warehouse logistics services Tokyo for more Victor Steel related information. I would like to thanks for sharing this article here.


Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f