Sean

Better still, you could use Apple Shortcuts. I originally just had English or German, but expanded this with some examples: You can launch FileWave from the Menu Bar and not only have as many preset servers and usernames as you like, but also specify language whilst you are at it. No need to even care about what is in the recent list, this will pre-populate username, server and port fields; ignoring the recent list. For text copy/paste purposes here is the German script example: #!/bin/zsh /usr/libexec/PlistBuddy -c 'Set :lastAdminName fwadmin' ~/Library/Preferences/com.filewave.FileWave\ Admin.plist /usr/libexec/PlistBuddy -c 'Set :lastServerAddr demo.filewave.ch' ~/Library/Preferences/com.filewave.FileWave\ Admin.plist /usr/libexec/PlistBuddy -c 'Set :lastServerPort 20016' ~/Library/Preferences/com.filewave.FileWave\ Admin.plist /Applications/FileWave/FileWave\ Admin.app/Contents/MacOS/FileWave\ Admin --lang de_DE & exit 0 Now, take that a step further and quit a current running version if running, editing the English version example: #!/bin/zsh osascript << EOF try tell application "FileWave Admin" quit end tell end try EOF /usr/libexec/PlistBuddy -c 'Set :lastAdminName fwadmin' ~/Library/Preferences/com.filewave.FileWave\ Admin.plist /usr/libexec/PlistBuddy -c 'Set :lastServerAddr demo.inotech.ch' ~/Library/Preferences/com.filewave.FileWave\ Admin.plist /usr/libexec/PlistBuddy -c 'Set :lastServerPort 20016' ~/Library/Preferences/com.filewave.FileWave\ Admin.plist /Applications/FileWave/FileWave\ Admin.app/Contents/MacOS/FileWave\ Admin --lang us_EN & exit 0 This could be extended even further still and alter the path for different versions of FileWave if really necessary, if you have different customers running different versions of FileWave. This takes this beyond anything we would offer in product and all in the click of a Menu Bar item.

If you have attempted to use Universal Apps through FileWave and have identified any Apps that came in as iOS instead, then please contact FileWave Support if you need this resolved sooner rather than later. This issue should be resolved in next release (15.1), but there is a patch that can be applied for the interim. https://support.filewave.com/

Are you satisfied that there are no additional spaces, new line characters, other hidden characters in either of the values? Have you made sure the key is exactly as provided by the company? Do you receive an error message as shown in the examples of their documentation? Does the device need to reach their servers to accept the license and could devices not have that network connectivity? Have you tried using 'defaults' to create the file and then upload this created plist file or are you adding the keys and values manually and directly into the FileWave interface?

Did you try adding both keys from their documentation: https://support.goodnotes.com/hc/en-us/articles/6543387103503-How-to-install-GoodNotes-for-Institutions-via-MDM <key>ManagedAppConfigurationVersion</key> <string>1</string> <key>LicenseKey</key> <string>AAAAAA-BBBBBB-CCCCCC-DDDDDD-123456-V3</string>

You have options. 1) Right click the group and 'Convert to Standard Group'. All devices currently in the group will be a part of this new static group and Smart rules will no longer apply. 2) Create a new Custom Field based upon the desired installation, e.g. boolean and default false. Select the group and set the Custom Field value for this group of devices to be a value of true (right click on group and choose to set Custom Field value). Create a new Smart Group based upon this new Custom Field, where Smart Criteria is: value of Custom Field is true. Associate the same Fileset to this new group and delete the original Smart Group. This second option has the benefit of easily adding devices to the group by way of the Custom Field, instead of generating new clones into the group as the first option would require.

Does you PC have the necessary port access to get to the server? We have a port tester you could try: https://supportresources.filewave.com

