Does MiCollab system name change require a reboot?

[mszodiac]

Hi Everyone.  Can anyone confirm if changing the system name of MiCollab 6.0 require a reboot -and more?

My colleague somehow recalls doing the following when he changed the system name.

-backup critical data/configuration
- delete VM
- rebuild VM with correct system name
- import backup data

Thank you!

[martyn]

All that is needed is a backup before hand (for good measure), and then you can change the name via the CLI server console (select option 2, and then only change the name of the server and nothing else).
A reboot will be required after the name change. This will also re-generate any certificates, so if you currently have a signed SSL cert then you will need to update that, or if you are distributing the self-signed cert in to trust stores then you will need to update that as well via your method of deployment (GPO for example).

[mszodiac]

Thanks martyn!