Currently we are running a project to merge 3 old servers into one cluster server.
So we moved our main server to a new machine, build a second identical machine and made a cluster.
But now we have two old servers of wich all the users will have to be moved to the cluster.
The move person command works but there are a few shortcomings.
Most of our users have local replica’s because the bandwith to remote offices wasn’t enough to work from the server and we wanted an extra level of availability.
Now if i move a user he gets a new shortcut on his workspace, but his local replication settings aren’t updated.
Also his home server setting in the local adresbook isn’t updated.
So this means i either have to change 200 users manually or i have to find another solution.
I’ve been thinking to add the old servers to the cluster and then restrict the old server untill everybody is working on the new servers and then shut down the old one.
Can i expect problems with this? it seems to me that this is the easiest way to move 200 users without having to change each client manually.
What you should have done is move the users while the server wasn’t online, then (in a weekend) shut the old server down and give the same name to the new one.
What you could do now, is write a little manual for the users, so they change the replication to the new server. It’s pretty easy (even for users haha) so you won’t have to run to all…
That is actually what we did, let me detail this a bit more,
we had 3 servers, A(200 users) B and C with 100 users each.
When we replaced server A we build a new machine, and switched in a weekend to the new server taking the 200 users to the new server, and a few weeks later we clustered it in a weekend. So i have 200 users on the cluster without a problem.
The problem is that i still have servers B and C on other locations and i want to move those users to my cluster now.
Changing the replication isn’t really hard, except with our users even the button read all/read unread is a difficult thing to master so i’m REALLY reluctant to go for that aproach.
hmm maybe you could write an agent that you put in a button for the users to klick, so the replication runs to the new server.I cannot help you with that tough, cause i wouldn’t know how… I wish you good luck !
Your questions sounds like one I am comtemplating. Our problem though is we have about 10 mail servers in the field and the people on those are moving to our cluster. The problem is bandwidth. Is there a way to point the replica they already have to the new server without them having to do a completely new one? This will take forever for some of our users.