Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Remote\s+Client\s+Updates\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Remote\s+Client\s+Updates\s*$/: 4 ]

Total 4 documents matching your query.

1. Remote Client Updates (score: 1): Author: "Norrgard, Nathan" <NNorrgard AT LIBERTY-BANK DOT COM>; Date: Fri, 27 Aug 1999 14:08:41 -0400; Is there a way that I can update clients, say from 3.1.0.6 to 3.1.0.7, remotely in my NT WAN? I have 30+ servers, at 30+ sites, all over the state; and that makes for a lot of driving every time I ne; /lists/html/ADSM-L/1999-08/msg01064.html (8,798 bytes)
2. Re: Remote Client Updates (score: 1): Author: "Viswanathan, Ramesh (CNA)" <ramesh AT SCR.SIEMENS DOT COM>; Date: Fri, 27 Aug 1999 20:28:18 -0400; This is one of the serious shortcoming of ADSM. There is no easy method to auto-update the clients. The answer from IBM is the use of Tivoli's software Distribution mechanism. I really wish there was; /lists/html/ADSM-L/1999-08/msg01072.html (9,723 bytes)
3. Re: Remote Client Updates (score: 1): Author: Joshua Bassi <jbassi AT GLORYWORKS DOT COM>; Date: Fri, 27 Aug 1999 18:23:25 -0700; For ADSM Microsoft's 32-bit clients there is the silent install procedure. For UNIX clients most customers have written their own scripts or used a common distribution manager that is targeted for th; /lists/html/ADSM-L/1999-08/msg01075.html (8,807 bytes)
4. Re: Remote Client Updates (score: 1): Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of; Date: Tue, 28 Jun 2011 17:20:56 -0500; This is one of the serious shortcoming of ADSM. There is no easy method to auto-update the clients. The answer from IBM is the use of Tivoli's software Distribution mechanism. I really wish there was; /lists/html/ADSM-L/1999-08/msg01076.html (9,825 bytes)

Current List: 1 - 4
Page: [1]