Why not just bind them to a TSM server client option set??  Changes are a
lot easier to apply to hundreds of nodes this way.


Regards,

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP



-----Original Message-----
From: J M [mailto:jm_seattle AT hotmail DOT com]
Sent: Thursday, September 12, 2002 12:38 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: mass Windows client dsm.opt file edit


yeah, we could write something in perl-- Thanks very much for the input-


>From: "Nelson, Doug" <DNelson AT CHITTENDEN DOT COM>
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: mass Windows client dsm.opt file edit
>Date: Thu, 12 Sep 2002 13:21:06 -0400
>
>The only way I can think of is to write a program and have it executed by
>the login script. It would be easy to do that way, and you can drop a
>sentinel file in there to make sure it only executes once. Do you know C++
>or Perl?
>
>
> >>> jm_seattle AT HOTMAIL DOT COM 09/12 12:48 PM >>>
>Does anyone have a clever technique / method to perform a dsm.opt file edit
>(ie. a new exclude statement) across 100's of Windows clients at one time?
>
>_________________________________________________________________
>Douglas C. Nelson
>Distributed Computing Consultant
>Alltel Information Services
>Chittenden Data Center
>2 Burlington Square
>Burlington, Vt. 05401
>802-660-2336




_________________________________________________________________
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.