New network adapters

Hi Guys,
We have the following problem. Our customer has the following equipment
Dell Latiude E7440 and Targus Docking stations (ACP70EU).
On every workplace is a dockingstation, now the Dell machine connects to the dockingstation and a new network adapter is created (Ethernet 3)
When we configure the 802.1x setting the client can connect to the network.
When we move the Dell machine to another workspace with another dockking station. the windows machine creates a new network adapter (ethernet 4) with the default windows settings (Window Protect Eap)
etc.
Do you know if there is a registry setting we can adjust so that every new network adapter gets the correct Windows Certificate settings?
regards,
Peter

Peter,
You can accomplish this through Group Policies. There is a VERY helpful guide to enable Certificate Templates and dot1x configuration on the client in the Partner GOLD Labs.
Start by going here:
http://tools.cisco.com/pecx/login?URL=searchCurricula?LOID=477399
Choose Path 3:
Then Choose the AD-LDAP lab:
You will have to have you CCO ID to get here. If you cannot log in, then you should ask your AM for access.
Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question. Otherwise, feel free to post follow-up questions.
Charles Moreton

Similar Messages

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.

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.

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 )

BUG: Access Connect Abort, when I create a new network profile.

Where can I report bugs?
My system is windows xp sp2 on X60.
I have been using AC-4.42(Access Connection) for a long time. And before, there is no problem when I added new network profile into it.
But yesterday, I wanted to add a new profile into it. I opened the "create profile" window and input the name of the new profile (I have two network adapters, wired and wireless. So by default, the both are selected. And I left the default selection unchanged.), then "Next". The 2nd window is about wireless config, I configured everything, then go on "Next", at this moment, an error occured and AC aborted with four error windows. The titles of those windows are "ACMainGUI.exe error" and "ACMainGUIWnd: ACMainGUI.exe".
Then I did it again, I opened the "create profile" window, and this time, in this (1st) window, I changed the selection of network adapter, besides inputing the name of the new profile. I only selected the wired adapter, and then "Next". Sadly, this time the 2nd(next) window did not appear(pop up) at all. Instead, those four error windows poped up one by one. AC aborted again.
I repeated the above operations many times, and everytime, AC aborted.
So I went to the online "support and download" to look for some updates about AC. And I found AC-4.52 with luck. After downloading and installing, unfortunately the problem still exists. AC-4.52 still aborts when I create a new network profile.
So now, what to do. I have no ways. I am expecting the developers could note this problem and fix it and give me a newer update as soon as possible.
Sigh...

I have exactly the same issue. Next to the actions mentioned by ixbm I have also fully uninstalled and reinstalled the AC-4.52, but this didn't help.
Any idea on how to solve, installing older version?
regards,
Bart

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

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.

SEVRAL Network Adapters

Recently purchased a new Envy 700-414 and when I go to control panel/system/device manager/network adapters, I see SEVERAL. Is this normal?

Hi,
It appears that your PC was configured with multiple adapters at some point. You can tell that by the #2. If your PC is working OK then don't worry about it. I also see IP version 6 which is somewhat unusual.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

After Windows 10 Pro N succesfull update all Network Adapters not working and not showing up

Hi all, After succesfully installing the new Windows 10 Pro N onto my Windows 8.1 Pro N operating system and restarting the system, I realized that all drivers are migrated succesfully, withouht any incompatibility issue, but none of the network adapters were working, so no WiFi, no LAN connection was ready to be used, checking the list of available network adapters showed an empty list. I am using a ThinkPad T520 laptop. I have tried to update all drivers from a USB, had several restarts, but no result. Any ideas I could use to get Windows 10 up-n-running with network connections? Thank you in advance, Regards, Gyula

Hello and welcome,
Do you have VPN software on your laptop? https://support.microsoft.com/en-us/kb/3084164
Z.

HP deskjet 3050 all-in-one J610 series printer won't recognize new network

I have recently changed internet provider and my network setting have changed. My printer is not recognizing my new network - help

