Remotely installing enic drivers via pnputil results in timeout error even though it is successful

Question

This is a followup question to my previous post regarding an error I was getting using pnputil remotely 
http://social.technet.microsoft.com/Forums/windowsserver/en-US/05116983-7de5-4987-919d-d0032c65c0bb/remote-use-of-pnputil-results-in-invalid-inf-passed-as-parameter?forum=winserverpowershell
I was able to get the script working copying the files locally then installing. Basically I'm doing:
if (!(Test-Path -path $DestinationFolder)) {New-Item $DestinationFolder -Type Directory}
Copy-Item -Path $SourceFNIC -Destination $DestinationFolder
Copy-Item -Path $SourceENIC -Destination $DestinationFolder
Invoke-Command -ComputerName $servers -ScriptBlock {pnputil.exe -i -a "C:\temp\fnicwl64.inf"}
Invoke-Command -ComputerName $servers -ScriptBlock {pnputil.exe -i -a "C:\temp\enic6x64.inf"}
The fnic installs no problem & reports back. The enic, understandably, loses connection temporarily while the driver updates. It then sits at: Processing inf:
enic6x64.inf for about 30 seconds before I get the error message:
Processing data from remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote
Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRemotingTransportException
    + FullyQualifiedErrorId : JobFailure
The blip for installing the drivers is maybe 5 seconds. Is there a way to get the script to wait for successful reply or for it to check again to make sure it was installed before it times out? Again, it is successfully updating all enic drivers, so just
trying to make the remote script see that for verification over multiple servers.

Answer 1

That should work in theory... however the problem I'm running into is that the job will report a "fail" everytime no matter what because it loses connection with the remote host while it's updating the network drivers. However, on the server, all network
drivers are in fact updated. The only results I get from the receive-job is a timeout, but if I redirect the actual results from the command to a text file on the server, then just wait 15 seconds for the drivers to complete their install I can read what actually
happened. I'm not sure why the job is timing out. It waits for a good 30-45 seconds before timing out when the host is only blipping for about 10 seconds, but it never tries to establish a connection back. 
Reading through, if our servers were updated with powershell 4.0 I could use the InDisconnectedSession
parameter I think... Hmmmm I'm gonna look into upgrading our powershell versions anyways.