Installing Workflow Manager for SharePoint 2013 on Domain Controller – Worked!


Many posts out there state that either Workflow Manager cannot be installed on a Domain Controller or is not supported. I know it’s not best practice to run applications on the Domain Controller or SQL Server, but I just had to try.

I have one server (my VM) with the following components installed:
1. Windows Server 2012
2. Domain Controller
3. SQL Server 2012
4. SharePoint Server 2013
5. Workflow Manager
6. Workflow Client
7. Workflow Manager Tools Preview for Visual Studio 2012
8. SharePoint Designer 2013

The workflow components were downloaded from

I’m only going to run through steps I took for installing and configuring Workflow Manager here.
Installing Workflow Manager was pretty straight forward. I accepted the default settings and followed the wizard.


After I finished configuring Workflow Manager, I noticed that Workflow Client was installed as well.


I chose ‘Configure Workflow Manager with Custom Settings’ when the Workflow Manager Configuration Wizard launched.  I chose this option to name my databases instead of using default ones the wizard creates during the configuration.


I installed Workflow Manager Tools Preview for Visual Studio 2012.

Launched SharePoint 2013 Management Shell (I used Windows PowerShell, too), run as Administrator.

Here’s where things didn’t work using either SharePoint 2013 Management Shell or Windows PowerShell:

Register-SPWorkflowService -SPSite http://veeintranet -WorkflowHostUri "http://sp2013.vee.local:12291" -AllowOAuthHttp

I got this error:
Register-SPWorkflowService : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

Looking at Workflow Service Application Proxy, I saw this:


After digging through log files, uninstalling Workflow Manager and its dependencies, deleting the databases several times, and searching all over, I’ve finally found a solution.

I uninstalled Workflow Manager Tools Preview for Visual Studio 2012 (downloaded from the link above).

I downloaded and installed Workflow Manager Tools for Visual Studio 2012 Preview 2 from here

Re-ran the Register-SPWorkflowService command again.

No errors:


I checked Workflow Service Application Proxy again. Woo hoo!


Checked my SharePoint Designer, and there it is, SharePoint 2013 Workflow.



Install SMTP Server (Not Exchange Server) on Your SharePoint 2013 Virtual Server


If you have a need to test SharePoint alerts or workflows from your virtual server and you don’t have access to an SMTP server, the following provides instructions on how to install and configure an SMTP server to test e-mail integration with SharePoint 2013 or previous versions of SharePoint.

1. Download Mail Enable Standard Edition (Free Edition)

2. Launch Mail Enable Standard Edition

3. Click OK on the Installation Note dialog box

4. Click Next on the Welcome dialog box

5. In Get Installation Settings dialog box, provide Name and Company, then click Next          

6. Click Next in the Terms and Conditions dialog box

7. Select Web Mail Service (Server) under MailEnable Messaging Services for Microsoft Windows, then click Next

8. Accept the default Destination Folder for Program Files Location or change location, then click Next

9. Click Next under Select Program Manager Group dialog box

10. Accept the default Destination Folder for MailEnable Repository Location or change location, then click Next

11. In Get Postoffice Details dialog box, type the domain name of your server or a meaningful name, and password


12. In SMTP Connector Configuration, type the domain name, DNS Host(s), and SMTP Port


13. Click Next to start the installation

14. During the installation process, you’ll be prompted to provide the Web site for MailEnable to use

15. In the Select WebMail Web Root dialog box, keep the Default Web Site setting, then click Next

16.   After the installation process completes, the application automatically launches its ReadMe, click OK or Cancel

17.   The Installation Complete dialog box appears, click Finish

18. If you’re running Windows Server 2012, click on Windows Charm –> Search

19. Type MailEnable, you should see the MailEnable Administrator tile, launch it

20. In MailEnable Management Console, expand Post Offices, locate the Post Office Name you created in step 11

21.   Right click on Mailboxes, select New –> Mailbox…


22.   In the Mailbox Properties dialog box, under the General tab, provide Mailbox Name and Password


23. Click on the Addresses tab, provide Reply To Address information (ex: vmaximiuk@vee.local)

Mailbox Properties

24. If you have Microsoft Office client installed on your VM, launch Outlook

25. Provide account information in the Add Account dialog box, then click Next

26. You can ignore the encryption error since this runs on your VM, then click Next

27. Complete the configuration and click Finish

That’s it! Now you should be able to send and receive e-mail message to and from your virtual server to your corporate e-mail account or any external (gmail, live, or yahoo) accounts.

SharePoint 2013 and MAXDOP


I started installing SharePoint  2013 on Windows Server 2012 and SQL Server 2012.  I used PowerShell to configure SharePoint Configuration and Central Administration Databases.

I used SPService account which has dbcreator and securityadmin rights to the SQL Server.  Normally, this would prompt me for SPService’s password and create SharePoint Configuration and Central Administration databases without any issues.

SharePoint 2013 now has intelligence, or whatever you want to call it, built in to detect whether SQL is set to perform at its maximum performance potential.

If you just install SQL without taking advantage of its performance settings, you’d get an error similar to this.

Open SQL Server Management Studio and right click on the SQL Server properties

Navigate to Advanced and change Max Degree of Parallelism (MAXDOP) from 0 to 1

After fixing what SharePoint and SQL are looking for, my PowerShell script ran with expected results.

Here’s how the databases (no GUIDs) look from SQL Server Management Studio.

I still have to finish configuring the Service Applications.  I’ll post my learning experience in my next post.