https://community.hpe.com/t5/proliant-servers-ml-dl-sl/teaming-issue/m-p/3902557#M59355 We do maintenance every quarter and upgrade to the latest Smart start version. We run Version control server. We have mix of W2K3, W2K and also some W2K3-X64 versions.<BR />I upgrade teh NIC drivers manually and do rest through http://localhost:2381/vcagent. When I upgrade NIC drivers, it works on most servers, but drops the NIC on some server. I would have to then drop the teaming, delete the NIC from "device manager" and readd them. <BR /><BR />Any one else have this issue? How do you guys handle this? Wed, 22 Nov 2006 07:57:15 GMT SrinivasR 2006-11-22T07:57:15Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/teaming-issue/m-p/3902557#M59355 We do maintenance every quarter and upgrade to the latest Smart start version. We run Version control server. We have mix of W2K3, W2K and also some W2K3-X64 versions.<BR />I upgrade teh NIC drivers manually and do rest through http://localhost:2381/vcagent. When I upgrade NIC drivers, it works on most servers, but drops the NIC on some server. I would have to then drop the teaming, delete the NIC from "device manager" and readd them. <BR /><BR />Any one else have this issue? How do you guys handle this? Wed, 22 Nov 2006 07:57:15 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/teaming-issue/m-p/3902557#M59355 SrinivasR 2006-11-22T07:57:15Z