Patrick,

Sorry if I my initial post was confusing in describing the situation. 
(That often happens when I don't experience the problem first-hand and 
then have someone try to describe what happened to me afterwards...)

There was no user.id on the machine when the upgrade started as it is a 
brand new pc. I see that it is legitimate function of the notes client 
install- I just didn't know how the user.id file got there. 

<Snip>

Anyway, I don't know your environment, but for ours, the ID-in-the-NAB has
been labelled a "bad thing" and we never store the ID there.  If you are
using default passwords, I would recommend you do the same.  Which means,
of course, changing the default settings in the Register Person dialog.

<End Snip>

I totally agree as it appears we are using ID-in-theNAB strategy. My guess 
is the BP who did the initial install set it up this way. Gosh I love 
inheriting cans of worms.

Chris - I guess that may have been the intent of the BP too - to make our 
installs simpler.

Anyway - thanks to all for clearing this up for me. Now I have to devle 
into this further to see how to move ahead and ensure that we don't open a 
security hole here. 

Regards, Jerry

Gerald Kern
IBM Certified AS/400 RPG IV Developer & RPG IV Programmer
MIS Project Leader, Lotus Notes/Domino Administrator
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx
*****
This email message, including any attachments, is for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
Any unauthorized review, use, disclosure or distribution is prohibited. If you 
are not the intended recipient, please contact the sender by reply email and 
destroy all copies of the original message.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].