I image the reason for defaulting to the current server is because this is the non-destructive choice. What I mean is that I have seen people do some interesting things with replicas and that while they may have a replica on ServerA and ServerB, they may not want to replicate the two. While we could argue why this would be done, the point remains that by guessing a server the user may just click OK and therefore cause a serious issue by replicating the two replicas. Therefore, the current implementation is the safe choice.

I think *blank* is a better choice that *random*, *first* or *same*.

A server replicating with itself is a very possible scenario. I use this feature to replicate real-time transaction data from a 4GB RAM disk to the hard drive replica databases of the same Domino server. RAM Disks are unavoidable when you have 300000+ users who perform several item transactions per second.

I'm fine with setting it to 'blank'
@3 - you have a point, but if you consider the total user base, that's an incredibly small slice of how this is used.

I'm not saying to disallow it, but it seems really silly to have the dialog box default to something that's 99.9% of the time going to wrong.

Blank is far better than that!