MDT 2013 Server 2012 R2 Core Deployment Fails After Disabling ChecksumOffloads on NICs

Question

When changes are made to the Checksum offloads, the NICs reset themselves and I'm losing connectivity to the deployment share during the deployment process (LiteTouch).  It happens during a custom PowerShell script I'm running in the Task Sequence
after "Tattoo".
PowerShell Script:
Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *
Here are the errors from the BDD.log (sorry couldn't get the _SMSTaskSequence.log)
ZTIPowerShell processing completed successfully. ZTIPowerShell 8/25/2014 2:27:28 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Unable to copy log to the network as no SLShare value was specified. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
What I was thinking about trying was adding a few lines to the end of my script:
1. PING 1.1.1.1 -n 1 -w 30000 >NUL
    This would give the server 30 seconds to right itself after resetting the NICs
2. net use command to remap the share.
Two questions regarding re-mapping the share.
   1. I'm assuming this will run as Administrator token.  Will this be an issue for continued deployment?
   2. At the beginning of the deployment process the Tech has to enter his/her credentials to access the deployment share to begin the deployment process.  Are those the credentials I need to continue using, or does MDT use some other credentials
to access the deployment share that far into the deployment process (during state restore phase)?
Thank you for taking time to read my post.
-Cheers!

Answer 1

Apologies for the delay in responding to this thread.
It turns out that Broadcom NICs are the culprit!
For some reason Broadcom doesn't grant you access to all the feature sets on their NICs when it comes to PowerShell.
Same script runs against Intel NICs with no issues.
I placed a 15 second pause in the script to allow NICs to reset, I then remap MDT network drive to continue the deployment process.  Big thanks to Keith for assisting with reconnecting the network drive!
Here is the script I settled on:
# All settings will not take, if target is using Broadcom NICs.
# You will still need to manually set TCP IPv4 and IPv6 to disabled.
# Commands to disable Checksum Offloads.
Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *
# Pause script for 15 seconds to allow ample time for NICs to reset.
Start-Sleep -s 15
net use %DeployRoot% /u:"%UserDomain%\%UserID%" "%USerPassword%"
# Pause script end for 5 seconds to allow completion of share recreation.
Start-Sleep -s 5