Software Deployment

When we had problems with installing WinPcap silently, we tried many options but weren't able to get a completely silent install.
In the end after weighing up the options we ended up capturing the install and creating our own MSI, so that we can be sure that the application will install silently when we deploy using SMS.
As always it's a calculated risk, but for our company we were better off recapturing than the install not being silent.

Thanks for pitching in Jill.. We tried to recapture winpcap as well, everyting seem to go fine with the only one thing missing.

I cant seem to get the default VPN capture interface at all.. Would you know how can i get that interface to show up in my MSI???

Thanks

Install your captured MSI, take a Pre-Snapshot, install the original installer, take a post snapshot. Include the captured bits into your earlier captured MSI and test it again. Your MSI could have missed something.

This looks old but since I have an answer I thought I would post it just in case it help someone else that comes across WinPcap.
Basically all WinPcap does is copy DLL's to their proper locations, then creates and starts a service that runs the npf.sys driver.

Here is what you need to do for a silent installation:
1. Extract the files from the WinPcap installer - using 7zip - using the autorename feature
2. There will be several duplicates that have a _1 or _2 etc on the end of their name
3. You will have to copy the proper versions of each file to their respecitive locations
4. Each file is for a different version of windows - jsut check the properties - details tab to see which version it is.
5. For 32bit Windows (I was using Windows 7) copy the following to C:\Windows\System32
Packet.dll
wpcap.dll
pthreadVC.dll

Then copy the driver to C:\Windows\System32\Drivers
npf.sys

Next create a service for the driver using the following command:
sc create npf binPath= system32\drivers\npf.sys type= kernel start= auto error= normal tag= no DisplayName= "NetGroup Packet Filter Driver"

For 64bit windows it is almost the same except the 32bit versions of the DLL's go into C:\Windows\sysWOW64
and the 64bit versions go into C:\Windows\System32

File names are the same so on 64bit you end up with a 64bit version in C:\Windows\System32
Packet.dll
wpcap.dll

32bit versions end up in C:\windows\System32
Packet.dll
pthreadVC.dll
wpcap.dll

Driver npf.sys ends up in the same place either way.

hope this helps someone

This is great, very useful. Have you posted it in the 'Package KB'?

Yes I did post it in the KB plus the following addition:

An addition to the note above:
when distributing this from SCCM on a 64bit system (Windows 7 for me) you will have to copy the files from a 32bit process such as CMD.exe and utilize the %windir%\sysnative to get the proper files into the real system32 directory

If you use the normal cmd or xcopy the files will be redirected to C:\windows\Syswow64 and Wireshare doesn't like that! it wants packet.dll to be in the system32 native directory - who knew?

At any rate here was my work around:
use a CMD file as the initial program in the SCCM package
C:\windows\syswow64\cmd.exe /c "%~dp0<SilentInstall.cmd>

obviously that silentInstall.cmd file can be called whatever you want to name it

then inside the silentinstall.cmd file put your "copy" commands and use the sysnative directory for system32
example:
copy "%~dp0npf.sys" %windir%\Sysnative\drivers

then copy the sysWOW64 files into their directory using the normal syntax.

Hope that helps for sccm