One of the problems with the current version of BizTalk is
that some of the administration tools are designed to work only within the BizTalk
group the machine is configured to be in. This is fine if you only plan to have one
group, but gets messy if you don’t want to dedicate an administration box to each
BizTalk group. Essentially the problem boils down to the fact that the configuration
tools don’t have their own configuration, but use the BizTalk registry settings to
discover where the group databases, etc are.
I’ve gotten around this in the past by using a batch fine which runs configframework
/u to leave the current group and configframework again
with a scripting configuration to join the new group. Scott
Colestock has an alternative on how to do this by changing the registry settings
all about it.