How safe/unsafe is it to make and use your own scripts to update/change the configuration for users/phones in the CCM database (given that you know sql quite well). The fields I would for example like to change are: Calling Search Space for all call forward settings, Phone Services Subscriptions, Media Resource Group and audio source for phones, External Data locations and so on.
Is there some documentation for the structure of the database that is how all the tables are linked to each other
I would personally suggest against it doing it. Anytime you do things like this you will have to at least stop the ccm service and sometimes much more to the get the changes to take effect. Is there something you want to change that BAT cannot change for you? I don't think Cisco would support this type of changes to the database directly. When you go through the tools we provide we put in certain checks in to make sure things are right for CCM to work correctly.
I think you are not able to change the CSS for any of the call forward fields, the External Data fields (Information, Directory, Messages...), the User or Network Hold Audio Source or the Media Resource Group List, External Phone Number Mask and so on.
I think I once tried to use BAT to change the Display and Description field of a group of autoregistered phones without luck. Does BAT support autoregisterd phones ?
You can make updates to any phones in the system. In BAT go to configure -> phones and in the upper right you will see Update phones. Please take a look at this because it looks like it addresses some of the things that you mentions. You basically right limited queries and updating phones like that.
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.