After recreate Network Intent in Azure Local, Azure Update Manager Failes in Environment Validator Exception

Question

After recreate Network Intent in Azure Local, Azure Update Manager Failes in Environment Validator Exception

Michael Mazzucca 51

Hi all,

we had an Bluescreen Problem with our Management Intent, so we decieded to delete this Intent and make a new Management and Compute Intent in azure Local 2504.

Now with the new Update 2505 we get an Error in the Environment Validator Exception in the azure update manager. In the Logs we can see that the script is searching for the old Intent, which result in an this error.
Somebody has faced this problem and now how to change this config, so that maybe the azure cloud will sync the changes?

Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-09T05:26:08.8866667+00:00

Hi Michael Mazzucca,

You attempted to resolve a Bluescreen issue by removing and recreating the configuration objects (Intents) that manage your Azure Local cluster's operations in azure Local 2504.

Now, you are trying with Azure Local 2505, and the validator throws an exception searching for an old intent, means that one or more nodes in your cluster still have configuration data or metadata referencing the deleted intent.

Check associated resources (like VM switches or edge device resources) were fully cleaned up on the affected node(s). Use PowerShell commands like Get-NetIntent and Get-VMSwitch on each Azure Local node to identify and remove any leftover resources related to the old intent

https://learn.microsoft.com/en-us/azure/azure-local/manage/troubleshoot-deployment?view=azloc-2503#remove-the-validation-error

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.

Michael Mazzucca 51

Thanks for your reply,

unfortunately, after try your advise the error still persists.

We disabled the management0 Adapter and deleted the management Intent.

In Eventlog I got the following Message:

Log Name: AzStackHciEnvironmentChecker

Source: AzStackHciEnvironmentChecker/Telemetry

Date: 09.06.2025 12:15:59

Event ID: 17205

Task Category: (1)

Level: Warning

Keywords: Classic

User: N/A

Computer: xxx

Description:

{

"Name":  "AzStackHci_Network_Test_HostNetworkConfigurationReadiness",

"DisplayName":  "Test if host network requirement meets for the deployment on all servers",

"Tags":  {

         },

"Title":  "Test host network configuration readiness",

"Status":  1,

"Severity":  2,

"Description":  "Checking host network configuration readiness status on 172.16.xx.xx",

"Remediation":  "Make sure host network configuration readiness is correct. Review detail message to find out the issue.",

"TargetResourceID":  "172.16.xx.xx",

"TargetResourceName":  "HostNetworkReadiness",

"TargetResourceType":  "HostNetworkReadiness",

"Timestamp":  "\/Date(1749464125401)\/",

"AdditionalData":  {

                       "Detail":  "On XXX:\nERROR: No VMSwitch is having the network adapter defined in the management intent\nERROR: Cannot find valid advanced property VlanId for adapter management0. Use Get-NetAdapterAdvancedProperty/Set-NetAdapterAdvancedProperty with parameter RegistryKeyword set to VlanId to verify and configure it.\nERROR: Cannot find valid RSS property for adapter management0. Adapter need support RSS. Use Get-NetAdapterRss to verify it.\nERROR: The following adapter(s) are not physical adapter or not Up in the system: management0. Intent adapters should be physical adapters and Up in the system.\nERROR: The following adapter(s) are already used by other intent in the system: compute1, compute2, compute3, compute4.\n       Intent adapters should not be used by other intent in the system.\nPASS: DNS Client configuration has valid data for all adapters defined in intent\nPASS: Hyper-V is running correctly on the system\nPASS: External VMSwitch ConvergedSwitch(compute_management) have 28 VMNetworkAdapter(s) attached to it\nPASS: Intent mgmt adapter(s) are not used by any other intent in the system\nPASS: Intent storage is already defined in the system with same adapter(s)",

                       "Status":  "FAILURE",

                       "TimeStamp":  "06/09/2025 10:15:25",

                       "Resource":  "HostNetworkReadiness configuration status",

                       "Source":  "172.16.XX.XX"

                   },

"HealthCheckSource":  "PreUpdate\\Standard\\Medium\\Network\\3d46b175"

}

Michael Mazzucca 51 Reputation points

2025-06-09T13:17:34.3666667+00:00

