Developer code behavior testing; sending a transaction from a server with its clock set with a future date/time
Yes, we’re aware of the consequences of operating a domain member-server with a large time offset.
General Process flow scenario----
From a page running on an IIS-web server, a customer submits a form populated with various information. The data in this form is transmitted as xml to another server that processes it, injecting it into a database on another server.
They want to be able to change the date/time of the web-server so as to simulate a transaction at some future date/time.
Other than building a complete [sand box] I’ve suggested, disabling W32time, reset the date as desired and testing.
Anyone with experience or knowledge manipulating date/time of a server for testing in this manor, please post your insight(s).