This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note For detailed hardware and software requirements or specific product versions and service pack levels that are supported for this version, see the topics in this section.
For hardware and software requirements of earlier versions, see the following topics. Dynamics version 8. Important The optional and dependent products listed here that have reached their mainstream support end date might only receive full support with the Dynamics application. If you use a certificate that is created by using a custom certificate request, the template that was used must be the Legacy key template. Custom certificate requests created by using the CNG key template are incompatible with Dynamics for Customer Engagement.
For more information about custom certificate request templates, see Create a Custom Certificate Request. Claims encryption. Claims-based authentication requires identities to provide an encryption certificate for authentication. This certificate should be trusted by the computer where you are installing Dynamics Server so it must be located in the local Personal store where the Configure Claims-Based Authentication Wizard is running.
Individual certificates for each host name are only valid if you use different servers for each web server role. For more information about available options, contact your certification authority service company or your certification authority administrator.
The CRMAppPool account of each Microsoft Dynamics Customer Engagement on-premises website must have read permission to the private key of the encryption certificate specified when configuring claims-based authentication. You can use the Certificates Microsoft Management Console MMC snap-in to edit permissions for the encryption certificate found in the Personal store of the local computer account. The following editions of the Windows Server operating system are supported for installing and running Dynamics Server:.
You must understand the limitations and best practices of server virtualization before you try to virtualize your installation of Dynamics for Customer Engagement. Before you install or upgrade, you must remove the additional bindings from the website used for Dynamics for Customer Engagement or select a different website. This is only required for some Dynamics for Customer Engagement language editions. The following components must be installed and running on the computer where Dynamics Server will be installed:.
If Dynamics Server and SQL Server are installed on different computers, both computers must be in the same Active Directory directory service domain. Windows Authentication is recommended for increased security and Dynamics for Customer Engagement will use only Windows Authentication.
The SQL Server service must be started and can be configured to automatically start when the computer is started. The SQL Server Reporting Services service must be started and configured to automatically start when the computer is started. However, SQL Server can be shared in all sandbox environments. Production IOPS depends on many factors. When you set up the virtual hosts for an environment, see the guidelines in Plan and prepare your Service Fabric cluster and Describing a service fabric cluster.
Each virtual host should have enough cores for the infrastructure that is being sized. Multiple advanced configurations are possible, where SQL Server resides on physical hardware but everything else is virtualized.
In all cases, make sure that the basic setup of the virtual host is highly available and redundant. In all cases, when virtualization is used, no VM snapshots should be taken.
For more information, read Support policy for Microsoft software. In short, we support our products in this environment, but if we are asked to investigate an issue, we may ask the customer to first reproduce the problem without the virtualization platform or on the Microsoft virtualization platform. For optimal performance and an optimal experience, we recommend that you use the latest version of a modern browser, especially Microsoft Edge. Version Support for Internet Explorer 11 was deprecated in December , with end of support for the browser occurring in August For more information, see Internet Explorer deprecation announcement.
Starting in version Before August 17, , Internet Explorer users will see an informational message that Internet Explorer support is soon ending. After that date, Internet Explorer users will see a warning that support has officially ended. Organizations are encouraged to keep these notifications on unless Internet Explorer is mandated for your users, in which case you can choose to suppress these notifications by disabling the Internet Explorer end-of-support notifications feature and relying on internal processes for migrating your user base to Microsoft Edge or another modern browser.
If your organization wants to block Internet Explorer earlier, and you're using version To prepare organizations and users for the upcoming block of Internet Explorer, in January , Internet Explorer users will start to receive a non-dismissible error message that states that Internet Explorer support will soon be blocked. This error message is not controlled by the Internet Explorer end-of-support notifications feature. Customers will have to contact Microsoft Support if this message must be suppressed for their organization.
0コメント