Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Many of you are very familiar with the on-premises installation process, however new changes and high availability capacities was introduced in platform 41 and later.
Stating in version 10.0.12/PU36 we introduce the possibility to have batch-only and interactive-only Application Object Server (AOS) nodes. With this new change, when you describing your configuration as we explained in Set up and deploy on-premises environments (Platform update 41 and later) - Finance & Operations | Dynamics 365 | Microsoft Docs, you should edit the configtemplate.xml to add the new node types like following:
Now, in platform 41 and higher a new change was introduced to have SSRS with high availability Configure high availability for SQL Server Reporting Services (SSRS) nodes - Finance & Operations | Dynamics 365 | Microsoft Docs
In the same way that above configuration nodes, you must edit the ReportServerType section to define the SSRS servers and define the names for the report node cluster:
At the end, your configuration can have the following servers, depending on the requirements of your implementation:
Additionally, in the configurationtemplate.xml you will see that exist a new parameter to generate the ADCS certificates and not use the self-signed certificates.
Self-signed certificates can be used only for testing purposes. For the sake of convenience, the setup scripts that are provided in LCS include scripts that generate and export self-signed certificates. If you're using self-signed scripts, you will be instructed to run the creation scripts during later steps in this topic. As has been mentioned, these certificates can be used only for testing purposes.
Important: Microsoft plans to discontinue support for the generation of self-signed certificates through the setup scripts, in favor of automatic certificate creation through AD CS, so its time to plane implement Active Directory Certificate Services if your does not have this in your local infrastructure.
If you have any questions you can leave it in the comments or the Local Business Data Yammer group is available. There, you can post any questions or feedback that you have about the on-premises deployment.
Business Applications communities