You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
whitverj edited this page Jul 3, 2024
·
4 revisions
FileWave has a knowledgebase article describing how to use InstallApplications and DEPNotify to take the place of their own FileWave client package.
The article does make certain assumptions; namely:
You'll be using DEPNotify along with InstallApplications
You'll be hosting the InstallApplications json and payload files (packages and/or scripts) on the FileWave server itself, using its embedded instance of Apache.
If both of those assumptions hold, you can follow the article as-written.
If you're not using DEPNotify, then naturally you can skip anything having to do with that.
If you're not using the FileWave server to host your json and payload files, then you can skip the section named "Hosting and Serving your packages via the FileWave Server" and also note that any URLs that point to <your_filewave_server> in the article should point to whatever server is actually hosting that content.