AnEngelsen

@Andreas Gluch search is working much better. When you perform a search it automatically switches you over to the Activity menu.

This custom field lists printers that are currently installed on any given desktop device. (The list does not contain a delimiter.) Installed Printers.customfields

FileWave allows you to see the computer's current IP. But you cannot see the list of DNS servers that the client is using. This custom field helps us determine if a client is currently on prem, connected to the VPN, or off site. (This is because our on-prem. computers use our Domain Controllers for DNS lookups.) DNS IPs.customfields

I was surprised to learn that FileWave doesn't natively support displaying the "uptime" for any given desktop device. As such, the following custom field (see attachment) can be applied all desktop devices to show system uptime. (How long it has been since the computer was last last rebooted.) Uptime.customfields

It's prob. preferable to generate a new discussion post for each custom field. That way people can offer a brief description for each of their custom fields. It will also be easier to search for & locate a specific custom field.

The search functionality on the Alliance Forum is broken.

@Pierre-Nicolas I have confirmed that both of these requirements have been met. The option to start a remote session is now available to me. However, when I attempt to start a remote session the iPad never receives a push notification. The FileWave Anywhere app presents me with the following error message:

If I install TeamViewer Remote Control app onto an iPad, can I use FileWave Anywhere to establish a TeamViewer session with another iOS/Desktop device? Currently, I'm not seeing the ability (within FileWave Anywhere) to connect (via TeamViewer) to any of my iOS device. Additionally, when I try establishing a Remote Session to a desktop device (from an iPad) I am not presented with a dialog message, prompting me to launch the TeamViewer app.

On second thought, my macOS fileset can probably be ignored. The fwcld service is set to "relaunch on crash". The Windows service has no such safeguards. This might be a good feature request. (Attempt to restart the FileWaveWinClient service if the service fails/stops.)

Sometimes, the FileWave Client service stops running. If this happens, the laptop/desktop device will no longer communicate with the FileWave Server. (In my experience) this behavior occurs more often on Windows devices, especially after deploying the FWwinclient upgrade fileset. As such, I created the following (2) filesets: Script - Verify FileWave Client is Running (macOS): Loads a LaunchAgent that runs a shell script (once an hour) to verify that the fwcld service is running. If not, the fwcld service is restarted. Script - Verify FileWave Client is Running (Win): Creates a scheduled task that runs once an hour. The task calls a .ps1 script that verifies that the FileWaveWinClient service is running. If not, the service is started. Both filesets are attached to this post. If the FileWave client is failing to start, try manually starting the service. Windows: Services app -> FileWave Client -> Start Service macOS: sudo fwcontrol client start If that doesn't work, a ticket should be opened with FileWave support. FilesetExport_VerifyFileWaveClientIsRunning.zip

@Pierre-Nicolas can you confirm that the FileWave client does not use an API call to install or uninstall kiosk filesets?

This issue is resolved in the v14.9.1 build of FileWave Server.

Can you explain what happens (in the background) when the end-user clicks the "Uninstall" button (within the FW Kiosk)? Standard associations can be configured with an "install on" and "removal at" timestamp. However, I never fully understood how Kiosk associations can toggle between two different states. ("Available in Kiosk" vs. "Installed via Kiosk")

@Josh Levitsky and @Pierre-Nicolas Dumb Idea: Does the FileWave API support a function that can send the "Uninstall" fileset command? If "yes", then a postflight script could be added to any fileset. After the activation script is finished running, the postflight script would transmit an API call that would send the uninstall Fileset command. Correct? (It might be necessary to include a "sleep 30" command at the start of the script; to ensure that the script doesn't get uninstalled too soon.)

I really appreciate the "Unread Content" feature (upper-right corner on the FileWave Alliance website). However, it appears as though General Discussion posts are being omitted when the "Unread Content" filter is applied. Can this be corrected? Or is this content filter intentional?

@Josh LevitskyIt doesn't appear to be a TCP port issue.

Good Morning @sean_a, Our FileWave server is hosted by FileWave. (Cloud hosted)

None of the desktop clients are updating to the latest FileWave "model". For example, the current model is 1424. All clients are reporting that their current model is 1421. I have verified that none of the clients are in a “locked” state. For me, this issue became noticeable immediately after being upgraded to FWServer v14.9.0

Haha. No worries.

Certain filesets can be duplicated. But Apple Profiles (.mobileconfig files) cannot. Instead, you would need to perform the following steps: Export the MDM profile. Create a new MDM Profile, then choose "Load Profile". Save, then choose "Create New".

AFAIK, FileWave doesn't have the ability to repeatedly "Run" a script via the FileWave Kiosk. Can anyone point me to the FileWave resource (written by @Josh Levitsky) that explains how to toggle an "Installed" fileset back to the "Install" state? Thanks!

Currently, it's possible to obtain the FileWave Client log (fwcld.log) file via the Client Monitor (application). However, if the client is in a remote location (not on the LAN) it's not possible to obtain the fwcld.log. It would be great if the WebAdmin could display the client log (in a new browser tab) preferably with color formatting--similar to the new fileset script editor. Alternatively, fetching the Client log file could result in a file download. Please rename the file to: clientNameHere_currentTimestampHere.log I'm attaching an image of what I would like the WebUI to look like. Sometimes the fwcld.log file can grow to a size of 30MB+. As such, I'm fine if the WebAdmin only grabs the 1,000 most recent lines. (This would diminish the file size to 100 KB.)

Is there a Moodle setting that allows you to disable file compression (for images)? I'm noticing that when I attach an image to the Alliance Forum is looks very blurry. Thanks!