Reputation: 1
I'm looking for a way to force a client computer to verify with our MDM filewave server preferably inside a script. Right now the only non gui way I have to force a verify on the client end, is by killing the fwcld service. This works well when ran directly on the client machine, but does not work when ran as a fileset from the filewave server.
The reason I need this, is because Kernel extension policies hang at "Handled via MDM" and will not activate until the next verification. This is way too slow when software is dependent on the kernel extension to install.
If anyone has a solution, either a script, or some other way to make the policy install quicker. I'd really appreciate. I've been banging my head against the wall for too long, the wall is looking pretty rough.
Upvotes: 0
Views: 723
Reputation: 93
According to FileWave's documentation MDM-managed clients auto-verify with the FileWave server, based on the "tickle interval".
“waits for a specified amount of time (Tickle Interval … ) before it tries to connect again.”
By default this value is set to 120sec. The tickle interval can be changed by using the "SuperPrefs Editor". When using the SuperPrefs Editor only modify the values that you want to change.
Use these instructions to help you upload and apply the new FWpreferences to the (necessary) FileWave clients. Link to Knowledgebase
**FileWave has moved the Knowledgebase. All links above have been updated. 9/21/22 **
Upvotes: 0