MS Windows NT 4.0 Resource Kit Year 2000 Updates

  • Article
Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Updated : October 1, 1999

Certain tools comprising the Windows NT4 Resource Kit Tools Supplement 2 were tested for year 2000 issues. Those tools comprising the Windows NT4 Resource Kit Tools Supplement 2 that were tested for year 2000 date related issues are identified below. The tools that have known year 2000 issues are identified below.

Following these, is a table of tools (Table A), that where tested and no year 2000 date related issues were identified at the conclusion of the year 2000 testing.

TOOLS WITH IDENTIFIED YEAR 2000 ISSUES

Available Updates for Windows NT Resource Kit:

This sample file is only available from the TechNet CD product.

Windows NT 4 Resource Kit Tools Module Exception Status

ForFiles.Exe

FORFILES.exe treats 2-digit dates as follows: 00 through 79 are assumed in the year 2000; 81 through 99 are assumed in the year 1900 and 80 does not produce any output.

The FORFILES.exe allows a single digit year entry and then treats that entry as a year in the 1900s. It does not allow 4-digit dates to be entered.

Logtime.Exe

Logtime.exe logs dates using 2 digits for the year. It is up to the consumer of the logged time to interpret it correctly.

TimeServ

The Windows NT Resource Kit Time service supports a number of different methods for obtaining the correct time. Some of these solutions are hardware based (GPS-based expansion cards, radio clocks, etc.) while others are software based (dial-up or NTP connection to a service such as USNO or NIST, Lanman within the network – as Primary and Secondary). Due to the lack of hardware availability, Microsoft cannot test the support for the hardware based solutions and therefore cannot comment on their Y2K compliance. Microsoft has tested the network-based synchronization (NTP and Lanman) and no year 2000 date related issues were identified at the conclusion of the year 2000 testing. Microsoft cannot explicitly test the dial-up support for the various Time Service providers. Based on our code review, there was no readily identifiable date dependent functionality in this portion of the application. The USNO and NIST (ACTS) return ASCII strings based on UTC Time. Neither the generation of these strings nor the handling of these stings by TimeServ revealed year 2000 date related issues at the conclusion of the year 2000 testing. Microsoft cannot test year 2000 date related issues for the numerous supported Time Service Providers (e.g. USNO, NIST, ACTS) or the numerous modems that may be in use. Microsoft recommends that customers perform their own testing of TimeServ in their environment and contact the Time Service Providers they are using to determine their year 2000 Compliance.

It should also be noted that, after the first successful synchronization, TimeServ will not replicate a Time/Date that is more than a 12 hour variation from the current time. This is to prevent an erroneous time propagating through the network.

Earlier in 1999, before TimeServ testing had been completed, Microsoft had made a version of W32Time available (above) for customers to use instead of TimeServ. W32Time is the time service that will be included as part of Windows 2000. It was modified to work with Windows NT 4.0 and made available for customers. This was done because of the complexities of TimeServ hardware support and the fact that Microsoft cannot test all of TimeServ. W32Time only supports the NTP/Lanman synchronization method. No year 2000 date related issues were identified at the conclusion of the year 2000 testing the NTP/Lanman synchronization used by TimeServ and that used by W32Time.

Customers who have deployed W32Time are recommended to continue using W32Time. An updated version of W32Time has recently been made available to address several customer reported, non-year 2000 related issues. Customers who are experiencing any of these issues should update their version of W32Time above.

A Note Regarding Platform Support and Interoperability: It should be noted that TimeServ can be used on Windows NT 3.51 and Windows NT 4.0. It should also be noted that our testing coverage of W32Time and TimeServ also included interoperability testing with both tools acting as both server and client.

In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain W32Time for NT4 as compliant through January 1, 2001. Additionally, Microsoft intends to maintain the tested portions of TimeServ as compliant through January 1, 2001.

WINAT has a known year 2000 issue that is addressed by Windows NT Service Pack 5.

KixStart has not been tested for year 2000 date related issues. At this time Microsoft has no plans to test these applications.

REXX has not been tested for year 2000 date related issues. At this time Microsoft has no plans to test this application. Microsoft is aware of one issue in the REXX application. The DATE("U") function within REXX operates using an offset from 1900. For example, if the system date is set to 09/27/2004, the function will return 09/27/104. At this time, Microsoft has no plans to make any updates to this application. Customers should evaluate their use of this function within REXX and ensure proper use of the function.

Applications in APPS folder have not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

Applications in PERL folder have not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

Applications in POSIX folder have not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

Public Domain software in the SOURCE\GNU folder has not been tested for Year 2000 date related issues. At this time Microsoft has no plans to test these applications.

TABLE A: Windows NT 4 Resource Kit Tools Tested

No year 2000 date related issues were identified at the conclusion of the year 2000 testing of the following NT4 Resource Kit tools.

ADDUSERS.EXE

DRIVERS.EXE

NETDOM.EXE

RCONMODE.EXE

SNMPUTIL.EXE

ANIEDIT.EXE

DSKPROBE.EXE

NETSVC.EXE

RCONSTAT.EXE

SOON.EXE

APIMON.EXE

DUMPEL.EXE

NETWATCH.EXE

RCONSVC.EXE

SRVANY.EXE

ASSOCIATE.EXE

EM2MS.EXE

NLMON.EXE

RCRUNCMD.EXE

SRVCHECK.EXE

