A Forum reader asked the following question:
I’m looking for clarification in the instructions for using emBox to do a tree merge. iManager is not an option for our situation at this point.
Specifically, in the documentation section titled “Using the eMBox client to merge trees” step 1 says to run the embox client. But it doesn’t say which tree/server should be running the client. Should I run eMBox on a server in the target tree or the source tree? Does it even matter which one runs it?
And here’s the response from Novell’s Jim Henderson …
It doesn’t matter. Start edirutil with a -i and then log in. (Make sure you use a valid interface and port combination – I was trying 127.0.0.1 and wasn’t connecting – eDir 8.8 doesn’t bind to the loopback interface by default, so I couldn’t get a connection on my Linux box). Do this:
login -s serverip -p port -u admin.context.whatever -w password
If you use the cleartext port, add a “-n” in there.
Then run this:
list -t dsmerge
This will give you the parameters that need to be passed to the tool. It states in the parameters which ones are used for the source and which are used for the target.
I strongly recommend health checks before and afterwards. If you visit the Cool Solutions pages, there’s an article I wrote on using iMonitor to perform health checks that will help you do this step. See:
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.