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

When will v17.1 ga be available by auto update

Hi folks,'

the general release of v17.1 seems to b e stuck, no updates to existing machines unless you do a ma hula install.

Is there a problem or series of problems preventing the v17.1 being deployed to all users?

Information to the forums seems to be lacking?

Ian



This thread was automatically locked due to age.
Parents
  • To clarify... is it still being phased via auto update or is it completely released? My console is still showing "no records found" under System > Backup & Firmware > Firmware > Latest Available Firmware. I had a problem over the last 6 months where I noticed it hadn't notified me of recent MR releases. I manually updated to 17.0.8 MR8 thinking this would fix it moving forward but I am now wondering if I still have a problem with auto update. If I manually apply the update I wont know and will miss future releases unless I go check. 

    Thx in advance.

  • Hi,

    You could activate the Forum notification via Email.

    https://community.sophos.com/products/xg-firewall/b/xg-blog

    The small gear on the right top. 

    Cheers

  • Okay, but I would put that in the "workaround" category. I would like to confirm if I have a problem with the auto update. Can you confirm if I should be seeing the auto update notice (has it been fully deployed)? If so, then I know I have a problem and will post a new thread. 

  • Hi,

    Just check the Log on CLI.

    Advanced shell : tailf /log/u2d.log 

    Press "Check latest firmware". Is there an Issue / error or is u2d server telling your appliance, there is no update? 

    We using a staging deployment for the automatic u2d. 

    Cheers

Reply
  • Hi,

    Just check the Log on CLI.

    Advanced shell : tailf /log/u2d.log 

    Press "Check latest firmware". Is there an Issue / error or is u2d server telling your appliance, there is no update? 

    We using a staging deployment for the automatic u2d. 

    Cheers

Children
  • Don't see an error. Assuming this means no update has been pushed:

     

    DEBUG     Jun 21 15:05:45 [8875]: Response code : 200                           
    DEBUG     Jun 21 15:05:45 [8875]: Response body :                               
    <Up2Date/>