Hello Gary,

I am responsible for all of your user's being restored in upper
case. Our version 2 client has that PER APAR fix. However,
I'm a little unclear on the current NDS restore problem. Can
you append here (or send to me offline) the details. If it's
an NDS problem that we or Novell is not aware of, we need to
fix it ASAP.


Thanks,
Frank Ramke

>>>>
When server xxxx  was restored after last year's crash, ADSM restored the
NDS while converting all lower-case object entries to uppercase.  Users
logging in at DOT could not gain access to their Midas application because
NOS passes %LOGIN_NAME to DOS for perimeter access processing.  It failed.
Only after re-doing the Midas security system (all users) were they able to
go back to work.

Recently, ADSM flunked the restoration test again by disallowing the
deletion of a user object in container xxxx.  This damaged NDS
structure is in production, left to be re-discovered by the ADSM authors or
whomever else chooses to look .....

I have the distinct impression that Netware (or maybe Westchester County) is
being used as a beta test site ....

Thus, since ADSM, as installed, can still damage Netware Directory Services,
it is not clear to me that this product is a viable alternative to
standalone backup solutions.
>>>>