This is a fileset that allows you to create a new user account through fileset deployment. If you would like to create new user accounts in Tiger, you can find instructions here.

1. Download the Create New User Fileset (OS X Leopard) and import it into your FileWave Server.

Summary

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

Summary ( If you are using Deploy Studio in your environment read this )

 A very common practice for FileWave Administrators is including the FileWave Client on their base image.  This ensures that all of your machines will have the ability to connect to the server remotely, so that you will never have to use any method other than FileWave to deploy software to the machine.

Many customers have asked us if there's a way to store their Server's data on a non-startup volume or on network shares ( AFP Shares for Mac or CIFS Shares for windows) . In in this posting you find  instructions for linking the Server Data Folder to another location on OS X, and Windows. You may follow these same steps for the Booster, accounting for small differences in folder names.

OS X

Starting with FileWave 3.5, all components feature a command line utility for performing often performed FileWave actions.

The tool is called fwcontrol. You can use it to restart any of the daemons, get the version, compact the server database, or purge user status. To get the usage and help screen, simply type fwcontrol from your command prompt or Terminal.
( The output is different in version 5.0 or higher )
Here is the help screen for fwcontrol:

|------------------------|

If you are using FileWave 4.x or higher, you can use  SuperPrefsEditor as described in the FileWave User Manual ( it can be found in the download page ).

If you are using FileWave 4.x or higher, you can use  SuperPrefsEditor as described in the FileWave User Manual (it can be found in the download page).

If you need to change booster settings in multiple clients prefrences, here is a script that can do it.

FileWave can deploy Windows security patches and service packs cleanly and efficiently, requiring no user interaction or disturbance. FileWave version 5.5 or later has the Software Update feature that can apply Windows Updates to your clients.

Security Patches (or Service Packs) can cause problems if you use FileSet WinMagic. The problem occurs when a Patch modifies registry keys outside the HKEY_LOCAL_MACHINE\Software directory (this is the only part of the registry FileWave currently captures).

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)