Jump to content

Tobias.vonLienen

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Tobias.vonLienen

  1. At this time we install almost all major or minor macOS updates manually but in the future we hope to do this automatically.

    The FileWave MDM Software Update solution is honestly not the most attractive option for us, so I've been reading through a few Apple KB articles which said that it is possible to create configuration profiles (Use MDM to deploy software updates to Apple devices - Apple Support) but I have not yet been able to find out how to do this in FileWave.

    I know that it is possible with Microsoft Intune, but we don't want to enrol our Macs to Intune (a Hybrid enrol is not possible anyways into two different MDMs).

    •  950 Mobile and 700 PC clients
    • Yes, we have 2 boosters
    • Yes, route server messages via Boosters is enabled on all our PC clients
    • No, shows nothing unusal.

     

    • what do you mean by API requests and how can I check
    • tickle time is standard 120s
    • Haven't noticed it before, but will check it out
    • Recently there have been more model updates as usual, since we're testing something. What do you consider as too frequent?
  2. this client -1133 incidentally updated its query now since I've posted. 

    I have another client -1317 where the log says "Data successfully sent to the inventory server" but the first time it was successful was only yesterday (2024-01-18 7:49:10.493), so it may explain why the query hasn't updated yet. 

     

    But the same client failed to update its inventory on January 16th even though it was connected to the filewave server that day. The log reads like this:

    Quote

    2024-01-16 8:59:10.014|main|FATAL|CLIENT|Failed to update inventory.
    Error -99: Connection timed out
    2024-01-16 8:59:10.014|main|FATAL|CLIENT|Retrying in 10 second(s)...
    2024-01-16 8:59:11.952|Thread (pooled)|FATAL|CLIENT|MS Update: Search failed: Unknown error code -2145123272
    2024-01-16 8:59:11.952|main|INFO|CLIENT|finished scan for InventoryScanner
    2024-01-16 8:59:21.110|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.125|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.157|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.172|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.172|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.172|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.204|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.204|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.220|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.220|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:21.415|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:23.072|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:23.072|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:31.206|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:31.238|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:41.185|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:41.185|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:48.471|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 8:59:48.514|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:00:00.457|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:00:00.479|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:00:00.498|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:00:00.500|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:00:00.510|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:00:02.124|main|FATAL|CLIENT|Failed to update inventory.
    Error -99: Connection timed out
    2024-01-16 9:00:02.124|main|FATAL|CLIENT|Retrying in 20 second(s)...
    2024-01-16 9:00:08.834|main|INFO|CLIENT|[void __thiscall KioskServer::slotUserLogin(const class QString &)] 
    2024-01-16 9:00:08.834|main|INFO|CLIENT|non threaded scan for InventoryScanner started
    2024-01-16 9:01:04.245|main|FATAL|CLIENT|Failed to update inventory.
    Error -99: Connection timed out
    2024-01-16 9:01:04.245|main|FATAL|CLIENT|Retrying in 40 second(s)...
    2024-01-16 9:02:26.380|main|FATAL|CLIENT|Failed to update inventory.
    Error -99: Connection timed out
    2024-01-16 9:02:26.380|main|FATAL|CLIENT|Retrying in 80 second(s)...
    2024-01-16 9:02:34.566|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:02:34.594|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:02:40.196|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:02:40.214|main|INFO|CLIENT|non threaded scan for NetworkScanner started
    2024-01-16 9:03:55.268|main|INFO|CLIENT|non threaded scan for NetworkScanner started
     

     

    fwquery.png

    fwclientinfo-1317.png

  3. We are having the problem that results in our inventory queries are not always updating properly. 

    For example, I have created a query that shows "FileWave Client Version" running on a specific client.  

    Let's take Client -1133 as example:

    The query shows that the installed FWClient version is 14.10.2, but when I open the Client Info it says that version 15.2.1 is installed. (different last connected times are because of the time between the screenshots) It's also now been almost a week since 15.2.1 has been installed.

     

    We have this problem in some other instances, for example when we want to find out what version of a program or app is installed on a client, and the query shows and older version even though we are sure that we have installed a newer version more than 24h ago.

     

    Is there a way to force a client to update its inventory? 

    Screenshot 2024-01-18 at 07.41.31.png

    Screenshot 2024-01-18 at 07.45.55.png

  4. Thank you Sean for the quick reply,

    a custom settings profile seems to be the easiest solution, unfortunately not all of our Macs are MDM enrolled (yet), meaning I still have to find a way to execute the command on the other Macs.

    I found this Execute macOS scripts ... | FileWave KB and inserted it on top of my script, but this also did not work.

    The Client Log tells me this:

    Quote

    2023-12-06 8:26:10.302|main|INFO|CLIENT|Fileset Container ID 8254, revision ID 8254 has version 3. It contains 1 files and 3 folders
    2023-12-06 8:26:10.303|main|INFO|CLIENT|Done processing Container Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254
    2023-12-06 8:26:10.605|main|INFO|CLIENT|about to downloadAllFileset files for Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254
    2023-12-06 8:26:10.719|main|INFO|CLIENT|Downloading Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254
    2023-12-06 8:26:10.966|main|INFO|CLIENT|finished downloadFileset files for Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254
    2023-12-06 8:26:10.970|main|INFO|CLIENT|Create all folders of fileset ID Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254, version 3
    2023-12-06 8:26:10.971|main|FATAL|CLIENT|Filesystem object at /var already exists but it is not a folder
    2023-12-06 8:26:10.977|main|INFO|CLIENT|Activate all files of Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254, version 3
    2023-12-06 8:26:11.086|main|INFO|CLIENT|Done activating all 1 files of Fileset Edge SSO, ID 8254, revision v1.0 TvL, ID 8254, version 3
    2023-12-06 8:26:11.337|main|INFO|CLIENT|Executed /var/scripts/8254/EdgeSSO.sh Return Code: 0
    2023-12-06 8:26:11.564|main|INFO|CLIENT|Installation(s) Completed.

     

  5. I'm having issues deploying superprefs filesets.

    Following all the steps provided by this KB post (Creating a Superprefs ... | FileWave KB) and deploying the fileset does not overwrite the client preferences on neither the macOS nor the Windows clients.

    I tested putting the .plist in /usr/local/etc and in both C:\ProgramData\FileWave\ for Windows and /usr/local/etc/FileWaveInstallers/ for macOS.

    After associating the fileset to my test Mac and Windows clients under Fileset Status it reports back "active" however I can still open the preferences with the old password ( I changed it to a new one in the superprefs) and the old booster configurations are still present (basically nothing has changed).

     

     

     

  6. Recently the app `Goodnotes`changed its licensing model for institutions from a paid app (which was free for a while) to a free app on the appstore which has to have a licence to be activated. We still deploy Goodnotes through Apple Business Manager and Filewave (VPP) as usual, but from now on I have to attach a licence key to the app so that it will be recognised as the full version.

    I have done so by editing the apps fileset under ´Configuration (iOS only)´ where I created a .plist file with the license code. This all seemed to work fine (see screenshot)

    But unfortunately it does not seem to work, as the deployed app still is only the regular free version.

    I have contacted Goodnotes support (still in contact with them) who told me that it seems right to them, they don't know the inner workings of filewave and would have me ask here as well.

     

    Is there anything I did wrong? Or is this an issue on Goodnotes site (perhaps a wrong license etc.)

     

    Screenshot 2023-08-02 at 15.18.05.png

  7. Let's say I have a Smart Group an app is associated to. Any new device (that automatically gets put into the Smart Group) will now get the app automatically. What would I have to do if I now decide that I don't want to install the app on new devices?

    1. Deleting the Smart Group would not make sense, as it contains more associations that I might want to keep.

    2. Deleting the association to the Smart Group also would not make sense, since then it will delete the app from all the devices that are currently in the Smart Group.

     

    My workaround is, to create a new deployment with just the App and adding the new devices as exclusions so that the app will not get pushed to those devices (It works, but isn't very practicable as I have to add every new device manually)

     

    Is there a smarter option to do this maybe?

×
×
  • Create New...