Designating a New Master Secret Server Manually
Cluster hardware can be expensive. If hardware cost is a concern, you can consider manually designating another Enterprise Single Sign-On (SSO) server to be the master secret server during failure scenarios. Using this option, any other SSO server in the SSO group can be promoted to the master secret server. When the master is down, you can manually promote one of the SSO servers to be the master secret server. The biggest disadvantage of this technique is that you cannot edit the existing deployments, restart the existing BizTalk Server services, or deploy new BizTalk applications until you promote a new master secret server.
To make the process seamless, you will need to implement some monitoring mechanism so you will discover the failure as soon as possible. You can also automate the promotion process by using a monitoring application such as System Center Operations Manager.
For more information about manually moving the master secret server, see How to Move the Master Secret Server (https://go.microsoft.com/fwlink/?LinkId=156841) in BizTalk Server Help.
See Also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for