You can find all the necessary and updated information regarding Setup and Deployment of on premises Environments here   

Catching up from the previous post ,

we have prepared our Vm’s for the service Fabric Installation , and executed following scripts on each vm ,

  1. .\Configure-PreReqs.ps1 -MSIFilePath <path of the MSIs>
  2. .\Add-GMSAOnVM.ps1
  3. .\Import-PfxFiles.ps1
  4. .\Set-CertificateAcls.ps1
  5. .\Test-D365FOConfiguration.ps1

If  Test-D365FOConfiguration.ps1 gives any errors , resolve them before moving forward with the install , recheck configTemplate , for any typos , and rerun the scripts on all machines , After that

Download the Service Fabric standalone installation package onto one of Service Fabric nodes.Unzip File. Ensure the infrastructure folder has access to this folder.

Navigate to the infrastructure folder and execute the following command to generate the Service Fabric ClusterConfig.json file

.\New-SFClusterConfig.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -TemplateConfig <ServiceFabricStandaloneInstallerPath>\ClusterConfig.X509.MultiMachine.json

Copy the generated ClusterConfig.json file to the <ServiceFabricStandaloneInstallerPath>.

Navigate to the <ServiceFabricStandaloneInstallerPath> in Windows PowerShell by using elevated privileges.

Run the following command to test ClusterConfig.

.\TestConfiguration.ps1 -ClusterConfigFilePath .\clusterConfig.json



make sure that  no previous artifacts from a failed deployment are there , if you haven’t changed the default installation directory , you can may find previous artifacts at C:\programdata\SF ,

If the test is successful, run the following command to deploy the cluster.

.\CreateServiceFabricCluster.ps1 -ClusterConfigFilePath .\ClusterConfig.json

this will download fabric run time package , before installing on the machines , it may take some time  ,


Service fabric Explorer

https://<servicefabric DNSName>:19080



you would be able to see this , after successful installation . after this   , you need to setup  a certificate to your Azure Portal  for LCS connectivity .

Follow the Link provided above for the below configurations , i am just highlighting some areas .

LCS connectivity for the tenant

Azure Ad is just required for LCS Connectivity , you do not have to setup  , AD for user Authentication ,

your Local AD  DS and AD FS will do that job , if you have office 365 account that would be enough for Azure AD , you do not need to buy any  extra subscription for that ,

thumbprint would be of  your local agent certificate , you can copy/paste it from configTemplate.

Set up file storage

setup 2 file shares as prescribed in the official link mentioned above at the top of the post

make sure to add all the necessary permissions , as mentioned .

Self-signed certificate for a Clustered SQL instance

create SSL certificates , based on your infrastructure design , either always on group , or clustered installation , if you are going with the single instance installation , follow the guidelines for clustered instance.

 Configure the databases

Run all the scripts in the configure Database section , and make sure you dont get any errors , if you do , sort those errors first , before , proceeding with the install ,

you will run scripts for Orchestrator Database , that would be utilized by the local agent , AXDB and Financial Reporting  Databases ,scripts will add necessary permissions for your accounts as mentioned in configTemplate.


Install SSIS on AOS Machines in Native mode


Configure SQL Server Reporting Services for an on-premises deployment. follow the instructions in the link , they are  pretty much straight forward .


Run the scripts provided for ADFS Configurations , you may arise an error while running scripts related to ADFS , error may arise due to a missing descriptor , in my case it was ‘allatclaims’ ,add it to the descriptors and rerun the scripts .

Do make sure to Copy ADFS server Certificate to all  AOS  Node Types.

After completing these steps successfully you are done with your machines configurations , now you need to setup local agent and deploy the environments , that we will discuss in the next post.



Leave a Reply

Recent Comments