Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+\[adsm\]\s+Re\:\s+Keeping\s+mgt\s+classes\s+in\s+sync\s+across\s+multiple\s+TSM\s+servers\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [ADSM-L] [adsm] Re: Keeping mgt classes in sync across multiple TSM servers (score: 1)
Author: Lloyd Dieter <ldieter AT ROCHESTER.RR DOT COM>
Date: Thu, 14 Jan 2010 18:10:08 -0500
Correct me if I'm wrong here, but I seem to recall that you could not replicate domain/policy/mgmtclass from a configuration manager if there were nodes assigned to the domain on the target (client)
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2010-01/msg00230.html (16,000 bytes)

2. Re: [ADSM-L] [adsm] Re: Keeping mgt classes in sync across multiple TSM servers (score: 1)
Author: Skylar Thompson <skylar2 AT U.WASHINGTON DOT EDU>
Date: Thu, 14 Jan 2010 15:33:31 -0800
That's true if there is a locally-managed domain of the same name on the node. If the domain is managed by the config server you can update without trouble. I've gotten around the problem like this t
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2010-01/msg00232.html (16,380 bytes)


This search system is powered by Namazu