I created a duplicate domain under a different name and migrated all
nodes to them one domain at a time.
Removed the old domains from the targeted "managed servers", added a
subscriber profile for just policy domains to my configuration manager,
replicated them to the managed servers, and finally moved the nodes
back.

Guess I could have went the route of creating the new managed domains
and moved the clients to them, but to not have to redo a lot of doco and
scripting I decided to take the extra steps and use the original domain
names.

I made sure that the temporary domains were configured the same as the
originals to avoid any data binding issues when their original domains
were deleted.

Hope that helps...

~Rick


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Langdale
Sent: Monday, January 31, 2011 11:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Centralised management of Policy domains

Hello

I'm adding another 6 TSM instances to our existing TSM infrastructure.

I wanted to take this opportunity to try an centrally manage the policy
domains from our config manager.

However as I'm sure most of you know, you cannot update a domain on a
subscriber if there are nodes in it.

So that leads me to my question....  What do you folks do to try and
centrally manage domains?  Is export policy a viable option?

Thanks all

Steven