Edit

Share via

Add or remove a node from an existing environment

This article explains how to add or remove a node in your existing Microsoft Dynamics 365 Finance + Operations (on-premises) environment. It describes the generic procedures that can be used for any node type. Specific node types might require further steps. In this case, refer to the documentation for the node type or the service.

Add a node

To add one or more nodes to your existing environment, follow these steps.

  1. Ensure that you download the latest infrastructure scripts. Learn more in Update the infrastructure scripts. To complete this procedure, you must have version 2.23.1 or later of the scripts.

  2. Update the ConfigTemplate.xml file with the new node information.

  3. Run the following command to ensure that your cluster has all the node types defined in the ConfigTemplate.xml file.

    .\Update-SFClusterConfig.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -AddNodeTypes

  4. If the previous command generates a configuration file and doesn't state that all node types already exist in the cluster, you must update the Azure Service Fabric cluster with the new configuration file. Learn more in Update the Service Fabric cluster configuration.

  5. Run the following commands to generate the prerequisites for the new node.

    .\Export-Certificates.ps1 -ConfigurationFilePath .\ConfigTemplate.xml
.\Export-Scripts.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -D365FOVersion <version of fno currently installed>

  6. Run the following command to update the group managed service account (gMSA) account so that the new node can use it.

    .\Create-GMSAAccounts.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -Update

  7. Run the following command to ensure that the Service Fabric diagnostic store can be accessed by the new node.

    .\Configure-FileShares.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -FileShareReference "sfDiagnostics"

  8. Run the following commands to ensure that all prerequisites are installed for the new node.

    .\Configure-PreReqs-AllVMs.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -MSIFilePath <file-path> -ForcePushLBDScripts
.\Complete-PreReqs-AllVMs.ps1 -ConfigurationFilePath .\ConfigTemplate.xml

  9. Run the following command to validate that the new node meets all prerequisites.

    .\Test-D365FOConfiguration-AllVMs.ps1 -ConfigurationFilePath .\ConfigTemplate.xml

  10. Run the following command to add the new node to the Service Fabric cluster. This command should be run from an existing node in the cluster.

    Note

    Run this command once for each new node that you want to add to the cluster.

    .\Add-ServiceFabricNode.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -VMName <vm name>

  11. Wait until all the new nodes are added to the cluster and any services are deployed to them.

  12. Run the following command to generate an updated cluster configuration file.

    .\Update-SFClusterConfig.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -UpdateServiceFabricSettings

  13. Update the Service Fabric cluster with the new configuration file. Learn more in Update the Service Fabric cluster configuration.

  14. Cycle through the application installation. To cycle the application installation, follow these steps:

    • In Lifecycle Services, open the on-premises implementation project.

    • In the on-premises implementation project, open Environment details of the environment to you added the node(s) too.

    • Maintain, select Update Settings.

    • Select Prepare to prepare your on-premises environment for servicing.

      Note

      While the environment is being prepared for servicing, its state is Deployed. The Deployment status field shows the progress of the preparation. During preparation, actions such formatting the package and downloading the package are performed.

      Because the environment isn't directly touched during preparation, there is no downtime at this point. Users can continue to use the system during preparation.

    • After preparation is completed, Abort and Update Environment buttons appear. To start to apply the update, click Update environment.

    • In the confirmation message that appears, select Yes. The servicing operation begins on the environment and this starts the downtime on your environment.

    • The environment state is changed from Deployed to Deploying.

    • After the update is completed, the environment state is changed back to Deployed. If application of the update fails, the environment state is changed to Failed.

Remove a node

To remove one or more nodes from your existing environment, follow these steps.

  1. Run the following command to generate an updated configuration file that instructs Service Fabric to remove the nodes. This command should be run from an existing node in the cluster.

    Note

    This command is case-sensitive.

    .\Update-SFClusterConfig.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -RemoveNode -NodeNames @("node1", "node2")

  2. Update the Service Fabric cluster with the new configuration file. Learn more in Update the Service Fabric cluster configuration.

  3. After the Service Fabric cluster configuration is updated, you must run the following command to clean up the nodes from the cluster configuration.

    .\Update-SFClusterConfig.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -CleanupRemoveNode

  4. Update the Service Fabric cluster with the new configuration file. Learn more in Update the Service Fabric cluster configuration.