No compatible network adapters found - UCSC C220 M3S

Hi all
I am a little new at the Cisco servers so here is my question.
I have been trying to install esxi on our new C220 M3S server.
But after the installation I get to the esxi screen it says "No compatible network adapters found. Please consult ...... "
Any sugestions to what could be wrong ?
I have tried to install different versions of the esxi Cisco custom image (5.5 5.1 5.0) with the same result.
/Thomas

Hi wdey
Yes you assume correct. This is a standalone server.
Hardware wise this is a C220 M3S with two E5-2620-V2. 4 x 8 GB RAM. 4 x 300 GB Disk set up to Raid-5 on the 2008M-8i Mezzanine Card. And finally this server was shipped with the Flexible Flash "module" (I cant even remember we ordered that, but it was in there ... so :-) )
No extra NICs where added, i just have the two onboard Gigabit ports (Intel I350 Ethernet controller as far as i know ?).
I have installed the ESXi on the Flash module.
In my opinion this ought to be pretty straight forward, and I just cant see what Im doing wrong.
The only thing i have been "playing" around with was the CIMC configuration.
The default configuration was set to Shared LOM EXT. I changed that to "dedicated" to use the specific mgmt port for CIMC. (I have also tried to change it back just in case.)
Furthermore I have updated "everything" : BIOS, CIMC, 2008M-8i Mezzanine Card bios and so on. Nothing has helped.

Similar Messages

Pci card for UCSC-C220-M3S

<< Original post by Shai Edny. Answered by Robert Burns. Moving from documents section to discussions. >>
Hello
I have a small problem , I have a server UCSC-C220-M3S
And I want to know If this PCI card can work on this server ? (UCSC-C220-M3S)
The card : N2XX-ABPCI01 - Broadcom 5709 Dual-Port Ethernet PCIe Adapter .
Please Assist

This is a document forum - please post your question in the "Discussions" forum.
btw - check out -http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
Robert

UCSC-C220-M3S Raid goes "off line"

HI all,
I have a UCSC-C220-M3S with 4 hard drives and 8gb memory, I create a raid 0, until this point is ok, but after the devices reboots, and shows the hard drives and the raid, is says
raid is "off line"
Any ideas?
Thanks.

This is a duplicate of https://supportforums.cisco.com/discussion/12386576/ucsc-c220-m3s-raid-goes-line please remove this one.
-Kenny

Dell Precision T5610 ESXi install error (No network adapters)

Hi everyone, i am trying to install vmware esxi 5.5 to my dell precision T5610 workstation. However i'm getting "No network adapters were detected" error. I tried to install Dell Customized Image of VMware ESXi 5.5 but i get the same error again.
I tried customizing the esxi iso file with esxi customizer. but it is asking for .vib or tgz file of my network adapter. Where can i download vib file of my network adapter which is Intel 82579 Gigabit Ethernet Controller. What should i do in this step? Any suggestions?
Thanks.

Hi wdey
Yes you assume correct. This is a standalone server.
Hardware wise this is a C220 M3S with two E5-2620-V2. 4 x 8 GB RAM. 4 x 300 GB Disk set up to Raid-5 on the 2008M-8i Mezzanine Card. And finally this server was shipped with the Flexible Flash "module" (I cant even remember we ordered that, but it was in there ... so :-) )
No extra NICs where added, i just have the two onboard Gigabit ports (Intel I350 Ethernet controller as far as i know ?).
I have installed the ESXi on the Flash module.
In my opinion this ought to be pretty straight forward, and I just cant see what Im doing wrong.
The only thing i have been "playing" around with was the CIMC configuration.
The default configuration was set to Shared LOM EXT. I changed that to "dedicated" to use the specific mgmt port for CIMC. (I have also tried to change it back just in case.)
Furthermore I have updated "everything" : BIOS, CIMC, 2008M-8i Mezzanine Card bios and so on. Nothing has helped.

How can I use PowerShell to Remove "Ghost" (Old Hidden) VMware Network Adapters in Windows 7?

