Unique (?) ADSM configuration question

Date:     February 14, 1996            Time:    07:28
From:    Jerry Lawson
    ITT Hartford Insurance Group
    (203) 547-2960    jlawson AT itthartford DOT com
-----------------------------------------------------------------------------
Yesterday, a customer who wants to do ADSM came to me with the following
Yesterday, a customer who wants to do ADSM came to me with the following
"challenge".

The customer runs our "Walk in Center".  This is a collection of machines
(primarily Windows based) that are used in an open environment.  They
typically include hardware options (such as scanners or color printers) that
individuals cannot justify for their own desktops.  They use a program called
"Saber Menus" (formerly from Novell?) to handle chargeback.  The program works
something like this:  When you walk up to a machine, the machine is booted,
with Saber Menus running.  A welcome screen is up, and you must enter
accounting information to get the process moving.  At this point, Windows is
not running.  After the accounting information is entered, Windows is
launched, and a person can now "do their thing".  At the end of the session,
they exit windows, Saber Menus takes back over, and the process starts over.
Currently, the machines are powered down at night, but this is not a
requirement.  Customers can access the room (via keycard) off hours and use
the facility at any time.

Does anyone else use Saber Menus and ADSM.  We kicked around several options,
but aren't thrilled by any of them - for example, we could use the DOS ADSM
version, but that would mean a different TCP/IP than we normally run.  We
don't want to put the ADSM Scheduler in the Startup folder - it would kick off
every time a user comes in, and might be confusing to some.  We could use the
"Password" feature to hide the password prompt, and with the schedule set for
off hours, it would probably not be an issue, but still this might be a
problem.  There was concern about leaving the machines in Windows all night,
as this would have to be assigned to a chargeback code, or would be
unaccounted for.  This would soon become the largest chargeback, but then this
could be handled administratively.   Lastly, of course we would prefer to have
the process handled automatically using the scheduled backup function, as
opposed to having the person who opens up in the morning go around and
manually run ADSM.

OK - a long explanation.  Does anyone out there have a similar situation?
Anyone have Saber Windows, and use it with ADSM?   Or even if you don't, do
you have any suggestions or fresh ideas (or even opinions on the old, dusty
ideas listed above?)

Thanks in advance
Jerry Lawson
jlawson AT itthartford DOT com