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

Upgrading enterprise console from 5.1.0 to 5.2.2 with 2 update managers

khey

Hi guys,

I am thinking of  upgrading the enterprise console from 5.10. to 5.2.2 and currently we have 2 update managers.

update manager A handles about 400 Pcs

update manager B handles about 100 Pcs

Is there a specific way or order in upgrading them? do I have to stop the service while doing the upgrade?

Also whats the chance that the upgrade will affect the Anti-virus and HIPS policies? for example, resetting it to default?

please advise.

Thank you.

:52713


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

    Hello khey,

    you upgrade just the management server, there's nothing to do for the SUMs.

    whats the chance that the upgrade will affect the Anti-virus and HIPS policies

    The policies are stored in the database. The database upgrade will either succeed or fail, in which case you will end up with an initialized and practically empty database - no endpoints, no groups, no policies except the defaults. You'd then retry the upgrade, perhaps manually (while the upgrade doesn't modify the "old" database you should back it up before upgrading - and you should regularly back up anyway). As for the chance, it's small though you might be one of the (un)lucky ones - but what's the alternative, wait for 5.3? Don't think this would reduce the risk.

    Christian

    :52717
Reply
  • 0

    Hello khey,

    you upgrade just the management server, there's nothing to do for the SUMs.

    whats the chance that the upgrade will affect the Anti-virus and HIPS policies

    The policies are stored in the database. The database upgrade will either succeed or fail, in which case you will end up with an initialized and practically empty database - no endpoints, no groups, no policies except the defaults. You'd then retry the upgrade, perhaps manually (while the upgrade doesn't modify the "old" database you should back it up before upgrading - and you should regularly back up anyway). As for the chance, it's small though you might be one of the (un)lucky ones - but what's the alternative, wait for 5.3? Don't think this would reduce the risk.

    Christian

    :52717
Children
No Data