First of all, I really wouldn't recommend bi-directional replication. It would be hard to avoid data conflicts, you'll probably have significant performance overheads, and you'd need to reestablish replication whenever a schema change is made (e.g. new field
or entity is created or deleted).
To answer the specific question about the MSCRM_Config database - this database should not be replicated in its entirety, as it contains deployment-specific data. However, it will contain information about users, so if you add a new user into one CRM deployment,
you'd have to add equivalent data into the MSCRM_Config in the other deployment, and there's no supported way to do this.
To summarise, you might be able to get this to work if you don't make any subsequent schema changes, and you don't add new users, and even so I wouldn't trust the stability. I'd suggest you either use log shipping, or backup/restore with an import of the
CRM organisation whenever you want to copy the data
Microsoft CRM MVP - http://mscrmuk.blogspot.com http://www.excitation.co.uk
