Advanced Search
Search Results
1071 total results found
Script Best Practices
Description Tips and tricks for running Filesets with scripts Don't put passwords in scripts The scripts are stored locally on devices. For security reasons, usernames and passwords should not be included within the body of scripts. For example: Example: pass...
Referencing Launch Arguments in Scripts
Description Scripts run by FileWave can receive Launch Arguments. The arguments are supplied by FileWave and referenced by the script, but they are not written into the script body. They may be supplied to any of the following: Fileset Scripts Custom Fields Po...
FileWave Network Imaging / IVS Overview
Network Imaging Network imaging is supported over ethernet using the FileWave Imaging Virtual Server (IVS). It uses the PXEboot system for Windows computers. For a complete guide on how to fully set up a FileWave Imaging Virtual Server (IVS): Network Imaging...
Intelligent downloader explained
Summary This KB article will explain the intelligent downloader and give the best practices to upgrade your self-healed software by benefiting from this feature through Filesets / Payloads. Intelligent Downloader When a Fileset / Payload is deployed and the...
Test PowerShell as SYSTEM with PsExec on Windows
What FileWave runs Windows deployment scripts as the local SYSTEM account. Microsoft PsExec lets you test a PowerShell script in that same security context before deploying it through a Fileset or Custom Field. When/Why Current FileWave Windows clients are 64-...
FileWave Firewall Scripts for Windows
Summary FileWave installers leave Windows Firewall settings untouched by default. This historical article provides scripts that add Windows Firewall rules for FileWave Windows components when needed. FileWave 15.5 added these firewall changes to the normal cli...
Booster Overview
Introduction A Booster in the context of FileWave is a component designed to scale the management of devices within a network. It is a server component that can be installed on macOS, Windows, and Linux systems and is used to distribute data from the FileWave ...
What is an API?
What Application Programming Interface (API). APIs programmatically provide the reading or writing of information to one or more services. FileWave has a rich set of APIs to allow customers to build connections. Some vendors also produce integrations, utili...
Command Line API (v1)
Command Line RESTful API It is probably easiest to consider this API as an interaction with Inventory Queries, allowing for example: Ad-hoc queries to be run to return results New Inventory Queries to be created The returning of Current Query results Deleting ...
FileWave Anywhere API (v2)
What FileWave Anywhere (formerly WebAdmin) talks to FileWave Server through API calls. You can use the same style of calls from scripts or third-party tools when you need automation that matches what FileWave Anywhere does. When/Why Use this when a workflow ne...
How to write to a custom field using the FileWave API
It is often desirable to alter FileWave Custom Field values, especially when it comes to driving automated workflows. API calls have the distinct advantage of changing Custom Field values directly on the server, essentially making the change immediate. Where...
Returning Device Information as a JSON
What The Client Info > Device Details of a particular client, contains a wealth of information that may be useful to repurpose in other systems (Help Desks, centralised inventory systems, etc). Using the FileWave API, this information could be pulled by alter...
Using the Command Line API to limit, sort, and offset values returned
Problem When utilizing FileWave's Command Line API to extract inventory information, you may find the need to limit the values returned, sort the data, or return results that are offset by a certain number of values. Because it can be a topic that can trip s...
Bulk Update the Enrollment User (auth_username) using API
What This problem and solution came from a customer who had many devices in FileWave, yet did not have the 'Enrollment User' (internally known as auth_username) populated. In order for automatic associations of iPads with Apple Classroom, devices must have an...
Working With APIs
Getting Started The purpose of this guides is two fold: First, to provide an introduction to those unfamiliar with using the FileWave API Second, to be a reference for commands that can be used within the API Command Line API refers to the original RES...
FileWave Anywhere API Documentation
What FileWave Anywhere includes a Swagger/OpenAPI documentation page for supported public API paths. The page lists public, non-internal URL paths and includes a Try it out option that can execute an API command directly from the documentation. Executing a com...
Sending MDM Commands
What FileWave Anywhere can send MDM commands to devices, and the FileWave Anywhere API can trigger those same commands for scripted or integrated workflows. The Swagger documentation shows the request structure: Note the reference to the device(s) is now by '...
Securing FileWave Server on the Internet for Remote Device Management
What This article provides guidance on securely exposing and managing your FileWave server on the internet for remote device management. When/Why You might need to expose your FileWave server on the internet to manage devices anywhere they might be, including ...