New Question

Revision history [back]

click to hide/show revision 1
initial version

Hello,

First of all, according to https://technet.microsoft.com/en-us/library/jj130875(v=wps.630).aspx, "Not all network adapters support setting the VLAN ID". In order to debug this issue, you might need to check the network card hardware information and/or your network infrastructure for VLAN support.

Secondly, Set-NetAdapter has no "Force" parameter. You can use -Confirm:$false to bypass execution prompt.

In order to help, can you elaborate more on your use case scenario? for example, is your Windows Server 2012 already virtualized?

Thank you.

Hello,

First of all, according to https://technet.microsoft.com/en-us/library/jj130875(v=wps.630).aspx, "Not all network adapters support setting the VLAN ID". In order to debug this issue, you might need to check the network card hardware information and/or your network infrastructure for VLAN support.

Secondly, Set-NetAdapter has no "Force" parameter. You can use -Confirm:$false to bypass execution prompt.

In order to help, get to the root cause, can you elaborate more on your use case scenario? for example, is your Windows Server 2012 already virtualized?

Thank you.