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

Updating policy stuck at "Awaiting Policy Transfer"

I have an updating policy defined which works fine for several machines, but on one particular machine, it gets stuck in the console for updating policy at "Awaiting Policy Transfer"

It does in fact assign the primary source correctly, and the client downloads and updates fine. This machine is also running the update manager, and that works fine as well.

I looked at C:\ProgramData\Sophos\AutoUpdate\Config\iconn.cfg file, and it contains the following. it contains a proxy port, which it shouldn't, and I am not sure how this is being populated, as I have never specfied a proxy.

I've tried uninstalling all Sophos apps, including the update manager, and reinstalling, but it keeps on creating the same iconn.cfg file with the proxy. i have also deleted it from the console and added it again.

Has anyone run into this issue and found a resolution ?

My next step is to unisntall everything again, delete it from the console, and then try and purge it from the database to see if tha t works. I would prefer to find an easier resolution though.

******

;****************************************************************************
;
; iconn.cfg
;
; Please do not edit this text file.
;
;****************************************************************************

[PPI.WebConfig_Primary]
AllowLocalConfig = 0
AutoDialTimeout =
LocalPath =
DownloadGranularity =
ConnectionAddress = \\PPQ001\SophosUpdate\CIDs\S000\SAVSCFXP\
PortNumber =
UserName = PP\Backup
UserPassword = password
ConnectionType = UNC

[PPI.ProxyConfig_Primary]
AllowLocalConfig = 0
ProxyPortNumber = 8080

[PPI.WebConfig_Secondary]
AllowLocalConfig = 0
AutoDialTimeout =
LocalPath =
DownloadGranularity =

[PPI.ProxyConfig_Secondary]
AllowLocalConfig = 0
ProxyPortNumber = 8080

*********

:55153


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

    It applys the primary source server fine, but it doesn't apply the  other policy parameters

    it doesn't apply the console policy at all - this is just the initial install location (i.e. the location setup.exe is run from). Does it comply with the other policies (e.g. Anti-Virus and HIPS, Tamper Protection).

    To narrow down the problem please stop and start the Sophos Agent service, then request Comply with -> All Group Policies from the console, wait a few minutes and then check (and post) the agent log. BTW, if you view the secondary SUM in the console's Endpoints view, tab Computer Details: Is the timestamp in the Last message time column more or less current? 

    Standard support is included with the license, you can contact Support at any time (phone, web form, or email).

    Christian

    :55174
Reply
  • Hello alizza78,

    It applys the primary source server fine, but it doesn't apply the  other policy parameters

    it doesn't apply the console policy at all - this is just the initial install location (i.e. the location setup.exe is run from). Does it comply with the other policies (e.g. Anti-Virus and HIPS, Tamper Protection).

    To narrow down the problem please stop and start the Sophos Agent service, then request Comply with -> All Group Policies from the console, wait a few minutes and then check (and post) the agent log. BTW, if you view the secondary SUM in the console's Endpoints view, tab Computer Details: Is the timestamp in the Last message time column more or less current? 

    Standard support is included with the license, you can contact Support at any time (phone, web form, or email).

    Christian

    :55174
Children
No Data