Example Filesets that you might have used to push out these settings: Windows (64) - [Kiosk\_Customizer\_for\_Windows64.fileset.zip](https://kb.filewave.com/attachments/13) Windows (32) - [Kiosk\_Customizer\_for\_Windows32.fileset.zip](https://kb.filewave.com/attachments/14) macOS - [Kiosk\_Customizer\_for\_macOS.fileset.zip](https://kb.filewave.com/attachments/15) macOS/Windows - [Applications Preventing Reboot](https://kb.filewave.com/books/kiosk/page/applications-preventing-reboot-macoswindows "Applications Preventing Reboot (macOS/Windows)")
# Customizable icons You might have included icon files that you used to replace them in Kiosk before 15.3. These icons will not appear in 15.3 or newer.| File name | Description | Example | Pixel Size |
| action\_back.png | Icon for the "Back" action in the Software Installation dialog |  | 48x48 |
| action\_forward.png | Icon for the "Forward" action in the Software Installation dialog |  | 48x48 |
| background\_icon.png | Icon used for the watermark | (FileWave icon) | 512x512 |
| rating\_star\_half.png | Icon for half a rating star |  | 40x40 |
| rating\_star\_off.png | Icon for a rating star that is off |  | 40x40 |
| rating\_star\_on.png | Icon for a rating star that is on |  | 40x40 |
| tray\_icon.png | System tray icon. If missing, the background\_icon.png is used. | (FileWave icon) | 16x16 |
| warning.png | Warning icon, displayed when a fileset has problems (e.g. missing VPP user) |  | 64x64 |
Use cautiously
Without Metal support, the Kiosk will not open and the user logs may show messages like these: ``` 2024-05-13 10:40:15.324 FileWave Kiosk[1241:5674] Could not acquire Metal device. 2024-05-13 10:40:25.936 FileWave Kiosk[1241:5674] Unable to create FlutterView; no MTLDevice or MTLCommandQueue available. ``` ## Configuration Shut down the VM before editing its configuration. Do not edit the file while the VM is running or paused. Open the folder that contains the VM and find its `.vmx` file. For example, if the VM folder is named `macOS 12.vmwarevm`, the VMX file may be named `macOS 12.vmx`: ``` /Users/sholden/Documents/Virtual\ Machines/macOS\ 12.vmwarevm/macOS\ 12.vmx ``` Add these two lines: ``` appleGPU0.present = "TRUE" svga.present = "FALSE" ``` Start the VM after saving the file. To undo the change, shut down the VM again and remove the same two entries. You may also need to define the display size in the same file. This example uses 1920 x 1080: ``` appleGPU0.screenWidth="1920" appleGPU0.screenHeight="1080" ```This workaround may let the Kiosk launch in a VMware test VM, but in practice the VM often crashed or became unusable. Because the host Mac may also kernel panic, avoid this configuration unless the test requires it. Remove the entries when the test is complete.
# Resolving SSL and Manifest Validation Errors with FileWave Kiosk Installation (15.3+) # What This article addresses an issue encountered during the installation of the new FileWave Kiosk v.15.3.1 on macOS and Windows devices. Users may encounter SSL errors and manifest validation failures that prevent the Kiosk from installing correctly. # When/Why These installation errors typically occur when upgrading to FileWave v.15.3.1 and are primarily due to conflicts with certain content filters or proxy settings that block or misclassify necessary URLs. This is particularly relevant for organizations using content filtering solutions like Lightspeed, which may categorize essential URLs as unknown, thus blocking them. ``` "InstallApplication command error 2024-04-22T07:36:38 2024-04-22T07:36:38 Could not validate manifest..An SSL error has occurred and a secure connection to the server cannot be made. com.filewave.ios.app.kiosk2 " ``` # How To resolve these installation issues, follow the steps below: 1. **Check Proxy and Firewall Settings**: Ensure that your organization's proxy or firewall settings are not blocking access to FileWave URLs. 2. **Whitelist Necessary URLs**: Add the following URLs to the whitelist in your content filter or proxy settings: - `https://fw-kiosk-v2-ipas.filewave.cloud/` - `*.filewave.cloud` This change allows devices to communicate securely with FileWave servers and access the necessary resources for installing the Kiosk. 3. **Reattempt Installation**: After updating your settings, reattempt the installation of the FileWave Kiosk on the affected devices. ```shell # Example command to verify if the URL is accessible from your network curl -Iv https://fw-kiosk-v2-ipas.filewave.cloud/ ``` If the issue persists, check your SSL certificate settings and network configuration for any discrepancies that might be interfering with secure connections. # Related Links - [Default TCP and UDP Port Usage](https://kb.filewave.com/books/filewave-general-info/page/default-tcp-and-udp-port-usage "Default TCP and UDP Port Usage") # Digging Deeper The SSL error typically indicates an underlying issue with the secure connection setup between the client device and FileWave servers. This can be caused by SSL certificate verification failures, misconfigured proxies, or stringent network security policies that incorrectly classify or block legitimate URLs required for FileWave operations. Adjusting content filtering policies or proxy settings often resolves these issues, but further investigation into SSL trust settings may be required for complex network environments.