In order to get around the whole hidden passwords thing for Cisco ASAs I've modified my template to run "more system:running-config" instead. This, however, causes problems for the startup config as you can't run "more system:startup-config". I got around that by creating a daily job that writes both the startup and running configs to the flash, then I updated my template to just pull them from flash.
This works great for getting both startup and running configs, but when trying to integrate RTCD it causes more problems. The reason is because once NCM finds out about a change from a syslog message, it pulls the config the way it normally does, which is the backed up config on the flash, i.e. not the most current copy. It then compares the new config with what it has on file and of course finds no changes because the config it pulled is out of date.
Does anybody have a solution for this? I'd like to have both startup and running configs managed by NCM in addition to RTCD. I've thought about using TFTP, but I'd like to avoid that if possible.