Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 8401 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

SEC 5.2 Upgrade - Update Subscriptions

Jonathan_IT

I'm looking at the SEC 5.2 Upgrade Guide and it shows on page 9 (section 7) that certain Software Package subscriptions will be changing or should be set before doing upgrade such as recommended, previous, oldest, etc. It doesn't mention preview at all. If I have most of environment set to preview since the Large April 15 Update has not rolled out as our Recommended yet then can I still upgrade SEC or do I need to wait until I can change all to Recommended? (They are all Preview because we had to slowly roll out after hours in advance.)

:49250


This thread was automatically locked due to age.
Parents
  • 0
    Hello Jonathan_IT,

    (usual "BTW": updates are never pushed, they are fetched; only policies are "pushed")
    A database/console upgrade doesn't change existing configurations or policies. An endpoint doesn't see any changes afterwards.

    I too am still on 10.3.1 for Recommended so I guess 10.3.7 is running late for whatever reason - you should have at least one month to revert from Preview to Recommended after the actual change.

    Christian
    :49370
Reply
  • 0
    Hello Jonathan_IT,

    (usual "BTW": updates are never pushed, they are fetched; only policies are "pushed")
    A database/console upgrade doesn't change existing configurations or policies. An endpoint doesn't see any changes afterwards.

    I too am still on 10.3.1 for Recommended so I guess 10.3.7 is running late for whatever reason - you should have at least one month to revert from Preview to Recommended after the actual change.

    Christian
    :49370
Children
No Data