- Jamf Nation Community
- Products
- Jamf Pro
- Restricted Software: Dropbox not Detecting
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 07-26-2012 10:05 AM
I've had Dropbox as an entry in the restricted software tab for a while now. I know it used to catch instances of Dropbox running and I just forgot about it. Recently something came up and I'm revisiting this, it seems that Casper is no longer catching the running Dropbox application.
I've tried listing the "Process To Look For" as both "Dropbox" and "Dropbox.app" with no luck. When I execute a "ps x", I get a matching process similar to "3409 ?? S 0:02.93 /Applications/Dropbox.app/Contents/MacOS/Dropbox -psn_0_421991".
Anyone else having similar issues? Solutions?
Edit: The problem seems to have fixed itself. I'm not sure why I was experiencing this issue, but I'm not anymore. Maybe when I updated to v8.61. Thanks everyone!
Solved! Go to Solution.
2 ACCEPTED SOLUTIONS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-08-2012 09:14 AM
I am unsure if you have solved this, but I haven't found any articles.
I just created a policy that searched for the app and killed/deleted it if it were detected, seems to be working just fine for me
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-08-2012 01:29 PM
Just built a secondary JSS to test, and still no luck. I know it used to work, so I'm wondering if it's an issue with the newer revisions of the software. What are you using in the "Process To Look For" field? I've tried "Dropbox" and "Dropbox.app".
I'm using JSS v8.6 and testing Dropbox 1.4.11
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-08-2012 09:14 AM
I am unsure if you have solved this, but I haven't found any articles.
I just created a policy that searched for the app and killed/deleted it if it were detected, seems to be working just fine for me
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-08-2012 01:29 PM
Just built a secondary JSS to test, and still no luck. I know it used to work, so I'm wondering if it's an issue with the newer revisions of the software. What are you using in the "Process To Look For" field? I've tried "Dropbox" and "Dropbox.app".
I'm using JSS v8.6 and testing Dropbox 1.4.11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-29-2012 05:57 AM
killing Dropbox works for me fine
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 01-02-2013 03:04 PM
We've note the same problem. After setting up a restriction while using v.8.6 for DropBox, Google Drive, and other cloud-based services, JSS never picked up on the restriction. When we updated to v8.62, JSS started blocking Google Drive, but nothing else. We deleted the restriction for DropBox and re-entered it, it started reporting blocks of DropBox. Each time, we had it look for "DropBox" rather than "DropBox.app" or any other permutation. Hope this helps.
