All known issues from FileWave 3.6.x and older

These are known issues for legacy versions of FileWave

FileWave XClient 3.5.0 (build 2378)

June 2, 2008

Microsoft Office 2008 Fails to Launch
Most applications that make up Office 2008 have a folder named Frameworks with symbolic links to folders. When a Fileset is changed to a new version, the Frameworks folders with only symbolic links are considered empty, therefore the folder is deleted as part of the Fileset modification process.

Workaround:
Add an empty text file to each Framework folder.

FileWave XAdmin 3.5.0 (build 2378)

April 25, 2008

error -150 downloading file ID xxxxxx

Replacing a Folder inside a fileset by drag and dropping a folder from your hard disk to the fileset window will cause the following issues:

--If the fileset is already associated, after updating the model, the changes in the fileset aren't becoming effective on the clients.

--If new associations are built, the fileset won't be downloaded by the clients. In the logfile you will find some error entries: error -150 downloading file ID xxxxxx

Workaround:

Make sure that after you replace folders via drag'n'drop inside a fileset, that the 'fileset container' has a modified state, to force this state adjust the comment of your fileset in some way (e.g. add a letter to the comment) before performing a 'model update'.

FileWave XAdmin 3.5.0 (build 2378)

May 5, 2008

Can't change Admin Server Password
Single-Admin License users of the FileWave Admin are not able to change the FileWave Admin User Password. If you wish to change your password, please follow this link to a Modified XAdmin that can perform this function.

FileWave Win 3.5.0

April 15, 2008

Dear Customer,

We received reports of problems with the FileWave Win 3.5.0 release. There issues are related to compatibility with the 2.6 release and the 3.5 release. It is recommended that you keep you FileWave Clients and version 2.6.X until we have the issues with the FileWave Win 3.5.0 resolved. Specifically, we have the following problems.

- SuperPrefs are not merged properly
- Certain regdiff.filewave files are not read properly cause failure to activate certain registry keys and values
- MSI based Patch Installer Filesets are not executed properly because the XAdmin and WinAdmin are not placing the installers in the proper directory.

If you have any questions or concerns please direct them to support@filewave.com

FileWave 3.0.1 XAdmin Build 148

October 02, 2007

- Sym-Link reconstruction failure while importing fileset
- The GUI disconnects from the Server during extremely long fileset export/import
Please download the prerelease of FW XAdmin version 3.0.2 to fix these issues.

FileWave 3.0 XAdmin Build 136

July 11, 2007

- Clients Manager Filter (PPC Only)
-The groups filter only works once and then stops functioning. Workarounds -- use Intel mac for XAdmin, or quit XAdmin and reopen to fix filter.

July 03, 2007

- FileWave Client Installer Assistant uses always Computer Name for Client name
Using the FileWave Client Installer Assistant to update or install FileWave clients remotely, is always overwriting the client name with the computer name, no matter if the checkbox; 'use computer name for client name' is set or not. It will be fixed in the next release.

- Please notice while upgrading a french version of FileWave XAdmin to FileWave XAdmin 3.0
Filewave 3.0 isn't available in french language yet. Because of this, upgrading a french version of FileWave XAdmin to FileWave XAdmin 3.0 will corrupt the GUI of the FileWave XAdmin 3.0 application. To workaround this please show Package Contents of FileWave XAdmin 3.0 and remove the folder /FileWave\342\204\242\ XAdmin.app/Contents/Resources/French.lproj

June 28, 2007

- Client Monitor does not display OS X 10.4.10
Apple changed the format for their display of the OS with this 10.4.10 release (due to the extra character). As a result, we'll change our code in order to read it properly. It will be fixed in the next release.

June 20, 2007

- Renaming name and comment of Clients and Groups in single user mode
The two issues are both related to the clients & groups window:
1 - right click to edit comment in single user mode fails to edit the field
2 - double click to edit name or comment does not work.

the work around for issue (1) is to use the right click contextual menu to choose the 'Rename selected item' option. There is presently no work-around for issue (2) above.

The issues are confirmed - we'll make sure that it is fixed in an upcoming patch release.

FileWave 2.6.1

November 22, 2006

- Issue with FileWave Let not installing XClients properly.
The configuration file; fwcld.conf won't be added in /usr/local/etc/ when installing XClients remotely by FileWave Let. Hence the installed FileWave XClient can't be launched.

Workaround: Please download the following XClient Installer; fwcld.pkg and replace it with the corrupt one in: FileWaveTM XAdmin/Contents/Recources/. The Package Contents can be shown by the contextual menu of the FileWaveTM XAdmin application.

This workaround should allow you to use the FileWave Let Assistant again for successful remote installations of XClients.

FileWave 2.6

October 24, 2006

- Issue with scripts on Mac OS X clients not executing.
Scripts set to execute on activation show a successful in the log file, however, the action contained in the script are never performed.

- Issue with Fileset Creation on Intel Macs.
Creating a Fileset with Fileset XMagic Assistant can fail on Intel Macs. To workaround the issue, make sure to leave the XMagic Assistant Window open when creating a Fileset on an Intel Mac.

- Issue with saving FileWave Booseter preferences.
FileWave Booster won't save its preferences properly after installing FileWave Booster on a system which doesn't contain the directory /usr/local/etc/. To workaround this issue make sure to create a folder "etc" in the directory /usr/local/. The permissions for this folder should be; system:wheel rwxr-xr-x.

FileWave 2.5.1

April 13, 2006

- Issue with SymLinks on Intel based Macs.
Creation of symbolic links on Intel based Macs is not working correctly with the FileWave XClient. Customers requiring an immediate solution should contact FileWave support (Email Support) for an updated FileWave XClient as a workaround.

- Clients stop connecting to FileWave XServer after update to FileWave XClient 2.5.1.
Please see the following forum for more information.
Updated 2.5.1 Client stops to connect to the Server

- Issue with iTunes installer packages.
FileWave XClient has trouble running iTunes installer package because the installer uses a shell script command (the "su" command) that can't be run as the root user.

Workaround. Create a Fileset using Fileset XMagic or edit the preinstall and preupgrade scripts removing the su command.

- Issue with Fast User Switching and reboot installer packages.
Installer packages requiring a reboot will not run with Fast User Switching enabled until all users are logged out of the computer.

- Issue with user status information when a user's Unique ID is reset.
The status information for that user is not deleted when the unique id is reset and therefore the status information will be out of date. This can be confusing if the associations have changed as Filesets that are no longer associated will have active status when they should have deleted status. Workaround is to delete the client account.

- Inconsistencies in the fwxserver process ids can occur.
Cases can occur where the fwxserver processes are not in a proper parent-child configuration. Workaround this problem by using the latest FileWave XServer Monitor to check the status of the fwxserver process. If the status is Faulty then restart the fwxserver process using FileWave XServer Status Monitor