We recently upgrade the virtual hardware of some of our VMware VM's running Windows 7. One side-effect is that in Windows on these machines, an instance of the NIC from the previous version of virtual hardware remains, as a hidden
device. This can be easily found manually on a machine by enabling Device manager to show hidden devices (registry and a menu option - View...Show Hidden Devices). You can then just right-click on the device in question and uninstall.
The problem here, like in so many other tasks, is that you may have multiple instances, on multiple machines. We had just that, and in scouring the internet for a PowerShell only script to resolve the issue, I could not find one. Therefore, I've written
my own.
This exact script is only seeking out VMware "VMXNET3" nic cards, but could be easily adapted to find Ghost NIC's for a different vendor using my example. There are also some commented lines left in to aid you as an example of how you can
test the various queries in your own environment, on a test machine, before a full-blown deployment.
NOTE: Please try this out (at your own risk - I am not responsible for how this works out for you), and please vote for my answer to this dilemma if this helped you. I'd appreciate it after all of the sweat the script took to crank out.
Thanks!
P.S. This script, of course, requires that Powershell is installed and enabled on the target computer. It then must be run as System - In our environment it is being remotely pushed through a software delivery systems, which runs this scrpt
as system.
THE SCRIPT:
CLS
#Querying WMI for Ghost NICs and Returning Criteria...
Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
Write-Host ""
Write-Host "Checking Powershell Version" -Foreground Yellow
$host.version
Write-Host ""
Write-Host "Searching for Ghost NIC's" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
  Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
  Write-Host ""
  else
  Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
  Write-Host ""
  EXIT 0
