Dameon,
Thanks. Used the SK you mentioned, but is is a littlie bit different for renaming a MDM server. This is what I did:
1. Log into MDM SmartConsole and edit the MDM server object at the top of the Domain lists.
2. Revoked the SIC certificate and accepted the warning.
3. Clicked OK and opened the MDM server object again so I could change the name.
4. Publish changes in MDM SmartConsole.
Now all Domains where disconnected because the certificate was revoked.
5. With SSH I performed a 'fwm sic_reset' which was successful.
6. Create a new CA with 'mdsconfig'. This was also successful.
7. Restarted all services with 'mdsstop / mdstart'.
MDM server and all Domain got up-and-running and I could could connect to all Domains with SmartConsole. It all looks good.
Performing this in my lab and SIC reset is not a concern for me. I would like to migrate a MDM server with only the Global Policies and Globale Objects. TAC told me 'migrate_global_policies' is not supported for R80.40 to R81.20 migrations, so my plan was to migrate the complete server, delete all Domains and then create them from scratch. Also we are building new VSX clusters so SIC is no problem there.
Regards,
Martijn