Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 985 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

Manage multiple Software Subscriptions for 9.5 and 9.7 rollout

DavidR

Our Sophos enterprise console has been updated to 4.7. We have one update manager that is currently updating from one Software Subscription (that is getting 9.5)
We want to roll out 9.7 in a staged manner - I figure this is done by:
    - adding a new Software Subscription set to update 9.7
    - creating a new software distribution share in the update manager
    - set the subscription to update to the new share
    - configure a new update policy and point the subscription to the new software subscription
However, when you are configuring the update manager the default distribution point of \\server\SophosUpdate is set to update, so if I have multiple distribution shares that default source is set to be updated.

This looks like having two distribution shares with different versions will conflict on updating that default share and possibly force all clients to 9.7 on the next update. Is this correct? If so how do I leave my existing distribution share with 9.5 and create a new one with 9.7 that can have the update policy changed to update the clients to 9.7?

We have a single Enterprise Console server with a single Software Subscription set to update to two shares. On the Updating policy the primary server is a http web address of publicdnsname/SophosUpdate and in IIS the SophosUpdate URL is pointing to the default C:\ProgramData\Sophos\Update Manager\Update Manager\  

Am I correct in the way to roll out to 9.7? If I add a new Software Subscription and add it to our Update Manager Distribution will it update the default SophosUpdate to 9.7 thus upgrading all clients to 9.7 on their next update? If so what's the best way to set up a new segregated 9.7 install so I can roll out the new version via Updating policy?

:13703


This thread was automatically locked due to age.
  • 0

    Hi,

    For each product that makes up a subscription SUM will create a Sxxx sub directory in the same SophosUpdate share by default.

    The view bootstrap locations in SEC will show you what you have to date.  So if you create a new subscription, e.g. SAV97 and choose SAV 9.7 as a product from the list available, it will create a new Sxxx directory in the SophosUpdate share.  If you look in the updating policies in SEC that the clients use, you can see the subscription tab.  So all the clients will continue to update from the original location. They would only change if you updated your existing subscription.

    The update location the clients get through policy in effect comprises of 2 components, the Update Share path, e.g. "\\server\Sophosupdate\" and the Subscription part.  The Subscription is essentially the "\CIDs\Sxxx\savscfxp\" bit.

    Regards,

    Jak

    :13733