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

slightly bodged migration

jjohnson1980

Greeings everyone.

I recently migrated my SEC4.5 installation from a 2k3 server to a new 2k8 server. Everything was going well and id followed the migration guide through. Unfortunately i got a bit over keen and removed the old server as a SUM before they did their daily contact which would have given the clients the new server settings through the ammended reinit.bat & sav.cfg files.

The clients are still trying to update to the old server which is still live and sophos is still running on it however it doesnt seem to be giving them the new server info and pointing them at it.

Is there a workaround for this or is it a reinstall from the new server?

Thanks
James

:12091


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

    Hello James,

    with the changed mrinit.conf the clients should report to the new server. Guess you did already edit the updating policies on the new server. The clients should now appear as connected and managed but not complying with the updating policy. Using Comply with you send them the new policies and from then on they should use the new CID.

    Note that RMS and updating are independent. mrinit.conf is "just" for locating the management server. The update location(s) are controlled by the updating policy. To change this without using RMS you'd export the policy on the new server (as sauconf.xml) and put this in the \sau subfolder of the old CID.

    HTH

    Christian

    :12171
Reply
  • 0

    Hello James,

    with the changed mrinit.conf the clients should report to the new server. Guess you did already edit the updating policies on the new server. The clients should now appear as connected and managed but not complying with the updating policy. Using Comply with you send them the new policies and from then on they should use the new CID.

    Note that RMS and updating are independent. mrinit.conf is "just" for locating the management server. The update location(s) are controlled by the updating policy. To change this without using RMS you'd export the policy on the new server (as sauconf.xml) and put this in the \sau subfolder of the old CID.

    HTH

    Christian

    :12171
Children
No Data
Unfiltered HTML