A couple. FileWave Magic can be used to generate a registry Fileset. PowerShell can be used to alter registry. Beware with PowerShell and ensure to test correctly. Take a look at: https://bbb.filewave.com/books/filewave-general-info/page/script-best-practices There is a section about simulating running commands through FileWave and an example of why. Details on command and usage: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/set-itemproperty?view=powershell-7.3 https://learn.microsoft.com/en-us/powershell/scripting/samples/working-with-registry-entries?view=powershell-7.3 You might want to consider testing a Get before using a Set, to confirm you are targeting a key successfully.

Not entirely sure I follow. Typical behaviour is the first prompt is an authentication of the actual enrolment. This may or may not be based upon LDAP and therefore may or may not be the intended user of the device. DEP enrolment profile has options regarding account creation. If you intend for domain users to authenticate, not only the enrolment (which is configured in Preferences > LDAP), but also for authentication once the login prompt for the OS appears, you would need to supply some form of domain binding to the device or similar. If binding is required, this could be achieved with a Profile, for example. If you need some additional method regarding authentication of the login to the OS by domain users, twocanoes have a product for use here, which was until very recently free, but unfortunately no longer the case: https://twocanoes.com/products/mac/xcreds/

You'll probably need to supply logs to support, but do you have any other services that communicate with the server? Perhaps some 3rd party items that make API calls to the server? Unix systems can swallow all RAM as standard use, but clearly that shouldn't be at the detriment of services not functioning correctly. I assume you have no kind of AV software on the server.

The one on the left is Fitness+ https://apps.apple.com/us/app/fitness/id1208224953 The other one is the Settings, but Apple don't let you remove that.

When double clicking on a VPP App in Licence Management view in FileWave Central, it should show at least the following: Device and Client name are part of the list.

Looks like Google may automatically do this: so in your case, very much unlikely it has expired. You may need to raise a support ticket, if you are happy that you don't have any Firewall rules that would be getting in the way.

In Azure you can define anything with the Custom Setting, but the recommended is the default if you don't alter anything:

Hmm, although you can define duration of expiry, but it would seem unlikely it were that short.

Sounds like your IDP cert may have expired. Try logging into your IDP and checking out the IDP Application expiry date.

As Josh suggested, duplicating a script with double association is good, as it reduces the time between association changes. Essentially, the button only has two possible options: Install Uninstall There are only two ways to change the button back to Install after activation: Press Uninstall in the Kiosk Remove the association (have the client realise this has occurred) and then re-associate Doing this with two duplicate Filesets associated with two different Smart Groups, which in turn are based upon the two alternative values of a Boolean Custom Field, halves the time taken, compared with a device leaving a Smart Group and then re-entering to re-establish the association again with a single Fileset. When Custom Field is True > join Smart Group True > associate Fileset True When Custom Field is False > join Smart Group False > associate Fileset False Fileset False and Fileset True do the same thing Couple of pointers to note. Although a Fileset must have a unique name, the Fileset Properties of the Kiosk Title does not need to be unique between different Filesets. To speed up the process of the Smart Group transition though, I would recommend using an API call to alter the Custom Field value within a Script inside the Filesets; you may wish to consider using a preflight, so this is handled as early on in the process as possible. The elevate permissions example has additional inherent delays, since it writes to a local file and then a Custom Field script needs to read that value and once that inventory is reported, only then will the next ran Smart Group evaluation notice the change in value, causing the device to move groups. Using an API in a Fileset script to directly change the Custom Field on the server, negates the need for Custom Field evaluations and inventory.

Probably from here: https://www.cyberdrain.com/automating-with-powershell-deploying-wifi-profiles/ I notice: Quoted? Perhaps not necessary. Also remember, scripts ran through FileWave are ran as System and are 32bit, unless set otherwise. Always test in same environment before trying through FileWave. https://fwkb.atlassian.net/wiki/spaces/KB/pages/4331036/Script+Best+Practices

For the query, you need not include version either, this will be auto generated during creation.

