Skip navigation.
Home

Knowledge Base: 2010, FileWave

Results 1 - 10 of 19

Results

Revert to Last Model can cause data loss

There is a known issue with reverting to the last model (FileWave Server -> Revert to Last Model) in FileWave 4.0 and 4.0.1 which can lead to deletion of fileset data files that are still used by valid filesets.  The file delete can occure during the next model update after the model is reverted.

It is recommended that this feature is not used until FileWave release 4.0.2.

Install Flash on Tiger, Leopard and Snow Leopard

This is a fileset that allows you to install Flash Player 10 on Tiger and Leopard Clients

If this fileset does not work for you, please refer to this white paper to create the fileset from scratch.

Download the Install Flash Player10 fileset (10.4 and 10.5)

iLife 11 Fileset Creation on Mac OS

White paper for iLife11 fileset creation:

Please follow the steps from below to build the iLife11 fileset.


Prerequisites:

Update quicktime components, and Llife Support on the client where you are going to create the fileset.  The minimum version of OSX is 10.6.3

Superprefs fileset doesnt change the client password as set in the superprefs file

 

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.

Having DB folder on a different Volume(symlink) slows the admin performance

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.

 

Adobe CS 5 Fileset Creation on Mac OS

Booster address configuration is not migrated during 3.6.x -> 4.1.1 upgrade

When upgrading from a 3.6.x client to a 4.1.1 client on Windows, any booster configuration values will not be saved out properly.  As such, they will need to be reset, possibly with a super prefs file.

Choosing About Client Monitor causes Client Monitor application to crash

Workaround for getting the version is to select the applicaiton in the Finder and get info on the application.