[prev in list] [next in list] [prev in thread] [next in thread] 

List:       novell
Subject:    Re: Year 2000
From:       "Cobb, Bryan" <bcobb () BURKE ! COM>
Date:       1999-07-29 12:20:40
[Download RAW message or body]

Thanks Joe...We still want to test our systems here to make sure nothing
goofy is going to happen come Year 2000.  Not that we don't trust Novell,
but it's better to be safe than sorry.  Plus rolling your server forward
tests all 3rd party apps that you have running ON the Novell server, plus
apps that get their time from the Novell server.  From what I gather from
Novell (I read their "Novell Year 2000 Test Guide"), DO IT IN A TEST
ENVIRONMENT.

Thanks again for the responses...

- Bryan M Cobb
Network Engineer
Burke, Inc. - Cincinnati OH
Phone:  (513)684-7526
    Fax:  (513)684-4981

-----Original Message-----
From: Joe Acquisto [mailto:ACQUISTJ@LAN.NEWPALTZ.EDU]
Sent: Wednesday, July 28, 1999 4:48 PM
Subject: Re: Year 2000


Given that DOS 6.22 is reported to be y2k, and Novell posts the y2k
compliance of it's stuff, that should be enough in that area.  The only
area of concern is the H/W, RTC.  And then only when the server needs to
reboot.

There are y2k test programs that will test the RTC and DOS.  They are
at various places on the net.  I can post the one I've used or post in
for download.  Or, I can give it to the One Who Remains Silent.

Basically, I would down the server, boot to DOS and run this program to
test the RTC's ability to handle the y2k issues.  This requires a reboot
or two, so make sure your autoexec.bat is renamed or altered to NOT
start the server.

After it passes, check the RTC time, to make sure it is within a few
minutes of what it would have been without this fooling around and
restart the server.

But, even if the server does not pass this test,  I hazard a guess that
it is only an issue if the server needs to restart after y2k.  Certainly
that is reasonable to expect.   So, if I could not replace the server, I
would just make sure that the autoexec.bat stops with all kinds of
warnings, threats, etc., to manually check the date/time, and forces the
operator to run server.exe manually.  You can even put time and date
commands in autoexec.bat to make it really easy.  Course that will only
work if the RTC can handle the dates after being manaully set.  But if
yours can't, then you really, REALLY, need to update your h/w.

This still might not be a reasonable solution for places that use
sntpcl4 or some other program that purports to mess with the RTC to help
in timekeeping.  Then a ny2k RTC might provide . . . excitement.

-----------------------------------------
Joe Acquisto
SUNY New Paltz
914-257-3134 (V)
914-257-6900 (F)
--------------------------------------------

>>> "Cobb, Bryan" <bcobb@BURKE.COM> 07/28/99 02:01PM >>>
Does anyone know of any products or a way to roll my Novell  servers
over to
the Year 2000 for testing purposes.  I will be running NW5.0 on all of
these
servers by the time I want to do this  (I have two 4.11's and one 5.0
now).
I know this is very dangerous (even crazy) with NDS.  I am getting
pressure
from management to test this out though.  Should this even be tempted?

What is everyone else doing to test for Y2K.  (Yes..I have already
"Ferret"
tested OK).   We want the "real deal" though.  I would rather not have
to
set up a testing environment, but if that's what I have to do, then so
be
it.

Anyone else???

- Bryan M Cobb
Network Engineer
Burke, Inc. - Cincinnati OH
Phone:  (513)684-7526
    Fax:  (513)684-4981

[prev in list] [next in list] [prev in thread] [next in thread]