Windows 2012 network teaming broken "host unmanageable"

Question

Hello,
we are in the process of migrating servers to new hardware using the Platespin Migrate tool. That process has been tested in controlled Proof Of Concepts now for Windows 2003, 2008 and 2008R2, but now we come to Windows 2012 and we run into an issue with
the Network Teaming reconfiguration after the copy is complete.
The Windows 2008R2 and below also had teaming software installed from HP (HPNCU), and after migration we could simply run the cqniccmd.exe /D command to remove the "ghost" Teaming configuration and setup a new Team on the new networkadapters in
the new (blade) server.
Now with Windows 2012 we also have teaming on the original server that was configured using lbfoadmin.exe, and it was expected that after server 'restore' using Platespin that the team would be broken, but I also expected to simply be able to remove that
leftover and configure a new one. But instead when I open the servermanager/lbfoadmin I see that the server shows "host unmanageable" and there is no sign of any old Team, nor does it show the new adapters to let me make a new team.
I hope anyone can help me cleanup the old team-config and make a new one.
Many thanks in advance,
Eric
Best regards and many thanks in advance, Eric Vegter

Answer 1

Hi Alex,
thanks for the reply. Basically it doesn't matter what tool is used to copy/clone/restore a machine to new hardware... After that process the NIC teaming will no longer work because the underlaying NICs that build the team have gone. That same thing happens
when doing this cloning whit an HP server that has the HP Nic Configuration Utility installed that you use to configure a Team. After clone/migrate the server has new NICs and the virtual Team-NIC that was created on the original server is still seen in the
Network-Adapters (NCPA.cpl) overview but it is invalid at that moment and must be removed. That remove/cleanup is simply done via the HP NCU commandline utility.. All works fine... On windows 2008r2 and below.. but 2012 is a different story.. That Virtual
NIC that was created by the Windows 2012 built-in teaming is not visible after Cloning in the network-adapters overview, but the system still thinks it has teaming configured and using the provided GUI or powershell commands I cannot undo that old configuration.
I also cannot setup a new teaming configuration. There is no firewall active on the system and the new physical NIC has an IP assigned and I can RDP and ping to the server as well, so the ICMP cause you mention will not be the case here..
The only way I could clone that 2012 system and afterwards setup a new team was to break the teaming on the original source server, then clone it and then on that new server setup a team. That was possible now that the original server did not have a Team
so nothing was left 'ghosted' somewhere in the registry/config. 
Still I wish this would be possible to simply cleanup via a powershell commandlet and a /force (or /include-hidden or so) parameter so I do not have to make changes to my original source.
If anyone has a suggestion how to (forcefully)  cleanup that Windows 2012 NIC Teaming config pls let me know. It would still help me migrate/clone the other few 2012 systems around here.
Thanks
Eric
Best regards and many thanks in advance, Eric Vegter