Well what exactly changed? New equipment? New router? New Gateway? New modem? Wired or wireless connection? OS of computer? Reinstalled the software? Reinstalled the drivers? Detail everything in order on what you are trying to do and where in the manual what steps you are following.
Say thanks by clicking the Kudos Thumbs Up to the right in the post.
If my post resolved your problem, please mark it as an Accepted Solution ...
I worked for HP but now I'm retired!

TS4611 Guys if you have these build: 12E3200 and your wifi is dropping, is not the your mid 2013 macbook air, is your router, I solve it by setting up my time capsule as a new network problem solved

Here is what I have been doing:
I got my new macbook air 11" two weeks ago, and have been haven problems with wifi connection dropping, I'm using verizon fioz at home, and their router
I also have a time capsule not set up as a network just join it to my current one.
After looking online all these days, I though, maybe is the verizon device that is updated..
I then reset the time capsule, created a new network
connected my system to the time capsule network, and there it is
DONE, everything works now.
So if you are haven the same problem,, that is the fix
hope that helps.
Oh before I did these I try everything, the wifi update from apple don't work it keeps dropping it
I try everything, so don't and delete the system as some people have done, I read somewhere.
try my fix hopes that works.
Message was edited by: rawreviewer

I have seen lots of issues on Yosemite with Wifi (and have been having issues myself), but yours seem different. It is a pretty new computer, have you tried taking it in under Applecare (if you live somewhere this is convenient)? Maybe you just got a defective wifi card. I won't defend Apple over this wifi mess, because it really is terrible, but your issue seems not the same as the ones I've read about while researching how to fix mine (unsucessfully....).

Thunderbolt to Firewire Adapter & New Network Interface Message

I am using the new Thunderbolt to Firewire Adapter. Why is it that every time I use it, I get the following message:
"A new network interface has been detected. The Thunderbolt FireWire Slot 2 network interface has not been set up. To set up this interface, use network preferences."
All I want to do is mount external hard drives that don't have Thunderbolt ports to my iMac, via Thunderbolt because I am using the iMac's single Firewire port for something else. The drives do successfully mount, but why do I keep getting this message whenever I connect them again?

I have no doubt what you say to do would get rid of the message for me. However, both myself and an Apple Store employee think it is odd that the message comes up in the first place. We're both curious about it, and he's going to look into it.
We tested it on a computer at the store, and found that it happens on Lion too.

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

I want to set up my time capsule on a completely new network & location without losing the old backups. How do I do this?

I want to set up my time capsule on a completely new network & location without losing the old backups. How do I do this? I cannot find anything in the user manual.

The TC is very hard to just move.. it retains too much of the old network setup.. buried deep in the bowels of the firmware configuration files.. or even on the hard disk special partitions used by the TC.. invisible to you btw.. !!
Do a factory reset and setup from scratch.
That factory reset will have no affect on your backups.. even if you rename the TC.. not a bad things since you also want clients to respond to the new network.. simply reset TM to the new TC name and location.
See A4 here.
http://pondini.org/TM/Troubleshooting.html
Factory reset.
The Factory Reset Gen1-4.
Unplug your TC. Hold in reset. and power the TC back on.. without releasing reset for about 10sec. When the status light flashes rapidly; release it.
Be Gentle! Feel the switch click on. It has a positive feel.. add no more pressure after that.
TC will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.
Factory reset Gen 5
Hold in reset for about 5sec until the status light flashes quickly.
If your AirPort Time Capsule still doesn’t respond, do a similar reset to the Gen1-4.
Unplug your AirPort Time Capsule .. hold in reset and power the TC back on.. without releasing the reset.. wait until status led flashes rapidly.

How can I set up a new network on my apple tv when my remote app isn't picking it up because they aren't on the same network?

How can I set up a new network on my apple tv when my remote app isn't picking it up because they aren't on the same network? The actual remote doesn't work anymore, so I've been using the remote app on my phone but now that our internet changed, I can't do anything at all. Please help!

You can't use the remote app to setup a network. If your physical remote isn't working you will need borrow another or purchase a replacement.

New network adapters

Similar Messages

Maybe you are looking for