Using proWin32.exe downloaded from the intel site, I can update the network drivers on my machine(s)
However, when I do this both the network settings and the VLAN (I use Vlan taging at the local machine) are lost.
This means updating the drivers remotely is not possible....since as soon as the drivers are updated, the machine
drops off the network
Does anyone know of a way to persist the network config post-update, without having to visit each machine in turn...?
Just few quick questions again, how many units were affected? are you using the latest driver version 19.5? at https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18713 Intel® Download Center
Any machine we tried was affected, which would have been about 300 except that we stopped deployment when we found this problem.
The version of prowin32 was the latest I could find in the download section... I will check driver version and let you know
Ok - yes the latest proWin32.exe
When installed, the driver version shows as
22.214.171.124 from 02/05/2014
Prowin32 was installed silently using the "/s" flag from a remote command prompt
The latest driver version is 12.11.97 dated 5/15/2014. Please try download latest PROSEt 19.5 (software that contain the driver) to test,
you may download the driver from here
https://downloadcenter.intel.com/download/18713/Network-Adapter-Driver-for-Windows-7- Intel® Download Center
Here is what you can try to see if this could be of any help:
1) Save your network adapter setting using the command below:
cscript savresdx.vbs save c:\settings
2) Then deploy it to machines using this command:
cscript savresdx.vbs restore c:\settings
You may refer more info at http://www.intel.com/support/network/sb/cs-028693.htm Network Connectivity — How Do I Save and rRstore Adapter and Team Configuration Settings?
I have tried a small batch file with:
There seems to be two issues though....
1) The "/s" flag seems to be being ignored - I am still getting a GUI prompting me for input. Any idea why...?
2) The test machine on which these drivers sit seems to loose its connection every few weeks, needing a reboot. So I may hold off further deployment for now
Please try using Prosetdx.msi, it is included in the PROSet software. The command for silent installation is as below:
C:\WINNT\System32\msiexec.exe /i PROSETDX.msi /qn /liew install.log
For more information about executing this command, you may refer to
Hope this helps.
Hmmm...the install log for the above gives me:
The MSI is not being ran through DxSetup, exiting install
1: [09:08:26] 2: Exiting IsDxSetupRunning()
CustomAction CA_IS_DXSETUP_ACTIVE returned actual error code 1602 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 09:08:26: CA_IS_DXSETUP_ACTIVE. Return value 2.