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

Clients cannot AutoUpdate - New Primary Server

Eggy

I'm looking to roll out Sophos Endpoint Security to 700 + clients in a school. The problem is that many of these clients already have Sophos Endpoint Security installed from a now defunct server. They are looking to autoupdate from the old server and we now have a new AutoUpdate server and Enterprise Console. When I try and manage these machines from the new server it fails. If I log on to one of these machines I have to cancel the autoupdate and uninstall Sophos and reinstall manually (it won't deploy from Enterprise Console). It would appear that because the clients are looking to autoupdate from a now invalid source, they won't listen to anything else. Any ideas?

:6641


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

    Hello Eggy,

    if your new server doesn't use the same certificates as the old one the management system on the clients (RMS) will refuse to talk to the new server. So these clients constitute a "foreign site" - how to take it over has been discussed .

    Deployment from SEC should be possible once you have uninstalled (but watch for a remaining mrinit.conf.orig in the Sophos\Remote Management System\ folder).

    There are many ways to make it work and it depends on what tools you have available for running scripts on the workstations.

    Christian

    :6671
Reply
  • 0

    Hello Eggy,

    if your new server doesn't use the same certificates as the old one the management system on the clients (RMS) will refuse to talk to the new server. So these clients constitute a "foreign site" - how to take it over has been discussed .

    Deployment from SEC should be possible once you have uninstalled (but watch for a remaining mrinit.conf.orig in the Sophos\Remote Management System\ folder).

    There are many ways to make it work and it depends on what tools you have available for running scripts on the workstations.

    Christian

    :6671
Children
No Data
Unfiltered HTML