If you want to change the client password using super prefs fileset please dont do it.

The password set in the super prefs file is not saved in the client prefrences prefrences, hence your old password will be changed to a passowrd that we dont know.

Resolution : This issue has been fixed in FileWave 4.1.

FileWave Clients running on Windows XP have a dependency for a certain Windows update patch to be installed. Without this patch installed the FileWave Client's software update feature (new in version 5.5.) will not work correctly.

The error as seen in the FileWave Client's log file will be

FATAL|MSSoftwareUpdate::fileWaveUpdateServiceId: failed to create the update service manager

The Microsoft patch that needs to be installed is KB898461. Details and download of the patch are available from http://support.microsoft.com/kb/898461

Delivering Filesets that contain Adobe PKG's might cause the installation to fail.

Adobe provides a tool called Adobe Application Manager Enterprise which is used to package Adobe installers into Apple's PGK's for mass deployment.
Unfortunately there is a problem with the FileWave Client in handling the post-flight scripts of Adobe PKG's. That might cause the installation to break.

August 12, 2011

Problem:
Cases have been reported where older 3.X series FileWave Clients delete all Filesets that are associated to them when communicating with the FileWave Server running version 5.X.

Solution:

The FileWave 5.2 client has an issue where it can crash given certain contents inside the /Users/ folder.  

If a client machine contains folders in the /Users/ directory that contain spaces in the name (other than the "All Users" directory), then fwcld may get into an infinite loop and/or crash.

Workaround:  Remove folders in the /Users/ directory that contain spaces on the affected client

This issue will be fixed in 5.2.1

Issue: If you use client monitor of verison 4.1.1 to estabilsh a connection to a client trough a VPN tunnel or over different subnets you will get the status message: Client Status: [disconnected] or Can't connect to client...

Workaround: In a such case use the client monitor of version 3.7.x to connect to the client. The client monitor 3.7.x is fully compatible with client version 4.1.1

There is an issue in FileWave 4.1.1 Server where groups don't properly get associations that should be propagated to them by group clones. 

You will not experience this issue unless you are using group clones that are deeply nested propagating associations to clients that are also deeply nested.

Example:

Group A in root contains Group B, Group B contains Group C, Group C contains Group D, and Group X is cloned into Group D.

Group X in root contains group Y, Group Y contains Group Z, the client is in Group Z.

The structure looks like this:

Some users with PPC and Intel Servers, following upgrade, find that their database appears empty.  

Don't panic!  Your database is fine, there was an error with the database migration.

Use the following steps to make the database appear:

1.  Stop the server (Terminal: sudo fwcontrol server stop)

2.  Delete /Library/Receipts/FileWave Server.pkg.

3.  Delete the /fwxserver/DB folder

4.  Install the 3.7.5 Server.

5.  Stop the server again (sudo fwcontrol server stop)

Deliveries made to the /Users/Shared folder can get the wrong ownership making it difficult for users to access files and folders contained within.

The workaround to the issue is to change the client settings. This value isn't in the UI of the SuperPrefs but you could modify the plist that the SuperPrefs creates. The key is named:

setUsersFilesOwner

and you want that to be an integer value 0

Go ahead and deliver that SuperPrefs file and that will solve the issue on the client

Issue : If you have a symlink to /fwxserver folder (Data Folder and DB folder are on network volume i.e NAS) it is possible that you experience performance issue's with the FileWave Admin

Resolution:  We strongly recommend that you that if you are on  version 4.0 & above only create the symlink to the Data Folder and keep the DB folder on the local machine.