Share via

BizTalk step-by-step: changing the group BizTalk Services run under

  • Article

 

Introduction

This is a step-by-step guide on how to change the group that BizTalk Services run under.

 

Prerequisites

  1. The user must be at least a LEVEL 3 or LEVEL 4 user (see Minimum Security Rights for security levels).
  2. The groups must be accessible to BizTalk Server and SQL Server.
  3. The system must  be currently operational, and there are no outstanding errors in the SQL Server event logs or BizTalk Server event logs.
  4. The groups should not require any additional privileges other than BizTalk, unless there are internal customer requirements.

 

Step by Step

  1. Create the groups.
  2. Create and add the BizTalk service accounts to the appropriate groups in the domain.
  3. Make sure that the SQL Server service accounts for SQL Database Service and SQL Agent Service have access to the domain that the groups are members of.
  4. Stop the SQL Server Agent Service on all SQL Servers.
  5. Open the BizTalk Admin console and go to the Platform Settings.
    1. Stop all host instances.
    2. Right-click the Host Instances that belong to this group and export their settings.
    3. Right-click the Host Instances that belong to this group and delete them.
    4. Right-click the Host that you want to change and select Properties.
    5. In the Windows Group field, change the group from the old group to the new group and close the dialog box.
    6. Recreate the Host Instances and import their settings.
    7. Start the BizTalk Services and confirm that they are running without errors.
  6. Start the SQL Agent Service.
    1. Manually run the backup job and confirm it is working.
    2. Manually run the DTA Purge and archive job and confirm it is working.
    3. Manually run the rest of the enabled BizTalk Jobs and confirm they are working.
    4. Review the event Log on SQL Server.

 

What could go wrong

  1. SQL Server can’t see the new groups because its service accounts are in a different domain.
  2. The logged-in user may not have sufficient rights in SQL Server or BizTalk.
  3. There might be special security requirements that are not part of BizTalk that could cause the service instances to fail.

 

See Also

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