Share via

BizTalk Server: Step-by-step Guide on How to change the BizTalk Server Group Domain account

  • Article

Introduction

The question came up recently on how to change the domain group for a BizTalk Host.

Step-by-Step

This step by step guide is pretty rough, but should give you an idea how to do this.

  1. Prerequisites:
    • The user must be at least a LEVEL 3 or LEVEL 4 user (see my article for security)
    • The groups must be accessible to the BizTalk Server and the SQL Server
    • The system must currently be able to operate, and there are no outstanding errors in the event log on the SQL Servers or BizTalk Servers
    • The Groups should not require any special additional privileges outside of BizTalk due to custom requirements
  2. Create the groups
  3. Create and add the BizTalk Service accounts to the appropriate groups in the domain
  4. Ensure that the SQL Service accounts for SQL Database Service, SQL Agent have access to the domain that the Groups are members of
  5. Stop the SQL Server Agent Service on all SQL Servers
  6. Open the BizTalk Admin console and go to the Platform Settings
    • Stop all host instances
    • Right click on the Host Instances that belong to this group and export their settings
    • Right click on the Host Instances that belong to this group and delete them
    • Right click on the Host that you want to change and select Properties
    • In the Windows Group field, change the group from the old group to the new group and close the dialog
    • Recreate the Host Instances and import their settings
    • Start the BizTalk Services and confirm that they are running without errors
  7. Start the SQL Agent
    • Manually run the backup job and confirm it is working
    • Manually run the DTA Purge and archive job and confirm it is working
    • Manually run the rest of the enabled BizTalk Jobs and confirm they are working
  8. Review the Event Log on the SQL
  9. What could go wrong
    • SQL Server can’t see the new groups because it’s service accounts are in a different domain
    • The logged in user may not have sufficient rights in SQL or BizTalk
    • You could have special security requirements that are not part of BizTalk that could cause the service instances to fail

Other languages

This article is also available in the following languages:

See Also

Another important place to find a huge amount of BizTalk related articles is the TechNet Wiki itself. The best entry point is BizTalk Server Resources on the TechNet Wiki