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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Server\s+Name\s+Change\s*$/: 3 ]

Total 3 documents matching your query.

1. Server Name Change (score: 1): Author: "Mann, Joseph" <mannjo AT FOSTERFARMS DOT COM>; Date: Mon, 10 Jan 2000 11:29:07 -0800; I am installing a new NT 4.0 server that will have a name change eventually when it goes into production. I want to install the client software (3.7) now before the name change. We are an new TSM sit; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-01/msg00405.html (10,613 bytes)
2. Re: Server Name Change (score: 1): Author: Nathan King <nathan.king AT USAA DOT COM>; Date: Mon, 10 Jan 2000 14:43:57 -0600; No Joseph, no need to re-install, but you may consider changing the nodename in the dsm.opt once you rename the server and if so updating the scheduler service as appropriate using dsmcutil. The best; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-01/msg00406.html (11,212 bytes)
3. Re: Server Name Change (score: 1): Author: "Laura G. Buckley" <buckley AT STORSOL DOT COM>; Date: Mon, 10 Jan 2000 13:48:53 -0700; Joseph, The TSM node name and the actual server node name are not required to match. In the dsm.opt file, you can enter the option NODENAME and provide whatever name you like (it has to match a regis; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-01/msg00407.html (12,293 bytes)

Current List: 1 - 3
Page: [1]