I do not support this script, and you are running it on your own risk.It works for both because it’s not done with PowerShell v3, maybe I will update it to get it even better.I have tested this with Windows Server 2008 R2, Hyper-V Server R2, Windows Server 8 beta, Hyper-V Server 8 beta.You can download the Scripts from my Skydrive Edit the networkconfig.xml on the second hosts with the right order of the NICs.Run the Get-NICInformation.ps1 on the first host and check the NIC order.I can now copy the Set-IPAddressfromXML.ps1 and the networkconfig.xml to each Hyper-V hosts and edit the IP Addresses in the xml file, run the PowerShell file and I am done. #endregion $adapters = Get-WMIObject Win32_PNPSignedDriver | Where-Object #endregion Write-Host " by Thomas Maurer " -BackgroundColor Black -ForegroundColor White Write-Host " " -BackgroundColor Black -ForegroundColor White Write-Host " PowerShell Get-NICInformation " -BackgroundColor Black -ForegroundColor White # created by Thomas Maurer # last Update by $Author: tmaurer $ on $Date: 14:07:36 +0100 (Fr, ) $ # - #region # INFO Write-Host " " -BackgroundColor Black -ForegroundColor White # - # Powershell Get-NICInformation $Rev: 748 $ # (c) 2011 Thomas Maurer. If you have a GUI server you could do that via GUI or if you have a Windows Server Core or Hyper-V Server you can do this via netsh. I have created two Windows PowerShell scripts which make my life a lot easier.įirst I configured the first Hyper-V host and renamed all the Network adapters. With this knowledge you can start to automate this very easy. Maarten Wijsman did a blog post how you can do this on the Hyper-V.nu blog. Now there is a solution, you can sort your NICs by PCI bus and PCI slot. And if you build Clusters up to 16 Hosts you really don’t want to do that. Now some times this one is one of the only solutions, but it takes a lot of time to do this on every host. So you can see which port is active and then you can rename the network adapter. But for this you still have to know which MAC address is on which network adapter port.Īnother way to do it is to plug in the network cables one by one. One of the possibilities to find out which network card is the right one is to check the MAC address of the network adapter. If you are working a lot with Hyper-V and Hyper-V Clustering you know that something that takes a lot of time is configure the Hyper-V Host Network Adapters. First because most of the time you have a lot of NICs build into your host for the different Hyper-V and Cluster networks and secondly Windows names the NICs in a random way and this makes it hard to find out which network card is the right one. Maybe your first NIC on your Hyper-V Host01 is called “Local Area Connection 2” and on your second Hyper-V Host with the same hardware configuration the “same” NIC is called “Local Area Connection 3”.
0 kommentar(er)
