Microsoft KB Archive/246568

From BetaArchive Wiki
Knowledge Base

Changing System Dates In Production Environments

Article ID: 246568

Article Last Modified on 1/25/2007


  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows 95
  • Microsoft Windows 98 Standard Edition
  • Microsoft Windows 98 Second Edition

This article was previously published under Q246568


Microsoft does not recommend or support the changing of system dates for test purposes (such as year 2000 testing) in a production environment.

Potential data integrity problems can result from performing this action.


Changing the system date to a date other than the current date in a production environment, followed by rolling back to the correct date, can have a serious impact on the integrity of program data as well as operating system functions.

This action can affect service functions that are date sensitive, such as DHCP leases and WINS registrations, and can also invalidate program data that is processed during the period that the date is incorrect.

Some of the known issues related to changing the system date are discussed in the following Microsoft Knowledge Base articles. Potential problems may not be limited to those problems discussed in the following articles. The effects of setting the system date to an invalid date are not entirely predictable.

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

244703 XGEN: Advancing and Rolling Back System Time Clock for Y2K Test

242502 Domain Logon List Is Not Updated

Keywords: kbenv kbinfo KB246568