Microsoft Dynamics 365 Blog

(Please note this article assumes you have working knowledge of SharePoint, IIS, DNS and host files)

1. Create a new Web Application on the SharePoint Central Administration Server. This Web Application URL should point to the common name or Network Load Balanced (NLB) name.

2. Modify the host file found in ‘\windows\system32\drivers\etc\hosts’ on each node

  • Point the NLB name to the IP of the local server. Example: epportal
  • Flush DNS after any change to the host file by opening a command prompt as Administrator and running: ipconfig /flushdns
  • If you are using the fully qualified domain name (FQDN) or a custom host header on the SharePoint web application, make sure that the following workaround is applied before you install Enterprise Portal:

3. Select a SharePoint node running the Central Administration service and run the Enterprise Portal installer.

  • During the install, select all 3 checkboxes in the ‘Configure a Web site for Enterprise Portal’ step to configure the Windows SharePoint Services, Create Web Site, and Restart IIS.
  • Verify Enterprise Portal renders successfully on this node before moving forward by opening Internet Explorer and browsing to the host header name specified in the creation of the Web Application. Example: http://epportal

4. On the other SharePoint nodes, run the Enterprise Portal installer and select only the first and third checkbox in the ‘Configure a Web site for Enterprise Portal’ step as shown below

After following these steps each node should be able to successfully render Enterprise Portal locally when browsing the NLB name.

For additional details and information on this topic please visit the TechNet article below:

Install Enterprise Portal in a Web farm [AX 2012]


— Last Modified by: James Wang

— Modified date: 11/3/2015

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!