| ** This based on SharePoint 2013 Preview and Windows Azure Workflow Services Beta, so may change. Also this has not been validated by anyone else yet :-) **
As you may know by now, there are currently limitations with the Windows Azure Workflow services and installer on a domain controller. See posts below:
http://www.andrewconnell.com/blog/archive/2012/07/27/sharepoint-2013-workflow-ndash-getting-around-installation-issues-creating-amp.aspx
http://www.justinkobel.com/post/2012/07/23/Configuring-Windows-Azure-Workflow-for-SharePoint-2013-Technical-Preview.aspx
Well after some testing I finally got this working. To do this it is actually pretty straight forward. To get it to work do the following:
Create the Windows Azure Workflow Service Account in the domain
Make sure this account is added to the local administrators group and allowed to log into the server locally, this is only to be able to log into the server. The account should technically be removed from this group in a domain controller environment, by being added to the specific power user group and granted local security policy permisisons.
- Now log into the server as that account
- Ensure this account has permission to SQL, either you have SQL installed on the same server or you have a separate server for that
Once logged in run the Workflow Configuration Tool
Once It loads either use the default or choose custom, for me I chose custom and set the following values:
Ensure the account you specify here is the service account you are currently logged in with, as well as ensure you are using the FQDN as shown below.
Complete the rest as shown below
Now configure the service bus components, mine is shown below.
As before make sure the service account is the same as the one you are logged in with
Complete the rest as below
Now we can review what is going to be done
And now we wait for it to install
When complete it should show this
Now to move on and get SharePoint 2013 installed over the top and working J |