This article summarizes the minimum system requirements to run SnapComms smoothly on your desktop or mobile devices.
Content Manager
Below are the browsers supported for accessing SnapComms' Content Manager:
- Google Chrome (Latest version)
- Microsoft Edge (Latest version)
Desktop Application
Windows
- OS: Windows 10, and Windows 11
- Minimum Processors: 2
- Memory: 3 GB
- Disk Space: 200 MB
- Other: .Net Framework 4.8.1 +, Microsoft Edge WebView2 Runtime
MacOS
-
OS: Monterey (macOS 12.0), Ventura (macOS 13.0), *Sonoma (macOS 14.0),
*Sequoia (macOS 15.0) - Processor: 1 GHz
- Memory: 1 GB
- Disk Space: 30 MB
- Other: Centrify 5.3.0-215 + (optional)
Native support for Silicon-based processors is available from v23.8.151773
Supports for Sonoma is available from v23.11.171997
Sonoma restrictions
Due to restrictions implemented by Apple, the following changes will apply.
- Publishing a screensaver will deliver it to end-users' Macs, but it will not be automatically applied. IT administrators will need to utilize MDM solutions like JAMF to select SnapComms screensavers as the default screensaver for their users.
- Local Network permissions are now required for the SnapComms App to communicate with the SnapComms screensaver.
Mobile Application
iOS
OS: iOS 16,17,18
Disk Space: 12 MB
Android
OS: Android 13,14,15
Disk Space: 13 MB
Thin Client Environments
The SnapComms Windows App is designed to be compatible with Windows-based desktops and may be compatible with Windows-based thin clients. Please review the Desktop Application requirements above to ensure compatibility with Windows devices.
If Screensaver, Wallpaper, and Lockscreen features are not enabled on thin clients, SnapComms cannot support these channels. SnapComms depends on these features being enabled in the system to work as intended.
Since thin client implementations vary across organizations, we recommend testing the SnapComms Windows App in your environment by setting up a SnapComms trial to confirm full compatibility with your thin client devices.
Comments
0 commentsArticle is closed for comments.