Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Thu, 17 Nov 2005 11:45:29 -0500
If the new domain has the same management classes as the old domain, all you do is : update node blah domain=newname. If the old domain has no management classes other than DEFAULT, that's also no pr
Author: William Boyer <bjdboyer AT COMCAST DOT NET>
Date: Thu, 17 Nov 2005 12:12:53 -0500
You will also need to re-define the schedule association with a schedule in the new domain and if you're running in PROMPTED schedmode you need to stop/start the TSM service(s) on the client before P
Author: "Ford, Phillip" <phillip.ford AT SPCORP DOT COM>
Date: Thu, 17 Nov 2005 12:04:09 -0500
I think Wanda is correct except I though that if a management class does not exist in the new domain then files in that management class will bind to the default class in the new domain. This is what
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Thu, 17 Nov 2005 12:29:58 -0500
Ah. Good point. I'm not sure... I think Wanda is correct except I though that if a management class does not exist in the new domain then files in that management class will bind to the default class