| 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 |
John Mackney
Educational Services Holland.
Before I launch into application programming, does anyone have a
procedure which automatically adds a range of user accounts to
ALL-IN-1.
Here at Nieuwegein, we give regular user training. The user accounts
we create are named after the seat number/classroom number the student
occupies (i.e. 123a, 008b etc.) This allows us to run 2 or more classes
in the same week. (It would be no use using Student1, Student2, or the
course number prefix as they would not be unique).
The problem: at the end of each week I have to remove the user's data
and create new accounts for the following week. The simplest way to
achieve this is to delete the accounts and create new ones. - Deleting
the accounts with XD is easy enough, but creating the new accounts is
very time consuming.
Has anyone done anything like this before, or does anyone have any
advice (i.e. use DCL in the subprocess, write some scripts...)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2085.1 | EDU in Reading have something similar, I think | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Thu Jan 14 1993 18:58 | 10 |
I think EDU Services here in Reading have an "automatic" account
generator and deleter, for exactly the purpose you describe. Maybe
they'd give it to you. I can't think who
you'd need to speak to about it though, sorry.
You could try DTN 830 4201 - that's apparently their Support Desk, or
830 8020, which is the general query number. Mail to MINNIE::SYSTEM
might be quicker at getting you to the relevant techy person.
Scott
| |||||
| 2085.2 | Seen 1423? | IOSG::TALLETT | Gimmee an Alpha colour notebook... | Thu Jan 14 1993 20:40 | 11 |
Our ed services just takes a backup after the system has been
set up, then restores it every week. This is good for security
as noone can plant a mole, and saves deleting all the crap that
the students create.
Alternatively you could havbe an automated procedure that
calls create user. See note 1423.
Regards,
Paul
| |||||