If you have mistakingly configured the wrong timezone in Cisco ACS during the build, and are concerned about changing the timezone in a production environment – you should be!
I attempted this on ACS 5.8, only to spend a few hours restoring the server. My second attempt however, after conversing with TAC, went a lot smoother.
My recipe for a smooth change was as follows;;
– Deregister and remove ACS from Active Directory in the GUI
– Stop ACS Services “application stop ACS”
– Reboot the server “reload”
– Re-register ACS to Active Directory in the GUI
According to Cisco TAC, you could get database corruption if you maintain the link to Active Directory when you change the time, or if you do with the services still running.