Whenever I've switched clients into a different domain - I've always had to restart the schedule service on the clients. We run in prompted mode, backups would not run until service restarted.
-----Original Message----- From: Gerald Wichmann [mailto:[EMAIL PROTECTED]] Sent: July 17, 2002 3:15 PM To: [EMAIL PROTECTED] Subject: Re: 15 domains into 3. Nope.. whats the actual question though? Assigning your nodes to a different domain isn't a big deal but you've got a lot of legwork to do to figure out what each of your node's uses as management classes, what domains they are assigned to, what all the in-use management classes are (and their respecting copygroup settings), and then recreate that all in the new 3 domains such that when you DO reassign the node, it simply rebinds the data and doesn't expire anything. Of course doing this is going to affect EVERYTHING including schedules, option sets, etc etc.. so the main work is just taking a comprehensive inventory of your server and planning it all out beforehand. Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -----Original Message----- From: Robert Molerio [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 11:53 AM To: [EMAIL PROTECTED] Subject: 15 domains into 3. Hi ADSM'ers, Has anyone had to collapse 15 domains into a smaller number preserving the attributes of the domains policy sets and mgmntclasses? I'm stucjk here and need help. Bob M.
