Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*cloptset\s+broken\s+for\s+Windows\s+4\.1\.2\.X\s+client\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*cloptset\s+broken\s+for\s+Windows\s+4\.1\.2\.X\s+client\s*$/: 7 ]

Total 7 documents matching your query.

1. cloptset broken for Windows 4.1.2.X client (score: 1): Author: Suad Musovich <suad AT CCU1.AUCKLAND.AC DOT NZ>; Date: Tue, 10 Apr 2001 15:07:44 +1200; I have upgraded a few Windows (2Kpro) boxes from the 3.7.2 TSM client to the 4.1.2.19 one. The new client seems to ignore the Client-Option set assigned to these clients? In our case, it ignores all; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00382.html (11,232 bytes)
2. Re: cloptset broken for Windows 4.1.2.X client (score: 1): Author: "Kleynerman, Arthur" <Arthur.Kleynerman AT MOODYS DOT COM>; Date: Tue, 10 Apr 2001 09:02:13 -0400; Suad, did you specify force=yes (to override the options in the dsm.opt file)? For example: def clientopt opt_set 'Exclude ........' seq=0 force=yes Arthur.; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00408.html (11,026 bytes)
3. Re: cloptset broken for Windows 4.1.2.X client (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Tue, 10 Apr 2001 09:15:37 -0400; Note that INCLEXCL and DOMAIN are additive options such that Force has no effect. That is, Force pertains only to singular options.; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00410.html (11,018 bytes)
4. Re: cloptset broken for Windows 4.1.2.X client (score: 1): Author: "Kleynerman, Arthur" <Arthur.Kleynerman AT MOODYS DOT COM>; Date: Tue, 10 Apr 2001 09:18:27 -0400; What if one has all of inclexcl statements defined in the client option set and none in the dsm.opt file?; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00411.html (10,986 bytes)
5. Re: cloptset broken for Windows 4.1.2.X client (score: 1): Author: "Jennifer I. Moore" <jim1 AT CORNELL DOT EDU>; Date: Tue, 10 Apr 2001 12:52:59 -0400; Greetings, We are running a test of Client Option Sets from an AIX server running TSM 4.1.2 and an NT 4.0 Workstation running TSM 4.1.2.12. Things *seem* to be behaving as expected with includes/excl; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00427.html (13,667 bytes)
6. Re: cloptset broken for Windows 4.1.2.X client (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Tue, 10 Apr 2001 13:41:55 -0400; "include-exclude options in a client option set will always be seen and processed during backup first, before any options set in the client options file." And: "Include-exclude options in the client; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00434.html (12,133 bytes)
7. Re: cloptset broken for Windows 4.1.2.X client (score: 1): Author: Suad Musovich <suad AT CCU1.AUCKLAND.AC DOT NZ>; Date: Wed, 11 Apr 2001 21:33:16 +1200; Aaarrggghh ... found out what the story is. When I actually demonstrated the 4.1 "daylight savings bug-fix" client install for a desktop (desktops get the "only backup the documents directory" Clopts; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-04/msg00456.html (11,856 bytes)

Current List: 1 - 7
Page: [1]