Sent: Thursday, September 12, 2002 12:38 PM
To: [EMAIL PROTECTED]
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" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager&q
2002 12:05 PM
To: [EMAIL PROTECTED]
Subject: Re: mass Windows client dsm.opt file edit
We only store setting in the local dsm.opt that can't be set using client
option sets on the TSM server. All of our include/exclude statements are
stored in client option sets based on client os. Makes
yeah, we could write something in perl-- Thanks very much for the input-
>From: "Nelson, Doug" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: mass Windows client dsm.opt file edit
&
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?
>>> [EMAIL PROTECTED] 09/12 12:48 PM >>>
Does anyone have a clever
We only store setting in the local dsm.opt that can't be set using client option sets
on the TSM server. All of our include/exclude statements are stored in client option
sets based on client os. Makes changes alot easier, since we make the change in one
place, and we don't have to refresh th
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?
_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
