Wednesday, July 26, 2017

Microsoft Dynamics 365 for Finance and Operations, Enterprise edition (on-premises) - Installation PART 2


Again here with the second part about the D365FO On-premise installation.

Before to Create the AppFabric Cluster, modify the ClusterConfig.json file created before and set the "diagnostics file share" path. This one will be use during the Installation process through all AppFabric nodes.

If during the Cluster installation you raised the error "Request is Invalid" check if the Primary NodeType (Orchestrator) have at least 3 Nodes!

Again, if during the Cluster installation you raised the error "Timed out waiting for Installer Service to complete for machine..."

You have to:

1- Verify if the Certificate are been installed in the Local Machine Node

2- Add the NETWORK SERVICE account for all certs used by Service Fabric.
In order to do this you have first download and install in all Cluster Nodes the WinHttpCertCfg.exe tool, Windows HTTP Services Certificate Configuration Tool (WinHttpCertCfg.exe)
Lastly, run the command for all Certificates in all Cluster Nodes, like "C:\Program Files (x86)\Windows Resource Kits\Tools\WinHttpCertCfg.exe" -g -c LOCAL_MACHINE\MY -s "" -a "NetworkService"

Till soon!


Johanna said...

Hi Denis,

Do you use environment (multiple VM) like in ?

Do you use self-signed certificate?

I am still got timeout issue when I setup standalone service fabric cluster.
I am using self-signed certificate.

Anonymous said...

Hi Denis,

thanks for your tips.
Do you know if we need to set up all nodes named in the minimal system reuirements (three AOS nodes, three orchestrator nodes, one management reporter node and one SSRS node) in the cluster? Or is it possible to configure a system with only one AOS and one Orchestrator node for testing puposes?
Setting up at least eight nodes with appropriate resources just for testing is a bit over the top..


Denis Macchinetti said...

Hi Johanna

Yes and for the Test Env I used the self-signed certificates generated by the Powershell scripts.

About timeout, you have followed my findings?

Denis Macchinetti said...

Hi Julius

As per my experience, is mandatory that the Cluster Primary NodeType (Orchestrator) is built at least from 3 Nodes.
So, the AOSNodeType, ReportServerType, etc. could be only one Node.

Sebastian said...

Hi Denis,
thanks for posting your results!

is it possible to use the same server for the 3 nodes (Orchestrator)
and is it possible to install an onpremise without management reporter
and is it possible to use the same server for sql & ssrs ?


Denis Macchinetti said...

Hi Sebastian

Good remark about try to use the same server Orchestrator. I didn't try yet.
I don't know if the Cluster or the Deployment works.

I didn't launch yet the Deployment through LCS. I'll do it in the next days
So, I don't have an answer about the last two questions.
Anyway, I think is possibile.

I'll let you know

Sandra Johnson said...

Nice blogpost and thanks for sharing such useful information about Microsoft Dynamics. If you are looking for Microsoft Dynamics AX solution then you should visit atDynamics AX Partner Australia. DFSM Consulting has Microsoft Dynamics AX support, upgrade & implementation solutions for your business needs.