I don't understand the issue. Is this ONLY happening on specific workstations? As in mfg/model?

I ask, because, I have installed Server 2012 R2 so many times and have also set up NIC Teaming via Server Mangler.... using an Integrated nic with a NIC on an add-in card. Created External vswitches and never had any issues what so ever.

The only issues I have run across were due to them being Broadcom NICs and having to disable Virtual Machine Queues option in the advanced properties of the NIC on the hosts. (before any teaming or anything is done). This needs to be done via Powershell on hosts running Core as well. I still have the commands handy if needed.

Great post and well said. This is similar advice to what I give... but much more thoroughly thought out and written.

If you are unable to connect to O365 via PowerShell and get an error similar to below, follow these instructions.

Error:
Import-PSSession : Could not load type ‘System.Management.Automation.SecuritySupport’ from assembly
‘System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.

The fix:

• Open up an elevated PowerShell prompt and type:
• wusa /uninstall /kb:3176934
• Reboot required

Link:

https://blogs.msdn.microsoft.com/powershell/2016/08/23/powershell-dsc-broken-in-kb3176932/