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 Enterprise Console 4.0 from one server to another.

Our SOPHOS server is being retired and I am trying to move Enterprise Console to a new server.  However, there is very sparse information in the knowledge base or the forums on exactly how to do this.  It has been a real struggle getting this to work and phone support isn't much help.  They told me I just need to reinstall EC4.0 on the new server and the computers will be picked up again.

The Macs were picked up but they are not updating and the PCs are greyed our and require me to reinstall the client again in order to be picked up. 

Why is there no support or documentation for this?  Does it not occur to anyone in SOPHOS that someone would need to do this?

:2740


This thread was automatically locked due to age.
Parents
  • Phone support told me not to export/import database

    Hmm ... then you started with your new server from scratch (already running SUM-only as you didn't mention EM Library)? And you had to re-create all your policies? The backup/restore should work (but not necessarily with exactly the same parameters - if for example you use a different SQL instance).

    While the clients report to the new server and magically appear they should all be in the Unassigned group. I have no clue why they don't report their status or SEC doesn't pick it up. But that seems to be the problem. As I have once in a while a client which "appears" on a management server (a client is "moved" into or out from a domain) I can attest that it reports it's complete state.

    I'd say you have two options:

    1. Find out why the clients do not report correctly although they connect to the management server
    2. Reprotect the clients

    Things you could check or try:

    • On SEC: what's on the Update details tab for the clients, in particular the columns Updating policy and Primary server?
    • On a Mac client: what does the autoupdate log say? Can you open the update location from a Mac (there might be a permission or network/share issue)
    • Windows: debugging the management system is not a simple thing. If you are able to protect the clients from the console and they then report correctly it's still some work but perhaps the least effort.

    HTH

    Christian

    :2774
Reply
  • Phone support told me not to export/import database

    Hmm ... then you started with your new server from scratch (already running SUM-only as you didn't mention EM Library)? And you had to re-create all your policies? The backup/restore should work (but not necessarily with exactly the same parameters - if for example you use a different SQL instance).

    While the clients report to the new server and magically appear they should all be in the Unassigned group. I have no clue why they don't report their status or SEC doesn't pick it up. But that seems to be the problem. As I have once in a while a client which "appears" on a management server (a client is "moved" into or out from a domain) I can attest that it reports it's complete state.

    I'd say you have two options:

    1. Find out why the clients do not report correctly although they connect to the management server
    2. Reprotect the clients

    Things you could check or try:

    • On SEC: what's on the Update details tab for the clients, in particular the columns Updating policy and Primary server?
    • On a Mac client: what does the autoupdate log say? Can you open the update location from a Mac (there might be a permission or network/share issue)
    • Windows: debugging the management system is not a simple thing. If you are able to protect the clients from the console and they then report correctly it's still some work but perhaps the least effort.

    HTH

    Christian

    :2774
Children
No Data