Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 33157 views
  • Users 0 members are here
Options
Suggested
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"

alizza78

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
  • 0

    Hi,

    I managed to resolve the issue myself. There was something wrong with the endpoint as well, it was updating, but it was showing wasn't showing 'Matches' and when I tried to force an update, it wouldn't update. To fix it, I performed the following:

    • Removed all sophos software from the machine. Rebooted, delete any lingering configuration files
    • Change all references in policy to primary SUM to allow deleteion of endpoing and computer object
    • Reinstall SUM on machine, configure and update. Reconfigure policies to point to new SUM.
    • After successful reinstall of SUM, machine reappeared in console in normal container, reprotected, and all policies successfuly applied. Rebooted and everything back in compliance.

    There was definitely something wrong with the iconn.cfg file. The reference to the proxy was causing a communication issue. i actually checked a backpup of the file before the update and there was no reference to a proxy. After a complete reinstall, the settings are as they were without reference to the proxy.

    Regards

    :55207
Reply
  • 0

    Hi,

    I managed to resolve the issue myself. There was something wrong with the endpoint as well, it was updating, but it was showing wasn't showing 'Matches' and when I tried to force an update, it wouldn't update. To fix it, I performed the following:

    • Removed all sophos software from the machine. Rebooted, delete any lingering configuration files
    • Change all references in policy to primary SUM to allow deleteion of endpoing and computer object
    • Reinstall SUM on machine, configure and update. Reconfigure policies to point to new SUM.
    • After successful reinstall of SUM, machine reappeared in console in normal container, reprotected, and all policies successfuly applied. Rebooted and everything back in compliance.

    There was definitely something wrong with the iconn.cfg file. The reference to the proxy was causing a communication issue. i actually checked a backpup of the file before the update and there was no reference to a proxy. After a complete reinstall, the settings are as they were without reference to the proxy.

    Regards

    :55207
Children
No Data
Unfiltered HTML