SharePoint 2016 - Changing The RunAsAccount Password For Workflow Manger

Krossfarm’s administrator is having issue to update the password for the Workflow Manager’s RunAsAccount. But there is no helpful information available which will guide us to update the password. As we know, WFM is little complicated product; if we are using the same account for Service Bus and WFM, then we have to update the same password for both services.

Resolution

We have to use the PowerShell commands for the Workflow Manager and Service Bus to update the password. We have to perform it in 2 steps.

1. Update the Service Bus host
2. Update the Workflow Manger host.

Note

We are using the same Service Accounts for both SB & WFM’s RunAsAccount.

Update Service Host

First, we have to update the Service bus host with the new password.

• Login on the Server with Configuration User Account (account which was used to install and configure the WFM).
• Open the Windows PowerShell command prompt (run it as Administrator).
• Now, execute the following command, 

  Import-Module ServiceBus
  Stop-SBHost
  $mypassword = ConvertTo-SecureString 'tpas2jupa' -AsPlainText -Force
  Update-SBHost -RunAsPassword $mypassword
  Start-SBHost

Note

If you have 3 Server farms, then you have to execute the above PowerShell on all Servers in the Workflow Farm.

Update the Workflow Manger host

Now, we have to update the Workflow Manager.

• Login on the Server with Configuration User Account.
• Open the Windows PowerShell command prompt (run it as Administrator).
• Now, execute the following command

Import-Module WorkflowManager
Stop-WFHost -Verbose
$mypassword = ConvertTo-SecureString 'tpas2jupa' -AsPlainText -Force
Update-WFHost -RunAsPassword $mypassword
Start-WFHost

Note

If you have 3 Server farms, then you have to execute the above PowerShell on all Servers in the Workflow Farm.

Testing

Finally, test the farm by running these commands.

Get-WFFarm
Get-WFFarmStatus

Note

Don’t try to use the Stop-SBFarm, as it will take too much time to restart and often ends up with timeout error, so always stop the host using stop-sbhost.