Testing time sensitive issues

[Carl]

We have an applicaiton running on a win2k member TEST server with a sql
database. We want to test the impact on the application of date changes by
moving the system time ahead a month. Testing is expected to continue for
two weeks. We don't want to move the entire domain time structure ahead,
just this server. At the end of the two weeks, we'll blow away this server.

I have a feeling other folks have run into this issue. Any suggestions?

 

[Chris White]

Have you tried disabling the "Windows Time" (W32Time) service?

 

[Carl]

No.
My next thought was to either disable the time service as you suggest or
change the timeserver this server uses to itself (instead of the domain
controller) by:
NET TIME /SETSNTP:localserver.

But, in either case, I believe users will lose rights to logon to services
on this server?

Correct?

 

[Chris White]

I think I may not understand your entire objective... But, essentially, I
believe that if you disable the time service, it should not effect any other
services. The only repercussion should be that users will not be able to
use that server as a time sync. server.