I have a four node failover cluster.
Our thought was, even though we are running Standard Edition, that if we failover Reporting Services we could just use RSKeyMgmt.exe to remove the key and restore the "real" one.
This seemed to have worked in early testing.
Now when we fail over we see four different keys using the -L parameter.
The -R switch sometimes removes an entry but when we try and remove another all four are there again.
I have even tried deleting the entries from the Keys table itslef but they automagically reappear.
Even after deleting numerous times via SQL when I run Reporting Services Configuration Manager and run through Database Setup all goes well except for a warning on:
Setting Connection Info for Reporting Server
You specified a connection to a report server database that contains encryption keys for another report server. If you are configuring a scale-out deployment, that feature is not supported by this edition of Reporting Services. If you want to use this report server database with the current report server instance, remove the existing encryption keys first.
The worst part of all this is that the instance had failed over for maintenance reboots and then been failed baack. It is actually running on the same physical node it has been on for the last year.
Any suggestions out there?