] On Behalf Of Wanda
Prather
Sent: 11 June 2009 14:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] SV: Windows Client DSM.opt file
A minor correction:
Even though you may find this example in some of the old TSM doc, this line
is incorrect:
INCLEXCL "exclude '*:\...\*.*'"
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Christian Svensson
> Sent: 11 June 2009 13:27 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] SV: Windows Client DSM.opt file
>
> Hi,
> Make sure your Exclude is first and not last.
>
> INCLEXCL &qu
Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Christian Svensson
Sent: 11 June 2009 13:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] SV: Windows Client DSM.opt file
Hi,
Make sure your Exclude is first and not last.
INCLEXCL "RETRYPERIOD 0"
INCLEXCL "CHANGINGRETRIES 0"
I
see
more information.
Best Regards
Christian Svensson
Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson
Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Adrian Compton
[acomp...@aspenpharma.com]
Skickat: den 11 juni 2009 11:24
Till
As Steven says, *always* do 'dsmc query inclexcl' to evaluate the
fully compiled set of Include-Exclude specs, from all sources. And,
when making client options changes, do 'dsmc query options' right
afterward, to assure correctness, to prevent client schedules from
failing. Those two commands s
Phone : +44 (0)1733 584175
( Mob: +44 (0)7876 216782
ü Conference: +44 (0)208 609 7400 Code: 331817
+ Email: steven.langd...@cat.com
Adrian Compton
Sent by: "ADSM: Dist Stor Manager"
11/06/2009 10:29
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
Hi All
I am trying to create a dsm.opt file to only backup all Office files as
Tech Support are rolling out new desktops and I want to make sure they
dont miss any critical data.
I have the following so far but it backups the entire C:
INCLEXCL "RETRYPERIOD 0"
INCLEXCL "CHANGINGRETRIES 0"
INCL
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
Adams, Matt (US - Hermitage) would like to recall the message, "mass Windows
client dsm.opt file edit".
- 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
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
14 matches
Mail list logo
