Alright Jamf Nation, I have a quick question hopefully people can elaborate more on.
Im noticing that some applications, when downloaded via self service, are ending up in the Root Directory instead of the Application Folder.
Is there a reason this can be happening ?
When creating these policies, I'm leaving the target drive to "/" but i've also heard that "/applications" can be the cause.
Let me actually rephrase the question above.
When creating a .pkg, using composer, if lets say have Dropbox located in my /applications folder and using snapshot to create the .pkg.
Since it was in my /Applications folder, is that why it will install in the same folder via self service when deployed?
If deploying via DMG (not PKG, pathing in PKG will be explicit) you can use your home folder as the source in Composer and it will place the items in the user's home folder's regardless of name if you enable FEU. It will also place them where appropriate in the user template if you enable FUT.
@hkabik you mentioned If one were to be downloading a .DMG package and dragging it straight to the JAMF admin repository, this would be the cause for the application be downloaded into the root folder?
How would i accomplish placing the .app into the User's Application folder when creating a .DMG via composer?
Place the app into your own ~/Applications folder. Then drag it into Composer. Use "Apply Owner and Group to Users and All Enclosed Items" on the /Users folder within Composer. That will ensure everything gets Owner: root and Group: admin recursively from that root folder down (needed for Jamf to assign ownership properly).
Then Build As DMG.
When you upload the .dmg to Jamf Admin, make sure you check Fill User Templates and Fill Existing User Directories.
You will want to make sure those are checked in Jamf Pro when you are creating your policy as well.
That will place the application in any user's ~/Applications that is currently on the machine as well as the user template's ~/Applications so it will be added for all future users.