Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 816 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 points issue

Xt

Hi all,

here is my trouble :

Laptops need to update through HTTP on a local server when they are on the local network or over VPN and HTTP on a public server we manage when they are on internet.

When over internet, no RMS connection to the central server, just the way to download update files to be up to date.

In the updating policy on the central server, I set Primary server http://InternalServer and http://NetServer for the secondary.

On the client, these 2 paths are automatically set to internalserver/.../S001... and http://NetServer/CIDs/S001/...

Problem is for the second one : this internet server publish the good package but not to this http path ! and moreover not the S001 !

How can I force a path without having the automatic /CIDs/S001 added ?

Thanks in advance,

Regards

:9527


This thread was automatically locked due to age.
  • 0

    Hello Xt,

    you can't change the part below the "update point" - it is set to CIDs\Snnn\productfolder depending on the subscription. Where does your secondary server get the updates from (and why has it a different sequence and not S001)?

    Christian

    :9545
  • 0

    Hello,

    the secondary server is from another part of the enteprise, so used for other clients => S00x is not linked to the same package as mine. This server takes updates from another one in this branch.

    The only solution I found is to use the Recommended because always set to S0000.

    Hope Sophos will update the policy  behaviour in the next version to have the possibility to set an updating server as we want...

    Regards

    :9591
  • 0

    Hope Sophos will update the policy  behaviour in the next version to have the possibility to set an updating server as we want

    I doubt this as this was only introduced with SEC4.0. While it is not enforced the idea is that the clients update from the "same" source, i.e. the same SUM hierachy (note that you also get the may not contain the selected software subscription warning). Updating from different hierarchies can cause the clients to "oscillate" between two versions.

    Christian

    :9595
Unfiltered HTML