Skip to main content
Solved

Beacons...

  • April 5, 2015
  • 4 replies
  • 37 views
A
Forum|alt.badge.img+6

I tried beacons with the example of JAMF's video (deploy Web Clip).
I tried limitation/exclusion option, nothing works :
- limitation : no Web Clip appears
- exclusion : no Web Clip disappear

Other question : why is it not possible to use Beacons to scope App deployment ?

Best answer by Antoine_Moussy


It works now. I just forgot to tick "Monitor iBeacons regions" in Mobile Device Management / Inventory Collection.
Thanks to Thomas from Jamf France.

    4 replies

    J
    Forum|alt.badge.img+9
    • Jalves
    • Contributor
    • April 6, 2015

    Which version of the JSS are you running? I just got some estimote beacons and was excited to set them up on my 9.65 JSS only to find out that basically everything is non functional. I emailed my account rep and he confirmed. I listed the defect number below. I am about to start testing on a 9.7 JSS. I'll post again if anything has changed.

    D-008318
    Currently, limiting a policy based on iBeacon region is not functional.

    A
    Forum|alt.badge.img+6
    • Antoine_Moussy
    • Author
    • Contributor
    • April 7, 2015

    My JSS version is 9.7. I have got Estimote beacons too. And it doesn't work!

    A
    Forum|alt.badge.img+6
    • Antoine_Moussy
    • Author
    • Contributor
    • Answer
    • April 10, 2015


    It works now. I just forgot to tick "Monitor iBeacons regions" in Mobile Device Management / Inventory Collection.
    Thanks to Thomas from Jamf France.

    M
    Forum|alt.badge.img+22
    • mike_paul
    • Employee
    • April 14, 2015

    As mentioned above, beacons have to be defined within the JSS and the Inventory Collection option listed above should be checked for both OSX and iOS.

    Then on the next check-in for computers the list of beacons to watch for is downloaded to a local plist, /Library/Application Support/JAMF/Config/iBeacons/monitoredBeacons.plist, and the /Library/LaunchDaemons/com.jamfsoftware.jamf.daemon.plist is modified to watch for entering or leaving beacon ranges and then tells the JSS that the event happened. If you plan to use it as a trigger for a policy you have to define a custom trigger, 'beaconStateChange'. For profiles it should kick off via APN when the daemon tells the JSS.

    On iOS the Self Service app has to be opened after the Beacons are defined so the list is downloaded to the device.

    And the above mentioned defect relates to being displayed within Self Service. Leaving a beacon range may take longer than you expect for it to tell the JSS you left but that should work.

    Terms & ConditionsCookie settingsAccessibility statement