Edit

Install Dynamics 365 Customer Engagement (on-premises) Full Server role on a server without Dynamics 365 Customer Engagement (on-premises) installed

  • Article

This article doesn't apply to the Dynamics 365 Customer Engagement (on-premises), version 9.1 update. For information about new features in update 9.1, see What's new.

For information about this topic for Dynamics 365 Customer Engagement (on-premises), version 9.0, select the version located above the left navigation pane.

Version selector

Install the Dynamics 365 Server software

  1. Meet all requirements specified in Microsoft Dynamics 365 Customer Engagement (on-premises) System Requirements and Required Components.

  2. Log on to the domain as a user who has administrator-level privileges where Dynamics 365 Server will be installed and who is a member of the Administrators group on the local computer. You cannot install the application as a member from a trusted domain.

  3. See the Dynamics 365 Customer Engagement (on-premises) Readme file to determine the location of the Dynamics 365 Server installation files.

  4. In the folder where the Dynamics 365 Server files are located, move to the Server\amd64 folder, and then double-click SetupServer.exe.

  5. On the Welcome to Microsoft Dynamics 365 Server Setup page, we recommend that you select Get updates for Microsoft Dynamics 365 Customer Engagement (on-premises), to make sure that Setup has the most recent installation files. Select Next.

  6. On the Product Key Information page, type your product key in the Product key boxes, and then select Next.

  7. On the License Agreement page, review the information and if you accept the license agreement, select I accept this license agreement, and then select I Accept.

  8. If Setup detects that components are missing, the Install Required Components page appears.

    • If you have already installed the required components, this page will not appear.

    • If you have not installed the required components listed, you can install them now. Select Install. When the components are installed, the status column will change from Not Installed to Installed, and you can select Next to continue.

    Note

    If you are prompted to restart the computer, do so, and then start Setup again.

  9. On the Select Installation Location page, accept the default location or enter a different file installation location, and then select Next.

  10. The Specify Server Roles page appears. By default, Full Server is selected and will install all server roles on the computer. Alternatively, you can select a predefined group of server roles or one or more individual server roles. Notice that all server roles must be deployed on the network in the same Active Directory domain for the deployment to operate correctly. For more information, see Planning your deployment of Dynamics 365 Customer Engagement (on-premises). Select Next.

    Important

    When you select a server role other than Full Server, Microsoft Dynamics 365 Server Setup does not create an organization database during the installation. If the deployment does not have an organization database, you must use the New-CrmOrganization Windows PowerShell cmdlet or Deployment Manager to create a new organization.

  11. On the Specify Deployment Options page, if Setup detects an existing deployment, you can select whether you want to create a new deployment or connect to an existing deployment. In the Enter or select the name of the computer that is running SQL Server to use with the deployment box, type or select the instance of SQL Server that will be used to store the configuration database (MSCRM_CONFIG).

    Important

    When you select Create a new deployment, Setup creates a new organization database using the name that you specified and a configuration database by using the name MSCRM_CONFIG. An error message will appear if an MSCRM_CONFIG database already exists. You must delete this database to create a new MSCRM_CONFIG database. Only one deployment is supported for each instance of SQL Server.

    When you select Connect to, and if necessary, upgrade an existing deployment, Setup requires that a configuration database (MSCRM_CONFIG) already exist on the computer that is running SQL Server. An error message will appear if an MSCRM_CONFIG database does not already exist.

  12. On the Select the Organizational Unit page, select Browse to display your Active Directory structure. Select the organizational unit where you want to add security groups, select OK, and then select Next.

  13. On the Specify Service Accounts page, select the security accounts for the Dynamics 365 Customer Engagement (on-premises) services, and then select Next.

    The services are described below.

    • Application Service. This service runs the Dynamics 365 Customer Engagement (on-premises) web application that is used to connect users to Dynamics 365 Customer Engagement (on-premises) data.

    • Deployment Web Service. Publishes the web service that provides the deployment interface described in the Developer Guide for Dynamics 365 Customer Engagement (on-premises), such as create an organization or manage the list of Deployment Administrators for the deployment.

    • Sandbox Processing Service. Enables an isolated environment to allow for the execution of custom code, such as plug-ins. This isolated environment reduces the possibility of custom code affecting the operation of the organizations in the deployment.

    • VSS Writer Service. The Dynamics 365 Customer Engagement (on-premises) VSS Writer Service provides an interface to back up and restore Dynamics 365 Customer Engagement (on-premises) data by using the Windows Server Volume Shadow Copy Service (VSS) infrastructure.

    • Asynchronous Processing Service. Processes queued asynchronous events, such as bulk email or data import.

      Important

      We strongly recommend that you select a low-privilege domain account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Dynamics 365 Customer Engagement (on-premises) service cannot be a Dynamics 365 Customer Engagement (on-premises) user. This domain account must be a member of the Domain Users group. Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must a member of the Performance Log Users security group.

      If you select to run the ASP.NET service under a domain user account that is not a domain administrator or a local administrator, you must set a local security policy after you install Dynamics 365 Server for the ASP.NET service to work correctly. Also, depending on the password policies that you have implemented for your organization, the password for the user may expire. For more information, see the Microsoft Knowledge Base (KB) article 329290, How to use the ASP.NET utility to encrypt credentials and session state connection strings.

    • Monitoring Service. This service will be installed with any Dynamics 365 Server role installation to provide event monitoring on Dynamics 365 Customer Engagement (on-premises) server roles that are running on the local computer.

  14. On the Select a Web Site page, select Create a new Web site or select Select a Web Site and select a website from the list. By default, Setup will use the default website.

    Important

    We strongly recommend that you verify the status of the existing website before you specify Setup to use an existing website.

    We strongly recommend that the website you select is configured for Transport Layer Security (TLS). For more information, see the IIS documentation. During the installation, Setup will bind the application to the HTTPS website. If you select a network port other than a default port, ensure that your firewall does not block the port.

    When you select the Create a new Web site option, Setup creates a new website for Dynamics 365 Server. You can specify the following option:

    • Port Number. Type the TCP port number that Dynamics 365 Customer Engagement (on-premises) clients will use to connect to the Dynamics 365 Server. The default port number is 5555.

  15. Select Next.

  16. On the Specify Email Router Settings page, in the Email Router server name box, type the name of the computer where the Email Router will be installed. This computer will route Dynamics 365 Customer Engagement (on-premises) email messages. If you will not install the Email Router (recommended), you can leave this box blank. However, if you install the Email Router later, you must add the computer where the Email Router service is running when you use Local System, or if you use a domain user account, the account, to the PrivUserGroupP security group. Select Next.

  17. On the Specify the Organization Name page, specify the following information:

    1. In the Display Name box, type the name of your organization.

    2. In the Name box, you can keep the name that is automatically generated or you can type a unique name that must be limited to 30 characters. Spaces and extended characters are not allowed.

    3. Under ISO currency code, click Browse, select the ISO currency code that you will use as the base currency for the organization in the list, and then click OK.

      You can change the currency's symbol, name, or precision.

    4. In the Base Language list, select the base language for the organization.

      With Dynamics 365 Server, only the base language of the first organization is tied to the language of the server installation. All other organizations can have different base languages, but you must first install Language Packs for the additional languages. For instructions about how to install Language Packs, see Install and enable a Language Pack.

    5. In the SQL collation list, keep the default selection or select a different database collation that the organization database will use to sort and compare data characters.

      The default SQL collation changes based on the base language selection.

      For more information, see Collation and Unicode support.

    6. Select Next.

      Important

      After Setup is complete, you cannot change the database collation, base ISO currency code, or the organization unique name. However, you can change the base currency name and base currency symbol.

  18. On the Specify Reporting Services Server page, type the Report Server URL. Make sure that you use the Report Server URL, not the Report Manager URL. To verify that you are using the correct URL, in a browser, type the Report Server URL as the address. Select Next.

  19. On the Help Us Improve the Customer Experience page, select whether you want to participate in the Customer Experience Improvement Program. When selected, the application automatically sends basic, anonymous information to Microsoft about how you use Dynamics 365 Customer Engagement (on-premises) and the types and number of errors you encounter. This information helps Microsoft solve problems and improve products and features. Microsoft does not collect your name, address, or other contact information. Select Next.

  20. On the Select Microsoft Update Preference page, select whether you want to use Microsoft Update for checking for updates for your Microsoft products, and select Next. We recommend that you use Microsoft Update to check for updates because this helps keep your computer up-to-date and secure.

  21. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings, appear, you can continue with the installation. To do this, select Next.

  22. The Service Disruption Warning page appears. Verify the suitability of the services that will be stopped or restarted, and then select Next.

  23. Review the Ready to Install Microsoft Dynamics 365 Customer Engagement (on-premises) page, and then select Back to correct any warnings. When you are ready to continue, select Install.

    When Setup completes successfully, the Microsoft Dynamics 365 Server setup completed page appears. If the Reporting Server instance that you specified during this Setup points to the local computer where Dynamics 365 Server is installed, Setup provides an option to invoke Microsoft Dynamics 365 Reporting Extensions Setup.

  24. To install Microsoft Dynamics 365 Reporting Extensions on the computer now, select the Launch Microsoft Dynamics 365 Customer Engagement (on-premises) Reporting Extensions Setup check box. Select Finish.

    Important

    • After you install Dynamics 365 Server, you must install the Microsoft Dynamics 365 Reporting Extensions to create, run, and schedule reports in Dynamics 365 Customer Engagement (on-premises). For instructions, see Install Microsoft Dynamics 365 Customer Engagement (on-premises) Reporting Extensions.
    • By default, Setup turns on HTTP compression on the server that is running IIS where the Dynamics 365 Customer Engagement (on-premises) web application is installed. If you use another method to compress HTTP communications, you may want to turn this feature off. To do this, start Internet Information Services (IIS) Manager, click the website, double-click Compression, and then clear the compression check boxes.
    • For an IFD deployment, after Microsoft Dynamics 365 Server Setup completes, you must configure claims-based authentication and the relying parties on the STS server. Then, run the Internet-Facing Deployment Configuration Wizard to complete the configuration.

See also

Microsoft Dynamics 365 Server installation
Install Microsoft Dynamics 365 Customer Engagement (on-premises) Reporting Extensions