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.

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. 

Filewave Client Firewall Opener

Filewave Server Firewall Opener

This Knowledge base article will help you troubleshoot mdm with FileWave.

 Before going deep into troubleshooting, make sure that you have got these steps correct:

As we got some requests from our Clients for the FileWave Client installer that can be used with InstaDMG we have created one.

You can use this installer and install Filewave client on any Volume you Select.

Please download the Client Installer from here:

FileWaveClient3.7.3 for InstaDMG

Thanks :-)

Deploy these filesets to end FileWave's control over a client; it will remove all FileWave executables and data files. Software controlled by FileWave will stay in its current state -- active applications and files will be left permanently.

FileWave Uninstaller Fileset (OS X)

FileWave Uninstaller Fileset (Windows)