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

*********

This thread was automatically locked due to age.

Parents

0 QC over 9 years ago

Hello alizza78,
the PPI.ProxyConfig_ sections are normal. You'll find them - slightly different - in the configuration files of the other endpoints as well. In particular AllowLocalConfig = 0 indicates a managed installation and that there is just one other line with ProxyPortNumber = 8080 suggests that this the initial policy built by setup.exe.
When a policy from the console is received and applied it's always the complete policy. After installation of the Endpoint components the status should be Awaiting policy from console ..... Anyway, if you see a status then RMS is basically working. Previously the RMS component was managed and updated by the Endpoint product but it has recently been put under the control of SUM. Did you ever reboot after installing SUM? Or just restart ... hm, is only the Updating Policy Awaiting ...? - then restart the AutoUpdate service.
Christian
:55159
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 QC over 9 years ago

Hello alizza78,
the PPI.ProxyConfig_ sections are normal. You'll find them - slightly different - in the configuration files of the other endpoints as well. In particular AllowLocalConfig = 0 indicates a managed installation and that there is just one other line with ProxyPortNumber = 8080 suggests that this the initial policy built by setup.exe.
When a policy from the console is received and applied it's always the complete policy. After installation of the Endpoint components the status should be Awaiting policy from console ..... Anyway, if you see a status then RMS is basically working. Previously the RMS component was managed and updated by the Endpoint product but it has recently been put under the control of SUM. Did you ever reboot after installing SUM? Or just restart ... hm, is only the Updating Policy Awaiting ...? - then restart the AutoUpdate service.
Christian
:55159
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data