Knowledge Base: Windows, FileWave
Results
Intelligent downloader explained
Summary
This KB article will explain the intelligent downloader and give the best pratices to uprade your selfhealed softwares by benefiting from this feature.
Intelligent Downloader
When a fileset is deployed and the time to download has come, the FileWave Client will check for existing exact copies of the fileset files before it starts the download.
The match is met only if:
Wild card deployment of files in Windows
Sumary
As of version FileWave version 5.5, files activation based on wild card expressions is not supported. Therefore, In cases where you want to push files and folders to a path that is different on each client follow the steps in this article . An example of this case would be firefox fileset on Windows where profiles files are located in: Drive:\Users\USER\AppData\Roaming\Mozilla\Firefox\Profiles\*.default (on Win7) where "*.default" can be any chain of characters.
SOP for upgrading your managed Softwares
Summary
There are different ways for upgrading your managed softwares and the method you choose depends on your filesets type.
This KB article describes the available options for the upgrade.
FileWave Server 5.6.1 and Automatic Proxy Configuration
Introduction
As of version 5.6.1 - the FileWave server will use the system's proxy configuration while making HTTP requests. This change was made to accomodate the software update feature that needs outbound http access for downloading the update catalogs for OSX and Windows.
By default, the fwxserver process will use your computers system settings for the proxy - but only if the fwxserver is running on Mac or Windows. Linux systems do not have a standard way of configuring their proxy settings and it's therefore not feasible to auto detect these.
Apple Software Update certificate expiration
Summary
Apple's certificate used to sign Updates for OS X Lion and Mac OS 10.6.8 has expired on March 23, 2012 and Apple reposted some of the updates. Therefore, Filewave server will not recognize the Filesets that were previously created (before Apple's change) because their internal IDs have changed in the Apple catalog.
Changing the Kiosk Port for FileWave Client Machines
Changing the Kiosk Port requires finding what ports are available, choosing method, making the change.
On occasion you may find that the default Kiosk Port of 20020 will conflict with other services, and needs to be changed.
Finding what ports are available
Open a command prompt
Mac - Apple's Terminal.app will work perfectly
Located in: Macintosh HD → Applications → Utilities → Terminal.app
use the netstat command to locate an unused port
FileWave Default TCP Listening Port Usage
FileWave TCP/IP Port Usage
By default the FileWave software listens on the TCP/IP ports listed below. These are the defaults and they can be configured to listen on different ports if required.
New ports numbers are in red.
FileWave Client Ports
20010 TCP/IP for monitor-client communication
20020 TCP/IP for Kiosk (fwgui to talk to client)
Merge updates to a fileset with FileSet Magic
Summary:
This knowledge base article describes the steps to use fileset merge feature in FilesetMagic to merge an update directly to the existing fileset. An example for when this might be useful is when you need to deploy a software update for a software package that is currently controlled by FileWave. Deploying software updates to client machines using pkg fileset can cause the changes to revert back if the software fileset files are set to self heal.
Procedure:
Filewave Firewall Scripts for Windows
FileWave Installers by default leave Windows Firewall settings untouched.
Use the attached .bat files to open the firewall for the respective executables at their standard install locations.
If you've installed a filewave component to a nonstandard path, please adapt the path inside the .bat files.
