How to get system diagnostics working on environments deployed in customer/partner subscriptions

With a purchased Azure subscription, customers and partners can deploy a Microsoft Dynamics 365 for Finance and Operations, Enterprise edition environment by using the Cloud Hosted Environments feature in LCS. Due to an issue in the environment deployment flow, system diagnostics was configured incorrectly in environments that were deployed after August 30th 2017. Because of this, key features in LCS such as the Updates tile, Performance dashboards, and other features are broken. To verify whether your environment is impacted by this issue, use the following list of symptoms to compare to your environment.


·         System Diagnostics and Detailed Version Information is not available from the LCS Environment page.

·         The LCS Environment page URL contains IsDiagnosticsEnabledEnvironment=false

·         The logs in the local administrator %AppData%\Roaming\JobLog folder contains invalid algorithm specified errors.


To fix this issue and get the Update tiles, system diagnostics, and SQL Insights performance dashboards working again, complete the following steps.

  1. Login to LCS and select the Shared Asset Library tile on the dashboard.
  2. Click the Model tab and download the System Diagnostics Hotfix folder.
  3. Using the local administrator account, remote into the machine that you want to fix. The account information is available on the Environment details page.
  4. Copy the hotfix archive to C:\Temp and extract it.
  5. From an elevated PowerShell command prompt, navigate to C:\Temp\’Extracted hotfix folder’ and run the LcsDiagHotfix_EnvironmentRegistration.ps1 script. When prompted, enter the password of the ‘axdbadmin’ user which is available on the Environment details page in LCS.

To run the script without being prompted for input or shown any output, use the following command line with the correct file paths and password for the database user:

PowerShell.exe -NonInteractive -Command “& {C:\Temp\LcsDiagHotfix_EnvReg_20170929\LcsDiagHotfix_EnvironmentRegistration.ps1 -LogFilePath C:\Temp\LcsDiagHotfix.log -DatabaseUserPassword (ConvertTo-SecureString -AsPlainText -Force -String ‘<Password>’); Exit $LastExitCode;}”

This will produce detailed output in C:\Temp\LcsDiagHotfix.log and return a non-zero exit code in case of any errors.

  1. After the script has completed, check the most recent LCS Diagnostics data collection logs in %AppData%\Roaming\JobLog. The latest log should show that a collection has started on this environment.
  2. Return to the environment in LCS and verify that the symptoms listed above are now fixed. The Update tiles take more time to refresh, but you should see detailed version information and the URL flag updated for this environment.
  3. If, after completing these steps, you still run into issues, log a support incident.