Unable to remove the service fabric due to there are 2 primary nodes.

Config validation: There should be exactly one NodeType marked as primary. Currently there are Best Practices Analyzer determined evironment has an issue. Please see additional BPA log output RemoveCluster Exception: System.Fabric.FabricValidationException: Cluster Setup cancelled due to analyzer. Inspect details in DeploymentTrace

Error at Publish-ADFSApplicationGroup.ps1 when publish ADFS

Error at Publish-ADFSApplicationGroup.ps1

Failed at step 18. Configure ADFS:

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/setup-deploy-on-premises-pu12#configureadfs

There is only 2 applications have been installed in the Application Group:

Grant-AdfsApplicationPermission : MSIS7628: Scope names should be a valid Scope Description name in AD FS configuration.
At \\dc\Share\InfrastructureScripts-367323\D365FO-OP-ADFSAppliationGrouppsm1: 204 char:5

Solution: 

In ADFS Management
ADFS >> Service >> Scope Descriptions >> Add new
allAtClaims >> OK

Delete Application and publish it again.

Error at .\Add-CertToServicePrincipal.ps1 : Update to existing credential with KeyId 'xxx' is not allowed.

Error at .\Add-CertToServicePrincipal.ps1 -CertificateThumprint ...


New-AzureRmADSpCredential : Update to existing credential with KeyId 'xxx' is not allowed.
At \

Solution:

Remove-AzureRmADSpCredential -ServicePrincipalName "00000015-0000-0000-c000-000000000000" -KeyId xxx

Error at Test-D365CFOConfiguration.ps1 on AOS1: Regkeys haven't been added

Error at Test-D365CFOConfiguration.ps1 on AOS1:

Stop-D365FOServies: The following services still need to be stopped/disabled: [WAS], [W3SVC]
At \\dc\Share\InfrastructureScripts-367323\VMs\aos1\Configure-PreReqs.ps1:236 char:2
.
.
.
Register0D365FOStrongName : The following RegKeys haven't been added in order to disable strong name verification: [HKLM:\SOFTWARE\Microsoft\StrongName\Verification\*,a7cf325ee2c8a9ff]

SOLUTION:
.\Configure-PreReqs.ps1 -MSIFilePath \\DC\share\Tools
Then restart the VM >> TestConfiguration again.