Well, consider if your "corporate environment" is 400 machines spread
over 15 buildings.

If you decide you want to EXCLUDE (i.e., not back up)
C:\Windows\TEMP\...\*,
you have to visit/touch all 400 machines somehow to update their client
option files.

If you put that exlude in a client option set, you can do it all in one
place on your TSM server.

So it's really a matter of convenience/ease of maintenance.  If the
situation doesn't apply to you, you don't need the server side
cloptsets.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Meadows, Andrew
Sent: Thursday, October 21, 2004 2:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Server Side options files


I have been looking into implementing the server side options for a
while now however the more I look into it the more I ask myself what
good it does. I was wondering if anyone else used this option in TSM and
if so are there any real benefits over having client based options files
in a standard corporate environment?
Thanks in advance,
Andrew
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************