Bob -
You are so very right. This issue is one my major beefs with vendors.
There is not enough input from the customers.
Version 3 was being developed before we could ask for input. We are
faced with the same issue although we are developing
ways to overcome this issue. One thing that we are doing is creating a
command line shortcut, WIN95, which does an incremental backup
of the client device sans GUI. It don't eliminate the ability to backup
through the GUI but if people are given the simple backup icon they tend
to take the shortest road to completing a backup. This process is used
by our portable users who are not plugged into the network during the
"normal" backup
window at night.

Also - There needs to be the facility to grant or deny functions on the
client GUI from the server. We would like to limit the client
interaction
with the server in certain cases like locking the preferences, denying
access to the preferences and access to the opt file. users just LOVE to
mess with that one!

Take care -
CR

________________________
Cris Robinson
Senior Technical Analyst
Desktop Services Technical Support
Liberty Mutual Insurance
603.431.8400.54837
cris.robinson AT libertymutual DOT com

> -----Original Message-----
> From: Bob Matthews [SMTP:Robert.Matthews AT SEINF.UNIGE DOT CH]
> Sent: Thursday, April 02, 1998 7:06 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: It's too easy !
>
> Thank you to those people who replied to my remarks about it being far
> too easy for a user of the version 3 GUI to backup the entire
> universe.
>
> Unfortunately, what I hear is not encouraging. Neither the latest fix
> nor the proposed future development come anywhere near solving the
> problem. There's no way we can upgrade our 1,000 clients to version 3
> while this situation exists. In my humble opinion, once a domain has
> been defined for a client, the client should never look at anything
> outside that domain irrespective of whether the backup is by GUI,
> non-GUI, scheduled or non-scheduled. If I understand the documentation
> correctly, I can "enforce" a domain in a client option set but the GUI
> will then ignore it. What's the use of "enforcing" something that can
> be ignored? This seems like a contradiction!
>
> Is this another example of IBM not listening to the requirements of
> its customers? Forgive me if I'm wrong.
>
> Bob Matthews,
> University of Geneva.