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

Moving EC 4.7 (Db on seperate server) to new server.

pm_10

Hi,

I am moving EC 4.7 to a new server with a different name, db is running on a seperate SQL server & have only been able to find information on moving the console when it is running on the same server as db, the EC system is also a primary update source for a number of endpoints & other update managers.

Apart from following the migration guide  (except for the part about backing up & restoring db) , are there any suggestions for making this as painless as possible?

Thanks,

:18703


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

    Hi,

    Before I start, just to help understand the environment, I have a few questions:

    The SEC server and the SQL server are member servers in the dame domain and the new SEC server is also a member server in the same domain?

    The new SEC server is a brand new server with no Sophos products?  It doesn't currently host a SUM or a distribution location?

    I assume that the management service is using a domain account to connect to the database, so this account can be re-used on the new server?  The account can be seen under:

    HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\EE\Management Tools\DatabaseUser

    on the management server machine.

    Do you know the password for the account the clients are using to update?  I.e the account in the updating policies.  Typically, unless you do a custom install, which I assume you must have done to perform the distributed install you have, the SophosUpdateMgr account gets created with a random password, it's better to know this accounts password for the migration so you can re-use that on the new install on the new server.  Do you have a custom account for this and know the password?

    Also, to redirect the clients, do you have a mechanism available to you to easily deploy a script to the clients, e.g. a VBScript?

    Regards,

    Jak 


     

    :18705
Reply
  • 0

    Hi,

    Before I start, just to help understand the environment, I have a few questions:

    The SEC server and the SQL server are member servers in the dame domain and the new SEC server is also a member server in the same domain?

    The new SEC server is a brand new server with no Sophos products?  It doesn't currently host a SUM or a distribution location?

    I assume that the management service is using a domain account to connect to the database, so this account can be re-used on the new server?  The account can be seen under:

    HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]\Sophos\EE\Management Tools\DatabaseUser

    on the management server machine.

    Do you know the password for the account the clients are using to update?  I.e the account in the updating policies.  Typically, unless you do a custom install, which I assume you must have done to perform the distributed install you have, the SophosUpdateMgr account gets created with a random password, it's better to know this accounts password for the migration so you can re-use that on the new install on the new server.  Do you have a custom account for this and know the password?

    Also, to redirect the clients, do you have a mechanism available to you to easily deploy a script to the clients, e.g. a VBScript?

    Regards,

    Jak 


     

    :18705
Children
No Data