You delete that registration, and re-add it using the hostname instead of using the default local registration.
Right-click on the (local) entry and click "Delete SQL Server Registration". Then right-click on the SQL Server Group and click "New SQL Server Registration". Enter your CallManager's hostname if you need to, but it should be present already in a list you can pick from. Use Windows authentication, and choose to add it to your existing group.
Does recreating the registration in any way effect a production Callmanager? I have a subscriber CM that has been offline for some time ... in re-establishing the subscription I realized the "(local)" registration and need to fix. I need to confirm that the active Callmanager will not be effected. Thanks.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.