Friday, December 15, 2017

Use the same ADFS Server for multiple On Premises Environment - Dynamics 365 for Finance & Operations On Premises Installation

Hi All

According to the Microsoft documentation you should have an ADFS Server for each On Premise Environment.

As per my understanding, the reason is related to the workflowClientId that is an hard coded value in  the \Publish-ADFSApplicationGroup.ps1 Powershell script.
Check my post as well.

Due to this reason, in order to use the same ADFS Server you have to add a new Host in the Application definition of the ADFS:

  1. AD FS Manager > AD FS > Application Groups > open "Microsoft Dynamics 365 for Operations On-premises" 
  2. Open Native application "Microsoft Dynamics 365 for Operations On-premises - Native application" 
  3. Add Redirect URI of new environment (DNS) and select Add button to include > OK 
  4. Open Native application "Microsoft Dynamics 365 for Operations On-premises - Financial Reporting - Native application" 
  5. Add Redirect URI of new environment (DNS) and select Add button to include > OK














































Till Soon!

Monday, October 30, 2017

The client id must be unique across all clients - Dynamics 365 for Finance & Operations On Premises Installation

Hi Guys

To the same Customer I'm going to install the second On Premise Environment.

During the "Step 18 - Configure AD FS" I had run the following command in order to create the new Application:

 .\Publish-ADFSApplicationGroup.ps1 -HostUrl 'https://ax.d365foENVNAME.onprem.contoso.com' -ApplicationName 'Microsoft Dynamics 365 for Operations On-premises ENVNAME'

 Here I raised the error "The client id must be unique across all clients"

I checked the log wrote in the same folder as the script and I notice that the process failed to the script "D365FO-OP\D365FO-OP-ADFSApplicationGroup.psm1” at line 199

Here the "workflowClientId" is set with a fixed ID value.

I guess is a error so, I changed the line in:

"$workflowClientId = ([guid]::NewGuid())"

Before rerun the script, delete the partial Application created before through the ADFS Management Console

P.S.  The workaround above have an issue, the workflow doesn't work anymore. 
Unfortunately, I don't know where, Microsoft Dynamics 365FO search the Fixed Value...
I will create another post in order to explain how to modify the same Application in order to handle also other Environments.

Till Soon!



Sunday, October 29, 2017

Setup the AOS Balancing on AIF WEB Services or WHS Mobile Portal - AX 2012

Hi Guys

In an AX Environment with a huge AX Services workload, it is suggested to enable the AX Services Balance.

In order to do that, you have to:
  1. First, enable the NLB or ILB if you are working in Azure
  2. If you want enable the Balance through:

    • AIF Web Services
    • Remote Desktop Host Server
    • SSRS Services
    • Management Reporter

      You have to follow the standard link High Availability best practices for Dynamics AX 2012 in order to setup the Balance through the Dynamics AX Configuration Utility.
      You have to do that on each Servers listed above.

      Practically you have to:
    • Through the Dynamics AX Configuration Utility create a new Configuration on “Local Client” and on “Business Connector” Target. You can named it “Balance”
    • On both Configurations, in the Connection Tab fill “Server Name” with the IP or Name of the Balance
    • Through the Registry (HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE) at the path “\Software\Microsoft\Dynamics\6.0\Configuration\new_configuration_name” create two key “wcflbservername” and “wcflbwsdlport” and fill them respectively with the Balance IP or name and the Wsdl Port
      “new_configuration_name” will be the new AX Configuration created
    • Come back to the AX Configuration Utility and refresh both configurations with the “Refresh Configuration” button


  3. If you are using the WHS Mobile Portal, modify the “Web.config” file that usually is store at “C:\Dynamics60\Warehouse Mobile Devices Portal\00” and modify the endpoint with your “Balance” IP or Name:


Talking about AIF Web Services or WHS Mobile Portal, in some cases, you have to create also an IIS Farm in order to balance the IIS Connections. If you are working on Azure you have to use the Azure Application Gateway in order to do that.

Till Soon!

Tuesday, October 24, 2017

High Availability AX 2012 Links

Hi All

I would like to share some useful links about how to handle the High Availability through AX 2012:


  1. High Availability best practices for Dynamics AX 2012
  2. Configure SSRS for load balancing in your Azure deployment
In the next days I will share in detail how to setup the "Services High Availability", in order to balance the WHS Mobile Portal and the AIF Web Services, especially in Azure using the ILB (Internal Load Balancer).

Till Soon!

Sunday, October 22, 2017

Empty Database in your VHD All-in-one Machine - Microsoft Dynamics 365 for Finance & Operations

Hi All

As you know, in an Azure Sandbox Environment you can decide if create it with or without Data.

This is not possible when you download the VHD All-in-one machine.

In order to achieve this result from my understanding there are two options:
  1. André post, https://kaya-consulting.com/how-to-start-with-empty-ax-database-in-your-local-vm/ where you have to create before the Env in Azure with an Empty Database, Backup it and move to your VHD
  2. I have Play around to the VHD Disk C and I notice a folder named “EmptyDataset” with inside a Database backup named “AxBootstrapDB_Empty.BAK”
    I have simply restore this backup file against the AX Database and set the right GUID and email id retrieved from the “old” AX Demo Data.

Till soon!

Saturday, October 21, 2017

Microsoft Dynamics 365 for Finance & Operations - Change the standard URL in a VHD Machine

Hi All

In a Business scenario, we can setup several VHD all-in-one box Environments in the same Datacenter for various purpose.
One issue is the standard base URL that usually is https://usnconeboxax1aos.cloud.onebox.dynamics.com/ for all Envs.

In order to change it and allow the team to reach the different Envs, for each Dev Box replace “usnconeboxax1aos” with the desired URL like “XXXXXXX”:

1-  Modify Endpoint URL on IIS

2- Modify web.config files in the C:\AOSService\webroot and replace all standard “url name” entries with the new one (XXXXX)

3- Modify wif.services.config as per the previous step 

4- Modify “Host” file on C:\Windows\System32\drivers\etc like that:
127.0.0.1           xxxxx.
cloud.onebox.dynamics.com

5-  Change the “hosts” file on C:\Windows\System32\drivers\etc in your Laptop, like:XX.XX.XX.XX     xxxx.cloud.onebox.dynamics.com 
where XX.XX.XX.XX will be the IP of the VHD Box
You have to add an entry for each VHD URL Env.

6- As the last step, make the Admin User Provisioning


Till Soon!


Wednesday, July 26, 2017

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

Hi

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 "client.xxxxx.com" -a "NetworkService"

Till soon!