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

SEC - Creating subscriptions in Update Manager

Hi,


My appologies for this possibly "too" easy to answer question but I'm new to Sophos.

I'm trying to create a subscription on a fresh install of SEC 4.5 via update manager. After adding it succesfully SEC tells me this:
The new software subscription "....." is not in use yet. You must configure update manager to distribute the subscribed software to a share and then configure one or more updating policies to fetch software from that share.

Can someone please tell me how to do this or point me to the specific location in a document?


Thanks

P.S.: To create poilicies is not the question, I just don't get how to link them to the subscription.

:8271


This thread was automatically locked due to age.
  • Hi,

    If you go into the SUM list view.  Double click on the SUM to bring up the configuration.  From there you can work through the tabs from left to right I would suggest.  On the tab that deals with subscriptions ensure your new subscription is on the right.  I.e. that the SUM is subscribed to use this subscription.

    In the updating policies you also select the subscription.

    Regards,

    Jak

    :8273
  • Hi Jak,


    Thanks a lot, I got that so far.
    But while editing the policy to point to the new subscription I get this:
    The primary update location may not contain the selected software subscription "...."
    Do you want to continue anyway?


    What is this about?
    Regards

    Martin

    :8275
  • HI,

    In that case, what sort of address are you putting in the Primary Update location?

    Is it one of the UNC paths the system presents/knows about or are you using a HTTP location.

    The system can only validate what it knows, the error would suggest that the path in the primary update location is not one that appears in the list of bootrap locations found in "View" - "Bootstrap Locations...".

    For example, the SUM could write out a UNC share which is shared by IIS.  So it's quite correct to add a http path that references that as the primary update path. The system however is not able to perform a lookup to check that th web share is the same as one of the distribution points it knows about so it's just a warning really in this context.

    Regards,

    Jak

    :8281
  • Hi,

    I guess I found to problem which is pretty much releated to what you say.

    Since we're having a pretty complex DMZ / DNS setup here I choose to use the IP for the UNC share to reduce complexity. I just needed to add, like you said, the IP UNC share to the subscription. The message doesn't appear anymore since then.


    Thanks a lot.
    Martin

    :8287