I am recently supporting an application that can be classified a 'rules engine' and the developers and business rely on testing scenarios whereby it is required to move the date to the future. Once that occurs, anyone is pretty much prevented from accessing the server remotely, as kerberos authentication blocks due to out of sychronization with system time(I think 5 minutes off).
Has anyone been exposed to this scenario (rolling dates forward, and back on server), and what are some of the negatives in doing so in regard to SQL Server ? It makes job history difficult to dicipher, but I also wonder what negatives from an engine it may have. i.e., if windows patches applied, group policy, txn log history...
Thanks