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

Upgrade Enterprise Console

Joetobai

Hi all,

I'm currrently running EC 5.1.0 on Windows 2003 Server. I'm thinking of moving EC onto a new Windows 2008 Server. Any advice/tips

Thanks

:36619


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

    Hello Joetobai,

    first you'd have to decide what to do with your second SUM. Does it provide the primary update location for a part of your clients and what's its source location - Sophos or the master server?

    If you use the same "identity" for the new server (certificates and IP/name) you naturally can't run them in parallel. While there is no change required on the clients they won't be able to update during the migration (unless they have Sophos as Secondary update location).

    If you you use the same certificate you can "move" the clients to the new server by pointing them to the new update location (you'd have to configure the CID with the appropriate mrinit.conf) but an extra step is required if using Patch. The usual method (which also works if the certificates are different) is re-protecting the clients, running setup.exe or employ the migration utility Jak has mentioned.

    Whether you import the database on the new server or start with an empty one you'll lose (at least some of) the clients' history with a parallel approach.

    Christian

    :36635
Reply
  • 0

    Hello Joetobai,

    first you'd have to decide what to do with your second SUM. Does it provide the primary update location for a part of your clients and what's its source location - Sophos or the master server?

    If you use the same "identity" for the new server (certificates and IP/name) you naturally can't run them in parallel. While there is no change required on the clients they won't be able to update during the migration (unless they have Sophos as Secondary update location).

    If you you use the same certificate you can "move" the clients to the new server by pointing them to the new update location (you'd have to configure the CID with the appropriate mrinit.conf) but an extra step is required if using Patch. The usual method (which also works if the certificates are different) is re-protecting the clients, running setup.exe or employ the migration utility Jak has mentioned.

    Whether you import the database on the new server or start with an empty one you'll lose (at least some of) the clients' history with a parallel approach.

    Christian

    :36635
Children
No Data