I've found the old configuration in Registry under Computer\HKEY_LOCAL_MACHINE\Cluster\ACS\RDictionary\ECEWinService\ECEWinService\ECEReliableStore\041DB82C52C9EA344B6B8572982ED646BE5C039A95D1CD411DC5187B35FE2CB1
Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-10T09:17:03.2333333+00:00

Hi Michael Mazzucca,

Thanks for the reply.

Try to clean up existing configurations left behind by an old intent on Azure Local nodes

If the Network ATC was already enabled, Stop the Network ATC service and remove existing virtual switches and NetQos configuration and make sure that no LBFO team is configured.

After successfully completing above steps, start the Network ATC service.

Please check the similar workaround documentation for more detailed steps mentioned here

https://learn.microsoft.com/en-us/azure/azure-local/upgrade/install-enable-network-atc?view=azloc-2505#example-intents

https://learn.microsoft.com/en-us/azure/azure-local/upgrade/install-enable-network-atc?view=azloc-2503#step-4-remove-previous-configurations

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.

1 answer

Your answer

Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-09T05:26:08.8866667+00:00

Hi Michael Mazzucca,

You attempted to resolve a Bluescreen issue by removing and recreating the configuration objects (Intents) that manage your Azure Local cluster's operations in azure Local 2504.

Now, you are trying with Azure Local 2505, and the validator throws an exception searching for an old intent, means that one or more nodes in your cluster still have configuration data or metadata referencing the deleted intent.

Check associated resources (like VM switches or edge device resources) were fully cleaned up on the affected node(s). Use PowerShell commands like Get-NetIntent and Get-VMSwitch on each Azure Local node to identify and remove any leftover resources related to the old intent

https://learn.microsoft.com/en-us/azure/azure-local/manage/troubleshoot-deployment?view=azloc-2503#remove-the-validation-error

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.
Michael Mazzucca 51 Reputation points

2025-06-09T13:17:34.3666667+00:00

I've found the old configuration in Registry under Computer\HKEY_LOCAL_MACHINE\Cluster\ACS\RDictionary\ECEWinService\ECEWinService\ECEReliableStore\041DB82C52C9EA344B6B8572982ED646BE5C039A95D1CD411DC5187B35FE2CB1
Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-10T09:17:03.2333333+00:00

Hi Michael Mazzucca,

Thanks for the reply.

Try to clean up existing configurations left behind by an old intent on Azure Local nodes

If the Network ATC was already enabled, Stop the Network ATC service and remove existing virtual switches and NetQos configuration and make sure that no LBFO team is configured.

After successfully completing above steps, start the Network ATC service.

Please check the similar workaround documentation for more detailed steps mentioned here

https://learn.microsoft.com/en-us/azure/azure-local/upgrade/install-enable-network-atc?view=azloc-2505#example-intents

https://learn.microsoft.com/en-us/azure/azure-local/upgrade/install-enable-network-atc?view=azloc-2503#step-4-remove-previous-configurations

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.

Answer 1

Michael Mazzucca 51

Hi, so i tried the steps mentioned above, but with no changes. The Error persists and the Update over the Azure Portal does not work.

I think the config must be somewhere in the Azure Cloud. I searched in the registry and in all files for the wrong entries and tried to rename it but with no result. Someone has any idea

Markapuram Sudheer Reddy 2,050 Reputation points Microsoft External Staff Moderator

2025-06-25T04:44:18.8566667+00:00

Hi Michael Mazzucca,

Check by cleaning up the Edge Device Azure Resource. On the edge device, use PowerShell to remove any old or incorrect VM switches and network intents and recreate the correct network intents

and refresh the cloud edge Devices data.

Now, ensure the physical adapters and VM switches on the edge device now match the intended configuration.

With device and cloud data now back in sync, you can go to the Azure portal and restart the deployment.

Please check the documentation for more information: https://learn.microsoft.com/en-us/azure/azure-local/manage/troubleshoot-deployment?view=azloc-2503#clean-up-the-edge-device-azure-resource-with-incorrect-vm-switch-information

You can also get deployment issues support for Azure Local by following the steps mentioned here.

If you have any queries, please do let us know, we will help you.

Share via

After recreate Network Intent in Azure Local, Azure Update Manager Failes in Environment Validator Exception

1 answer

Your answer