Share This Post

Deployment

D365 On-premises Deployments Local Agent Updation

This article explains how to update the D365 On-premises Deployments Local Agent. The latest version of the local agent is version 2.1.1.

The on-premises solution allows you to deploy MS Dynamics 365 either on your own servers or those of your IT partner. You can keep all your data in-house and ensure high levels of security and accessibility.

The on-premise deployment option uses Finance and Operations components running on the premises, leveraging service fabric standalone clusters.

D365 On-premises Deployments Local Agent Version Capabilities

  • Null

This initial version deploys Platform update 8.

  • 1.0.0

This version enables the Reconfigure feature for failed deployments.

  • 1.1.0

This version enables the Reconfigure feature for successful deployments, enables multi-model package deployments and deploys Platform update 8 and 11.

  • 2.0.0

This version enables servicing flows and deploys Platform update 12.

  • 2.1.0

This version enables two-phased servicing where Preparation and Update are two separate steps.

  • 2.1.1

This version fixes an issue that occurs when the download fails and the LCS Maintain button is not available. Additional changes include updates to Azure storage libraries to improve communication with Azure storage and enable TLS 1.

D365 On-premises Deployments Local Agent Features

  • Local Agent 2.1.0

    • Local agent 2.1.0 enables the two-phased servicing where Environment preparation and Environment update are two distinct steps and explicit actions.
    • This reduces the total downtime customers must take when applying updates to their on-premises environments by preparing upfront and allowing users to use the environment during preparation and then communicating the downtime when the actual update environment action is triggered.
  • Local Agent 2.0.0

    • Local agent 2.0.0 can deploy Platform update 12.
    • It permits the Reconfigure feature until the first deployment of Platform update 12 succeeds.
    • It disables the Reconfigure feature on the first successful deployment of Platform update 12.
    • After deployment succeeds, you can use the regular update experience to update the environment.

Downloading Latest D365 On-premises Deployments Local Agent

You must have version 2.0.0 or later to deploy Platform update 12 and complete update flows.

  • In LCS, choose the Project settings > On-prem connectors.
  • Select the connector to your environment, and then select Edit.
  • On the menu on the left side of the page, choose Setup host infrastructure and then choose Download agent installer.

You must now verify that the zip file that is downloaded is unblocked.

  • Navigate to the zip file, right-click it, and then select Properties.
  • In the Properties dialog box, choose Unblock and then choose Apply.
  • On the Configure agent tab, select Download configurations to download the localagent-config.json configuration file.

Updating the D365 On-premises Deployments Local Agent

You must utilize the current agents binaries to clean up the agent. If you don’t have the current agent’s binaries, you can delete the local agent application from Service Fabric Explorer.

  • Replicate the zip file and the localagent-config.json file into one Orchestrator nodes, such as c:\DynamicsAgent in the Orch1 virtual machine (VM).
  • Unzip the agent installer to C:\DynamicsAgent\LocalAgent.
  • Copy the localagent-config.json file to C:\DynamicsAgent\LocalAgent.
  • In a Command Prompt window, navigate to C:\DynamicsAgent\LocalAgent, and run the following command.

LocalAgentCLI.exe Cleanup <path of localagent-config.json>

  • Press any key to exit the cleanup operation.
  • Authenticate that the local agent has been successfully cleaned up by looking in Service Fabric Explorer and making sure that there are no apps in the Deployed Applications section in the Orchestrator nodes.
  • After the local agent is successfully cleaned up, run the following command.

LocalAgentCLI.exe Install <path of localagent-config.json>

  • After the local agent is successfully installed, navigate back to your on-premises connector in LCS.
  • On the Validate setup tab, select Message agent to test LCS connectivity to your new local agent.

Configuring Proxies for On-premises Environments

You may want to secure the Microsoft Dynamics 365 for Finance and Operations on-premises environment behind a proxy. Proxy is a server that hides the actual servers serving traffic from the clients. The proxy server accepts requests from the clients on behalf of the Finance and Operations environment and forwards the traffic to it.

The clients are not aware of the actual servers that compose the Finance and Operations environment. This adds another measure of security and enables load balancing.

Configure the Proxy

Perform the following steps in each node of type OrchestratorType in the Microsoft Azure Service Fabric cluster.

  • Use remote access to connect to the Orchestrator virtual machine (VM).
  • Execute the following PowerShell script to retrieve the path of the machine.config file.

[System.Runtime.InteropServices.RuntimeEnvironment]::SystemConfigurationFile

  • Edit the machine.config file to add the following code example.
<system.net>
<defaultProxy enabled=”true” >
<proxy <<<SET YOUR PROXY SETTINGS>> />
</defaultProxy>
</system.net>
  • Save the file.
  • Restart the virtual machine.

The above procedure must be performed for all Orchestrator node VMs. For more information on MS D365 On-premises Deployments Local Agent Updation, please contact us.

Share This Post

Leave a Reply

avatar
  Subscribe  
Notify of
Skip to toolbar