ATANLYZR.EXE

EMPTY.EXE

NLTEST.EXE

REG.EXE

SRVINFO.EXE

AUDITPOL.EXE

EMPTY.EXE

NOW.EXE

REGBACK.EXE

SRVINSTW.EXE

AUTOEXNT.EXE

ENUMPRN.EXE

NTIMER.EXE

REGDMP.EXE

SRVMON.EXE

AUTOLOG.EXE

EXCTRLST.EXE

NTRIGHTS.EXE

REGFIND.EXE

SU.EXE

BREAKFTM.EXE

EXCTRLST.EXE

NTUUCODE.EXE

REGINI.EXE

SUBINACL.EXE

BROWMON.EXE

EXETYPE.EXE

OH.EXE

REGKEY.EXE

SUSS.EXE

BROWSTAT.EXE

EXPNDW32.EXE

OLEVIEW.EXE

REGREST.EXE

SYSDIFF.EXE

C2CONFIG.EXE

FILEVER.EXE

PASSPROP.EXE

REMOTE.EXE

TDISHOW.EXE

CCDIST.EXE

FINDGRP.EXE

PATHMAN.EXE

RKILL.EXE

TELNETD.EXE

CCDIST35.EXE

FIXACLS.EXE

PDLCNFIG.EXE

RKILLSRV.EXE

TEXTVIEW.EXE

CHOICE.EXE

FLOPLOCK.EXE

PDLSVC.EXE

RMTSHARE.EXE

TIMEOUT.EXE

CLEARMEM.EXE

FREEDISK.EXE

PDUMP.EXE

ROBOCOPY.EXE

TIMETHIS.EXE

CLEARMEM.EXE

FTEDIT.EXE

PERF2MIB.EXE

RSHSETUP.EXE

TLIST.EXE

CLIP.EXE

GETMAC.EXE

PERFMTR.EXE

RSHSVC.EXE

TLIST.EXE

CLIPSTOR.EXE

GETSID.EXE

PERFMTR.EXE

RSMSVC.EXE

TLOCMGR.EXE

COMPREG.EXE

GFLAGS.EXE

PERMCOPY.EXE

SC.EXE

TOP.EXE

COMPRESS.EXE

GLOBAL.EXE

PERMS.EXE

SCANREG.EXE

TOPDESK.EXE

CPUSTRES.EXE

GRPCPY.EXE

PFMON.EXE

SCLIST.EXE

TOTLPROC.EXE

CPUSTRES.EXE

HEAPMON.EXE

PFMON.EXE

SCOPY.EXE

TRANSLATE.EXE

CREATFIL.EXE

IFMEMBER.EXE

PMON.EXE

SECADD.EXE

TZEDIT.EXE

CREATFIL.EXE

IMAGEDIT.EXE

PMON.EXE

SECEDIT.EXE

UNDOINST.EXE

CTRLIST.EXE

INET.EXE

PPERF.EXE

SETEDIT.EXE

UPTOMP.EXE

CTRLIST.EXE

INSTALER.EXE

PROBE.EXE

SETEDIT.EXE

USRSTAT.EXE

DATALOG.EXE

INSTEXNT.EXE

PROBEPRC.EXE

SETUPMGR.EXE

USRTOGRP.EXE

DATALOG.EXE

INSTSRV.EXE

PROFILE.EXE

SETX.EXE

VADUMP.EXE

DEFPTR.EXE

KERNPROF.EXE

PSTAT.EXE

SHORTCUT.EXE

VDESK.EXE

DELPROF.EXE

KILL.EXE

PSTAT.EXE

SHOWACLS.EXE

WAIT.EXE

DELSRV.EXE

KILL.EXE

PULIST.EXE

SHOWDISK.EXE

WAIT.EXE

DEPENDS.EXE

LEAKYAPP.EXE

PVIEW.EXE

SHOWGRPS.EXE

WAITFOR.EXE

DESKTOPS.EXE

LEAKYAPP.EXE

PVIEW.EXE

SHOWINST.EXE

WHOAMI.EXE

DFLYDIST.EXE

LINKCK.EXE

PVIEWER.EXE

SHOWMBRS.EXE

WINDIFF.EXE

DH.EXE

LOCAL.EXE

PVIEWER.EXE

SHOWPERF.EXE

WINMSDP.EXE

DHCPCMD.EXE

LOGEVENT.EXE

QSLICE.EXE

SHOWPERF.EXE

WINSCHK.EXE

DHCPLOC.EXE

LOGOFF.EXE

QUICKRES.EXE

SHUTDOWN.EXE

WINSCL.EXE

DIRUSE.EXE

MIBCC.EXE

RASLIST.EXE

SHUTGUI.EXE

WINSDMP.EXE

DISKMAP.EXE

MONITOR.EXE

RASUSERS.EXE

SIPANEL.EXE

WNTIPCFG.EXE

DISKSAVE.EXE

MONITOR.EXE

RCLIENT.EXE

SLEEP.EXE

WPERF.EXE

DISKUSE.EXE

MUNGE.EXE

RCMD.EXE

SMCONFIG.EXE

WRKILL.EXE

DNSCMD.EXE

NETCLIP.EXE

RCMDSVC.EXE

SNMPMON.EXE

XCACLS.EXE

DOMMON.EXE

NETCONS.EXE

RCONGRP.EXE

 

 

DRIVERS.EXE