Janos Varga

Check out the difference between
[powershell]Get-NetAdapter | Select-Object -ExpandProperty InterfaceAlias[/powershell]
and
[powershell]Get-NetAdapter | Select-Object InterfaceAlias[/powershell]

Do you catch the difference? That’s PowerShell-related, not Get-Netadapter related. 🙂

You may also use [powershell](Get-NetAdapter).InterfaceAlias[/powershell]

Cheers

Hi Emanuel!

Every answer I get is like a new window of knowledge! Thank you!

I’ve actually used something similar to your 2nd suggestion. In fact, here’s my test code:

Invoke-Command -VMName Win10VMTest004 -ScriptBlock {
$InterfaceIndex = Get-NetAdapter | Select-Object InterfaceIndex
$InterfaceAlias = Get-NetAdapter | Select-Object InterfaceAlias
Write-Output $InterfaceAlias
If ($InterfaceAlias -eq “Ethernet 2”)
{
$InterfaceIndex = $InterfaceIndex4Set
Write-Output $InterfaceAlias, $InterfaceIndex4Set
}}

However, using the 1st write-output that I’ve placed to trace where the process flows through, I’ve found out that it doesn’t enter or satisfy the IF statement. It displayed this:

InterfaceAlias PSComputerName RunspaceId
————– ————– ———-
Ethernet 2 Win10VMTest004 ffd983d1-21bf-42af-b123-bb0ec402dd3f
Ethernet Win10VMTest004 ffd983d1-21bf-42af-b123-bb0ec402dd3f

I need to ‘catch’ Ethernet 2. Suspecting that the second value ‘Ethernet’ is overwriting the 1st value ‘Ethernet 2’, I’ve tested a code where the IF tries to catch ‘Ethernet’ only. To no avail.

You’re right, YouTube videos will surely do a lot of help also.

Thank you! Your replies are always very helpful and enlightening.

Hi.
You can do it in several ways:

(Get-NetAdapter).InterfaceIndex
or save everything in a variable and then use it in a similar way.
$Nics = Get-Netadapter
$Nics.InterfaceIndex

or

Get-NetAdapter | Select-Object -ExpandProperty InterfaceIndex

These approaches are applicable to pretty much all PowerShell commands, not really to this one in particular. If you’re new with PowerShell, getting comfortable with these concepts will be of great help. There are quite a few PowerShell courses on Pluralsight that could be a boost for you at this stage (pretty much anything from Jeff Hicks would be an excellent choice, but start with the “beginner” courses). Pluralsight is not free, but it’s completely worth the investment, and it’s roughly the cost of a Netflix subscription. 🙂
(I’m not affiliated in any way with them, but it helped me and I learned a lot).
Alternately, there are tons of free resources on YouTube and elsewhere. The only limit is your time. And your curiosity. 🙂

Hi Emanuel!

This is great help. However, how do I get the value of InterfaceIndex only? If my guess is correct, the code you provided will dump all of what’s contained in Get-NetAdapter.

Thank you!

Hi, Lee Roy (and Anthony).

You could do something like
$info = Invoke-Command -ComputerName Dc01,FS03 -ScriptBlock {Get-NetAdapter}.
to store the info in the variable $info.

However, for Get-Netadapter you don’t need Invoke-Command. Get-Netadapter can get info from remote systems .
$info = Get-NetAdapter -CimSession Dc01,FS03

Hi Emanuel!

Invoke-Command is now my new best friend!

In fact, I’ll also be using it for a code to extract the value of InterfaceIndex (thru Get-Netadapter). But how do I get the value/s of the property/ies (like InterfaceIndex and InterfaceAlias) of Get-Netadapter and use it/them, say move the value/s to a variable/s?

Thank you!

Is there a way to get the value of InterfaceIndex and move it to a variable?

I got this error when run that script. Please help

I got this error when run that script. Please help

Export-Csv : Cannot bind parameter ‘Delimiter’. Cannot convert value “NoTypeInformation” to type “System.Char”. Error: “String must be exactly one
character long

Please help. I got below error when run script

Export-Csv : Cannot bind parameter ‘Delimiter’. Cannot convert value “Encoding” to type “System.Char”. Error: “String must be exactly one character
long.”
At D:MyselfPSToolsCollectingSystemStability&ProblemOri.ps1:5 char:102
+ … ERPROFILEDocumentsReliabilityStabilityMetrics.csv ‑Encoding ASCII – …
+ ~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Export-Csv], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.ExportCsvCommand

Export-Csv : Cannot bind parameter ‘Delimiter’. Cannot convert value “Encoding” to type “System.Char”. Error: “String must be exactly one character
long.”
At D:MyselfPSToolsCollectingSystemStability&ProblemOri.ps1:6 char:84
+ … V $env:USERPROFILEDocumentsReliabilityRecords.csv ‑Encoding ASCII – …
+ ~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Export-Csv], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.ExportCsvCommand

The -h switch of PsExec takes care of elevation problems. By the way, if nothing else works, you could use regular PowerShell remoting command like this:

Invoke-Command -ComputerName remoteServer -FilePath D:ScriptsyourScript.ps1 -Credential domainadmin

But how can one use Psexec to execute a PowerShell script on a Windows server, and inject domain username/password (eg. Create-FailoverCluster that requires permissions to create AD computer object)?

The user invoking the PowerShell script is NT AUTHORITYSYSTEM (from an Azure DevOps automated pipeline), but need the PS1 file to run with domain credentials. I can get the username and password to the script, but seems that it is not allowed to elevate the creds.

Any advice?

You’re welcome, Lee

Hi Emanuel!

This is great! I’ll go ahead and try.

Thank you so much!

In this case, PowerShell Direct is your friend. The VM needs to be on, but otherwise you can run the commands from the host. If the VMs are not in the same domain as the hosts, you can specify different credentials.

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/powershell-direct#run-a-script-or-command-with-invoke-command

Hi Emanuel!

Thank you for replying! Well, my situation is that I need to run your commands ‘outside’ the VM. Sorry for the newbie term (‘coz I’m exactly that – a newbie). Specifically, the Set-DNSClientServerAddress command. This command necessitates me to be ‘inside’ the VM so I can change it’s DNS IP address. I need to do this while I’m ‘outside’ the VM. In fact, I’m adding this line of code to a Powershell syntax that automates VM creation installed with a virtual hard drive (to also automate OS installation) plus setting up virtual network connection with a specific DNS server. The part with the DNS server that I have to specify for the VM is the tricky part for me.