[simon hornby]

Resetting SIC does not require a reboot of the module, but it does require a restart of the cp processes on the module. Because it no longer trusts the source that it got the old policy from (that's what resetting SIC does), it will load the default, called InitialPolicy. You should be able to establish trust with a module in this situation, because the InitialPolicy does not block SIC traffic, but a fw unloadlocal from the command line will let you talk to it anyway, i there is a problem.

You should make sure it has TCP/Ip conenctivity to the new management station before doing this.

Once you have reset SIC on the module, you should be able to initialise it with the new management station and then push the policy to the firewall. Downtime is minimised by creating the policy on the new SmartCenter before you start, obviously.