Dynamics 365 On-Prem

Want to get a better idea where your Local Business Data (LBD) / On Prem deployment is when you are deploying a new package to it during servicing? Here are a few areas to check.


First, once a package has been prepared and downloaded, you can check what is happening with it by finding the orchestrator that has the "ArtifactsManagerPkg" installed on it. In the Service Fabric Explorer, expand the orchestrator nodes then LocalAgent and look for the package.

Create a cluster with 4 nodes for Dynamics 365 for Finance and Operations

Restarting an AOS in AX 2009 and 2012 is easy. Depending on the topology in D365, that can also be easy. However, performing the same action with Dynamics 365 For Finance and Operations on-premise isn't quite as easy because the service fabric is there. You have to ask the service fabric to restart the service rather just restart a windows based service. Here is the powershell that can restart the AXService.exe services for you which is, in simple terms, restarting the AOS.

Dynamics 365 For Finance and Operations has pretty decent documentation available on how to configure and setup an environment. However, some areas need some additional detail to really help them be ready for prime time. Specifically in the area of describing your proposed environment, things are sort of high level. The official documentation can be found here.

Learn how to run a database sync via command line for an Azure based instance of Dynamics 365 for Finance and Operations as well as how to perform the same action in an on premise environment.

Learn how to import and license file into Dynamics 365 For Finance an Operations for an azure based install plus how to do it in an on premise environment.

Deployment scenarios between AX 2012 and Dynamics 365 For Finance and Operations can now be compared with the on premise version, called Local Business Data, of Dynamics 365 For Finance and Operations, or F&O for short. Below we'll compare and contrast each scenario, sizing, latency, other hidden requirements as well as when you would select Dynamics 365 F&O in Azure or the LBD flavor.

AX 2012 / 2009

The initial document and ConfigTemplate.xml from Microsoft and LCS is actually pretty good. The instructions are somewhat high level in some areas leaving a few details out and also there is very little assistance when it comes to the configTemplate.xml file. Below are some additions I made to the standard file from LCS which I hope will help others. It is also available for download if you prefer.

After running through a few installs, I have come up with a simple list of suggestions to help streamline the process and eliminate a little of the headache. For reference, these are the official steps to follow from MS for PU12 can be found here.

Install Azure Powershell Extentions On Template (also, use a template)

When creating the on-premise connector or creating an environment to deploy, want to know where to source all of the values you are being asked for? There are some scripts to help.

Creating The On-premises Connector

Included with the scripts to setup the service fabric cluster is this one:

.\Get-AgentConfiguration.ps1 -ConfigurationFile .\ConfigTemplate.xml

This gives a nice table of output with almost everything you need to create the on-premise connector.