As a FileWave user you may have noticed some issues with different Adobe Plugin installers.  

Shockwave

When you first download Shockwave Player and open the DMG, you are presented with a file that has a .pkg filename.

Right clicking on the .pkg and selecting “Show Package Contents” give us the all of the parts that are going to be installed. We discover that there is a compressed file inside the pkg installer (Archive.pax.gz).

To migrate the FileWave server from one machine to another, use the following procedure:

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.

This is a fileset that allows you to install Flash Player 10 on Tiger, Leopard and Snow 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

If you are using Deploy Studio in your environment read this

One efficient way to deploy the FileWave Client is to use ARD. This posting will outline the necessary steps to mass-deploy the FileWave Client.pkg with the proper preferences.

What you need:
-FileWave Client.pkg (you can find this on the FileWave dmg)

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.

Many customers ask us how to upgrade from one version to the next. In this posting, we will discuss the procedure, complete with best practices.

For best results, upgrade the components in the following order:

1. Server
2. Admin Console(s)
3. Boosters
4. Clients

The Procedure

Backing up your FileWave server is always a good idea. Back in '97 a friend of mine spilled a pot of coffee on our server rack; you never know when bad things can happen to your hardware. Now, it's bad enough to lose the hardware, but think of all the hours represented by those perfected, irreplacible FileWave filesets! In order to prevent this disastrous loss, we have created a script to automatically back up your FileWave Server's database and data files:

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)

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.