Deployment error "VlanID" vs "RegVlanID" Azure Stack HCI 23H2

Hampus Söderberg 0 Reputation points
2024-12-13T14:23:06.8366667+00:00

Hello!

I am trying to deploy Azure Local /Azure Stack HCI 23H2 using the "Deployment through portal" method. The deployment fails during network validation and network configuration steps. It seems to look for the "RegistryKeyword" "VlanID" while my network card has the RegistryKeyword "RegVlanid" instead.

As far as I know this is defined inside the NIC driver and therefore cannot be changed. Is there any way to proceed with this deplpoyment?
The NIC is a Realtek RTL868H.

PS>TerminatingError(Get-NetAdapterAdvancedProperty): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: No matching MSFT_NetAdapterAdvancedPropertySettingData objects found by CIM query for instances of the ROOT/StandardCimv2/MSFT_NetAdapterAdvancedPropertySettingData class on the CIM server: SELECT * FROM MSFT_NetAdapterAdvancedPropertySettingData WHERE ((Name LIKE 'Port0')) AND ((RegistryKeyword LIKE 'VlanID')). Verify query parameters and retry."

User's image

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
382 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sai Krishna Katakam 1,510 Reputation points Microsoft Vendor
    2024-12-13T21:24:46.4033333+00:00

    Hi Hampus Söderberg,

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    Based on the detailed explanation provided, the deployment issue you're encountering is due to a mismatch in the registry keywords for VLAN settings on your network card. Here are some steps which help to resolve this issue:

    Verify that your NIC driver is up to date. Sometimes, driver updates can resolve compatibility issues.

    Confirm that the Realtek RTL868H NIC driver is certified and compatible with Azure Stack HCI 23H2.

    If modifying the script is not feasible, consider using a different network adapter that uses the "VlanID" registry keyword.

    If an answer has been helpful, please consider accept the "Answer" and "Upvote" to help increase visibility of this question for other members of the Microsoft Q&A community. 

    User's image

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.