This isn't entirely correct. FileWave has two different APIs Command line - has existed for years and may run queries Web - Created when we introduced the Web Admin and may do much more The Web Admin API relies upon Client ID when attempting to reference devices directly, but as suggested if you build out a query in advance you may then interrogate the query for details. You may even use this API to create a query The command line API on the other hand can be provided a query and return results without it actually creating a new query in the database. As such, you can build out anything you can akin to using the FileWave Central (Admin) App Inventory Query and the result should be posted back. Here is an example query using the Command Line API: #!/bin/zsh query='{"criteria":{"column":"serial_number","component":"Client","operator":"is","qualifier":'\"$serial_number\"'},"fields":[{"column":"device_name","component":"Client"},{"column":"type","component":"OperatingSystem"}],"main_component":"DesktopClient"}' curl -k -s -H "Authorization: $auth" https://$server_dns:20443/inv/api/v1/query_result/ --data $query -H "Content-Type: application/json" This example will report the Device Name and OS Type for the defined serial number and is the same as the following (I've put an exact serial_number in the GUI example to make it easier to see: If you don't know the component names and types, then use the Web Admin API Docs to find them out. Build out a query, save it then use the API doc to report all queries: Find your query in the list (if you just created it, it will be at the bottom), e.g. { "id": 253, "name": "OS Type", "favorite": true, "group": null, "version": 4 } Then use the API Doc again to examine the query: { "criteria": { "column": "serial_number", "component": "Client", "operator": "is", "qualifier": "C02Z90WDLVDQ" }, "favorite": true, "fields": [ { "column": "type", "component": "OperatingSystem" } ], "main_component": "DesktopClient", "name": "OS Type", "id": 253, "version": 4, "group": 0 } Note the URL paths between Web Admin and Command Line differ. Hopefully that is enough information for you to achieve your goal.

If there are no associations then we should expect the App to be removed. This returns the licence into the pool of VPP licences such that the App may then be associated with another device. If you wish for the App to remain on the device, then the association must continue to exist.

Try something like: C:\Windows\Sysnative\msg.exe * /TIME:100 Party Time https://ss64.com/nt/msg.html

Custom Fields and Smart Groups are the typical way to manage this. The Admin then sets the Custom Field to the pre-defined values and everything then triggers. When using this method, it can be considered useful to add an API PATCH within the script to reset the value of the Custom Field. However, since the Fileset has already ran at this point and it won't run again unless manually triggered by an Admin, the association could remain in place; any Fileset can be be re-actioned by the 'Reinstall Fileset' option found either in the device's Client Info or through the Fileset Report. This same theory can be used for associations though without Custom Fields and without Smart Groups. If you build out the script such that the first time it runs it does nothing, then these Filesets could be associated whenever in advance. With the association already in place, at the time you wish to 'fix' the device with the script, you trigger the Reinstall Fileset from the Admin console. Not proper code, but to give the idea: if [ first time ran == true ] then exit 0 else do some code fi This would give the idea of a script being dormant on the device until triggered by the Admin.

Please take a look at our KB: https://fwkb.atlassian.net/wiki/spaces/KB/pages/4329227/Filewave+Firewall+Scripts+for+Windows As noted in the article, FileWave does not touch any of the Firewall rules by installing FileWave, but we offer the details, such that you can if you wish.

If you want to alter the debug mode, then you could do this with Smart Group associations and use an Administrator Custom Field to trigger that change. You would then have two Filesets, one to set the value as 10 and the other as 99. Hence: Administrator Custom Field has two possible values: Standard or Debug Smart Group - Standard Log Level - Associate Fileset to set the value as 10 - Criteria based upon Administrator Custom Field of value Standard Smart Group - Debug Log Level - Associate Files to set the value as 99 - Criteria based upon Administrator Custom Field of value Debug However, rather than script this, you could use a Superpref Fileset to set the value. Another alternative: One Fileset that scripts the change, but based upon a Custom Field value Set a Launch Argument or Environment Variable to be the parameter value of the Custom Field After altering the Custom Field value for the chosen devices, trigger a reinstall Fileset for those devices If you don't wish to have to do a reinstall of Fileset, then use a Blocker Script to read this value and alter the client debug level Hope that provides enough options to give you an idea of how to approach this.