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.
Additionally, DO NOT use Launch Arguments to provide passwords to scripts. Launch Arguments are visible in the process list during script execution. Instead supply the username and password as Environment Variables:
During script execution, the Launch Argument is seen:
Using the example Environment Variables from the image, they would be addressed as:
Keep Requirements Scripts Small
Requirements scripts are pulled from a fileset and sent before the remainder of the fileset.
It behaves this way because if a requirements script fails, there is no point in downloading and installing the remainder of the fileset.
A fileset whose requirements have failed will not even show up in the kiosk.
Where possible, avoid piping commands. This increases overhead on the scripts. If pipes are required, try to reduce the quantity of pipes. If nothing else, this makes the scripts easier to read.
And other commands may achieve the same result more efficiently without the need to pipe.
Consider this for all scripts beyond just requirement scripts.
Leverage Dependancies and Scripts
If there is a script that several filesets will need, don't paste the same script into each one. Create an empty fileset with that script, and make the other filesets dependent upon it.
Log Script Output to the Client Log (macOS only)
Have a script that needs to write details steps to a log?
Want a quick status of the script.
Have a script write to the client log.
You can then use Client Monitor, and pull and view the log as things are happening.
Windows log file is locked such that additional appending may not take place
Scripts run by FileWave are run by root or System. As such, scripts should be tested using the same user context to prevent erroneous results. Many commands will yield the same result regardless, but this cannot be relied upon.
E.g. Run the following on a Windows 10 Professional system locally through Powershell as either user or 'Run As Admin' will see the following result:
However, as a Custom Field running the same script, the result is surprisingly different:
This is because Windows is providing a different answer based upon either the user running the script or may provide different responses based on 32-bit or 64-bit.
Take a look at Getting a CMD prompt as SYSTEM in Windows Vista and Windows Server 2008 for details about running scripts as System. Note, that by default, this will start an executable as 64-bit, for native 64-bit OS. However, the above example is because the FileWave fwcld process is calling the 32-bit version of PowerShell.
This relies on downloading and installing, onto the test machine, PsTools.
To mimic this experience, consider the guide to starting the CMD. When launching an executable, like PowerShell, the 32-bit version would need to be referenced. For example:
For CMD, the equivalent would be:
Similarly, when attempting to run some commands, it may be necessary to ensure Windows is using the correct version of a binary with the 'sysnative' redirect. An example would be bitlocker's 'manage-bde.exe'. To use this in a Fileset, try the following:
If you have a requirement to run a particular command through the 64 bit version of Powershell this can be achieved as follows:
Create a new admin account
Two Fileset Environment Varaibles would be supplied. To add the user 'rstephens' with the password 'filewave'
Parameters may be supplied, that can then be added to the execution of Powershell from within the script:
On macOS, running commands as sudo is not necessarily the same as actually becoming root.
E.g. Run the following commands to evaluate the local variable $HOME, once using sudo and once as root.
It is common to see plist files edited with the 'defaults' command. However this command is unique when it comes to ownership and permissions of files. The 'defaults' command will both take ownership and change permissions of files when used to write to plist files:
As such, ensure to add a repair to scripts to reset permissions and ownership after the command has been used or consider using the following command instead:
Other Script Recipes
DeepFreeze (Knowledge Base)
Execute as Console User (Knowledge Base)
Firmware (macOS 10.6 - macOS 10.12) (Knowledge Base)
Full macOS Model name to Inventory (Knowledge Base)
Hide local admins (Knowledge Base)
Remotely Enable Screen Sharing for a user - Pre macOS 10.14 (Knowledge Base)
Remove Casper JSS Client Components (Knowledge Base)
Remove mobileconfig signature (Knowledge Base)
Script Best Practices (Knowledge Base)
User Icon (Knowledge Base)
Windows Firewall rules (Knowledge Base)