I'm a bit confused by your post but I'll answer what I think you mean:

First, about 'migration'. When you migrated 1.0.1.1 to 2.0 that migrated
all your repository workspaces (on the server). Any further actions you
need should only be updating your metadata in your local eclipse
workspaces.

You mention creating/loading a repo workspace from an eclipse workspace.
Do you mean load an eclipse workspace from a repo workspace? If so, if you
are loading a repo workspace into a new eclipse workspace, then you should
not have any prompts to 'migrate', because it will be a 'fresh load' and
everything should come on disk and the metadata will be set up properly.

If you are starting eclipse and selecting an eclipse workspace that has
files shared with RTC that were loaded previously with 1.0.1.1 but now
things have changed to 2.0, then yes, you will be prompted to fix your
metadata when the client starts up. Note the repair metadata in the
preferences does exactly the same thing as the prompt on startup, but is
used for when 'you' know the metadata is corrupt and out of date, but
somehow RTC didn't figure out the metadata was corrupt to prompt you.

Thus, running repair metadata only affects your local sandboxes managed by
that instance of RTC. So when you say you want to 'go into each of these
and force their migration', I think you are talking about repairing the
metadata of your local instances of eclipse. So obviously you can't do
that remotely. You have to go to each machine and do it.

Personally, I try to make sure all my work is checked in before upgrades
happen. Then instead of letting RTC repair my metadata, I just delete my
old workspace and load again. It probably takes a bit longer but atleast
that way I can browse work items while Eclipse loads.

On Mon, 14 Sep 2009 11:53:00 -0400, tfeeney
<tfeeney> wrote:

I have several Eclipse workspaces used with 1.0.1.1 and have now
upgraded RTC to 2.0. When creating/loading a repo workspace from one
of these Eclipse workspaces, I'm prompted to migrate the workspace.
That all works fine. What I want to do is to go into each of these
and force their migration, ie. I don't want to wait for the prompt.
I tried the Repair Metadata option from the Jazz Source Control
preferences dialog but that had no effect.

Is there a way to force the workspace migration?

--