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 Christian,

    you are correct.

    Essentially, i was doing an update of the Sophos Console from 5.21 to 5.22, and I use a separate SQL server, so have to run the database scripts first. I wasn't paying attention, and botched the database update (as in wiped it clean!), but didn't realize until had already installed the 5.22 update. 

    So, no problem, reinstalled 5.21, restored database, The primary site running the console and SUM was fine, however my other SUM server, the one having the issue, was stuffed The SUM wouldn't update, so i had to reinstall SUM. All the clients worked, fine but the actual SUM server, because i didn't have time to get it working straight away, I used the primary SUM distribution point temporarily, and i did reinstal sophos on it directly from the primary SUM distribution point.

    When i had time, I reinstalled SUM, pointed the clients back, and it was all fine. However, the actual server running SUM updates fine, but only the updating policy is only showing as awaiting policy update. It applys the primary source server fine, but it doesn't apply the other policy parameters, such as frequency etc. The exact same update policy works fine on all the other clients though.

    At this point, i am waiting on approval of a Sophserv support account, and i will put in a support request. This is my first issue, so I have never acutally contacted support.

    I have tried everyting you suggested, but am out of ideas. It's either a residual setting on the server from a file or the registry,or a setting in the database, because even after total uninstall and reinstall and multiple reboots, the exact same settings keeps returning.

    :55167
Reply
  • 0

    Hi Christian,

    you are correct.

    Essentially, i was doing an update of the Sophos Console from 5.21 to 5.22, and I use a separate SQL server, so have to run the database scripts first. I wasn't paying attention, and botched the database update (as in wiped it clean!), but didn't realize until had already installed the 5.22 update. 

    So, no problem, reinstalled 5.21, restored database, The primary site running the console and SUM was fine, however my other SUM server, the one having the issue, was stuffed The SUM wouldn't update, so i had to reinstall SUM. All the clients worked, fine but the actual SUM server, because i didn't have time to get it working straight away, I used the primary SUM distribution point temporarily, and i did reinstal sophos on it directly from the primary SUM distribution point.

    When i had time, I reinstalled SUM, pointed the clients back, and it was all fine. However, the actual server running SUM updates fine, but only the updating policy is only showing as awaiting policy update. It applys the primary source server fine, but it doesn't apply the other policy parameters, such as frequency etc. The exact same update policy works fine on all the other clients though.

    At this point, i am waiting on approval of a Sophserv support account, and i will put in a support request. This is my first issue, so I have never acutally contacted support.

    I have tried everyting you suggested, but am out of ideas. It's either a residual setting on the server from a file or the registry,or a setting in the database, because even after total uninstall and reinstall and multiple reboots, the exact same settings keeps returning.

    :55167
Children
No Data
Unfiltered HTML