Customize Windows Installs: FileZilla nLite Addon Explained
If you deploy Windows regularly or build custom installation ISOs, integrating essential apps like FileZilla into your slipstreamed setup saves time and ensures a consistent environment. This article explains what the FileZilla nLite Addon does, why you’d use it, and a step-by-step process to create and integrate the addon into an nLite-built Windows installation.
What the FileZilla nLite Addon Is
The FileZilla nLite Addon packages the FileZilla FTP client (installer or portable files) into the nLite addon format so the FTP client installs automatically during Windows setup. It can be configured for a silent install or to drop files into specified locations for a portable setup.
Why Add FileZilla to a Slipstreamed Install
- Time savings: Pre-installing avoids repeating manual installs on each machine.
- Consistency: Ensures the same FileZilla version and settings across systems.
- Automation: Silent installs streamline unattended or mass deployments.
- Portability: Optionally include a portable build for technicians or recovery environments.
What You Need
- A Windows installation source (e.g., an extracted Windows XP/2003/7 folder) supported by nLite.
- nLite (or a similar slipstreaming tool compatible with your Windows version).
- The FileZilla installer (setup executable) or portable zip for the desired FileZilla version.
- Basic knowledge of creating addons for nLite (this guide includes concrete steps).
- Optional: Tools to create silent installer switches (e.g., 7-Zip, Inno Setup knowledge if repackaging).
Preparing the FileZilla Addon
nLite addons are structured folders containing an addon.inf file and the files to be copied or installed. Below are step-by-step instructions to create an addon that performs a silent FileZilla installation during Windows setup.
1. Choose Installer Type
- Prefer the official FileZilla installer (NSIS-based) for standard installs.
- Use the portable zip if you want to drop files into a folder without installing.
2. Create the Addon Folder Structure
- Create a new folder named something like: FileZilla_nLite_Addon
- Inside it create:
- addon.inf
- files\ (directory to hold the installer or portable files)
- install.cmd (optional wrapper to run the installer silently)
Example structure:
- FileZilla_nLite_Addon
- addon.inf
- files
- FileZilla_3.x.xwin64-setup.exe
- install.cmd
3. Write addon.inf
The addon.inf controls what files are copied and which commands run during setup. Use this minimal template and adjust paths/filenames:
Code
[Version] Signature=”\(CHICAGO\)” Provider=“FileZilla nLite Addon” Name=“FileZilla FTP Client” Category=“Applications”[Files] files\FileZilla_3.x.x_win64-setup.exe,%5%\FileZilla_3.x.x_win64-setup.exe[Actions] RunProg=“%5%\FileZilla_3.x.xwin64-setup.exe /S”
Notes:
- %5% expands to the Program Files folder on the target system during setup.
- The “/S” switch is commonly supported by NSIS installers for silent install; verify the correct switch for your FileZilla version (or use an install wrapper).
4. Create an install.cmd Wrapper (Optional)
If you need pre- or post-install steps (e.g., creating folders, copying config files, or using different silent switches), put commands in install.cmd and reference it in addon.inf:
install.cmd example:
Code
@echo off start /wait “” “%~dp0files\FileZilla_3.x.x_win64-setup.exe” /S REM Copy default config xcopy “%~dp0files\default_sitemanager.xml” “%ProgramFiles%\FileZilla\filezilla.xml” /Y
Update addon.inf Actions to: RunProg=“%5%\install.cmd”
5. Including Configuration (Optional)
To ensure consistent FileZilla settings (site manager, transfer settings), add the FileZilla XML config files to the files\ folder and have the install wrapper copy them into the user or program data locations:
- Per-user: “%USERPROFILE%\AppData\Roaming\FileZilla”
- All users: “%ProgramData%\FileZilla”
Be mindful of Windows version differences (AppData vs Documents and Settings).
Integrating the Addon with nLite
- Launch nLite and point it to your extracted Windows installation source.
- Proceed to the “Add-Ons” section.
- Click “Insert” and select the FileZilla_nLite_Addon folder.
- Continue with your nLite customizations (unattended setup, hotfixes, etc.).
- Build the ISO and flash or burn it to media.
During Windows installation, nLite will copy files and execute the RunProg action, performing the silent install or file placement.
Testing and Troubleshooting
- Test the addon in a VM before deploying widely.
- If installer doesn’t run, check:
- Correct filename and paths in addon.inf.
- Silent switch compatibility (/S vs /VERYSILENT for NSIS/Inno).
- Permissions — ensure actions target appropriate system folders.
- For portable installs, confirm the target folder is created and FileZilla’s config path is correct.
Security and Maintenance
- Keep the addon updated with new FileZilla releases to patch vulnerabilities.
- Verify digital signatures of installers when possible.
- Document the addon version and included configuration for auditing.
Example Addon Files (Summary)
- addon.inf — controls copy and run actions
- files\ — contains installer or portable files and optional config XMLs
- install.cmd — executes installer silently and copies config files
Conclusion
Creating a FileZilla nLite Addon streamlines deployments and ensures consistent FTP client setups across machines. By packaging the installer or portable files with an addon.inf and optional wrapper scripts, you can automate FileZilla installation during Windows setup. Test in a VM, confirm silent switches and paths, and update the addon when new FileZilla versions are released.
Leave a Reply