See above. I'd like to be able to automate this if possible.
This thread was automatically locked due to age.
Hello jcerio,
only on Windows RMS can be reconfigured without uninstall and reinstall.
Configuring a Mac OS S X CID to use a Message Relay suggests that RMS in 9.4+ will apply changes to mrinit.custom and thus talk to a new console - provided the certificates have been exported/imported during migration (and the endpoints are still updating, i.e. don't already need a new updating policy). Sophos for Mac OS X is already available in the Preview subscription.
What exactly comprises new console? If you've preserved the certificates it might - depending on the contents of your mrinit.conf - be possible to work (temporarily) with a DNS alias. mrinit.conf normally contains IPv4,IPv6,FQDN,NetBIOS (please see 120296 and 120396 for details on RMS). If you create the old FQDN as an alias for your new server your endpoints. BTW - an alias works for the update locations as well.
Christian
Hello jcerio,
only on Windows RMS can be reconfigured without uninstall and reinstall.
Configuring a Mac OS S X CID to use a Message Relay suggests that RMS in 9.4+ will apply changes to mrinit.custom and thus talk to a new console - provided the certificates have been exported/imported during migration (and the endpoints are still updating, i.e. don't already need a new updating policy). Sophos for Mac OS X is already available in the Preview subscription.
What exactly comprises new console? If you've preserved the certificates it might - depending on the contents of your mrinit.conf - be possible to work (temporarily) with a DNS alias. mrinit.conf normally contains IPv4,IPv6,FQDN,NetBIOS (please see 120296 and 120396 for details on RMS). If you create the old FQDN as an alias for your new server your endpoints. BTW - an alias works for the update locations as well.
Christian