What happens when you try to open it? I don't know what "DP" means, so it's hard to help with this. If the software is being deployed by a Jamf Pro policy, the Jamf log on the Macs may help. Also the install log may provide information that could lead to why this is happening. Both of these logs are located in /var/log. The log for the Jamf Pro policy may provide some clues.
What happens when you try to open it? I don't know what "DP" means, so it's hard to help with this. If the software is being deployed by a Jamf Pro policy, the Jamf log on the Macs may help. Also the install log may provide information that could lead to why this is happening. Both of these logs are located in /var/log. The log for the Jamf Pro policy may provide some clues.
DP means distribution point here.
When I am opening it nothing opens, I mean no response, mac restarted and no software update is pending.
DP means distribution point here.
When I am opening it nothing opens, I mean no response, mac restarted and no software update is pending.
Ah thanks! DP = distribution point. Duh! I see that LogMeIn downloads as a disk image. Are you using a script or command to copy the app from the disk image to /Applications or did you create a package installer for the app? I wanted to understand first how you setup the install policy since manually installing the software works.
Ah thanks! DP = distribution point. Duh! I see that LogMeIn downloads as a disk image. Are you using a script or command to copy the app from the disk image to /Applications or did you create a package installer for the app? I wanted to understand first how you setup the install policy since manually installing the software works.
App owner gave me .pkg , I did not modify anything it. I distribute using by installer command. No .DMG, .pkg is having .app file
App owner gave me .pkg , I did not modify anything it. I distribute using by installer command. No .DMG, .pkg is having .app file
The problem may be how the package was built. There may be some missing components or it's just a bad package. Have you checked the policy details from each computer that has ran the install policy? The details may provide some clues as to why this is happening.