#Using Criteria to Obtain the GUID of each Ghost NIC
Write-Host "Getting NIC Variables" -Foreground Yellow
foreach ($_ in $Ghosts) {
  $DID = $_.DeviceID
  If ($DID -NE $NULL)
  Write-Host "The NIC DID: $DID"
  else
  Write-Host "$DID is NULL - Exiting..."
  EXIT 666
  if($DID -NOTLIKE "1*")
   Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
   Write-Host ""
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000$DID"
  ELSE
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00$DID"
  $GUID = $NICREG.NetCfgInstanceId
  Write-Host "The NIC GUID: $GUID"
                $PNPDID = $NICREG.DeviceInstanceID
  $PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
  Write-Host "The truncated PNPDevice ID is $PNPDID"
  Write-Host ""
  Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
  $NICREGPATH = @(1..50)
  foreach ($_ in $NICREGPATH)
   $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
   if($TESTREG -EQ $FALSE)
    #Write-Host ""
    #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED
    ELSE
    #Write-Host "True - NIC $_ Exists" -Foreground Green
    $NICID = $_
    $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath1"
    $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath2"
    $NICProperties = Get-ItemProperty $SubPath1
    #$NICProperties
    $Match = $NICProperties.ServiceName
    #$Match
    foreach ($_ in $Match) {
    #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
    #Write-Host ""
    if($_ -NE $GUID)
    #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                               #Write-Host ""
    ELSE
    Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
    Remove-Item $SubPath1 -Recurse -ErrorAction SilentlyContinue
    Remove-Item $SubPath2 -Recurse -ErrorAction SilentlyContinue
    $CCS = @("ControlSet001", "ControlSet002")
    foreach ($_ in $CCS) {
     $CCS = $_
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
                                         if($DID -NOTLIKE
"1*")
              $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                         Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
       ELSE
       $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
       Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
#This is our Success check at the end
Write-Host ""
Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
          $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
  If ($Ghosts -NE $NULL)
  Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
  Write-Host ""
  EXIT 666
  else
  Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
  Write-Host ""
  EXIT 0

THE SCRIPT:
CLS
#Querying WMI for Ghost NICs and Returning Criteria...
Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
Write-Host ""
Write-Host "Checking Powershell Version" -Foreground Yellow
$host.version
Write-Host ""
Write-Host "Searching for Ghost NIC's" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
Write-Host ""
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0
#Using Criteria to Obtain the GUID of each Ghost NIC
Write-Host "Getting NIC Variables" -Foreground Yellow
foreach ($_ in $Ghosts) {
$DID = $_.DeviceID
If ($DID -NE $NULL)
Write-Host "The NIC DID: $DID"
else
Write-Host "$DID is NULL - Exiting..."
EXIT 666
if($DID -NOTLIKE "1*")
   Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
   Write-Host ""
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000$DID"
ELSE
   $NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00$DID"
$GUID = $NICREG.NetCfgInstanceId
Write-Host "The NIC GUID: $GUID"
                $PNPDID = $NICREG.DeviceInstanceID
$PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
Write-Host "The truncated PNPDevice ID is $PNPDID"
Write-Host ""
Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
$NICREGPATH = @(1..50)
foreach ($_ in $NICREGPATH)
   $TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
   if($TESTREG -EQ $FALSE)
    #Write-Host ""
    #Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED
    ELSE
    #Write-Host "True - NIC $_ Exists" -Foreground Green
    $NICID = $_
    $SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath1"
    $SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
    #Write-Host "The Sub-Key Path To Query = $SubPath2"
    $NICProperties = Get-ItemProperty $SubPath1
    #$NICProperties
    $Match = $NICProperties.ServiceName
    #$Match
    foreach ($_ in $Match) {
    #Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
    #Write-Host ""
    if($_ -NE $GUID)
    #Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
                                #Write-Host ""
    ELSE
    Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
    Remove-Item $SubPath1 -Recurse -ErrorAction SilentlyContinue
    Remove-Item $SubPath2 -Recurse -ErrorAction SilentlyContinue
    $CCS = @("ControlSet001", "ControlSet002")
    foreach ($_ in $CCS) {
     $CCS = $_
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
                                         if($DID -NOTLIKE
"1*")
              $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
                         Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
       ELSE
       $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
       Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
     $reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
     Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
#This is our Success check at the end
Write-Host ""
Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
          $Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "vm*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
Write-Host ""
EXIT 666
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0
Hello Octavio,
I'm having similar issues with azure VMs (windows server 2008 and 2012). I noticed that the name of the network adapter changes every time the servers are turned off and then on.
For example every time I perform that action on each VM, the network adapter became to "Microsoft Hyper-V Network Adapter #3" (and then #4, #5, etc).
I found in to many forums that to resolve that is needed to remove Hidden (Ghost) Network Adapters and most of the people is doing that manually from the device manager (right click on the hidden network adapter and select uninstall).
Then I found this script created by you and made some changes to find Description -like "Microsoft Hyper-V Network*".
It seems to find the adapters and also remove them (based on the script results). But if I go to the device manager after restarting the server, all hidden (ghost) adapters are still there (for example Microsoft Hyper-V Network Adapter
#2, Microsoft Hyper-V Network Adapter #3, Microsoft Hyper-V Network Adapter #4, Microsoft Hyper-V Network Adapter #n).
The only thing I noticed after running the script is that, in the Control Panel -> Network and Sharing Center, the name of the adapter has no # (Now is shown as “Ethernet” and before as “Ethernet #”)
This is my script, could you please take a look and tell me if there is something wrong o missing?
CLS
#Querying WMI for Ghost NICs and Returning Criteria...
Write-Host "VMware Ghost NIC Remover" -Foreground GREEN
Write-Host "Author: Octavio Serpa AKA Octavio-Admin"
Write-Host "Copyright Octavio Serpa - Octavio-Admin - 2014"
Write-Host ""
Write-Host "Checking Powershell Version" -Foreground Yellow
$host.version
Write-Host ""
Write-Host "Searching for Ghost NIC's" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "Microsoft Hyper-V Network*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "One or more ghost NIC'S do exist on this machine. Script will continue..." -foreground RED
Write-Host ""
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0
#Using Criteria to Obtain the GUID of each Ghost NIC
Write-Host "Getting NIC Variables" -Foreground Yellow
foreach ($_ in $Ghosts) {
$DID = $_.DeviceID
If ($DID -NE $NULL)
Write-Host "The NIC DID: $DID"
else
Write-Host "$DID is NULL - Exiting..."
EXIT 666
if($DID -NOTLIKE "1*")
Write-Host "Adding additional 0 to registry lookup since the DID is just one character..." - foreground yellow
Write-Host ""
$NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\000$DID"
ELSE
$NICREG = Get-ItemProperty "hklm:\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\00$DID"
$GUID = $NICREG.NetCfgInstanceId
Write-Host "The NIC GUID: $GUID"
$PNPDID = $NICREG.DeviceInstanceID
$PNPDID = $PNPDID.Trimstart("PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\")
Write-Host "The truncated PNPDevice ID is $PNPDID"
Write-Host ""
Write-Host "Searching for Registry Keys that match NIC GUID: $GUID" -Foreground Yellow
$NICREGPATH = @(1..50)
foreach ($_ in $NICREGPATH)
$TESTREG = Test-Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_" -Verbose
if($TESTREG -EQ $FALSE)
#Write-Host ""
#Write-Host "FALSE: HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\$_ DOES NOT EXIST" -Foreground RED
ELSE
#Write-Host "True - NIC $_ Exists" -Foreground Green
$NICID = $_
$SubPath1 = 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
#Write-Host "The Sub-Key Path To Query = $SubPath1"
$SubPath2 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\NetworkCards\'+$NICID
#Write-Host "The Sub-Key Path To Query = $SubPath2"
$NICProperties = Get-ItemProperty $SubPath1
#$NICProperties
$Match = $NICProperties.ServiceName
#$Match
foreach ($_ in $Match) {
#Write-Host "The NIC GUID found in this registry key is: $_" -Foreground Yellow
#Write-Host ""
if($_ -NE $GUID)
#Write-Host "NO MATCH - THIS NIC HAS NOT BEEN TOUCHED" -Foreground GREEN
#Write-Host ""
ELSE
Write-Host "MATCH - Registry Entries for this NIC will be DELETED" -Foreground RED
Remove-Item $SubPath1 -Recurse -ErrorAction SilentlyContinue
Remove-Item $SubPath2 -Recurse -ErrorAction SilentlyContinue
$CCS = @("ControlSet001", "ControlSet002")
foreach ($_ in $CCS) {
$CCS = $_
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Services\Tcpip\Parameters\Adapters\'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#PCI#VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01#$PNPDID#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\'+$GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\JNPRNA\Parameters\Adapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\NetBT\Parameters\Interfaces\Tcpip_' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Psched\Parameters\NdisAdapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Adapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\DNSRegisteredAdapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\Tcpip\Parameters\Interfaces\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\services\WfpLwf\Parameters\NdisAdapters\' + $GUID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
if($DID -NOTLIKE "1*")
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\000' + $DID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
ELSE
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00' + $DID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
$reg1 = 'HKLM:\SYSTEM\' + $CCS + '\Enum\PCI\VEN_15AD&DEV_07B0&SUBSYS_07B015AD&REV_01\' + $PNPDID
Remove-Item $reg1 -Recurse -ErrorAction SilentlyContinue -verbose
#This is our Success check at the end
Write-Host ""
Write-Host "Searching for any remaining Ghost NICs:" -Foreground Yellow
$Ghosts = gwmi win32_NetworkAdapter | ?{$_.Description -like "Microsoft Hyper-V Network*" -and $_.Installed -like "True" -and $_.MACAddress -eq $null}
$Ghosts | Select-Object Name,DeviceID
If ($Ghosts -NE $NULL)
Write-Host "There is still at least one ghost NIC present. The remover script may not be functioning correctly. Please contact Octavio-Admin on Microsoft Technet Forums with any questions" -foreground RED
Write-Host ""
EXIT 666
else
Write-Host "No ghost NIC's Found :) - Exiting..." -Foreground Green
Write-Host ""
EXIT 0

Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2. I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster. After upgrading the cluster I am unable to migrate some VMs from one node to another. When trying to do
a live migration, I get the following notifications under the Rating Explanation tab:
Warning: There currently are not network adapters with network optimization available on host Node7.
Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue.
I get this error for 3 out of the 4 nodes in the cluster. I do not get this error for Node10 and I can live migrate to that node in VMM. It has a green check for Network optimization. The others do not. These errors only affect
VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues. In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to. I've checked the network
adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM. I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
queue" and Enable IPsec task offloading" checked. I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1. Why is this an issue now but it wasn't before
running on the new cluster? How do I resolve the issue? VMM is useless if I can't migrate all my VMs with it.

I checked the settings on the physical nics on each node and here is what I found:
Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading". I unchecked those
2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
It seems to me that if I could adjust those VM settings from VMM that it might fix the problem. Why isn't that an option to do so in VMM?
Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager? That would be a lot of unnecessary work but I don't know what else to do at this point.

PDF documents which are made OCR compatible cant be found on AirPort Time Capsule 3TB Disk

Hi,
HW/SW : iMAC 27 OSX Mavericks 10.9.2
HW/SW : AirPort Time Capsule 3TB Disk Version 7.7.3
SW : Acrobat XI PRO 11.0.06
SW : ABBYY FineReader Pro 12.0.4
PDF documents which are made OCR compatible cant be found on latest TimeCapsule (folders).
I use my TC additionaly as drive to share across my Wi-Fi network.
When I save the folder on my Local MAC I search via finder/spotlight a word and the PDFs which have the words in the document show up but when I save the folder on the TimeCapsuleDisk they dont.
I use Acrobat XI PRO to make the PDF OCR capable and also ABBYY FineReader PRO
Saved OCR'ed PDF's on local disk of my iMAC
Saved OCR'ed PDF's on AirPort Time Capsule 3TB Disk ( latest firmware etc. )
Search via finder in Folders & "Spotlight"
PDF OCR'ed files popup on local MAC disk
PDF OCR'ed files (same folder c&p to TC) on TC disk do not popup ( clicked in search also on the specific folder but no finding )
The finder/Spotlight finds documents on TC "names" but looks like from my point of view, it does not go into the documents which are OCR capable to search for these words.
Why ?
Any possebility to solve this ?
Thanks and best regards,
Sandro

Did you ever figure this out?

LMS 4.2.2 Fault Discovery - Network Adapters Limit Exceeded

Running fault device discovery after adding approx 50 new devices to LMS DCR. It seems I have reached a limit in DFM with regards to how many device components it can manage. The devices are put into questioned mode and the following error is seen in the Question State Device Report
Network Adapters Limit Exceeded.The number of Network Adapters discovered by Fault Management exceeded the maximum supported limit.Please check on screen help for more information.
What is the limit that is being referred to here? Is it independent of the LMS device licence? Where can I see how many "network adapters" LMS is monitoring? I have approx 900 devices being managed by LMS on a 1500 device licence. I am running LMS 4.2.2
Any light you could shed on this would be appreciated
Thanks,
Mark

I've come across this a few times. I did not find a solution. It went away with a reinstall.
What seems to happen is that somehow DFM puts all the device interfaces in a managed state.
It should not.
It should only manage the ports and interfaces that connect to another managed device.
There is a hardcoded limit of 40.000 managed ports in DFM.
Suspected situations:
On one server where I found this the system locale that I put to us-english, was somehow put back to be-french. Maybe even during the installation, not sure who or what did this.
On another server the anti-virus which I had turned off, was turned back on during installation,probably by a policy server.
Cheers,
Michel

UCS C220 M3S with PCI mezzanine card raid SAS 2008M-8i :((

Hello
May be someone has already spend a little time with this configuration. the main stuff is my ucsc doesn't think he has disk to boot one even if with CIMC I see the opposite.
I configure with server conf utility ucs-cxx-scu-3.1.3b.iso with raid1 and as I have 2 UCS C220M3S I do also with Raid0 on another one. the trick is when I install ESXI 5.1 (VMware-VMvisor-Installer-5.1.0-799733.x86_64.iso) during install the setup od VMware detect the disk and install on it but after reboot always same storie no disk !!!
I don't see where to do something ??? So If someone encountered this problem, my be has already find the trick
The bios is C220M3.1.4b.0 and I have also a PCI Broadcom 5709 1Gbps 4 port NIC on slot 2 on both UCSC
here is the config 2xXeon CPU E5-2650 @2.00Ghz with 64 GB of Ram.
Any idea is welcome
Cheers
CX
and for the one configure with raid1

UCS C220 M3S with PCI mezzanine card raid SAS 2008M-8i
file attach UCSC220M3S right setup.pdf give illustrated answer
Point was VM distribution but bios which does not see SAS PCI Mezzanine Ctrl
Thanks to PDI help

No network adapters (HP Pavilion p7-1415). Can't get them back.

This PC suddenly lost its network adapters. No wireless. No LAN.
When I plug an ethernet cable into the LAN port, no lights.
No network adapters in Device Manager - Scanning for hardware changes brings up nothing and there are no exclamation points or yellow icons to even show if there is one malfunctioning
Things i've tried:
-Re-installing the network drivers. I now get the error message of: "Your system does not meet the minimum requirements for this update. Update has been cancelled (9996)"
-Virus and Malware scans bring up nothing
-Deleting the Config Registry key from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network (I backed up my config)
-Restarting
-sfc /scannow
-I used a USB wi-fi dongle and was able to connect to the internet using that. Under device manager it says it is a RealTek wifi adapter, but I don't believe it is...
any ideas?
thanks

According to THIS PAGE, the onboard network device is listed as RTL8171FH-CG gigabit Ethernet controller, which is Realtek. The wireless adapter is listed as Wireless LAN 802.11 b/g/n featuring Single-band (2.4 Ghz) 1x1, which is an adapter card. The page I linked has a picture of the card, which shows a RALINK RT5390. It is possible that one of them has failed but not likely both.
If the USB WiFi dongle works then possibly the internal WiFi became unseated or failed.
{---------- Please click the "Thumbs Up" to say thanks for helping.
Please click "Accept As Solution" if my help has solved your problem. ----------}
This is a user supported forum. I am a volunteer and I do not work for HP.

Migrate Roles failes when migrating VMs with legacy network adapters (2008R2 - 2012)

I'm working on a upgrade of Hyper-V 2008R2 cluster to Hyper-V 2012 cluster. I am using the "migrate roles" feature of failover clustering to migrate the CSV's and VM's. The wizard ask to which switch the VMs need to be connected on the target cluster.
All VMs with network adapters can be started in the new cluster without any issues. If you look at the XML file of the migrated VMs with normal network adapters, a new XML has been generated in the proper 2012 format. However, all VM's with a legacy
network adapter fail to start. Also there is no migrated XML file in the VM directory. It is impossible to check or adjust the settings of the migrated VMs with legacy network adapters using the failover clustering console.
I have reproduced the issue in my lab several times, and it seems like a bug.
There are several workarounds, but I am looking for a real solution.

Hi,
We recommend that you use the legacy network adapter only to perform a network-based installation or when the guest operating system does not support the network adapter.
If the virtual machine continues to use the legacy network adapter it will not be able to leverage many of the features available in the Hyper-V virtual switch. You may want
to replace the legacy network adapter after the operating system is installed.
The related KB:
Building Your Cloud Infrastructure: Converged Data Center without Dedicated Storage Nodes
http://technet.microsoft.com/en-us/library/hh831829.aspx
Configure Networking
http://technet.microsoft.com/en-us/library/cc770380.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Removing Logical Networks and Subnets from Hyper-V Host Network Adapters that are greyed out

Hello All
I am new to SCVMM 2012 R2 and I have create a Hyper-V Cluster and now creating Logical Networks and Port Profiles and Logical Switches. I have figured out how to create all of them properly now, but I have made some mistakes in the past. I have a Logical
Switch created and assigned to network adapters on the hosts. Now I am trying to add the other switches to other adapters, but I have associations on network adapters to Logical Switches and Subnets that are not correct and need to be removed so I can add
the correct ones, but in the console the network adapters that I need to work with the information is grayed out and I can't change the information.
I am not an expert at Powershell. Below you can see a Logical Network and Sunets associated
to a Network adapter. Can someone help figure out how to remove the information so I can assign the correct Logical Network?
I woul so much appreciate this. I know there is a way to do this in
PowerShell but I don't know Powershell that much. I
am savoing all the
powershell scripts ever time I configure something in SCVMM but I have had no luck trying to
revearse what I did.
Help Please
Christopher
Christopher Scannell

This shows that an Uplink profile associated with this host, links to these logical networks. In order to remove this successfully, you must remove the logical switch and uplink deployed to the hosts.
For a complete overview and guidance on the required configuration, have a look at the whitepaper we created.
http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

2 wired network adapters on 1 computer

I have 2 wired network adapters on 1 computer (windows XP sp3). I used to use on board one, but now I want to use the plugged in one. The problem is I don't know how to use it because windows doesn't automatically change to it. Could you show me how to do
this?
In additional, I want to connect this computer to the other one using the plugged in adapter, and the other computer will connect directly to the internet. Can I do this and how?
Thanks & Best Regards,
Pham Thanh Long

Switching between the two should be fairly straight forward, assuming Windows has both adaptors detected and installed obviously. Down by the clock, right click on the network icon and select Open Network Connections (if that's not visible, go to Start,
Control Panel, make sure you're in classic view mode, then open Network Connections). Confirm that both adaptors are listed.
Right click on the currently used adaptor and go into Properties, then select "Internet Protocol (TCP/IP)". If the IP and DNS settings are set to obtain them automatically then that's simple, if they're statically assigned then make a note of the settings
and come out of there. Right click on the adaptor and select Disable. Now right click on the adaptor you want to use and if Enable is listed then click it. Go into the properties of this adaptor and set the IP and DNS address details to the same as they were
on the other adaptor, and close those windows. Now, if you move the network cable from the onboard network connection to the other one you should find that Windows starts to use that one.
In terms of connecting to the other machine, I assume you mean using the onboard adaptor that is now unused? That's possible but a little more tricky. You could connect direct between that adaptor and another computer (though if you're going direct rather
than via a switch/hub then you need to use a crossover cable not a normal network cable). You'll need to setup the network IP address details on this adaptor, and they must be on a different network range to the one you've just configured for your main
network. The two machines can now talk to each other using that adaptor.
If you want to be able to access the internet via that second computer (note, you can't have internet access via the other computer AND the normal network since only one adaptor can be configured with a gateway address) then you'd need to configure
Internet Connection Sharing on the other computer as described here
http://support.microsoft.com/kb/306126

"No airport networks were found" - setup problem

I'm trying to setup a new airport network with an AEBS. I plugged it in to the outlet and then plugged the cable modem ethernet cable into the AEBS. The light turns green. Then I open Airport Setup Utility and get the following message:
"No airport networks were found"
I then opened the Airport Admin Utility, and it is also unable to see the AEBS.
Any suggestions?

Okay, I updated the firmware to 6.3 and am now able to see the AEBS network. However, I can't connect to the Internet using the network I created in the Admin Utility.
The Network control pane says Aiport is active and connected to the Internet, but I can't get online. I have a Comcast cable high-speed Internet. I'm not exactly sure what my settings should be in Network?

Lost all my network adapters - network icon is X'ed out but still online

Win7 x64 - little backstory to explain how i got here...
This was a vista machine that i upgraded to win7. Everything worked after the upgrade except for hamachi (version 1). I did a reinstall of that and it fixed it, except i had 2 hamachi network interfaces listed in device manager, one of which was showing up as broken (yellow exclamation mark). Since everything was working i left it alone.
Fast forward to today - i tried to upgrade hamachi to hamachi 2. Seemed to work ok but i couldn't connect to any peers. Looking into it it said the hamachi adapter was faulty and looking at my network connections there was no hamachi adapter listed.
I opened device manager and there was just one hamachi nic listed and it was the broken one. I selected uninstall - checked the box to remove the driver and it uninstalled.
I then manually installed another instance of the hamachi network adapter. Hamachi still cant connect to peers - same error msg about the network adapter.
Only now, ALL of my network adapters are missing in the network connections folder. And the network status icon in the status tray is showing a red X as though it's not connected, even though this PC is online (i'm connecting to it through RDP).
I've already tried rebooting - no effect. So any ideas where all my network connections/adapters went and how to get this all sorted?
One more piece of info - if i right click on the network icon in the status tray and select troubleshoot, having another problem, specific adapter - on that screen it then lists 3 network adapters. Tried letting it diagnose all of them but no effect.
And if i open the network connections folder and go to help, advanced options, i get an 'unexpected error'

Hi,
This issue can occur by incompatible NIC driver or corrupted files. I suggest you try the following steps.
1. Uninstall the NIC driver and reinstall the driver for Windows Vista or Windows 7 in Compatibility Mode.
2. Restart the computer in Safe Mode with Networking and check the result.
If there is any error message, please capture and upload it for research.
Thanks,
Novak

No compatible network adapters found - UCSC C220 M3S

Similar Messages

Maybe you are looking for