MSI package?

[TiKu]

Is there a MSI setup package available for FileZilla? It would make it possible to update the clients in a Windows 2003 domain to the latest version using ActiveDirectory and Group Policies.

[eddan]

No, there isn't one available.

[TheAngryPenguin]

Why not create your own MSI package based on the .zip version?

[botg]

Personally I don't like msi at all, msi installers take ages to initialize, several rounds of unpacking, initializing, configuring repeated a couple of times.
NSIS is a lot faster

Have you already tried the silent installation provided by the FZ installer? Just pass it the /S parameter. With the /D parameter you can set the installation directory. (e.g. /D=C:\Program Files\FZ)

[TiKu]

I'll try to do it with the silent installation.
Before I became the admin of a Win2003/WinXP domain, I didn't like MSI that much, too. But it's really nice in domains.

[snackmaster]

Personally I don't like msi at all, msi installers take ages to initialize, several rounds of unpacking, initializing, configuring repeated a couple of times.
NSIS is a lot faster

Faster isn't always better, especially if you wish for FileZilla to break through in the enterprise realm. Domain admins, SMS Admins... MSI & Transforms rule. Complex bloated etc. yes

Have you already tried the silent installation provided by the FZ installer? Just pass it the /S parameter. With the /D parameter you can set the installation directory. (e.g. /D=C:\Program Files\FZ)

Thanks, that helped! Is there anyway to control the install beyond using /S /D ?

[TiKu]

I'm creating my own FileZilla MSI packages now. If anyone is interested in the packages, please contact me.

[menthos]

Personally I don't like msi at all, msi installers take ages to initialize, several rounds of unpacking, initializing, configuring repeated a couple of times.
NSIS is a lot faster

Have you tried Advanced Installer? It's a simple and fast application for creating fully standards compliant Windows Installer (MSI) packages. Furthermore, the features of the freeware version are enough for creating FileZilla MSI packages.

If you prefer scripted, automated MSI builds, have a look at the WiX toolset.

Have you already tried the silent installation provided by the FZ installer? Just pass it the /S parameter. With the /D parameter you can set the installation directory. (e.g. /D=C:\Program Files\FZ)

Probably, the most common (and cheapest) way of deploying applications in the enterprise world across Windows domains is via Group Policy. Unfortunately, Group Policy only supports the standard Windows Installer (MSI) packages. No custom silent installers, no Nullsoft installers, only proper MSI will do.

So if you're a Windows admin and want to deploy FileZilla, you're currently left with the option of repackaging FileZilla yourself, or go look for something else. Granted, repackaging FileZilla is relatively easy to do if you use applications like Advanced Installer, but many admins are lazy, or simply do not have the time. The latter is probably closer to the truth in most cases.

[TiKu]

Here's a wxs file for FileZilla 3.0.10. It can be used with WiX 3.x to build a MSI package from the ZIP version.
Some notes:

• Any additional language other than German isn't installed by default. To change this, search for lines like e. g. <Feature Id="LocalsItalian" Absent="allow" AllowAdvertise="yes" Level="2" Title="Italian"> (they start in line 642) and change Level="2" to Level="1"
• The Blukis and Cyrill themes aren't installed by default. To change this, change to Level="1" in line 782 and 788.
• The 64 Bit shell extension isn't installed. It is commented out in line 131-133. You'll also have to change line 136 from <RegistryValue Id="RegKey002" Root="HKLM" Key="SOFTWARE\Classes\CLSID\{DB70412E-EEC9-479c-BBA9-BE36BFDDA41B}\InProcServer32" Value="[#fzshellext.dll]" Type="string" /> to <RegistryValue Id="RegKey002" Root="HKLM" Key="SOFTWARE\Classes\CLSID\{DB70412E-EEC9-479c-BBA9-BE36BFDDA41B}\InProcServer32" Value="[#fzshellext_64.dll]" Type="string" />
  I'm not sure whether the GUID {DB70412E-EEC9-479c-BBA9-BE36BFDDA41B} must be changed, too.

http://www.timosoft-software.de/stuff/FileZilla.wxs

[botg]

The 64 Bit shell extension isn't installed. It is commented out in line 131-133. You'll also have to change line 136 from <RegistryValue Id="RegKey002" Root="HKLM" Key="SOFTWARE\Classes\CLSID\{DB70412E-EEC9-479c-BBA9-BE36BFDDA41B}\InProcServer32" Value="[#fzshellext.dll]" Type="string" /> to <RegistryValue Id="RegKey002" Root="HKLM" Key="SOFTWARE\Classes\CLSID\{DB70412E-EEC9-479c-BBA9-BE36BFDDA41B}\InProcServer32" Value="[#fzshellext_64.dll]" Type="string" />

The location of the 32bit shell extension key is only correct on 32bit systems. On 64bit systems, the key for the 32bit shell extension has to be HKLM\SOFTWARE\Wow6432Node\Classes\CLSID\{DB70412E-EEC9-479c-BBA9-BE36BFDDA41B}\InProcServer32

I'm not sure whether the GUID {DB70412E-EEC9-479c-BBA9-BE36BFDDA41B} must be changed, too.

Both the same.

[botg]

Same goes for HKLM\SOFTWARE\Classes\directory\shellex\CopyHookHandlers\FileZilla3CopyHook and HKLM\SOFTWARE\FileZilla 3\fzshellext, for the 32bit shellextension, both need to be in the Wow6432Node key on 64bit systems.