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

UpdateMgr will not connect after W2003 to W2012 R2 SEC 5.2.2 migration

Brown-Bear

I have migrated my SEC 5.2.2 from Win 2003 to Win 2012 R2 by following the Server to server migration guide.

All went fine. However when i setup the new SUM and put "Sophos" in as the source with the username and password which are valid I keep getting a message about a "timeout while connecting to the specified address (Sophos) and that there may be a problem with the network2 which there is not.

Also while my pc continues to update it is still looking at the old server and I tried to re-protect my clients within the console and all are waiting on a "policy update" so i guess they are still looking at the old server.

Any one got any ideas? I followed the guide exactly but couldn't find any files that required editing in the registry (my win 2003 was x86 bit and win 2012 is x64) in section 8 of the guide after completing the "Merge" by right clicking the CertificationManager.reg.

Thanks all.



This thread was automatically locked due to age.
  • 0

    OK quick update. I have verified that my PC and assume all PC's are still looking at the old Server.

    So I downloaded the Sophos Endpoint Migration Utility which was mentioned on various forums - however when I run it to update the location of cac.perm and mrinit.conf and point it to the default \\New-server\SophosUpdate folder there is no files there.

    Thanks if anyone has any ideas.

Unfiltered HTML