This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos End Point wont change update location

I have several computers that are managed by  the Enterprise Console.  I switch the updated location for all of the computers via the console and all but will use the new location.

I have physically gone to the computer and uninstalled Sophos from the computer and placed it back in.  Made sure that all of the policies have been accepted but it still shows a error log every once and a while that it can't find the previous update folder.

How can I make sure it will update from the new location?  I am assuming it's located in that computers registry somewhere.

Sincerely,

Ken

:44579


This thread was automatically locked due to age.
Parents
  • Hi,

    Does the computer show as same as policy for "Updating" in Enterprise Console?  

    Is it that the system believes it is correct as the client makes the comparion on the client side and just sends back the result to SEC.

    The config for SAU is stored in iconn.cfg under the config directory of SAU. 

    • Program files\sophos\autoupdate\config\ for XP/2003
    • Programdata\sophos\autoupdate\config\  for Vista+

    You could turn on message trails on the client, and then check the XML files which represent the messages sent down from the management server.  This will confirm what the client is getting from the management server. To do so, on the client:

    1. Stop the Sophos Message Router service

    2. Create a new DWORD value called MessageTrail and set it to 1 under :

        64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router\

        32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router\

    3. Start the Sophos Message Router service

    4. Delivered message files will start to be created under the "Envelopes" directory:

      Vista+: C:\ProgramData\Sophos\Remote Management System\3\router\envelopes\

      XP/2003: C:\documents and settings\all users\application data\Sophos\Remote Management System\3\router\envelopes\

    Have a look through the XML files following a comply with updating policy command from SEC to a problematic computer, you are looking for a message of type EM-SetConfig, it should be obvious it is an updating policy from the XML.  Is the path correct in that?

    Where exactly do you see the problem? In the ALC.log file, where it shows the path and this is not expected?

    Regards,

    Jak

    :44587
Reply
  • Hi,

    Does the computer show as same as policy for "Updating" in Enterprise Console?  

    Is it that the system believes it is correct as the client makes the comparion on the client side and just sends back the result to SEC.

    The config for SAU is stored in iconn.cfg under the config directory of SAU. 

    • Program files\sophos\autoupdate\config\ for XP/2003
    • Programdata\sophos\autoupdate\config\  for Vista+

    You could turn on message trails on the client, and then check the XML files which represent the messages sent down from the management server.  This will confirm what the client is getting from the management server. To do so, on the client:

    1. Stop the Sophos Message Router service

    2. Create a new DWORD value called MessageTrail and set it to 1 under :

        64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router\

        32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router\

    3. Start the Sophos Message Router service

    4. Delivered message files will start to be created under the "Envelopes" directory:

      Vista+: C:\ProgramData\Sophos\Remote Management System\3\router\envelopes\

      XP/2003: C:\documents and settings\all users\application data\Sophos\Remote Management System\3\router\envelopes\

    Have a look through the XML files following a comply with updating policy command from SEC to a problematic computer, you are looking for a message of type EM-SetConfig, it should be obvious it is an updating policy from the XML.  Is the path correct in that?

    Where exactly do you see the problem? In the ALC.log file, where it shows the path and this is not expected?

    Regards,

    Jak

    :44587
Children
No Data