
2017-07-05_15-07-33.png [https://filedb.experts-exchange.com/incoming/2017/07_w27/1180024/2017-07-05_15-07-33.png]

Error I receive when attempting to do in place upgrade after Teamed NIC has been removed.

2017-07-05_15-07-33.png

<div>
Did you restart the computer after deleting the teams? Do that for a test.
</div>


Did you restart the computer after deleting the teams? Do that for a test.

<div>
Yes, the server was restarted after deleting the Teamed NIC.
</div>


Yes, the server was restarted after deleting the Teamed NIC.

<div>
Please upload the file C:\$Windows.~BT\Sources\Pa<wbr />nther\setu<wbr />perr.log
</div>


Please upload the file C:\$Windows.~BT\Sources\Panther\setuperr.log

<div>
I figured out the issue on my own this past weekend as I was able to perform an in place upgrade to my other DC with no assistance from the questions asked on the form.
</div>


I figured out the issue on my own this past weekend as I was able to perform an in place upgrade to my other DC with no assistance from the questions asked on the form.

<div>
<div class="content wysiwyg-content">
I am in the process of upgrading all of our physical servers from 2012 / R2 to 2016, the issue I am running into is our servers have Teamed NICS. I use the Server Manager to delete the NIC Team and run powershell's Get-NetLbfoTeam, Get-NetLbfoTeamMember and Get-NetLbfoTeamNic, results are null. However when I run the upgrade I get the following attached error. <br />
<br />
I have been successful at doing in place upgrades on my VM's, however I have had to do a couple of fresh O.S. install on my DC's, I need the in place to work to speed up the process, any and all help is much appreciated.
</div>
</div>


I am in the process of upgrading all of our physical servers from 2012 / R2 to 2016, the issue I am running into is our servers have Teamed NICS. I use the Server Manager to delete the NIC Team and run powershell's Get-NetLbfoTeam, Get-NetLbfoTeamMember and Get-NetLbfoTeamNic, results are null. However when I run the upgrade I get the following attached error. 

I have been successful at doing in place upgrades on my VM's, however I have had to do a couple of fresh O.S. install on my DC's, I need the in place to work to speed up the process, any and all help is much appreciated.

In Place Server Upgrade 2012 R2 to 2016

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.