Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 0 subscribers
  • Views 24534 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

Enterprise Console Migration

RBGE

Hi all,

I've finally decided to bite the bullet and migrate Enterprise Console from an ancient Windows 2003 (32-bit) server to a slightly more up-to-date Windows 2008 R2 (64-bit) server, but am encountering a problem in this process.  The console is version 5.2.1 R2, and I'm following the migration guide linked to from http://www.sophos.com/en-us/support/knowledgebase/28276.aspx ( link leads to this document http://www.sophos.com/en-us/medialibrary/PDFs/documentation/sec_52_mgeng.pdf ).  The problem I'm encountering happens at point 4 of section 8 (on page 14) when attempting to restore the database to the new server.  The errors returned are in the attached text file, and contain an alarming amount of red text :smileyindifferent:

I notice it mentions the previous databases from 5.2.1 and before, which I'm not too concerned about as I just haven't removed them yet after the version upgrade, but it's not looking too promising for 5.2.1 R2 either.  Does anyone have any idea what I could be missing here?  I suspect it's something really simple which I've missed.

Many thanks for any help!

:49132


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

    Just an update here, in case anybody else finds this post at a later date and has the same problem.

    As mentioned above, things fell over (again!) when trying to migrate client machines over to the new server.  The script generated by the Endpoint Migration Utility just did not work for me, even if I had the force option selected.  While manually reprotecting each machine from the console did work, this wasn't really practical as not every machine was on-line at the time, and there are lots of machines that get taken off-site for various reasons, so wouldn't know to look at the new server.  A simple DNS alias solved this problem for me:  oldserver as an alias for newserver caused the clients to at least contact the new server, and then it was just a case of waiting for the correct configuration to be deployed.  Obviously this only works for a successful migration - it doesn't if you install a new copy of Enterprise Console on the new server and set it up from scratch.  Yes, this was one option I tried in my many attempts to get it to work :smileyindifferent:

    With regards to the local management console which wouldn't connect even after updating the settings, this was a simple case of fully uninstalling it, rebooting my machine then installing again from scratch.

    Maybe these won't help for everyone, but hopefully it should help solve some problems for anyone else experiencing the same issues I did.

    Who knows, I may even end up finding this thread when Windows 2012 goes end of life.......... :smileylol:

    :54967
Reply
  • 0

    Just an update here, in case anybody else finds this post at a later date and has the same problem.

    As mentioned above, things fell over (again!) when trying to migrate client machines over to the new server.  The script generated by the Endpoint Migration Utility just did not work for me, even if I had the force option selected.  While manually reprotecting each machine from the console did work, this wasn't really practical as not every machine was on-line at the time, and there are lots of machines that get taken off-site for various reasons, so wouldn't know to look at the new server.  A simple DNS alias solved this problem for me:  oldserver as an alias for newserver caused the clients to at least contact the new server, and then it was just a case of waiting for the correct configuration to be deployed.  Obviously this only works for a successful migration - it doesn't if you install a new copy of Enterprise Console on the new server and set it up from scratch.  Yes, this was one option I tried in my many attempts to get it to work :smileyindifferent:

    With regards to the local management console which wouldn't connect even after updating the settings, this was a simple case of fully uninstalling it, rebooting my machine then installing again from scratch.

    Maybe these won't help for everyone, but hopefully it should help solve some problems for anyone else experiencing the same issues I did.

    Who knows, I may even end up finding this thread when Windows 2012 goes end of life.......... :smileylol:

    :54967
Children
No Data
Unfiltered HTML