[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
|
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
1434.0. "Admin versus Manager creating accounts" by BRUMMY::MARTIN::BELL (Martin Bell, TCC, Birmingham UK) Wed Sep 16 1992 16:40
This was asked back in the 2.4 conference, but never received a reply, so i am
asking again just to see if anyone has any thoughts or input.
When creating an ALL-IN-1 account (using CU), for a user with an existing VMS
account, using MANAGER, the [.A1] sub-directory is created under the SYS$LOGIN
directory (as specified in SYSUAF.DAT. When the account is created by an
ADMINISTRATOR, the [.A1] sub-directory is created on one of the disks specified
in the account TEMPLATE
Why does this happen?
mb
p.s.
Original note follows ...
<<< SHALOT::NOTE$:[NOTES$LIBRARY]ALL-IN-1_V24.NOTE;1 >>>
-< Old ALL-IN-1 Support Conference: Aug 1990 - Feb 1992 >-
================================================================================
Note 1670.0 ADM MUA CU with UAF record already created problem No replies
GIDDAY::ROUT 26 lines 29-APR-1991 01:11
--------------------------------------------------------------------------------
A customer has reported a problem with ADM MUA CU on an ALL-IN-1 V2.4
system. Unfortunately I don't have a V2.4 system to test this out on.
When Creating a new account when a UAF record already exists, the
administrator found the account created on a disk(A) specified in the
template rather than the UAF Default disk(Z).
Because the two disks in template and UAF differed the customer then
added two other disks(Z and B) to the template field
"Names of disks available", one of these was the same as the
UAF Default Device.... and still no dice... it created the account
on the other disk(B)
The customer then had luck in logging into the managers account and
creating the account.
I checked the logical disks were OK (concealed)
Could someone tell me what the rules are for already created UAF records
in respect of the administrator creating accounts... the behaviour
above seems strange and I know at V2.4 the create account code has been
modified extensively.
thanks in advance
Caroline
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1434.1 | Oops | BRUMMY::MARTIN::BELL | Martin Bell, TCC, Birmingham UK | Wed Sep 16 1992 17:02 | 14 |
| Oh dear,
maybe i am about to answer my own question!
Reading the v3.0 SM_CR_USER_DETAILS.SCP it appears that it _does_ use the
UAF device (even though it does a SM_SELECT_DISK for no apparent reason).
Phew, 27 pages of script is a whole lot more complex than the old 6 pages!
mb
p.s.
It still contains a bug on page 1!!!!!
|