COMMAND

    Y2K

SYSTEMS AFFECTED

    Win NT

PROBLEM

    Steve Kastl posted following.  During Y2K testing with Windows  NT
    Server 4.0 (SP3) he came across this problem:

		THE YEAR 2000 IS A LEAP YEAR

    Using User Manager for Domains, try to set an account to expire on
    2-29-2000.  You  will get an  error message "February  only has 28
    days in  this year."   If you  try set  the account  expiration to
    2-29-2002 you  will get  the same  error.   If you  try to set the
    account expiration to 2-29-2004 and you will success.

    This is not  security bug, but  it is a  serious error.   For some
    reason, MS  is not  using a  correct date  calculation method when
    UsrMgr performs its  error checking (or  has an even  more serious
    problem w/ UsrMgr interpreting the date).

SOLUTION

    This problem will  be fixed in  SP4.  hotfix  is available.   This
    fix should have the following time stamp:

        09/10/97 11:44a 295,184 Netui2.dll (Intel)
        09/10/97 11:42a 528,656 Netui2.dll (Alpha)

    For those who don't know rules for leap years, read on.  The three
    rules which the Gregorian calendar uses to determine leap year are
    as follows:

        1. Years divisible by four are leap years, unless...
        2. Years also divisible by 100 are not leap years, except...
        3. Years divisible by 400 are leap years.

    Therefore, the year 2000 is  a leap year according to  rule number
    three.



More information is available from the following Knowledge
Base article:

Q175093 User Manager Does Not Recognize February 2000 As a
Leap Year